On Mon, 27 Oct 2014 00:54:54 +0000 Ben Hutchings <b...@decadent.org.uk> wrote:
> > 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. > > Please provide the output of 'mount' on one such system. Sorry, I forgot to mention that: # mount | grep 803 803 on / type ext4 (rw,noatime,nodiratime,discard,errors=remount-ro,data=ordered) (this is another system that had the same problem btw) > You are recommended to specify the root device on the kernel command > line using the syntax 'root=UUID=...' I use lilo: boot=/dev/sda root=/dev/sda3 map=/boot/map delay=20 compact prompt timeout=20 default=Linux image=/vmlinuz label=Linux read-only initrd=/initrd.img [..] I tried both, UUID= and /dev/sda3 in /etc/fstab, but the result was the same. I haven't tried lilo.conf yet. I'll let you know. BTW, UUID is great for mounting removable devices, but for fixed devices it may be problem: you cannot simply copy images to a disk without adapting the UUID. E.g.: I run a big number of devices and the disks are copies of a central image. Using UUID would make things more complex than using /dev/sdX in that case. 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-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141027083232.169365c621becc619614d...@xaq.nl