October 19, 20214 yr Woke up this morning to a disabled disk - going off the syslog, appears to be my LSI controller flaked out while mover was running and the disk was disabled. Disk itself seems to be fine, SMART passes and no re-allocated sectors. Diagnostics attached. Seems like I should be good to follow these instructions - just want to be sure before proceeding. Thanks! saturn-diagnostics-20211019-0948.zip Edited October 19, 20214 yr by emb531 Attach diagnostics
October 19, 20214 yr Looks more like a power/connection problem, I would recommended replacing/swapping cables/slot to rule those out if it happens again to the same disk, then and if the emulated disk is mounting and contents look correct you can rebuild on top using the instructions above.
October 19, 20214 yr Author 8 minutes ago, JorgeB said: Looks more like a power/connection problem, I would recommended replacing/swapping cables/slot to rule those out if it happens again to the same disk, then and if the emulated disk is mounting and contents look correct you can rebuild on top using the instructions above. Is there anyway to just bring the disk back online without having to rebuild from parity?
October 19, 20214 yr 26 minutes ago, emb531 said: Is there anyway to just bring the disk back online without having to rebuild from parity? You either have to rebuild the parity disk and lose the data that was written to the data slot while it was disabled, or rebuild the data disk from parity. Your choice, but if the emulated disk is mounting and reading properly it's better to rebuild the data disk to match.
October 19, 20214 yr Author 1 minute ago, JonathanM said: You either have to rebuild the parity disk and lose the data that was written to the data slot while it was disabled, or rebuild the data disk from parity. Your choice, but if the emulated disk is mounting and reading properly it's better to rebuild the data disk to match. Thanks - the reconstruction is in progress now, 14 hours to go for 10TB
October 19, 20214 yr The reason why is that the only time a disk is red-balled is because a write failed to it. To make the drive reflect that failed write, you rebuild the disk (Because parity is correct). If you accept the whatever write failed is meaningless, then you rebuild parity to reflect the drive's contents (which include the previous contents of whatever sector failed to write). Corruption (whether noticeable or not) will occur on the file(s) if you use the latter option.
October 21, 20214 yr Author My rebuild was successful, I have disabled turbo-write for the time being as well just to be a little proactive. Thanks for the help.
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.