-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to boot into a snapshot since kernel 6.8 (read-only), but i can with 6.6 #328
Comments
I get some more information once i boot into my snapshot in tty :
findmnt
Does anyone also have some issues with grub-btrfs-overlayfs and kernel 6.8 ? Thanks |
I can confirm the issue with Dracut and kernel 6.8. Kernel 6.6 has no issue. |
Did you also have this issue in your VM with mkinitcpio eventually ? |
Yes |
Hello, You should add the rw option in the snapshot CMDLINE to resolve this issue. |
This issue would be obsolete. It was fixed for me using kernel 6.10 on Arch Linux. I already tested SDDM and GDM on overlayfs on VM, a result: no issue. |
Hello @Zesko, I use this fix on a Kernel 6.9 and 6.10 with my own initramfs script to boot into an overlay fs. That works. I was developed an initramfs script for Kaisen Linux foundable here: https://gitlab.com/kaisenlinux/packages/grub-btrfs/-/blob/main/debian/initramfs/local-bottom/kaisen-grub-btrfs?ref_type=heads |
Hi,
I cannot boot into a snapshot since kernel 6.8. I have two kernels installed in my system 6.6 lts and 6.8.
Presets for both are exactly the same, and i can boot into any snapshot if i choose kernel 6.6 in the grub menu after i have chosen the snapshot itself.
If i boot on a snapshot with kernel 6.8, it does not want to start KDE, i can switch with ctrl+alt F to tty, i can then login in, and when i want to start KDE with startx i have the following message :
Can't move /var/log/Xorg.0.log to /var/log/Xorg.0.log.old
. This is surprising because/var/log
is a subvolume, and i do not make any snapshot of it, only the subvolume /.By checking the logs, yes, my snapshot's filesystem is read-only, therefore i cannot boot to kde. But i really do not understand why,
Once again i do not have this issue at all with 6.6, i can boot my snapshots normally with it.
I do not know really how to investigate more. Do you have any nice idea ? I have Manjaro/KDE with Snapper and Btrfs-Assistant.
Thank you
*Here is the hook line from mkinitcpio.conf :
HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth encrypt filesystems grub-btrfs-overlayfs)
*Here is my config
The text was updated successfully, but these errors were encountered: