hmm - my guess is that the initramfs is corrupted (hence the inability to find 'init')
boot a live-cd - chroot into the installation (with all necessary bind-mounts) and run `update-initramfs -k all -u`
boot a live-cd - chroot into the installation (with all necessary bind-mounts) and run `update-initramfs -k all -u`
You can use the PVE installer in debug mode - the second debug shell should have the zfs userspace available and the kernel module is also presentHow can I create a bootable live cd / usb with latest ZFS as this is zfs root boot ??
So I booted in debug modeYou can use the PVE installer in debug mode - the second debug shell should have the zfs userspace available and the kernel module is also present
is this an uefi system? - then you would also need to sync the initramfs etc to the ESPs with pve-efiboot-tool
I hope this helps!
update-initramfs -u
, and state whether you are booting using UEFI or legacy/BIOS boot.Will do that later as I haven't got access to the machine now.you can check the content of initramfs with "lsinitramfs", and extract it with "unmkinitramfs". it might also help if you post the output ofupdate-initramfs -u
, and state whether you are booting using UEFI or legacy/BIOS boot.
update-initramfs -k all -u
and after I run pve-efiboot-tool refresh
it finishes without any errors. After the machine restart, it gives me options to select the kernel but no matter which kernel I choose now I get to the same point of no returnI didyou can check the content of initramfs with "lsinitramfs", and extract it with "unmkinitramfs". it might also help if you post the output ofupdate-initramfs -u
, and state whether you are booting using UEFI or legacy/BIOS boot.
lsinitramfs
and it looks ok, at least "init" is in root folder there, I actuall don't know what I should be looking at ...update-initramfs -u
is as it should be and not reporting any errors, google doesn't say much about this and usual trick ( yours and picked up from web ) do not fix the issue help would be much appreciated.pve-efiboot-tool refresh
and system booted afterwards. When I had live system back again I extracted both working and non working intrd image and made a md5sum diff :root@ent:~/init# diff <(find 1/ -type f -exec md5sum {} + | sort -k 2 | sed 's/ .*\// /') <(find 2/ -type f -exec md5sum {} + | sort -k 2 | sed 's/ .*\// /')
8,11c8,11
< 8ac273081969ac3e66cfc63bf4ef8dee hostid
< e4e636027ef4bf3c9f411931e7dd7ce2 hostname
< 81cf7375ac642c516023cb67b0c5fa3b initiatorname.iscsi
< 2a3551da270b60b53703a0266372291a ld.so.cache
---
> 36b6783f6889514feae6a784b99e6c7e hostid
> a4309b13fb632be8ddea6e9139ef3268 hostname
> 0ecd7fea5d953c554e635055d1d27630 initiatorname.iscsi
> 7d268169569a3257961c8c51d142c1ae ld.so.cache
29a30
> 4d9fdd2bb856a4b4ca90f571b809b535 zpool.cache
361c362
< 37e1fd29ab50948e094a00c405043741 blacklist_pve-kernel-5.3.10-1-pve.conf
---
> 37e1fd29ab50948e094a00c405043741 blacklist_pve-kernel-5.3.18-1-pve.conf
while read u; do mkdir -p "/media/esp/$u"; mount "/dev/disk/by-uuid/$u" "/media/esp/$u"; done < /etc/kernel/pve-efiboot-uuids
/media/esp/$UUID
, and you could then check whether they lack space, contain corrupt/truncated initrds, etc.pp. don't forget to unmount them again once you are done with investigating.then I'd next check if your ESP contents differ from what's in /boot. you can find a list of ESP UUIDs in /etc/kernle/pve-efiboot-uuids. e.g.,
Code:while read u; do mkdir -p "/media/esp/$u"; mount "/dev/disk/by-uuid/$u" "/media/esp/$u"; done < /etc/kernel/pve-efiboot-uuids
will mount each of them in/media/esp/$UUID
, and you could then check whether they lack space, contain corrupt/truncated initrds, etc.pp. don't forget to unmount them again once you are done with investigating.
apt-get remove --purge pve-kernel*=ver*
, system still boots with copied initrd image, after that I tried to install 5.3.18-1-pve from repo and it is still happening, somehow intird image gets corrupted at build ...