Hello,
some days ago I tried to install siduction for the first time. I only changed the file system to btrfs.
Installation seams to work, but after a restart it ended up on the console. After some time i recognized that the root file system was mounted read only. I tried this several times on a phyiscal notebook and in a qemu/kvm virtual machine.
After leaving the default file system to ext4 anything works fine.
Any idea or is this a (known) bug?
Regards
Kiwix
Not a known bug to my knowledge. I will try to replicate the behavior.
Confirmed, For me, it hangs on reboot right after graphical target was reached. A quick glance at auntie google showed no known bugs in that direction. Right now, I don't have time to look further into this.
Its sure known.
Calamares is making wrong options in fstab of the installed System. It mount's the subvolume read only.
Change that from a live medium and it is working.
Oh right, we even talked about that some time ago. I forgot.
Is there workaround for this?
Sure, boot from Live, mount the partition and just remove the ro entry in the corresponding line of fstab.
thanks. Let me try
Ithink eveything looks fine in my fstab but still same error
UUID=ad1ee115-f3d0-4a52-bb3a-2d785cde1980 / btrfs subvol=/@,defaults,noatime,space_cache,autodefrag 0 0
UUID=f9f45338-3295-4dc5-9165-e20a12a53b48 /tmp btrfs defaults,noatime,space_cache,autodefrag 0 0
UUID=0c05e513-8dd7-41e8-9868-ac2653a2abe3 /opt btrfs defaults,noatime,space_cache,autodefrag 0 0
UUID=4B9A-087C /boot/efi vfat umask=0077 0 2
UUID=f4e6c3ee-fe4e-4119-83fd-742279c72f23 /home btrfs defaults,noatime,space_cache,autodefrag 0 0
You have to change
space_cache
to
space_cache=v2
Then it should work.
Yeah that worked. Thanks!