October 15, 20187 yr In my ongoing saga, a cable got disconnected (actually, it's the metal cage on the SAS backplane that holds the SAS cable in place that's partially broken off so it no longer securely locks the cable in place) during a disk replacement data rebuild. After resecuring the cable, I ran a parity check (no write corrections) and now its coming across sync errors but the log shows very generic entries, an example of which: Oct 15 09:05:16 UnRAID kernel: md: recovery thread: P incorrect, sector=9344918184 I don't know which disks these errors are being detected on or if it's on the parity disk itself so my question: How do I rebuild the replacement drive correctly? Should I reinstall the original drive and do a parity rebuild of the parity drive, then once successfully completed, reinstall the replacement drive? Or is there another way I could just restart the data rebuild? I really need to know which drive(s) the sync errors are occuring on as I want to make sure it's only on the replacement drive itself. All other data drives should be fine and parity drive should be accurate as I rebuilt it from scratch a few days ago after my previouis SNAFU. Edited October 15, 20187 yr by Auggie
October 15, 20187 yr Community Expert 13 minutes ago, Auggie said: I don't know which disks these errors are being detected on or if it's on the parity disk itself so my question: There's no way of knowing, I assume the earlier rebuild finished but with errors, if so best bet would be to rebuild the same disk again.
October 15, 20187 yr Author 55 minutes ago, johnnie.black said: There's no way of knowing, I assume the earlier rebuild finished but with errors, if so best bet would be to rebuild the same disk again. Yea, the data rebuild finished with massive errors; I didn't know anything was wrong until I got home and the rebuild was completed. Before I left, I had been checking in on it all day and it had less than 2TB left to go in rebuilding from 4TB to 6TB and there were zero errors at the time. I'm just going to reinstall the original 4TB and rebuild the parity disk itself. Can't wait to migrate this server to the new Chenbro case with new SM X11 board. This current RPC4224 case with that broken SAS backplane has always given me fits since day one.
October 15, 20187 yr Community Expert 3 minutes ago, Auggie said: I'm just going to reinstall the original 4TB and rebuild the parity disk itself. If that's an option it's the best one.
October 16, 20187 yr Author 9 hours ago, johnnie.black said: If that's an option it's the best one. I bit the bullet and did the long route. I just didn't want to spend another 48 hours or more building parity then rebuilding drive, but it's the safest bet.
Archived
This topic is now archived and is closed to further replies.