Yeah, that is normal. That is probably a rights issue.
Does btrfs-assistant work now?
1 Like
Amazingly yes!
Was it the
sudo mount /dev/sda1 /mnt
command? (I did with sda1 and sda2)
Yes, with sda2. btrfs-assistant reads your mounted btrfs filesystems.
Thatâs great! Thank you very much @dalto.
I will bookmark the post, just in case I mess up or something happens and I need to roll back. You know unfortunately I converted to systemd-boot.
Thank you very much for your help as usual.
Sorry, it is working, but everything blank!
I do not see the âprofilesâ/ âconfigâ system and /home.
Yes, go to the restore tab.
It is under the snapper tab
1 Like
Sorry⌠It seems I am so ⌠everything is blank!
P.S. Tried clicking Refresh several times. Nothing.
Is anything in the dropdown if you click on it?
Nothing. Even clicking the drop down does nothing.
What does sudo btrfs sub list /mnt return?
1 Like
[liveuser@eos-2022.06.23 ~]$ sudo btrfs sub list /mnt
ID 256 gen 57671 top level 5 path @
ID 257 gen 57671 top level 5 path @home
ID 258 gen 57623 top level 5 path @cache
ID 259 gen 57671 top level 5 path @log
ID 260 gen 27 top level 256 path @/var/lib/portables
ID 261 gen 28 top level 256 path @/var/lib/machines
ID 264 gen 57673 top level 257 path @home/.snapshots
ID 265 gen 232 top level 264 path @home/.snapshots/1/snapshot
ID 385 gen 3730 top level 264 path @home/.snapshots/35/snapshot
ID 541 gen 11751 top level 264 path @home/.snapshots/108/snapshot
ID 679 gen 17037 top level 264 path @home/.snapshots/157/snapshot
ID 693 gen 57673 top level 256 path @/.snapshots
ID 694 gen 17931 top level 693 path @/.snapshots/1/snapshot
ID 697 gen 17960 top level 693 path @/.snapshots/3/snapshot
ID 717 gen 19037 top level 264 path @home/.snapshots/174/snapshot
ID 773 gen 21893 top level 264 path @home/.snapshots/198/snapshot
ID 825 gen 24735 top level 264 path @home/.snapshots/222/snapshot
ID 826 gen 24736 top level 693 path @/.snapshots/75/snapshot
ID 880 gen 27608 top level 264 path @home/.snapshots/246/snapshot
.
.
.
ID 1565 gen 57382 top level 693 path @/.snapshots/539/snapshot
ID 1566 gen 57500 top level 264 path @home/.snapshots/498/snapshot
ID 1567 gen 57500 top level 693 path @/.snapshots/540/snapshot
ID 1568 gen 57621 top level 693 path @/.snapshots/541/snapshot
ID 1569 gen 57622 top level 693 path @/.snapshots/542/snapshot
ID 1570 gen 57628 top level 264 path @home/.snapshots/499/snapshot
ID 1571 gen 57628 top level 693 path @/.snapshots/543/snapshot
[liveuser@eos-2022.06.23 ~]$
That may be a bug. I will need to look at that on my side and see if I am seeing the same issue.
1 Like
OK. No problem.
I hope at least I could provide something useful⌠even a bug!
(Just to double confirm, I am on a live session, not the installed one)
A feature may be missing? âBrowse/Restore Tabâ doesnât know UUID of other Btrfs file system.
But it uses the config /etc/btrfs-assistant.conf â [Subvol-Mapping] to get defined UUID, but it is for the flat Btrfs layout.
1 Like
That should only be needed with a custom layout. @limotux doesnât have a custom layout so it should âjust workâ. ButâŚit isnât so it needs investigation.
2 Likes
Initially I had low disk space, (<5 GiB) then I freed up some space while having BTRFS assistant open. Assistant is aware of the change but still tells me âSituation criticalâ. Perhaps that text doesnât refresh?
EDIT: It still tells âSituation criticalâ even after a relaunch of assistant.
Sounds like I made a good decision to give the GRand United Bootloader another chance 
1 Like
Is possible to mark a snapshot to avoid Snapper cleanup from removing it?
Perhaps a new feature?
1 Like