mrichards

That would be disk 8 with 12,000+ reallocated sectors. Followed by disk 3 with only 12 reallocated sectors. Disk 6 doesn't have any reallocated sectors, but has 88 current pending sectors.

ah. ok. I misinterpreted. That's what I'm doing. I've already excluded the bad drives from user shares, and am copying the files from those drives.

Is there a high risk of losing data by moving versus rebuilding to a new drive? Was hoping to hold off on buying more new drives for a couple of months, because I have to set up a better backup system. With the 2 new drives, I'm at around 50% capacity.

Thanks so much for the help, @JorgeB and @trurl ! I have 3 other drives that are very close to dying, so will work on moving the files off of those before this happens, again.

Rebuild is complete. Everything looks ok. I'll have to go through all of the lost+found files. Attached another diagnostics, just in case mrplex-diagnostics-20260701-1110.zip

Done. Estimated rebuild finish in 15 hours.

Great! Now I mount the new Disk 9?

Sorry. Yes, it started. Diagnostics, attached. mrplex-diagnostics-20260630-1254.zip

That worked. Disk 7 error is gone

This is the message I received: Caution: invalid backup GPT header, but valid main header; regenerating backup header from main header. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: ERROR Main partition table: OK Backup partition table: ERROR Invalid partition data! Information: Creating fresh partition table; will override earlier problems! Warning! Mismatched GPT and MBR partition! MBR partition 1, of type 0x83, has no corresponding GPT partition! You may continue, but this condition might cause data loss in the future! The operation has completed successfully. I rebooted, but Disk 7 still shows 'wrong'. Posted a new diagnostics mrplex-diagnostics-20260630-1115.zip

The device letter changed from sdh to sde, so I used fdisk -l /dev/sde Disk /dev/sde: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: ST8000NT001-3LZ1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 16773120 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sde1 64 3907029167 3907029104 1.8T 83 Linux I also upgraded to 7.3.1 last night. I attached a Diagnostics in case it provides more info than in 6.8.0. mrplex-diagnostics-20260629-2052.zip

Attached. What do you look for in the diagnostics? plex-diagnostics-20260628-1107.zip

attached xfs_repair-disk7-verification-after-repair-noN.txt

ok. I'll upgrade to the latest release after things are up and running. attached the file. xfs_repair-disk7-verification-after-repair.txt

I've never done an xfs_repair before. I saw this somewhere, but I may have done things incorrectly. I unplugged those drives and posted a new diagnostic. Should I start using the latest version of Unraid? plex-diagnostics-20260627-1234.zip