Lean_

Also, thank you for joining in JorgeB, the support from you and trurl has been invaluable!

I do not have any backups of my array, only flash and appdata, and prefer to stay on the stable version of unraid. I don't mind losing some of the data on disk19 as I can get it back pretty easily. Is there a way to keep whatever is being emulated and get back to a healthy parity/array state even if I lose some of what's on that bad disk19?

Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... entry "A Shot Through the Wall (2022) {imdb-tt8588414} [WEBDL-1080p][AC3 5.1][h264]-EVO.mkv" in directory inode 135 not consistent with .. value (15032385667) in inode 34359738564, junking entry entry "A Shot ThroumiHT2BPO3022) {idb-tt8588414} [WEBDL-1080p][AC3 5.1][h264]-EVO.nfo" in directory inode 135 not consistent with .. value (10737418369) in inode 136, junking entry fixing i8count in inode 135 bad hash table for directory inode 33693602 (no data entry): rebuilding rebuilding directory inode 33693602 entry "Season 12" in dir ino 2147483794 doesn't have a .. entry, will set it in ino 4294967438. bad hash table for directory inode 2147483835 (no data entry): rebuilding rebuilding directory inode 2147483835 bad hash table for directory inode 2165900194 (no data entry): rebuilding rebuilding directory inode 2165900194 entry ".." in directory inode 2351323147 points to free inode 176, junking entry bad hash table for directory inode 2351323147 (no data entry): rebuilding rebuilding directory inode 2351323147 corrupt block 1 in directory inode 4294967424: junking block entry "Memories of Murder (2003)" in dir ino 4294967424 doesn't have a .. entry, will set it in ino 4294967454. corrupt block 3 in directory inode 4294967424: junking block entry "Triangle of Sadness (2022)" in dir ino 4294967424 doesn't have a .. entry, will set it in ino 4294967436. rebuilding directory inode 4294967424 Metadata corruption detected at 0x47b3d2, inode 0x10000008f dinode fatal error -- couldn't map inode 4294967439, err = 117 This is the end of the output

Thank you for all of your help by the way, I am very appreciative of your time.

Unfortunately the file is empty and this is what was returned in console.

I did not, just CHECK, and "No file system corruption detected."

I feel like I should also mention I have spare disks just in case that makes any of this easier.

That started automatically with the array, but I cancelled it like you suggested yesterday.

superplex-diagnostics-20250409-1311.zip

Cable has been swapped, drive 19 is still unmountable Parity 2 also still needs to be resynced, how should I proceed?

I've since swapped to a spare PSU so hopefully that doesn't happen again. So what you're saying is, there's a chance that when I plug in the new cables, everything 'just works' ?

Okay thank you! I've just cancelled it, would you mind outlining for me what the potential next-steps would look like?

Does it change anything if those errors occurred after I passed the 4TB mark?

Oh? Stop the parity sync/rebuild?

You are correct, they are all on the same controller. I just uninstalled mover tuning plugin. Generally want files to live on the cache for as long as possible to minimize the spinup of other disks. Saves me about $700 a year iirc. Additionally, I did have a weird uptime reset last week with no actual power outage. Also, for more context, I'm using a LSI 9300-8i controller and a supermicro chassis with a sas3 backplane and SQ PSU's. Thank you for the response, I will update with a new post as soon as the rebuild is complete.

Not sure what is going on with my system, but I had a scheduled bi-quarterly parity check that kicked off a few days ago that disabled 2nd parity disk and my disk 19. in an effort to resolve this I shutdown re-seated every cable and my HBA and most of my disks came back to normal and were no longer disable but the one disk 19. Parity sync / rebuild kicked off and currently while I type is at 84% complete with ~5hrs left to go. I'm really hoping this disk comes back to life with the almost 9tb of data that it has but if not, I'm okay with losing some data as none of it is precious to me and I believe I can get most of it back. I just want to have my server back into a healthy state, any help or direction is welcome. Additionally I have a new set of Mini SAS HD SFF-8643 to SFF-8087 cables showing up tomorrow to replace my current ones as a precautionary measure. Below is my current state superplex-diagnostics-20250408-1200.zip