Please post the diagnostics after a mount attempt with UD

I first went down the road of mounting my 'wrong disk' drive into a linux environment and tried to inspect the drive. This is the output i got (Sorry looks like formatting is bad):

xfs_repair_wrong_disk.txt

Looks like it would try to repair if you removed -n. Whether you would like the results of the repair is another question.

Do i have any other better options? What would you recommend?

1. Disconnect the wrong disk w/ a new disk and see if i can boot the rest of the drives (including parity) and then rebuild the wrong disk. If I went this route, could I check the health of the parity drive first to determine if it's still in a good state?

2. run xfs repair and accept the data loss. I believe this would invalidate my parity drive?

3. boot up all drives, start array in maintenance mode if possible, and try and run xfs repair on the wrong disk drive, which would maintain parity.

Edited January 17Jan 17 by peteopp

1. No reason to expect parity rebuild would give you a different result

2. If you repair it outside the array, parity would no longer be in sync with it since it would have writes independent of parity. You could always rebuild parity.

3. That would maintain parity and otherwise give you the same result as option 2.

4. You could clone the drive and try to repair the clone to see what the results of the repair would be.

On 1/16/2026 at 5:56 PM, peteopp said:

Given my test results on the parity drive,
Tested the parity drive.

2 seconds of slight clank noise on startup. Went away. Discovered in bios. Turned off. Full clanking sound on spin down. Concerned about the health of that drive more so than disk5.

It is worth noting that parity is the least important drive in the array because it contains none of your data. Parity does allow you to rebuild a missing disk, but all other drives are also required to rebuild a missing disk, and those other drives have your data.

I’m currently using ddrescue and doing 4.

I don’t quite follow the comment on 1. Though. Disk 5 “wrong” disk got kicked out of the array , that was the original problem that started this spiral of crap. Wouldn’t the parity be able to rebuild a new disk correctly if I just removed disk 5 from the system and booted up the array? Do this vs repairing xfs repair disk 5 and accepting data loss.

Edited January 18Jan 18 by peteopp

Usually parity is in sync with the corrupted data, so rebuild will just result in the same.

If parity plus all other disks are working, you should be able to start the array with disk5 missing and see if emulated disk5 mounts. The emulated disk is exactly what will be rebuilt. If emulated disk5 is unmountable, we always try to repair the emulated disk before rebuild.

This is what we usually recommend, but I thought there were more problems going on that prevented disk5 from being emulated.

13 hours ago, trurl said:

If parity plus all other disks are working, you should be able to start the array with disk5 missing and see if emulated disk5 mounts. The emulated disk is exactly what will be rebuilt. If emulated disk5 is unmountable, we always try to repair the emulated disk before rebuild.

This is what we usually recommend, but I thought there were more problems going on that prevented disk5 from being emulated.

I have the parity plus all disks (minus disk5) working in the array. Disk5 is successfully emulated. I already pulled all my essential data to a backup drive (YAY!). Attaching diagnostics which should have recent SMART runs. I believe everything is passed.

given the xfs report i reported for disk5 up above, would you recommend just putting a new disk in and rebuilding disk5 off the emulation? Or is it easier and faster just to repair disk5, as you said it most likely reflects parity anyways.fridge-diagnostics-20260118-2127.zip

Edited January 19Jan 19 by peteopp

You can still try to repair the filesystem for the emulated disk to see how it looks, before a rebuild, no point in rebuilding if the results aren't good. Also keep the old disk5 intact if you still have it.

7 hours ago, JorgeB said:

You can still try to repair the filesystem for the emulated disk to see how it looks, before a rebuild, no point in rebuilding if the results aren't good. Also keep the old disk5 intact if you still have it.

With disk5 emulated, I did a filesystem check and repair. Output for both attached.

disk5_xfs_fix.txt

Looks like a clean repair. I don't see a Lost+found folder in disk5 and currently have the array started in normal mode emulating disk5.

Path forward....

I unfortunately have 4 10TB drives that I could put into the system, but disk5 is 12TB. If it's the best path, i can purchase a new drive. I also purchased a 18TB that I was planning to replace my 12TB parity with.

Given I've successfully did a ddrescue image of disk5, is there any real danger/risk to just reusing disk5 and let parity rebuild on-top of it?

Given - i have a ddrescue .img of disk5 preserved.
1. Buy a new 12TB drive and rebuild disk5 off parity. This allows me to reserve disk5 in-case i need to walk backwards.

2. Format/clean disk5 and let unraid treat it as a new drive and have parity rebuild onto original harddrive.

3. Rebuild physical disk5 using xfs repair, add back into the array and rebuild parity. Not sure why i would like this option?

Really appreciate the help JorgeB and trurl! Almost done.

Edited January 19Jan 19 by peteopp

20 minutes ago, peteopp said:

Given I've successfully did a ddrescue image of disk5, is there any real danger/risk to just reusing disk5 and let parity rebuild on-top of it?

And is old disk5 healthy, i.e., no read errors when the ddrescue image was done?

Correct, perfect 1st pass with 0 read and no other errors.

Post SMART report for that drive.

Disk5 smart attached.

disk5_smart.txt

That looks OK.

I’m arguing with AI on this and could use an Unraid lesson.

My current array . All smart passes

Parity - 12tb. Old

-data1 - 10tb - good

-data2 - 10tb - good

-data3 - 10tb - good

-data4 - 10tb - good

-data5 - 12tb - MISSING

-data6 - 5tb - very old

-data7 - 5tb - very old

I bought two 18tb drives. I’m trying to upgrade the parity and data5 disk without putting stress on the system given the age of a couple of the drives.

Can I just follow parity swap section or does that not apply here ?

1 . Move 18tb into parity

2. Move 12tb parity into data 5.

3. Hit button to copy parity to new parity.

4. Then start array and allow new parity and data disks to rebuild onto data5 (which is the old parity disk)

Edited January 20Jan 20 by peteopp

15 minutes ago, peteopp said:

Can I just follow parity swap section or does that not apply here ?

You can, but that will rebuild disk5 to the old parity.

1 hour ago, peteopp said:

I’m trying to upgrade the parity and data5 disk without putting stress on the system given the age of a couple of the drives.

And whatever you do, any rebuild, whether parity by itself or disk5 by itself or parity swap is going to read all disks completely.

7 hours ago, JorgeB said:

You can, but that will rebuild disk5 to the old parity.

That should be fine. I resolved emulated disk5 and all appears well.