Cache disk unmountable Wrong or no file system after upgrade to 6.10.2-rc3 from 6.10.0-rc4

[Bovin]

I upgraded OS by Update OS Tool. I cannot find stable version, only 6.10.2-rc3, so I upgraded to it.

 

After reload, cache disk is not able to mount.

 

I tried to delete cache pool and create it again, but the problem is persisted. Please help.

bovin-lab-diagnostics-20220605-1158.zip

[Bovin]

I rolled back to 6.10-RC3 by replace all files from backup to flash, but he problem is persisted. 

[Bovin]

The problem is isolated to btrfs superblock broken.

 

Fix this by use backup superblock. But I am afraid that I hit this again if upgrade to 6.10.2

 

root@Bovin-lab:/mnt# btrfs check /dev/nvme0n1p1
Opening filesystem to check...
No valid Btrfs found on /dev/nvme0n1p1
ERROR: cannot open file system

 

root@Bovin-lab:/mnt# btrfs check -s 1 /dev/nvme0n1p1
using SB copy 1, bytenr 67108864
Opening filesystem to check...
Checking filesystem on /dev/nvme0n1p1
UUID: 1e4f3935-8a24-49dd-9fea-6b7a7d4b2fac
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
^[[B[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 29662449664 bytes used, no error found
total csum bytes: 28911732
total tree bytes: 56836096
total fs tree bytes: 15187968
total extent tree bytes: 7110656
btree space waste bytes: 9062485
file data blocks allocated: 311883104256
 referenced 28859248640

 

 

root@Bovin-lab:/mnt# btrfs-select-super -s 1 /dev/nvme0n1p1 >>>>>>>>>before overwrite, confirm backup superblock is good. 
using SB copy 1, bytenr 67108864

 

 

 

Edited June 5, 2022 by Bovin

[ChatNoir]

That's a question only JorgeB can answer. I would suggest that you wait for him to connect.

[JorgeB]

Device was wiped, possibly because the name changed, the last command above usually works for this:

 

2 hours ago, Bovin said:

btrfs-select-super -s 1 /dev/nvme0n1p1

 

It should now now mount again.

[Bovin]

23 minutes ago, JorgeB said:

Device was wiped, possibly because the name changed, the last command above usually works for this:

 

 

It should now now mount again.

Hi JorgeB,

 

Thanks for reply. How to avoid hit this? I would like to upgrade again. Should I try a fresh install? 

[JorgeB]

53 minutes ago, Bovin said:

How to avoid hit this?

Did the device change name when you updated? If yes first unassigned it, start array, stop array, then re-assign it.

 

Also you should update to latest stable, not to a test release.