EdgarWallace

Members
  • Content count

    752
  • Joined

  • Last visited

Community Reputation

1 Neutral

About EdgarWallace

  • Rank
    Advanced Member
  • Birthday 09/05/63

Converted

  • Gender
    Male
  • Location
    Germany
  1. Thanks a lot @johnnie.black. Meanwhile I have edit the initial post with the error messages that I found.
  2. I was building an unRAID server for my brother and it was running well until beginning of May. The amount of errors is even higher now and I don't know where to additionally look at. He checked the cabling and the memory test passed without issues. The diagnostic file is attached maybe someone is identifying the root cause. Here are errors: May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946560 May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946568 May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946576 May 2 13:21:44 NAS kernel: md: recovery thread: PQ corrected, sector=1119946584 It is a ASROCK E3C224D4I-14S mobo with 2 controller: Intel C224 : 4 x SATA3 6.0 Gb/s (from mini SAS connector), 2 x SATA2 3.0 Gb/s, Support RAID 0, 1, 5, 10 and IntelĀ® Rapid Storage LSI 2308: 8 x SAS2 6Gbps ( from 2x mini SAS 8087 connector Thanks a lot. nas-diagnostics-20170503-1658.zip
  3. I just discovered this really nice docker and it is running well. Only thing I discovered it an error message from "Fix Commun Problems" plugin: Docker application CrashPlan has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option My USB drive is not attached right now, can this cause the message? I don#t know what the SLAVE option is....
  4. SUCCESS A second parity check after the xfs_repair /dev/md5 was showing 14 sync errors that were corrected. The final parity check reported 0 errors. I rate my issues with the removal of the AOC-SAS2LP-MV8 and the insert of a DELL PERC H200 as fixed. Good to rely on my backup server (again). Thanks to all who were helping, mainly @johnnie.black and @Fireball3
  5. @Joseph, this was at the start of the parity check, the average was about 90MB/s, which is about the same speed I was getting with my AOC-SAS2LP-MV8. @johnnie.black thanks a lot, see the outcome below....looks pretty good right? Parity Check ended with 24 errors. I am going to run a Parity Check once again with "Write corrections to parity" option. root@Tower2:~# xfs_repair /dev/md5 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 Metadata corruption detected at xfs_inode block 0x11c002b18/0x2000 - agno = 3 bad CRC for inode 6811791504 bad magic number 0x0 on inode 6811791504 bad version number 0x0 on inode 6811791504 bad CRC for inode 6811791504, will rewrite bad magic number 0x0 on inode 6811791504, resetting magic number bad version number 0x0 on inode 6811791504, resetting version number imap claims a free inode 6811791504 is in use, correcting imap and clearing inode cleared inode 6811791504 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 2 entry "ja.js" at block 0 offset 152 in directory inode 6642449595 references free inode 6811791504 clearing inode number in entry at offset 152... Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 6642449595 (no data entry): rebuilding rebuilding directory inode 6642449595 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done
  6. I have finally received my Dell Perc H200 and thanks to the HUGHE efforts of @Fireball3 my backup server is running it's first Parity Check. I have unchecked the "Write corrections to parity" option in order to see if the server will stay at 8 errors that came up with the AOC-SAS2LP-MV8 card. If everything's running well I will check again including the "write corrections" options and running a 3rd check finally. Cross fingers..... EDIT: 9 Sync Errors detected at 38,3% Parity Sync. What is making me nervous is this: Pastebin
  7. Thanks to the HUGHE efforts of @Fireball3 my Dell Perc H200 is running it's first Parity Check at an impressive speed at 168,4 MB/sec. Thank you VERY much.
  8. Meanwhile I was looking into this https://hardforum.com/threads/flashing-it-firmware-to-dell-h200-on-x9scm.1773245/ and this: https://forums.lime-technology.com/topic/25420-m1015-x9scm-f-usb-firmware-tools/ According to these links I was booting into the EFI Shell of my X9SCL-F board and copied the Toolset_PercH310 to LSI9211_P20.00.07.00_efimod to the flash drive. Here is the outcome: sas2flash -l Adapters.txt -listall Adapter Selected is a LSI SAS: SAS2008(B2) Controller is not operational. A firmware download is required. Enter firmware file name or quit to exit: Firmware fault occurred. Fault code: D04 Due to error remaining commands will not be executed. Unable to Process Commands. Exiting SAS2Flash. The boot menu of the adapter card is gone by the way....seems that 1.bat in a previous run did it's job. I will happily test your V2 as soon as it's uploaded. Thank you VERY much for your help.
  9. Sorry for confusion I caused. I meant that I am getting the same error messages that his screen shot showed. For further clarification I attached the IPMI screen shot
  10. It is a Dell PERC H200, please see my signature: unRAID Test & Backup: 6.3.3 Pro, Supermicro X9SCL-F, XEON E3-1240V2, AOC-SAS2LP-MV8 trying to flash a Dell PERC H200 to IT Mode
  11. Thanks a lot Fireball, this explains my issues. I am still confused though. This was my first landing page: I clicked in Dell Perc H200 dedicated instructions link: This is where I got the file from and the message "Tested on a stock H310 as well as a H200" made me think that I used the right material. What should I use instead? Thanks a lot.
  12. I am having the same issue as yaldex. I was using: How were you solving your issues?
  13. I have installed a SAS2LP in my Backup Server, disabled VT-d and still having parity check errors. I ordered a Dell Perc H200 today and will report back If that card is going to resolve my issues. Btw. is it safe to run the parity check once the new controller is installed with the "Write corrections to parity" option?
  14. @speeding_ant do you have any news for us? When I remember correctly your update should have been available a couple of weeks ago. Or should we rather remove the App? Please advise. Thanks a lot. ar 27 14:04:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:04:57 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:05:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:06:17 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:06:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:07:37 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:07:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:08:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:08:57 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:09:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:10:17 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:10:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:11:37 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:11:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:12:43 Tower root: error: webGui/include/Notify.php: missing csrf_token Mar 27 14:12:57 Tower root: error: webGui/include/Notify.php: missing csrf_token hanks.
  15. Ahh, so similar to the ASUS board that I had. Can anyone who owns this board confirm? thank you very much @saarg.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.