April 25, 201610 yr i followed these directions: Replace drive: - Stop the array - Unassign the old drive, if it's still assigned - Power down - [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing) - Install the new drive - Power on - Assign the new drive in the slot of the old drive - Go to the Main -> Array Operation section - Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button - The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives Drive rebuilt with no issues but it now shows as unmountable. see screenshot. any ideas?
April 25, 201610 yr Did you change the default filesystem on that drive? Click it and see what file system it's using. My guess is the system (or you) set the drive to XFS, when the drive you were replacing was resierfs. You must keep the same filesystem for data rebuilds.
April 25, 201610 yr Author yea i saw that. but why would raid rebuild the disk then want you to format it afterwards and wipe it out then have to rebuild it again?
April 25, 201610 yr yea i saw that. but why would raid rebuild the disk then want you to format it afterwards and wipe it out then have to rebuild it again? Sorry I miss-read your post and edited the above.
April 25, 201610 yr That's really strange. Definitely would not hit the format button, might be a corrupt filesystem or something. Hopefully someone who has seen this before has a solution. One thing that strikes me is I see no "Parity is valid" or even a date of your last ran parity check. Were you doing monthly parity checks? Are you position your parity was valid? You have errors showing on both the parity drive and the failed disk in that second screenshot.
April 25, 201610 yr Author i was in the middle of doing a parity check when drive3 went offline and became unmountable.
April 25, 201610 yr Community Expert You should post diagnostics, ideally from before the reboot, but at first sight it looks like a corrupt rebuild due to parity disk issues or from the parity being incorrectly updated if you were running a correcting parity check when the disk failed. Is the old disk still readable?
April 25, 201610 yr Community Expert You should post diagnostics, ideally from before the reboot, but at first sight it looks like a corrupt rebuild due to parity disk issues or from the parity being incorrectly updated if you were running a correcting parity check when the disk failed. Is the old disk still readable? Or perhaps the original disk was already corrupt. coldhammer, what made you decide to replace the drive?
April 25, 201610 yr Author everything was running fine. i ran my monthly parity check and about half way through the check it was stopped and disk 3 was flagged as unmountable.
April 25, 201610 yr Community Expert everything was running fine. i ran my monthly parity check and about half way through the check it was stopped and disk 3 was flagged as unmountable. So the original disk was unmountable then? Rebuilding an unmountable disk will just result in an unmountable disk. You need to try to repair the filesystem. See wiki for Check Disk Filesystems.
April 25, 201610 yr You should post diagnostics, ideally from before the reboot, but at first sight it looks like a corrupt rebuild due to parity disk issues or from the parity being incorrectly updated if you were running a correcting parity check when the disk failed. Is the old disk still readable? I never thought of this, but wouldn't a failed disk during a correcting parity check result in a non-valid parity 100% of the time?
April 25, 201610 yr Community Expert You should post diagnostics, ideally from before the reboot, but at first sight it looks like a corrupt rebuild due to parity disk issues or from the parity being incorrectly updated if you were running a correcting parity check when the disk failed. Is the old disk still readable? I never thought of this, but wouldn't a failed disk during a correcting parity check result in a nonvalid parity 100% of the time? Not always, and in fact it shouldn't happen, but it does, that's why I recommend always doing non-correcting parity checks.
April 25, 201610 yr Community Expert everything was running fine. i ran my monthly parity check and about half way through the check it was stopped and disk 3 was flagged as unmountable. Disk is mounted on the screenshot after it was disabled.
April 25, 201610 yr You should post diagnostics, ideally from before the reboot, but at first sight it looks like a corrupt rebuild due to parity disk issues or from the parity being incorrectly updated if you were running a correcting parity check when the disk failed. Is the old disk still readable? I never thought of this, but wouldn't a failed disk during a correcting parity check result in a nonvalid parity 100% of the time? Not always, and in fact it shouldn't happen, but it does, that's why I recommend always doing non-correcting parity checks. I'll try not to hijack the thread anymore, but that still doesn't seem like a solution. If you end up with even 1 sync error, you still have to run a correcting parity check next. If there were sync errors, chances are there's a dying drive or dying hardware, so the risk of having something go really wrong during the next check seems high. Your method still makes more sense to me, the risk is lower but not completely gone. Kind of makes me think twice about how secure my data really is.
April 25, 201610 yr Author everything was running fine. i ran my monthly parity check and about half way through the check it was stopped and disk 3 was flagged as unmountable. Disk is mounted on the screenshot after it was disabled. that was the screenshot previous to rebooting. after i rebooted the drive changed to unmountable.
April 25, 201610 yr Community Expert You should post diagnostics, ideally from before the reboot, but at first sight it looks like a corrupt rebuild due to parity disk issues or from the parity being incorrectly updated if you were running a correcting parity check when the disk failed. Is the old disk still readable? I never thought of this, but wouldn't a failed disk during a correcting parity check result in a nonvalid parity 100% of the time? Not always, and in fact it shouldn't happen, but it does, that's why I recommend always doing non-correcting parity checks. I'll try not to hijack the thread anymore, but that still doesn't seem like a solution. If you end up with even 1 sync error, you still have to run a correcting parity check next. If there were sync errors, chances are there's a dying drive or dying hardware, so the risk of having something go really wrong during the next check seems high. Your method still makes more sense to me, the risk is lower but not completely gone. Kind of makes me think twice about how secure my data really is. Naturally if there are sync errors you have to correct them, but unless there's a good reason, like a hard reset or power failure, there shouldn't be any, I don't remember the last time I had an unexpected sync error, and I use unRAID for almost 10 years, and if there are you can look for any disk issues before doing a correcting check.
April 26, 201610 yr Community Expert You have to remove the "-n" flag and run it again, or it will only check and not repair.
Archived
This topic is now archived and is closed to further replies.