> Loading, please wait... > /scripts/init-top/udev: line 24: /lib/systemd/systemd-udevd: not found > Begin: Loading essential drivers ... /init: line 150: modprobe: not found > /init: line 150: modprobe: not found
So basically, none of the binaries are in the initramfs, or else they're in the initramfs but not on the PATH. How was this initramfs generated? Please attach to this bug report. ** Summary changed: - Initramfs-tools: iSCSI boot resulting in modprobe not found error message + Initramfs-tools: iSCSI boot resulting in error message about not finding executables -- 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 error message about not finding executables 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
