Herewitht the bootlog from serial console of the PI (btw this is from Kinetic Kudo e.g. bug is persistent in multiple versions 22.04.1 and 22.10)
To reproduce: 1. Install pristine Ubuntu Server for PI/ARM64 on SD or USB. 2. Install open-iscsi, lvm2, nfs-common 3. Configure iSCSI initiator 4. Attach iSCSI volume from NAS 5. Create LVM on iSCSI volume 6. Reinstall linux-image, linux-modules and linux-modules-extra to generate initramfs 6. Rsync SD card to iSCSI 7. Copy /boot/firmware to TFTPBOOT dir on NAS 8. Alter cmdline.txt for iSCSI boot 9. Reboot PI from iSCSI 9a PI4 gets vmlinuz, cmdline.txt, config.txt and initrd.img from NAS 9b Kernel boots succesfully 9c Init in RAM disk complains about binaries that it cannot find Hope this helps ** Attachment added: "pi4-iscsi-initramfs-boot.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+attachment/5620431/+files/pi4-iscsi-initramfs-boot.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1991324 Title: Initramfs-tools: iSCSI boot resulting in modprobe not found error message Status in initramfs-tools package in Ubuntu: Incomplete Bug description: My RPi4's are having their rootvg on iSCSI and boot from them. The kernel modules etc are in the initramfs. However since 22.04 the initramfs is not generated corrected and while booting from it it results in error messages stating various binaries/scripts are not locatable. E.g. modprobe, systemd-udev, mdadm etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
