I have been trying to install eos on my btrfs partition but calamares starts the mounting of the partition, creates the @ subvolume and then fails
inxi -Fxxc0z --no-host | eos-sendlog
journalctl -b -0 | eos-sendlog
This is the popup error message that the installer spits out:
Command '['btrfs', 'subvolume', 'create', '/tmp/calamares-root-fjqwonz2/@']' returned non-zero exit status 1.
File "/usr/lib/calamares/modules/mount/main.py", line 350, in run
mount_partition(root_mount_point, partition, partitions, mount_options, mount_options_list)
File "/usr/lib/calamares/modules/mount/main.py", line 282, in mount_partition
subprocess.check_call(["btrfs", "subvolume", "create",
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
Can you explain what you are trying to do? Are you trying to install into an existing btrfs partition? Are you using manual partioning?
Yes i am using manual partitioning.
The partition scheme i have is as follows:
sda1 fat32 /boot/efi
sda2 btrfs /
So in manual partitioning i set those 3 partitions and then press install. The installer starts moiunting sda2 and creates the root subvolume @ then crashes with the error i posted on the first post.
My guess would be that either you didn’t check the box to format the btrfs partition or you are installing into an existing partition where
@ already exists.
i do not need/want to format the partition, I have other OS’s there.
@archlinux @gentoo @home @snapshots @
@ is the partition that eos installer creates before crashing.
It might be that it fails to create the @home subvolume as it alredy exists.
I will try to rename my current one and see if it still fails.
Will report in a bit
It seems like that was the problem. The installer was failing cause there was alredy a @home subvolume present. I solved it