[SOLVED] Proper setup to boot snapshots with /home subvol within / snapshot

[FGD-Garuda]

Hello,

I am normally using 2 subvols, @ for root and @home for home.
The @home subvol is mounted through fstab to /home.

Since I want grub-btrfs to boot a snapshot without the need to manually edit fstab and point to the corresponding @home subvol of each snapshot, I have copied all my userdir from @home subvol into the /home FOLDER of @ snapshot.

I booted from the snapshot, got to the SDDM login screen. After entering PW I got a bunch of failures to write files due to permissions.
So as a crude testing method I sudo chown -R user:user /home/userdir and rebooted into the snapshot.

Still after entering PW now permission errors are gone but ksplashqml closes right away and I'm stuck on a blank screen.

journalctl -xb showed me failure to create runtime directory /run/user/1000 with permission denied.

I highly suspect there are still some permission issues but can't find where.

Since by default when installing Kubuntu and some other distros it automatically creates 2 subvols, one for @ and one for @home, you have to migrate your @home into @ in order to achieve a fully bootable snapshot that would contain all user files.

What have you guys did to migrate your user files within one subvol along with root files?

Thanks

[FGD-Garuda]

Ok so it seems I have trouble booting with my user files inside the /home folder of @ root subvol. I get permission issues on /run/user/1000, which isn't good.

I gave up on merging my user files into my root subvol. For now...

Instead I built myself a script which uses kdialog to minimize typos and I can select subvols to snapshot and where to snapshot them. Once that is done, with the magic of setting variables within the script, sed is running through /etc/fstab and substitutes subvol=@ and subvol=@home with the newly created root and home subvols. This way I can boot with a seperate @home subvol without the need to manually edit anything at any point. Works flawless so far! grub-btrfs is really useful.

One more thing, for those who would decide to remove the root fstab entry for your root subvol, you will miss your non-default mount options. There are a few ways to get around this, although not really mandatory for me to change them, I am testing a way to include noatime in the kernel's rootflags. But anyway that is a detail, however for some systems those mount options are important, therefore if you remove your root line in fstab just remember it's not yet the end of the process.