Gravitate

Hmmm... I shut down and added another drive to try ddrescue as you suggested. However, when I booted up again, I couldn't get it to recognise my NVMe drive at all. No matter what I tried, it just wouldn't show up as connected, not even in bios. So, I have just replaced the drive and I am in the process of restoring from a recent backup (fortunately, I don't think I have lost much). I have ordered a NVMe to USB adapter, just to see if the drive is totally shot. I'm probably going to try returning it but as it is just over a year, I am not sure I will get anywhere. I thought I got a bargain at the time... probably should have paid a bit more for a better brand. Oh well. Thanks for your help. I really do appreciate it.

I am starting to suspect that... a bit surprising as it's only 1 year old. I tried to run the extended SMART test... but I can't see anything obvious (SMART report attached). Although, it did seem to start at 50% and finish extremely quickly (under 1 minute). Is that normal for NVME drives? I know HDDs usually take much longer than that. nas-smart-20240930-1613.zip

I am not too sure what has happened, but after a restart, docker wasn't working. Upon investigation, it was because the NVME cache drive containing the appdata folder etc, was unmountable. The logs show the following errors: Sep 30 14:59:38 NAS emhttpd: mounting /mnt/cache Sep 30 14:59:38 NAS emhttpd: shcmd (2907): mkdir -p /mnt/cache Sep 30 14:59:38 NAS emhttpd: shcmd (2908): mount -t xfs -o noatime,nouuid /dev/nvme0n1p1 /mnt/cache Sep 30 14:59:38 NAS kernel: XFS (nvme0n1p1): Mounting V5 Filesystem Sep 30 14:59:38 NAS kernel: nvme0n1: I/O Cmd(0x2) @ LBA 2000399760, 1 blocks, I/O Error (sct 0x2 / sc 0x81) Sep 30 14:59:38 NAS kernel: critical medium error, dev nvme0n1, sector 2000399760 op 0x0:(READ) flags 0x1800 phys_seg 1 prio class 2 Sep 30 14:59:38 NAS kernel: XFS (nvme0n1p1): log recovery read I/O error at daddr 0x0 len 1 error -61 Sep 30 14:59:38 NAS kernel: XFS (nvme0n1p1): empty log check failed Sep 30 14:59:38 NAS kernel: XFS (nvme0n1p1): log mount/recovery failed: error -61 Sep 30 14:59:38 NAS root: mount: /mnt/cache: mount(2) system call failed: No data available. Sep 30 14:59:38 NAS root: dmesg(1) may have more information after failed mount system call. Sep 30 14:59:38 NAS kernel: XFS (nvme0n1p1): log mount failed Sep 30 14:59:38 NAS emhttpd: shcmd (2908): exit status: 32 Sep 30 14:59:38 NAS emhttpd: /mnt/cache: no btrfs or device /dev/nvme0n1p1 is not single Sep 30 14:59:38 NAS emhttpd: /usr/sbin/zpool import -f -d /dev/nvme0n1p1 2>&1 Sep 30 14:59:38 NAS emhttpd: no pools available to import Sep 30 14:59:38 NAS emhttpd: cache: no uuid Sep 30 14:59:38 NAS emhttpd: shcmd (2909): mount -t reiserfs -o noatime,user_xattr,acl /dev/nvme0n1p1 /mnt/cache Sep 30 14:59:38 NAS root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. Sep 30 14:59:38 NAS root: dmesg(1) may have more information after failed mount system call. Sep 30 14:59:38 NAS emhttpd: shcmd (2909): exit status: 32 Sep 30 14:59:38 NAS emhttpd: /mnt/cache mount error: Unsupported or no file system Sep 30 14:59:38 NAS emhttpd: shcmd (2910): rmdir /mnt/cache Sep 30 14:59:38 NAS kernel: REISERFS warning (device nvme0n1p1): sh-2021 reiserfs_fill_super: can not find reiserfs on nvme0n1p1 Any suggestion how I can recover it? I tried xfs_repair but no joy: root@NAS:~# xfs_repair -v /dev/nvme0n1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... superblock read failed, offset 1024203603968, size 131072, ag 2, rval -1 fatal error -- No data available Any help would be greatly appreciated. Thanks. nas-diagnostics-20240930-1447.zip