GozuTashoya

Rebuild went off without a hitch. Thanks!

Yes, it was.

So, I had to move the server around a bit because of some house stuff, leaving it powered down for a few days. After getting it set back up and powering it on, I went into the Main screen to see if everything was good. Unfortunately, one of my disks was disabled, and so here I am. Diagnostics are attached. Thanks in advance for any help and advice. tower-diagnostics-20240624-2033.zip

Just to clarify my earlier comment, Old Disk 4 (Physical, as UD) is the one that reports no file system corruption. Disk 4 (emulated, in the array) still fails filesystem check. With that in mind, is Option 2 still an option, or would rebuilding result in the same broken/unusable filesystem? Anyway, that said, Old Disk 4 (physical) does mount fine and the contents indeed look OK. Assuming I want to go with Option 1, do the steps look like this? Stop array. Tools -> New Config. Choose "All" for Preserve Current Assignments. Click "Yes i want to do this" checkbox. Click "Apply". Main Tab -> Change Disk 4 (currently unassigned) to Old Disk 4 Drive (physical). Start array. Let Unraid create new parity sync. (Array should be usable, if slowish?) And will those steps preserve the data on Old Disk 4 (physical), almost as though the whole filesystem corruption didn't happen? I.e., Old Disk 4 won't need be formatted/precleared?

Disk 4 now reports "No file system corruption detected!" (Results attached in case it helps.) Next step is to re-add Disk 4 to the array? Disk 4 filesystem check - UD 2024-01-13.txt

Is it safe to start the array and use Unraid as usual while Disk 4 is removed from the array and just hanging out as an unassigned device?

Disk 4 mounted successfully as UD. Ran filesystem check (attached). Safe to go ahead and hit "run with correct flag"? Ran Disk 5 filesystem check with -n, and it fixed stuff. Running it again had more items, so I re-ran it with -n. Logs attached. Disk 4 filesystem check.txt Disk 5 filesystem check (3rd run with -n flag removed).txt

To check Disk 4 with UD, I need to stop the array and remove the drive from the array (set Disk 4 to "no disk")? Also, attached is the output of the disk 5 filesystem check. Disk 5 filesystem check.txt

So, I swapped out one of the older/smaller disks in my array -- disk #5 of 6 -- for a larger one, and after starting the machine up, and found that one of the other disks (disk 4) was also offline. Because two disks were missing (#4 & #5), Unraid wouldn't let me rebuild disk 5. I shut the server down to check the cables and after powering back on found that disk 4 was now reporting "Unmountable: Unsupported or no file system" (which I believe was different from the initial error). It was, however, now giving me the option to rebuild disk 5 which, for better or worse, I did. Rebooted again, disk 4 was still offline, running emulated. Restarted the array in maintenance mode and ran the filesystem check from the GUI. It ran for ~3 hours, starting with "Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!!" and ending with "Sorry, could not find valid secondary superblock Exiting now." Diagnostics are attached from after the filesystem check failed (though I also have diagnostics from earlier). Any advice on what to do next would be greatly appreciated. Thanks. tower-diagnostics-20240111-2106 - post-fix attempt.zip