[SOLVED] Array Disk Unmountable: No file system

[MEEXXX]

Was working on my unraid server today and it went through a few power cycles. The issue im having is my disk 4 is throwing an error, Unmountable: no file system. 
I've read through some forums here and tried the following:
- Put array into maintenance mode
- xfs_repair -nv /dev/md4
- xfs_repair -vL /dev/md4
- start array back up normally
- rebooted

After these steps i'm still having the issue. 



Found the following in the logs (attached):

Jan  7 00:37:01 RyzNas emhttpd: shcmd (42): mkdir -p /mnt/disk4
Jan  7 00:37:01 RyzNas emhttpd: shcmd (43): mount -t xfs -o noatime,nodiratime /dev/md4 /mnt/disk4
Jan  7 00:37:01 RyzNas kernel: XFS (md4): Filesystem has duplicate UUID 77844dfc-e01b-4d6d-b906-66598a67833c - can't mount
Jan  7 00:37:01 RyzNas root: mount: /mnt/disk4: wrong fs type, bad option, bad superblock on /dev/md4, missing codepage or helper program, or other error.
Jan  7 00:37:01 RyzNas emhttpd: shcmd (43): exit status: 32
Jan  7 00:37:01 RyzNas emhttpd: /mnt/disk4 mount error: No file system

What would be my next best step to try resolve this? Thanks in advance.

- Luke

 

ryznas-diagnostics-20210107-0040.zip

[JorgeB]

23 minutes ago, MEEXXX said:

XFS (md4): Filesystem has duplicate UUID 77844dfc-e01b-4d6d-b906-66598a67833c - can't mount

This means there's already an fs mounted with the same UUID, please post output of:

blkid

 

[MEEXXX]

[JorgeB]

Something is mounting the disk before Unraid:

 

Jan  7 00:36:52 RyzNas kernel: XFS (sdf1): Mounting V5 Filesystem
Jan  7 00:36:52 RyzNas kernel: XFS (sdf1): Ending clean mount

 

Also note that because of that parity won't be 100% in sync.

[MEEXXX]

I have a 10TB HDD UD that mounts on boot. It changed from /dev/sdf to /dev/sdb due to using dev names instead of UUID in the boot script.


Thanks @JorgeB

[itimpi]

The /dev/sdX type names can always change between boots as Linux assigns them dynamically during the boot process so you should avoid using them if at all possible.     You should use one of the /dev/by-id ways of identifying the drive instead as they are invariant.

[MEEXXX]

11 hours ago, itimpi said:

The /dev/sdX type names can always change between boots as Linux assigns them dynamically during the boot process so you should avoid using them if at all possible.     You should use one of the /dev/by-id ways of identifying the drive instead as they are invariant.

I have since changed to /dev/disk/by-uuid. But thanks for the follow up info @itimpi