Restart in normal mode and post new diagnostics

Here you go.

plex-diagnostics-20260626-1531.zip

Now emulated disk7 is unmountable again. Probably something with another disk causing emulation problems.

Your syslog is extremely cluttered due to the connections to the known bad disks.

ST2000DM001_Z560842G-20260626-1531  (sde)
ST3000DM001_W1F2GS5R-20260626-1531  (sdb)

Shutdown, unplug these disks, reboot, start the array in normal mode, and post new diagnostics.

We usually tell you to use the webUI to check filesystem, and you can do the repair there as well, but I'm not sure how much of the current methods applies to your old Unraid version, so I have been letting you do the command line. And you seemed to be doing it right the first time

Just now, trurl said:

xfs_repair -nv /dev/md9

Have you always specified the md device when you did xfs_repair? Using the sd device will invalidate parity when used on an array disk.

Sorry, it was disk9 that was being emulated, and it is mountable.

Do this.

10 minutes ago, trurl said:

Your syslog is extremely cluttered due to the connections to the known bad disks.

ST2000DM001_Z560842G-20260626-1531  (sde)
ST3000DM001_W1F2GS5R-20260626-1531  (sdb)

Shutdown, unplug these disks, reboot, start the array in normal mode, and post new diagnostics.

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

Edited June 27Jun 27 by mrichards

4 hours ago, mrichards said:

Should I start using the latest version of Unraid?

Lots of security updates since your version, as well as new features. I always recommend latest stable release. But that can wait.

Check filesystem on disk7

ok. I'll upgrade to the latest release after things are up and running.

attached the file.

xfs_repair-disk7-verification-after-repair.txt

Do it again without -n

attached

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

Looks repaired

Post new diagnostics with the array started in normal mode.

Attached. What do you look for in the diagnostics?

plex-diagnostics-20260628-1107.zip

Disk7 still unmountable.

Might be worthwhile to upgrade Unraid since xfs_progs has been updated since your version.

Jun 28 11:02:09 Plex emhttpd: /mnt/disk7 mount error: Unsupported partition layout

Disk is not mounting due to the partition; the filesystem should be OK, with the array stopped post the output from:

fdisk -l /dev/sdh

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

Edited June 30Jun 30 by mrichards

9 hours ago, mrichards said:

/dev/sde1 64 3907029167 3907029104 1.8T 83 Linux

That's an MBR partition, only using 2TB for an 8TB disk.

With the array stopped type:

sgdisk -o -a 8 -n 1:32K:0 /dev/sde

Then reboot and see if that disk no longer shows as wrong, if it doesn't start the array and post new diags.

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 partition still isn't correct; do this, first, wipe the existing one (this won't wipe the data)

wipefs -a /dev/sde

then again

sgdisk -o -a 8 -n 1:32K:0 /dev/sde

You shouldn't see any errors this time; if so, reboot again.

That worked. Disk 7 error is gone

And did it mount correctly after array start?

Post new diagnostics with the array started in normal mode

Sorry. Yes, it started. Diagnostics, attached.

mrplex-diagnostics-20260630-1254.zip

Looks good, and the data on disk 7 should all be fine, since it was a partition issue, not the filesystem.

If you are happy with the emulated disk9 contents, the main thing left is to rebuild it.