March 17, 20224 yr Hi. I recently upgraded to 6.9.2 (I had lots of VM issues with 6.9.2 previously, and stayed with 6.9.1 until now), and moved my NVMe M.2 drive from slot 2 to slot 1 on the MB (it's faster, and I removed GPU #2 so it would release the bus). Yesterday all worked perfectly, and I got my Windows VM up and running. Today I tried booting a Linux VM. It resulted in a hang, and I had to do a power button hold to stop it. After that, the main cache drive (the NVMe I moved) says it's unmountable. In the syslog it says there's a "bad fsid on block ... (long number)". I tried disabling VM Manager and Docker, but it does not help. Moving the NVMe back to slot 2 also doesn't change anything. The array is working fine, but since docker and VMs are running on the cache, it is not a good situation... Can anyone help? t-tower-diagnostics-20220317-1703.zip t-tower-syslog-20220317-1502.zip
March 17, 20224 yr Community Expert Solution Cache filesystem is corrupt, there are some recovery options here.
March 17, 20224 yr Author None of the options worked... What's left - reformat and restore manually..? ====== root@T-TOWER:/mnt/disk1# mount -o degraded,usebackuproot,ro /dev/nvme0n1p1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. ====== root@T-TOWER:/mnt/disk1# btrfs restore -vi /dev/nvme0n1 /mnt/disk1/restore No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme0n1 Could not open root, trying backup super ====== root@T-TOWER:/mnt/disk1# btrfs check --repair /dev/nvme0n1 enabling repair mode WARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. Eg. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1 Starting repair. Opening filesystem to check... No valid Btrfs found on /dev/nvme0n1 ERROR: cannot open file system ======
March 17, 20224 yr Community Expert 6 minutes ago, mrtrilby said: nvme0n1 missing the partition, it's nvme0n1p1
March 17, 20224 yr Author Got it, running a btrfs restore now - it's copying stuff over to the array.
March 17, 20224 yr Author Successfully ran a restore. Then I tried a --repair. Does the result below mean a reformat is needed..? ====== root@T-TOWER:/mnt/disk1# btrfs check --repair /dev/nvme0n1p1 enabling repair mode WARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. Eg. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1 Starting repair. Opening filesystem to check... bad tree block 22036480, bytenr mismatch, want=22036480, have=30425088 ERROR: cannot read chunk root ERROR: cannot open file system
March 18, 20224 yr Community Expert 13 hours ago, mrtrilby said: Does the result below mean a reformat is needed..? Yep.
March 18, 20224 yr Author Got it, setting up everything again. I'm glad reinstalling docker containers in Unraid is a breeze! Thanks for your help!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.