cyberstyx

Done without any errors (except the missing Disk 2) and Disk 1 is enabled. tower-diagnostics-20230915-2040.zip

Yes, please let me know what I can do to fix this. The array is in maintenance mode. I have attached the status of the Main page.

I replaced the failed drive (md2) with the new bought disk, I didn't add it as a new drive. Yes, I let it finish whatever it was doing, but I think it was doing a parity check not a rebuild. On the Dashboard GUI I see on the top right (Parity area): Last check completed on Thu 14 Sep 2023 08:00:17 PM EEST (yesterday) Duration: 25 minutes, 54 seconds. Average speed: 3.9 GB/s Finding 1465130633 errors And this is the only thing it did. It was automatic after I replaced the disk, I didn't initiate anything. Now on the Main screen I see for both Disk 1 (the failed disk) and Disk 2 (the newly replaced): Unmountable: Wrong or no file system Also those two disks are available for formatting in the Main screen / Array Operations: Unmountable disks present: Disk 1 • WDC_WD60EFAX-68SHWN0_... (sdd) Disk 2 • WDC_WD60EFAX-68JH4N1_... (sdi)

I had a mechanical disk failure (md2) on an old 4TB disk. I replaced it with a new 6TB disk. When I added it unraid started preparing it (not rebuilding it yet). After 20-30% of its process another disk (md1) got disabled. I now have 2 disks to be formatted and I can't proceed with rebuilding the new disk until I sort things out firstly with the disabled disk. I did a "Check -n" from Disk 1 properties (unraid GUI), I left it running yesterday night and return from work today afternoon only to find it "dotting" the progress window for 22 hours: Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ....found candidate secondary superblock... unable to verify superblock, continuing... ............................ etc. I don't expect anything helpful after so many hours. I am not sure how to proceed fixing md1 before rebuilding md2, and I have one parity disk. Some of the errors you can see in the appropriate logs: Sep 14 20:34:32 Tower kernel: XFS (md1): Mounting V5 Filesystem Sep 14 20:34:32 Tower kernel: XFS (md1): Internal error !uuid_equal(&mp->m_sb.sb_uuid, &head->h_fs_uuid) at line 253 of file fs/xfs/xfs_log_recover.c. Caller xlog_header_check_mount+0x60/0xb4 [xfs] Sep 14 20:34:32 Tower kernel: XFS (md1): Corruption detected. Unmount and run xfs_repair Sep 14 20:34:32 Tower kernel: XFS (md1): log has mismatched uuid - can't recover Sep 14 20:34:32 Tower kernel: XFS (md1): failed to find log head Sep 14 20:34:32 Tower kernel: XFS (md1): log mount/recovery failed: error -117 Sep 14 20:34:32 Tower kernel: XFS (md1): log mount failed Sep 14 20:34:32 Tower root: mount: /mnt/disk1: mount(2) system call failed: Structure needs cleaning. Sep 14 20:34:32 Tower root: dmesg(1) may have more information after failed mount system call. I would rather ask experts about this as I 'm not a Linux OS user and I 'd rather not make a bigger mess. Any help will be greatly appreciated. Thank you in advance, Christos. tower-diagnostics-20230915-1850.zip

