rayray14 Posted January 12, 2022 Share Posted January 12, 2022 (edited) Hello, Thanks in advance for any help. I made the mistake of trying to follow instructions very late at night on how to swap out a healthy disk, for a larger one. I skipped the step where I was to supposed to set the drive too be replaced as "No Device" and then reboot. Instead, I just shut down, swapped the drive, pre-cleared it, then identified it as the new "Drive 2". Something happened along the way and I the parity drive was rebuilt, and now the contents of the old drive aren't acessible on on the new one. I get this error in the GUI: And this when trying to naviate to the share over the network: The array is looking healthy as-is: What I'd like to do, is just put my old drive back in, rebuild the parity, get back to a working array, and then follow the steps very meticulously to replace it correctly. Where I'm at now: I swaped out the new drive (WSD57175 - 8 TB) with the old one (ZDH1NBHJ - 4TB), assigned it as Drive 2, and marked the parity as "no device". I thought that would get me on the right path, but I can't start the array due too "Invalid configuration / Too many wrong and/or missing disks!". Any help guidance would be truly appreciated. Thanks! unraid-os-diagnostics-20220112-1123 - Post-change.zip unraid-os-diagnostics-20220112-1201 - Current Working (but broken) Array.zip Edited January 12, 2022 by rayray14 Quote Link to comment
JorgeB Posted January 12, 2022 Share Posted January 12, 2022 15 minutes ago, rayray14 said: I skipped the step where I was to supposed to set the drive too be replaced as "No Device" and then reboot. That can be skipped, problem is filesystem corruption, check filesystem on disk2. Quote Link to comment
rayray14 Posted January 12, 2022 Author Share Posted January 12, 2022 1 hour ago, JorgeB said: That can be skipped, problem is filesystem corruption, check filesystem on disk2. Thanks JorgeB. To be clear, do you mean the filesystem on the old 4TB or the new 8TB? Quote Link to comment
rayray14 Posted January 12, 2022 Author Share Posted January 12, 2022 Without understanding everything, this looks pretty bad. Safe to assume I should re-run it without the -n flag? Disk2 Filesystem Check.txt Quote Link to comment
trurl Posted January 12, 2022 Share Posted January 12, 2022 10 minutes ago, rayray14 said: looks pretty bad It does look bad, but since you still have the original you will get another chance to recover files from it. 11 minutes ago, rayray14 said: re-run it without the -n flag? yes Quote Link to comment
rayray14 Posted January 12, 2022 Author Share Posted January 12, 2022 Thanks Trurl, that brought everything back to a running state, but I'm missing A LOT of data: What's the best way to go back to my old drive from this point, get to a working array, and then do the swap to the new 8TB disk? Disk2 Filesystem FIX.txt Quote Link to comment
trurl Posted January 12, 2022 Share Posted January 12, 2022 See if the original disk mounts as an Unassigned Device. Quote Link to comment
rayray14 Posted January 12, 2022 Author Share Posted January 12, 2022 My SATA slots are full and I'd have to use an existing one. How should I proceed? I did confirm it does still mount and my data is intact in a prior step. Quote Link to comment
Solution trurl Posted January 12, 2022 Solution Share Posted January 12, 2022 You could New Config the original back into the array and rebuild parity. Quote Link to comment
rayray14 Posted January 13, 2022 Author Share Posted January 13, 2022 21 hours ago, trurl said: You could New Config the original back into the array and rebuild parity. Thank you, that did the trick. I've been using unRaid for 5+ years and didn't know that was an option (probably because it's been rock solid and never had to think about it ) 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.