Hi @dmbaturin
Thanks for the explanation!
I’ve successfully build linux-image package. Now I got following issue when I tried to install it:
dpkg -i linux-image-4.19.134-amd64-vyos_4.19.134-1_amd64.deb
(Reading database … 77268 files and directories currently installed.)
Preparing to unpack linux-image-4.19.134-amd64-vyos_4.19.134-1_amd64.deb …
Unpacking linux-image-4.19.134-amd64-vyos (4.19.134-1) over (4.19.134-1) …
Setting up linux-image-4.19.134-amd64-vyos (4.19.134-1) …
update-initramfs: Generating /boot/initrd.img-4.19.134-amd64-vyos
live-boot: core filesystems devices utils udev wget blockdev.
/usr/sbin/grub-probe: error: failed to get canonical path of `overlay’.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
dpkg: error processing package linux-image-4.19.134-amd64-vyos (–install):
installed linux-image-4.19.134-amd64-vyos package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-4.19.134-amd64-vyos
It looks like there is a problem with /usr/sbin/grub-probe which not recognized overlay filesystem.
What is the “feng shui” with kernel deb package installation?
Is there any wiki describing this procedure?
Hi Dmitry,
thanks a lot for the suggestion.
Looks like that start update-initramfs manually works well:
update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-4.19.134-amd64-vyos
live-boot: core filesystems devices utils udev wget blockdev.
update-initramfs: Generating /boot/initrd.img-4.19.134-amd64-vyos-mlnx
live-boot: core filesystems devices utils udev wget blockdev.
-rw------- 1 root root 26684596 Aug 26 08:54 initrd.img-4.19.134-amd64-vyos
-rw------- 1 root root 26675415 Aug 26 08:55 initrd.img-4.19.134-amd64-vyos-mlnx
Unfortunately, dpkg left unconfigured packages, so there is a little mess in OS:
apt-get -f install
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 34 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-4.19.134-amd64-vyos-mlnx (4.19.134-1) …
update-initramfs: Generating /boot/initrd.img-4.19.134-amd64-vyos-mlnx
live-boot: core filesystems devices utils udev wget blockdev.
/usr/sbin/grub-probe: error: failed to get canonical path of overlay'. run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 dpkg: error processing package linux-image-4.19.134-amd64-vyos-mlnx (--configure): installed linux-image-4.19.134-amd64-vyos-mlnx package post-installation script subprocess returned error exit status 1 Setting up linux-image-4.19.134-amd64-vyos (4.19.134-1) ... update-initramfs: Generating /boot/initrd.img-4.19.134-amd64-vyos live-boot: core filesystems devices utils udev wget blockdev. /usr/sbin/grub-probe: error: failed to get canonical path of overlay’.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
dpkg: error processing package linux-image-4.19.134-amd64-vyos (–configure):
installed linux-image-4.19.134-amd64-vyos package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-4.19.134-amd64-vyos-mlnx
linux-image-4.19.134-amd64-vyos
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
Total disk space freed by localepurge: 0 KiB
E: Sub-process /usr/bin/dpkg returned an error code (1)
Hi Dmitry,
that’s exactly what I did, and the kernel was built without any issues.
The problem is with installation of linux image deb package, because of read only filesystem.