On Mon, 2013-04-29 at 13:57 +0500, Subhashis Roy wrote: > Hi, > > > This panic is expected if the root filesystem could not be mounted. So > > the question is, why did that fail? Is the root device a simple > > partition or logical volume? Is the physical device attached by SATA, > > USB, or other means? > > The root device is a simple partition '/dev/sda2' (the details of it was > already part of the mail as captured by > 'reportbug' when it booted from the kernel on which I flled the bug > report). > The physical volume is attached by SATA.
OK, so this is a very simple case and it's very surprising that it fails. If you reboot back to the old kernel version, does that still work? Can you capture the kernel log from a failed boot? If you add 'break=bottom' to the kernel command line, you should get to a shell in the initramfs. You can then mount a USB flash drive or similar, and copy the boot messages to it, e.g.: (initramfs) ls -l /dev/sda2 # did the SATA drive appear? ls: /dev/sda2: No such file or directory (initramfs) mkdir /mnt (initramfs) mount /dev/sda1 /mnt # removable drive should be sda (initramfs) dmesg > /mnt/dmesg (initramfs) umount /mnt (initramfs) reboot -f Ben. -- Ben Hutchings Knowledge is power. France is bacon.
signature.asc
Description: This is a digitally signed message part
