lovol2 Posted March 2 Share Posted March 2 (edited) Hi All, I hope you can help in some way. I migrated over data from Windows etc. to Unraid Then added parity disk after during the parity create process - disk1 failed with an x. It was working fine before this, yes I'm sure there were some files that were unradable as the disk is old 4TB. Ok, in Windows you do a chkdisk and mark the sectors bad and then all continues fine. It would seem I can't do that in Unraid? I run the check and get Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error the parity creation got 98% complete, close! SMART test short and complete were both ok prior to parity build overnight Thanks for any help. the disk is xfs format 4TB. Edited March 2 by lovol2 Quote Link to comment
lovol2 Posted March 2 Author Share Posted March 2 unraid-diagnostics-20240302-1157.zip Hi, thanks for the reply. they are attached. Having engaged chatGPT, not looking good. I also got the following output root@unraid:~# sudo badblocks -v /dev/sdd Checking blocks 0 to 3907018583 Checking for bad blocks (read-only test): 73724752 73724753 73724754 73724755 73726692 73726693 73726694 73726695 73728624 73728625 73728626 73728627 73728628 73728629 73728630 73728631 73730568 73730569 73730570 73730571 73734448 73734449 73734450 73734451 73777368 73779308 73781244 73781245 73781246 73781247 73783184 73783185 73783186 73783187 73785120 73785121 73785122 73785123 73785124 apparently, XFS has no way of marking bad sectors like NTFS. Quote Link to comment
itimpi Posted March 2 Share Posted March 2 9 minutes ago, lovol2 said: unraid-diagnostics-20240302-1157.zip 98.63 kB · 0 downloads Hi, thanks for the reply. they are attached. Having engaged chatGPT, not looking good. I also got the following output root@unraid:~# sudo badblocks -v /dev/sdd Checking blocks 0 to 3907018583 Checking for bad blocks (read-only test): 73724752 73724753 73724754 73724755 73726692 73726693 73726694 73726695 73728624 73728625 73728626 73728627 73728628 73728629 73728630 73728631 73730568 73730569 73730570 73730571 73734448 73734449 73734450 73734451 73777368 73779308 73781244 73781245 73781246 73781247 73783184 73783185 73783186 73783187 73785120 73785121 73785122 73785123 73785124 apparently, XFS has no way of marking bad sectors like NTFS. You should not need these with modern drives - they should be able to reallocate these sectors instead. Marking bad sectors is a hangover from the days of IDE drives. Quote Link to comment
JorgeB Posted March 2 Share Posted March 2 xfs_repair can fail in a disk with bad sectors, with this error: 1 hour ago, lovol2 said: fatal error -- Input/output error Since there's no parity to emulated the disk, suggest you clone the disk with ddrescue, then run xfs_repair Quote Link to comment
lovol2 Posted March 3 Author Share Posted March 3 On 3/2/2024 at 12:17 PM, JorgeB said: xfs_repair can fail in a disk with bad sectors, with this error: Since there's no parity to emulated the disk, suggest you clone the disk with ddrescue, then run xfs_repair Thanks for that. We got close to having parity, it did say it was emulating at one point, but given the disk was running perfectly fine at one point, I swapped some cables round and the partity disk dropped out. Another update. So I decided I need to run some kind of full disk check prior to adding them back to the array, don't want to go through this again. found this video about preclear, seems as good as anything *Do you have any suggestions/better ways to do a full and complete disk check (and ideally get SMART to 'know' where the bad sectors are and ignore them)?* The plot continues... So, the array said Disk 1 was in need of a format, but I... stopped the array set 'disk 1' (the problem disk we have) to 'no device' on the array start array 'unassigned.devices.plg' showes both the Parity Disk (5TB) and the problem disk (4TB) now. I clicked Mount on the 4TB problem drive can browse folders. using Krusader as setup here ( and I can access my files, which is great. the only real downside is having to setup all my dockers again since I didn't know this was avaialble until after they were half setup, but oh well. thanks for your help. Quote Link to comment
lovol2 Posted March 7 Author Share Posted March 7 @JorgeB could you perhaps assit a little more, so i've got my data off as documented above. However, I can't seem to 'fix' the array. I've done pre-clear on both my 4TB and 5TB drive, both are fine. so I just want to put them back in the array but whatever I do, It just says "Stopped. Configuration valid." Things I've tried 1. Doing just 1 drive edit at a time - adding parity back, nope - adding disk 1 back, nope 2. Going to Tooles-> new config - with and without preserving anything, no chages at all. any help with this hopefully final hurdle appreciated. unraid-diagnostics-20240307-1713.zip Quote Link to comment
lovol2 Posted March 7 Author Share Posted March 7 I should add, I can start the array, and disk 2 and 3 work fine. Quote Link to comment
JorgeB Posted March 7 Share Posted March 7 Do a new config - Tools - New Config 1 Quote Link to comment
Solution lovol2 Posted March 7 Author Solution Share Posted March 7 3 hours ago, JorgeB said: Do a new config - Tools - New Config Thank you, face plant moment, didn't press 'yes' and 'apply', just clicked 'done', hence it doing... nothing... doing to many things, thanks for your help, much appreciated. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.