Summary: | KDE Neon install fails to boot when using btrfs | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | Julius Vitkauskas <zadintuvas> |
Component: | Live/Install images | Assignee: | Neon Bugs <neon-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | carlosdemaine, clay, jlp, jr, martin, mrp, neon-bugs, orangewinds, sitter, U.Koehler_sec, zadintuvas |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Julius Vitkauskas
2022-10-24 22:54:14 UTC
The way i figured this out is that i booted into rescue mode (added "1" to kernel params) and got a shell, tried to remount / rw and it threw an error message, googled the error message and saw that space_cache=v2 option helps. I am (In reply to Clay Weber from comment #2) > I am I am also seeing this, tested on two systems and in virt-manager I seem to remember that the installation into a btrfs partition newly created crashed. Will not try again since it took 15 attempts to get KDE Neon installed. Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: Acer Product Name: Aspire A515-45G System Version: V1.08 I also installed to a btrfs partition and the booting process hung with the same error messages. I fixed it by rebooting into another linux installation on that computer, mounted the partition with neon installed on it, and edited /etc/fstab, changing space_cache to space_cache=v2 in the mount options for both / and /home. I could then reboot into neon with no problems. I am seeing this again today, Need to edit the fstab for the btrfs mounts to change space_cache to space_cache=v2 /calamares/desktop/modules/fstab.conf can be edited during the live session to replace space_cache with space_cache=v2 to fix this *before* beginning an installation calamares has been updated to 3.3.0 which according to release notes handles btrfs file systems by no longer adding space_cache=* of any variety to fstab. all modern kernels automatically default to space_cache version2 and btrfs-progs no longer needs a configuration, it checks version 1 then falls back to version 2. new iso building now. needed an updated calamares-settings as well which is now in user. new iso running now. verified that btrfs install works in a virtualbox vm. closing as fixed. |