OK, I had a quick look into this. I'm afraid at this stage I'm a little out of my depth, so the following is just a flailing noob's thoughts.
We do know that the script in question is udev, but it's the one in /usr/share/initramfs-tools/scripts/init-bottom, judging from the output. I don't know why it's being invoked, because the S10udev in /etc/rcS/ will get rid of anything that initramfs builds anyway:
Code: Select all
if mountpoint -q /dev; then
# uh-oh, initramfs made some kind of /dev, get rid of it
umount -l /dev
So my initial suggestion would be to head into /usr/share/initramfs-tools/scripts/init-bottom and bin udev, by which I mean carefully move it to a backup folder.
Will it work? Who knows.
[EDIT:] Wait, I just looked at the photos again and spotted "Done." just underneath the init-bottom call. Which suggests that initramfs's udev isn't breaking, but I still stand by my initial suggestion since it might be breaking S10udev for reasons I don't even begin to start understanding.
At least we know roughly where we are in the boot process when it fails. The only other suggestions I've ever heard of in cases like these include passing -noapic and/or -noacpi to the kernel, messing with BIOS settings, up to and including the rather drastic removal of video cards. It's worth noting that the script which runs just before S10udev is S07linux-restricted-modules-common, which might be connected with a buggy BIOS/graphics card interaction.