On Mon, 27 Oct 2014 00:54:54 +0000 Ben Hutchings <b...@decadent.org.uk> wrote:
> > Processing triggers for initramfs-tools (0.116) ... > > update-initramfs: Generating /boot/initrd.img-3.16-3-amd64 > > /803: No such file or directory > > [update continues] > > > > After a reboot, the system is unbootable due to a missing rootfs. > [...] > > We support hexadecimal device numbers in the 'root=' kernel parameter > when booting, but do not expect to see them at build time in the mount > table. [..] > You are recommended to specify the root device on the kernel command > line using the syntax 'root=UUID=...' Setting fstab to UUID does not make any difference, OTOH, setting lilo.conf to root="UUID=xxxxx" resolves the problem. The command "mount" does not show up with "803" anymore. As an initramfs nitwit, I'd say it seems to be a bug anyway. Am I right or wrong? R. -- ___________________________________________________________________ It is better to remain silent and be thought a fool, than to speak aloud and remove all doubt. +------------------------------------------------------------------+ | Richard Lucassen, Utrecht | +------------------------------------------------------------------+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
