[SOLVED] Array disk - Unmountable: not mounted

[Hyp3z]

Added a new disk to the array today and stopped the clear that unraid was doing.

 

Now I'm getting Unmountable: not mounted

 

 

 

Jan 17 17:19:59 MirinServer root: mount: /mnt/disk1: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error.

Jan 17 17:19:59 MirinServer emhttpd: /mnt/disk1 mount error: not mounted

 

I have done the below:

- Put array into maintenance mode
- xfs_repair -nv /dev/md1
- xfs_repair -vL /dev/md1

 

I didn't know what "Clear" was so I cancelled it. Not sure if this is what caused the above error or not. 

 

Any help would be appreciated.

 

Thanks

- Kyle 

 

 

mirinserver-syslog-20210117-0630.zip

[itimpi]

A ‘Clear’ is the action Unraid takes when adding a disk to a parity protected array as that is the action needed to ensure parity remains valid.

 

i am a bit confused as your screenshot shows only 1 data drive - were you trying to add disk2?   Has disk1 ever been formatted in Unraid?

[Hyp3z]

Hi @itimpi Yes I was trying to add disk2. I have removed it from the array.

 

4 hours ago, itimpi said:

Has disk1 ever been formatted in Unraid? - To my knowledge no, unless Unraid does it by default when loading the array for the first time.

 

[itimpi]

What was the output from the xfs_repair commands?

[Hyp3z]

Phase 1 - find and verify superblock...
        - block cache size set to 1477912 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 0 tail block 0
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 1
        - agno = 3
        - agno = 0
        - agno = 7
        - agno = 4
        - agno = 2
        - agno = 6
        - agno = 5
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
Maximum metadata LSN (1:837510) is ahead of log (1:2).
Format log to cycle 4.

        XFS_REPAIR Summary    Sun Jan 17 23:47:02 2021

Phase		Start		End		Duration
Phase 1:	01/17 23:46:29	01/17 23:46:29
Phase 2:	01/17 23:46:29	01/17 23:46:39	10 seconds
Phase 3:	01/17 23:46:39	01/17 23:46:41	2 seconds
Phase 4:	01/17 23:46:41	01/17 23:46:41
Phase 5:	01/17 23:46:41	01/17 23:46:41
Phase 6:	01/17 23:46:41	01/17 23:46:41
Phase 7:	01/17 23:46:41	01/17 23:46:41

Total run time: 12 seconds
done

 

[JorgeB]

There's something mounting disk1 before the array:

 

Jan 17 17:06:58 MirinServer kernel: XFS (sde1): Mounting V5 Filesystem
Jan 17 17:06:58 MirinServer emhttpd: shcmd (3): /usr/local/emhttp/webGui/scripts/update_access
Jan 17 17:06:58 MirinServer sshd[1887]: Received signal 15; terminating.
Jan 17 17:06:59 MirinServer kernel: XFS (sde1): Ending clean mount

 

Then it cant be mounted again:

 

Jan 17 17:07:05 MirinServer kernel: XFS (md1): Filesystem has duplicate UUID eb78e917-4f51-464e-8114-d251dc7845f5 - can't mount

 

[Hyp3z]

I had an unassigned SSD that changed its dev name. I have changed my boot script to use UUID instead.

 

Everything is now working as you can see below. 

 

 

Thanks for the help @JorgeB & @itimpi