The fact that the drive had 6 and is slow on the post-read may mean it's starting to fail. Zeroing it *may* have fixed those 6, but if the drive is going bad, there may be more now. You can let it complete or stop it, but I would do at least one more Preclear on it, preferably 2 more. You want perfect Preclears, running at normal speed, before you can trust it. From the web GUI I checked Tools > Preclear > Log option, and the pop-up window gets regularly spammed with these Nov 8 18:45:54 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x0 Nov 8 18:45:54 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:45:54 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:45:54 Tower kernel: ata17.00: cmd 60/08:c0:70:00:44/00:00:7c:00:00/40 tag 24 ncq 4096 in Nov 8 18:45:54 Tower kernel: res 41/40:00:70:00:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:45:54 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:45:54 Tower kernel: ata17.00: error: { UNC } Nov 8 18:45:54 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 Sense Key : 0x3 [current] [descriptor] Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 ASC=0x11 ASCQ=0x4 Nov 8 18:45:54 Tower kernel: sd 17:0:0:0: [sdg] tag#24 CDB: opcode=0x28 28 00 7c 44 00 70 00 00 08 00 Nov 8 18:45:54 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084831344 Nov 8 18:45:54 Tower kernel: Buffer I/O error on dev sdg, logical block 260603918, async page read Nov 8 18:45:54 Tower kernel: ata17: EH complete Nov 8 18:45:57 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0 Nov 8 18:45:57 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:45:57 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:45:57 Tower kernel: ata17.00: cmd 60/08:18:70:00:44/00:00:7c:00:00/40 tag 3 ncq 4096 in Nov 8 18:45:57 Tower kernel: res 41/40:00:70:00:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:45:57 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:45:57 Tower kernel: ata17.00: error: { UNC } Nov 8 18:45:57 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 Sense Key : 0x3 [current] [descriptor] Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 ASC=0x11 ASCQ=0x4 Nov 8 18:45:57 Tower kernel: sd 17:0:0:0: [sdg] tag#3 CDB: opcode=0x28 28 00 7c 44 00 70 00 00 08 00 Nov 8 18:45:57 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084831344 Nov 8 18:45:57 Tower kernel: Buffer I/O error on dev sdg, logical block 260603918, async page read Nov 8 18:45:57 Tower kernel: ata17: EH complete Nov 8 18:46:00 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 Nov 8 18:46:00 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:00 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:00 Tower kernel: ata17.00: cmd 60/08:88:20:04:44/00:00:7c:00:00/40 tag 17 ncq 4096 in Nov 8 18:46:00 Tower kernel: res 41/40:00:20:04:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:00 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:00 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:00 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 ASC=0x11 ASCQ=0x4 Nov 8 18:46:00 Tower kernel: sd 17:0:0:0: [sdg] tag#17 CDB: opcode=0x28 28 00 7c 44 04 20 00 00 08 00 Nov 8 18:46:00 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084832288 Nov 8 18:46:00 Tower kernel: Buffer I/O error on dev sdg, logical block 260604036, async page read Nov 8 18:46:00 Tower kernel: ata17: EH complete Nov 8 18:46:03 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 Nov 8 18:46:03 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:03 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:03 Tower kernel: ata17.00: cmd 60/08:88:a8:08:44/00:00:7c:00:00/40 tag 17 ncq 4096 in Nov 8 18:46:03 Tower kernel: res 41/40:00:a8:08:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:03 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:03 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:03 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 ASC=0x11 ASCQ=0x4 Nov 8 18:46:03 Tower kernel: sd 17:0:0:0: [sdg] tag#17 CDB: opcode=0x28 28 00 7c 44 08 a8 00 00 08 00 Nov 8 18:46:03 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084833448 Nov 8 18:46:03 Tower kernel: Buffer I/O error on dev sdg, logical block 260604181, async page read Nov 8 18:46:03 Tower kernel: ata17: EH complete Nov 8 18:46:05 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0 Nov 8 18:46:05 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:05 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:05 Tower kernel: ata17.00: cmd 60/08:b0:a8:08:44/00:00:7c:00:00/40 tag 22 ncq 4096 in Nov 8 18:46:05 Tower kernel: res 41/40:00:a8:08:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:05 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:05 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:05 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 ASC=0x11 ASCQ=0x4 Nov 8 18:46:05 Tower kernel: sd 17:0:0:0: [sdg] tag#22 CDB: opcode=0x28 28 00 7c 44 08 a8 00 00 08 00 Nov 8 18:46:05 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084833448 Nov 8 18:46:05 Tower kernel: Buffer I/O error on dev sdg, logical block 260604181, async page read Nov 8 18:46:05 Tower kernel: ata17: EH complete Nov 8 18:46:09 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0 Nov 8 18:46:09 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:09 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:09 Tower kernel: ata17.00: cmd 60/08:c8:88:29:44/00:00:7c:00:00/40 tag 25 ncq 4096 in Nov 8 18:46:09 Tower kernel: res 41/40:00:88:29:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:09 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:09 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:09 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 ASC=0x11 ASCQ=0x4 Nov 8 18:46:09 Tower kernel: sd 17:0:0:0: [sdg] tag#25 CDB: opcode=0x28 28 00 7c 44 29 88 00 00 08 00 Nov 8 18:46:09 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084841864 Nov 8 18:46:09 Tower kernel: Buffer I/O error on dev sdg, logical block 260605233, async page read Nov 8 18:46:09 Tower kernel: ata17: EH complete Nov 8 18:46:11 Tower kernel: ata17.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0 Nov 8 18:46:11 Tower kernel: ata17.00: irq_stat 0x40000008 Nov 8 18:46:11 Tower kernel: ata17.00: failed command: READ FPDMA QUEUED Nov 8 18:46:11 Tower kernel: ata17.00: cmd 60/08:30:88:29:44/00:00:7c:00:00/40 tag 6 ncq 4096 in Nov 8 18:46:11 Tower kernel: res 41/40:00:88:29:44/00:00:7c:00:00/40 Emask 0x409 (media error) <F> Nov 8 18:46:11 Tower kernel: ata17.00: status: { DRDY ERR } Nov 8 18:46:11 Tower kernel: ata17.00: error: { UNC } Nov 8 18:46:12 Tower kernel: ata17.00: configured for UDMA/133 Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 Sense Key : 0x3 [current] [descriptor] Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 ASC=0x11 ASCQ=0x4 Nov 8 18:46:12 Tower kernel: sd 17:0:0:0: [sdg] tag#6 CDB: opcode=0x28 28 00 7c 44 29 88 00 00 08 00 Nov 8 18:46:12 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2084841864 Nov 8 18:46:12 Tower kernel: Buffer I/O error on dev sdg, logical block 260605233, async page read Nov 8 18:46:12 Tower kernel: ata17: EH complete which don't look promising...

