A few days ago I decided to add a new drive to my array, not removing or replacing any existing drive.

These are the steps I took:

1. shutdown server from unraid UI.

2. Remove power cable and press power button.

3. connect a ext4 formatted drive from my old server. Same model as one of my current drives in my unpaid setup, but different serial of course.

4. boot server and unraid.

5. unraid says "wrong" on drive 1. The serial matches though.

6. I shutdown the server and removed the newly added disk to make sure that everything is like I were before.

7. boot again but same "wrong"-error.

8. some people suggested to create a new config and start the array. 

9. Drive is not "unable to mount" and I think I f-ed up the parity as well.
10. I tried different cables and both using my HBA (dell h200 flashed to it mode) and the on board sata controller with same result.

 

If I run blkid I can see that my parity disk and one of my data disks (the one that still mounts) have the same UUID. My unmountable disk though, have a PARTUUID but missing all of the other attributes.

 

/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272B-4CE1" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/nvme0n1p1: UUID="ed596e68-7909-4f24-adb6-1c20b7420d91" UUID_SUB="b887f981-68d6-423b-8ebe-59c1ecd9ed2b" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdd1: UUID="c8af5809-8de7-4a0a-b836-a4c9a6840769" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="58f90655-682e-46c1-805f-4f1a56da6598" (This is my parity drive)
/dev/loop0: TYPE="squashfs"
/dev/sdc1: UUID="c8af5809-8de7-4a0a-b836-a4c9a6840769" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="ab6cf320-af9e-43dd-8498-8c0d5b82c9b1" (this is my working data drive)
/dev/sdb1: PARTUUID="3f7ed1fd-a05f-4bb6-8a08-da77d2df9a70"" (this is my unmountable data drive)

So, what could be the cause? It can't be that I added an identical disk and some collision happened?
Is the lack of UUID something I can fix with xfs_admin, or is it a sign that something is broken, hardware wise?

Attach Diagnostics to your NEXT post in this thread 

agda-diagnostics-20231009-0640.zip

 

6 hours ago, trurl said:

Attach Diagnostics to your NEXT post in this thread 

Here you go!

It would be important to know why the disk was "wrong", most likely the capacity changed by a few bytes, post the output of 

xfs_repair -n /dev/sdb1

 

13 minutes ago, JorgeB said:

It would be important to know why the disk was "wrong", most likely the capacity changed by a few bytes, post the output of 

xfs_repair -n /dev/sdb1

 

I’m not at my computer right now, but it’s just a bunch of dots, in stage 1..

Partition is likely starting on a different sector, assuming no backups, best bet to recover data would be use a file recovery util like UFS explorer, the free trial should show what data can be recovered.

28 minutes ago, JorgeB said:

Partition is likely starting on a different sector, assuming no backups, best bet to recover data would be use a file recovery util like UFS explorer, the free trial should show what data can be recovered.

Thank you so much for taking the time to answer! Isn’t it strange that that disk is missing a UUID?

I suspect that it's because the partition starting sector/size changed, but would need the diags from when the disk showed as wrong to confirm.

I found a backup drive with nearly all of the files on it. Should have have any hope that this could be solved or should I format my drive and move over the files from backup? if this ever happens again and my parity is good, how would I recover?

12 hours ago, billynu said:

Should have have any hope that this could be solved or should I format my drive and move over the files from backup?

You'd need to try something like UFS explorer as mentioned.

 

12 hours ago, billynu said:

if this ever happens again and my parity is good, how would I recover?

If parity is valid a rebuild will usually fix it.