Systemd-boot: some new-beginner's questions

[pebcak]

Got it! I’ll get back right after I have done this. Thank you!

[manuel]

@pebcak

options root=UUID=400a15cd-f695-4984-ad3d-8b8fad9003ef rootflags=subvol=@arch-gnome-root rw

@pebcak

# /dev/nvme0n1p2
UUID=400a15cd-f695-4984-ad3d-8b8fad9003ef	/var/log  	btrfs     	rw,noatime,compress=lzo,ssd,discard=async,space_cache,subvolid=259,subvol=/@arch-gnome-log

Looks suspicious, why root partition has the same UUID as /var/log?

[dalto]

@manuel

why root partition has the same UUID as /var/log?

Because they are both in the same btrfs partition. That is normal.

What isn’t normal is the fact that for some reason @pebcak keeps specifying his mount lines by both subvol and subvolid.

[pebcak]

I’m in! Thanks a lot!
I am beginning to feel at home in a black TTY

@dalto

What isn’t normal is the fact that for some reason @pebcak keeps specifying his mount lines by both subvol and subvolid.

I’m not to blame! genfstab is! It does generate those entries like that. I remove them afterwards since you pointed it out to me once before.

Thank you so much again! Now I can breath until I start messing around with multi-booting.

I just take the moment to enjoy the black of the TTY with the white text saying:

Arch Linux 5.13.13-zen-1-zen (tty1)
arch-gnome login: _

and the blinking _ inviting me to yet new adventures.

[dalto]

Congrats!

As a side note, you might consider switching to zstd for compression as well.

[keybreak]

@dalto

As a side note, you might consider switching to zstd for compression as well.

Yep, i approve!
Very fast.

[pebcak]

Thanks to you and thank you!

Apropos zstd, I will change that too. Just recall reading in btrfs wiki that for most use cases lzo was as good an alternative. I’ll link to that later if you want me to. But if you think zstd is a better option, then I go for that.

[dalto]

@pebcak

Just recall reading in btrfs wiki that for most use cases lzo was as good an alternative.

It used to use lzo but in most cases I think zstd is better. It has only been an option since kernel 4.14.

[pebcak]

Alright! Will change it!
I can’t thank you enough for your support. That means a lot.

[pebcak]

I had this error message just now:

==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-zen'
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-zen'

and looking for the “boot” folder linked to /efi/arch-gnome it was eampty and the link seems to have been broken. Don’t know why it happened. I don’t seem to be able to recreate the link.

[dalto]

@pebcak

I don’t seem to be able to recreate the link.

Why not? Do you get an error?

[pebcak]

I tried to make a link from inside Nemo, opened as root in the /efi directory and it said

But I did it now from the terminal and it worked. I wonder what happened that it just vanished.

[pebcak]

@dalto

If you want to continue with the manual approach, a common work-around is to mount your ESP at /efi, create a subfolder for each distro and then symlink or bind mount that subfolder to /boot.

Since the incident of the the symlink being “mysteriously” broken/vanished yesterday, I think perhaps mount-binding the two directories is a more robust solution. For making a persistent mount-bind, do I need to add something like the following to /etc/fstab?

/efi/arch-gnome /boot none bind 0 0

[dalto]

@pebcak

do I need to add something like the following to /etc/fstab?

Yes. Make sure you test it before you reboot.

• Add the entry to /etc/fstab
• Delete the symlink
• sudo mkdir /boot
• sudo mount /boot

[pebcak]

Worked a treat! Everything came up after a reboot!
Grazie mille!
(just for a linguistic change )