New install with btrfs

I just created an RPI4 installation SSD using the EndeavourOS_Artemis_neo_22_7.iso on my laptop. It didn’t seem any different from the ios from June and when I noticed the release notes about removing the subvolid from fstab, I was surprised that once booted on my RPI4, I still had subvolid’s in my fstab.

Are there some stale images around?

The subvolid removal is done in the script not in the images. It’s not an image issue.
The script was working well last time I tested it.
Can you post your /etc/fstab?

Also if possible copy that file somewhere and run this command on it?

sed -i 's/subvolid=\d*,//g' /etc/fstab

I thought the fix was going to occur as part of the install. Below is the original fstab after install:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>

UUID=7953-E972  /boot  vfat  defaults  0  0
# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /               btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=256,subvol=/@        0 0

# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /home           btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=257,subvol=/@home    0 0

# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /var/log        btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=258,subvol=/@log     0 0

# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /var/cache      btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=259,subvol=/@cache   0 0


Below is the fstab after the sed is run:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>

UUID=7953-E972  /boot  vfat  defaults  0  0
# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /               btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=256,subvol=/@        0 0

# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /home           btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=257,subvol=/@home    0 0

# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /var/log        btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=258,subvol=/@log     0 0

# /dev/sdb2
UUID=374a6f3b-a412-4ce5-91b4-d9c9c7f888da       /var/cache      btrfs           rw,noatime,compress=zstd:4,ssd,space_cache=v2,commit=120,subvolid=259,subvol=/@cache   0 0

So it looks like the sed didn’t work??

Yes the fix occurs in the install script

Is this the script that is run on the ISO too.

well it doesn’t work. I can manually edit but if it’s supposed to be done by the sed, it’s not happening

I will take a look later and see if I can fix it. Must be some regex thing I got wrong

It is probably whatever you are trying to do with \d

Something like this would probably work as long as the subvolid isn’t at the end of the line:

sed 's/subvolid=.*,//g'
2 Likes

This worked, @jfabernathy @Pudge , I will push the change proposed by dalto to github in a few minutes, can you test again?

1 Like

I just now created a new SSD install using the Method #2 from images It still had subvolid’s in the fstab. I’ll test with a boot from ISO on a PC method.

Just did a install booting my laptop from the EOS Artemis-Neo ISO and that install still had the subvolid’s

So I started playing the sed command and got

sed 's/subvolid=.*,//g' /etc/fstab

to work at least I thought I did. It printed to the console correctly , but when I cat’ed fstab, it hadn’t changed. Then I remembered to use the -i option:

sudo sed -i 's/subvolid=.*,//g' /etc/fstab

Yes, my command was just an example to show the syntax. If that ended removing the -i that wasn’t my intention, sorry for the miscommunication.

i thought I fixed that yesterday, let me try an install again.

It still looks the same here:

Did you push your commit?

I forgot I had to do it at two places :man_facepalming:

Edit:
Fix pushed now, sorry for the trouble @jfabernathy

On my test install:

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>

UUID=1036-BE4C  /boot  vfat  defaults  0  0
# /dev/sda2
UUID=b3c64e4e-8571-41b3-a5f3-6473626ad5f3       /               btrfs           rw,noatime,compress=zstd:4,space_cache=v2,commit=120,subvol=/@  0 0

# /dev/sda2
UUID=b3c64e4e-8571-41b3-a5f3-6473626ad5f3       /home           btrfs           rw,noatime,compress=zstd:4,space_cache=v2,commit=120,subvol=/@home    0 0

# /dev/sda2
UUID=b3c64e4e-8571-41b3-a5f3-6473626ad5f3       /var/log        btrfs           rw,noatime,compress=zstd:4,space_cache=v2,commit=120,subvol=/@log     0 0

# /dev/sda2
UUID=b3c64e4e-8571-41b3-a5f3-6473626ad5f3       /var/cache      btrfs           rw,noatime,compress=zstd:4,space_cache=v2,commit=120,subvol=/@cache   0 0

Just built a new SSD using bootable x86_64 ISO and launching ARM installer. The resulting ARM image after installation completed no longer had subvolid’s.

I have not tested Method 2 using currently running EOS system.

1 Like

Is the same thing. Both methods use the same script. The ISO downloads the script