Hmm thanks!
OK, so I don't have a /dev/root either; what seems to happen (see /usr/share/initramfs-tools/hook-functions) is that it
checks the output of
mount
to see where / is mounted, and it's finding that it says /dev/root - and so that's what it uses /dev/disk/by-uuid to look at via blkid to see where it really goes; if mount is saying /dev/root then mkinitramfs is expecting there to be a /dev/root, and looking at the attched
So, time for some more questions:
* What does cat /proc/cmdline show
* Does this machine have any odd boot process?
* Is there anything else odd you've seen, I see:
[ 4.743386] init: Failed to create pty - disabling logging for job
[ 4.743486] init: Temporary process spawn error: No such file or directory
Hmm thanks! initramfs- tools/hook- functions) is that it
OK, so I don't have a /dev/root either; what seems to happen (see /usr/share/
checks the output of
mount
to see where / is mounted, and it's finding that it says /dev/root - and so that's what it uses /dev/disk/by-uuid to look at via blkid to see where it really goes; if mount is saying /dev/root then mkinitramfs is expecting there to be a /dev/root, and looking at the attched
df
output:
rootfs 36612928 22853144 11924828 66% /
/dev/root 36612928 22853144 11924828 66% /
It's obvious something is a bit weird.
So, time for some more questions:
* What does cat /proc/cmdline show
* Does this machine have any odd boot process?
* Is there anything else odd you've seen, I see:
[ 4.743386] init: Failed to create pty - disabling logging for job
[ 4.743486] init: Temporary process spawn error: No such file or directory
in the logs - that's a bit odd.