Command: sudo eggs dad -d
Produces on fresh install of penguins-eggs output:
command: dad -d
Daddy, what else did you leave for me?
- creating configuration dir...
Due the lacks of calamares package set force_installer = false
/_active/rootvol/boot/vmlinuz-linux not exists!
contents of boot directory, where vmlinuz-linux is found:
ls /boot
efi grub initramfs-linux-fallback.img initramfs-linux.img intel-ucode.img syslinux vmlinuz-linux
I think the issue is that the parsing for location of vmlinuz-linux doesn't understand the btrfs subvolume setup, where
/dev/sda3 contains _active and _snapshots subvolumes and /_active/rootvol subvolume in /dev/sda3 is mounted to / -directory. Instead it tries to find _active from under the filesystem / -directory, which obviously doesn't exist.
The idea of this setup is that all snapshots of subvolumes are available under /_snapshots in /dev/sda3 and the snapshotted files can then be accessed through /mnt/defvol, where the /dev/sda3 is mounted.
orion% ls /mnt/defvol
_active _snapshots
orion% ls /mnt/defvol/_active
homevol rootvol
orion% ls /mnt/defvol/_active/rootvol
bin boot dev etc home lib lib64 mnt opt proc root run sbin srv sys tmp usr var
I think it should figure out that subvol=/_active/rootvol of /dev/sda3 is mounted to / and be able to remove the /_active/rootvol from the attempted path somehow.
Hi Apocalyt
you're probably right, I'm not too familiar with btrfs, anyway this is the code that retrieve vmlinuz, I hope you can give me some suggestions.
Command:
sudo eggs dad -d
Produces on fresh install of penguins-eggs output:Contents of fstab:
contents of boot directory, where vmlinuz-linux is found:
I think the issue is that the parsing for location of vmlinuz-linux doesn't understand the btrfs subvolume setup, where /dev/sda3 contains _active and _snapshots subvolumes and /_active/rootvol subvolume in /dev/sda3 is mounted to / -directory. Instead it tries to find _active from under the filesystem / -directory, which obviously doesn't exist.
The idea of this setup is that all snapshots of subvolumes are available under /_snapshots in /dev/sda3 and the snapshotted files can then be accessed through /mnt/defvol, where the /dev/sda3 is mounted.
I think it should figure out that subvol=/_active/rootvol of /dev/sda3 is mounted to / and be able to remove the /_active/rootvol from the attempted path somehow.