I was using the 30 day trial license for some days and yesterday I wanted to move to a full löifetime license. With this I also changhe the USB boot drive. I did a backup of the running system from within unraid and used the USB creator to create the new USB drive with this backup. 

Booted the device from the new USB drive and followed the steps to put in my new lifetime license. All that worked so far.

But then I noticed, that all my drives, expet the parity drive, has status "Unmountable: No File System".

In the syslog I found:

Aug 21 19:09:37 Loch-NAS2 emhttpd: Mounting disks...
Aug 21 19:09:37 Loch-NAS2 emhttpd: mounting /mnt/disk1
Aug 21 19:09:37 Loch-NAS2 emhttpd: /sbin/blkid /dev/md1p1 2>&1
Aug 21 19:09:37 Loch-NAS2 emhttpd: /dev/md1p1: UUID="7c12f40b-76f5-171a-31ea-2856dcbc3f35" UUID_SUB="cdfd0c12-d3b7-ac14-05de-9afb2c1bfd1d" LABEL="UGREEN-CORE-x86_64-0CBE9E" TYPE="linux_raid_member"
Aug 21 19:09:37 Loch-NAS2 emhttpd: disk1: mount error: no file system
Aug 21 19:09:37 Loch-NAS2 emhttpd: mounting /mnt/disk2
Aug 21 19:09:37 Loch-NAS2 emhttpd: /sbin/blkid /dev/md2p1 2>&1
Aug 21 19:09:37 Loch-NAS2 emhttpd: /dev/md2p1: UUID="7c12f40b-76f5-171a-31ea-2856dcbc3f35" UUID_SUB="276ce6fd-5317-2175-fb97-2616b375fb03" LABEL="UGREEN-CORE-x86_64-0CBE9E" TYPE="linux_raid_member"
Aug 21 19:09:37 Loch-NAS2 emhttpd: disk2: mount error: no file system
Aug 21 19:09:37 Loch-NAS2 emhttpd: mounting /mnt/cache
Aug 21 19:09:37 Loch-NAS2 emhttpd: /sbin/blkid /dev/nvme2n1p1 2>&1
Aug 21 19:09:37 Loch-NAS2 emhttpd: /dev/nvme2n1p1: UUID="7c12f40b-76f5-171a-31ea-2856dcbc3f35" UUID_SUB="1bf083d5-baa3-33c1-4741-7d05984e7a5d" LABEL="UGREEN-CORE-x86_64-0CBE9E" TYPE="linux_raid_member"
Aug 21 19:09:37 Loch-NAS2 emhttpd: cache: mount error: no file system

There is also a unclean shutdown detected, but I don't know why as I used the WebUI to comnpletely shutdown the device.

Before I rebooted the device, I also added anothe new/never used NvME drive to the NAS as well, but this should actually not cause such a problem, right?

 

Furthermore a parity check was issued and it found several error but after let it running over night I stopped it this morning. It is 3 20TB drives with one of them as parity, so it takes totally more than 20h.

 

Is there something I can now do to fix this problem?

 

loch-nas2-diagnostics-20240822-0704.zip

So I was able to fix the Pool drives with the xfs_repair from WebGUI. However my cache drive, which is formatted in btrfs cannot be repaired by this. btrfs status gives me this:

checksum verify failed on 490995712 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 490995712 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 490995712 wanted 0x00000000 found 0xb6bde3e4
bad tree block 490995712, bytenr mismatch, want=490995712, have=0
Couldn't read tree root
ERROR: cannot open file system
Opening filesystem to check...

 

All you devices are appearing as:

 

TYPE="linux_raid_member"

 

This is not normal, they should have the current filesystem signature, post new diags to see the btrfs errors.

OH now I know what probably caused this problem. I firstly forgot to plug the USB and the device ( a ugreen nas) started to boot the UGOS which I then aborted as soon as I saw it. But looks like the ugreen OS wanted to access a storage pool on these drives. Damn.. I now at least set the UGOS to factory that this cannot happen again.

 

Nevertheless... Would be great if I can restore the cache drive anyway somehow.

 

Here is the new diags

loch-nas2-diagnostics-20240822-1158.zip

Edited August 22, 20241 yr by Dudi

Post the output of

btrfs fi show

 

it gives no output at all

That means there's no valid btrfs filesystem being detected, you can try these recovery options, but something strange is going on there.

Thanks for your help. After that didn't work I decided to not spend more time in trying to repair it and formatted the cache drive.