September 23, 2025Sep 23 Author Ok thanks. I was just hoping there's some sort of a block on the parity disk with the identifiers of data disks it was built from or something like that, to take the guesswork out of this.
September 23, 2025Sep 23 Community Expert 45 minutes ago, jon00001 said:I was just hoping there's some sort of a block on the parity disk with the identifiers of data disks it was built from or something like thatI'm afraid there's not; you would need to know the last array config where the parity was synched or checked.
September 23, 2025Sep 23 Author Ah that's a shame - would be nice to have that written to the parity disk as it's only valid when paired with those now-unknown disks :-)Do you think there's only one parity check here? I'm not clear about the "disk-check" items - they're in the "Parity Operation History" so maybe they're a flavour of parity check too? If not it looks like I only actually managed to build it once, so that would have been with all three of the original three data disks and I'll need at least two in place to rebuild from.
September 23, 2025Sep 23 Community Expert Yep, that suggests there was only one sync and no checks. Read checks means no parity or a disabled disk, also, there were errors during the parity sync.
September 23, 2025Sep 23 Author I think the errors were coming from the SMART errors on the two old disks, but unraid did eventually say it'd successfully built parity.
September 23, 2025Sep 23 Author Current situation is 1TB drive exhibiting "click of death" so that's probably gone now. 0.5TB disk might be recoverable to some extent but it's not looking great for my data resilience :-/If I had my time again I'd buy the additional 4TB disk before juggling everything into the new array and write to that instead of the ancient decaying disks I had. Oh well!
October 3, 2025Oct 3 Author Just a quick update: after your comments on what the parity disk was most likely built against I added the semi-failing 0.5TB back to the array, with the completely failed 1TB disk still emulated. Started with "parity is valid" and voila, most (possibly all) of the data I was expecting was restored.The only downside is that there were so many errors along the way that the repair process lost a lot of directory paths so all of the recovered data ended up in lost+found and there's going to be a lot of work to put things back in the right places.Still, very nice not to have completely lost stuff like old photos etc. Yes those should be backed up not just on a single resilient array. That's next!Thanks for your help - little bit of beer money sent. Edited October 3, 2025Oct 3 by jon00001
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.