Hey all, I have added an older 2TB disk for PreClearing (2016.09.26b), and although it started at nice speeds now at step 5 it's really crawling - 61 hours at current step ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdg # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [9:58:19 @ 55 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [7:34:05 @ 73 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read in progress: (53% Done) # # # # # # # # # # # # ** Time elapsed: 61:24:10 | Current speed: 30.2 MB/s | Average speed: 4 MB/s # # # ############################################################################################################################ # Cycle elapsed time: 79:00:36 | Total elapsed time: 79:00:37 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 41989 - # # 194-Temperature_Celsius 30 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 6 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ And I have a new WD RED 6TB waiting to joing the Array. Is this normal? Can I / should I stop the process and if so will unRaid (6.2) allow me to add it in the array? There was a "197-Current_Pending_Sector 6" which Googled to "zeroing the disk fixes it", and SMART overall status is passed. Thank you, Christos.

Don't remember seeing that error before, you can try the new beta plugin: http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938 I tried the PreClear Beta plugin, but as I could not follow the procedure mentioned (http://lime-technology.com/forum/index.php?topic=39985.msg453938#msg453938 - I could not format the drives in 6.1.7 as first they need to be added in the Array) I run the plugin to try to PreClear the disks. I got some fails again so I stopped bothering. I was "sitting" on it for quite some time and a a few minutes ago I thought I give it another go. I stopped the Array and then I noticed that the two HDDs in question were now available to join the Array (unRaid - Adding Disks 1.JPG). After adding them I also got the option to format them (unRaid - Adding Disks 2.JPG). Format completed successfully and the two "new" disks are now added in the array (unRaid - Adding Disks 3.JPG) So... what happened? PreClear erased the disks, but failed in testing them, but as the disks are now erased they can be added and formatted in the Array? Will the disks work as should or will the errors shown by PreClear eventually start to appear when saving data to disks? For the time being all shares are ignoring the two new disks until I am sure they can be used. Do you think they are ok or should I now use the steps mentioned in the PreClear Beta post: 1) Pick a formatted disk or format it with Unassigned Devices and copy some files to it; 2) Go to Settings/PreclearBeta and start a Clear operation; 3) Once it's over, please run a Verify All the Disk operation; 4) If successful, please run both Test and Run the post-read verify operations from the older plugin; 5) If possible, assign the precleared disk to the array and start a Check Parity operation. Should I run all of the above steps? I 'm kind of confused with the 5th step. As I have somehow managed to add both disks to the Array, should I just do a Check Parity?

Beh... == WDCWD2003FYYS-02W0B1 WD-WMAY04480522 == Disk /dev/sde has NOT been precleared successfully == skip=1131600 count=200 bs=1000448 returned 00049 instead of 00000 skip=1131800 count=200 bs=1000448 returned 00003 instead of 00000 skip= 1363800 count=200 bs=1000448 returned 00101 instead of 00000 skip=1829600 count=200 bs=1000448 returned 16489 instead of 00000 So, like, this disk will never be added in the array and I can use it only in Windows?

Started a Preclear for 3 HDDs simultaneously, on a WD 2TB RE4 + a WD 2TB Caviar Green on a DIGITUS 30104-1 and on another WD 2TB RE4 on a secondary same controller. All disks were bought a few years ago and have had some operation on a VMWare ESXi host at home, which are now been migrated to unRAID. One WD 2TB RE passed preclear, the one that was the only HDD connected on a controller. The other two failed as following: - WD 2TB RE4 (SMART says it has 4 months of operation) == Disk /dev/sde has NOT been precleared successfully == skip=461200 count=200 bs=1000448 returned 16433 instead of 00000 - WD 2TB Caviar Green (SMART says it has 5 years of operation - oh oh...) == Disk /dev/sdf has NOT been precleared successfully == skip=1478200 count=200 bs=1000448 returned 00065 instead of 00000 skip=1603800 count=200 bs=1000448 returned 00005 instead of 00000 skip=1604400 count=200 bs=1000448 returned 00065 instead of 00000 I then found out about this post and some preclear general thoughts, so I am now running again a single Preclear on the WD 2TB RE4 that failed, as preclearing many drives simultaneously may give strange results when reading data back from disks during testing. I 'm doing single passes btw. Will report back tomorrow when preclearing has finished. (Damn that Caviar Green one is sooooo slow with 5400rpms ) Preclear_Finish_WDCWD2003FYYS-02W0B1_WD-WMAY04480522_2016-03-24.txt Preclear_Finish_WDCWD20EADS-00S2B0_WD-WCAVY0562655_2016-03-24.txt