Okay thanks. One possibility is that the new kernels are not
recognizing your regular hard drives. It would be most useful if we can
get some information from the newer kernels when they fail to boot, such
as the output of 'dmesg'. To do that may require some playing around at
the (initramfs): since you have no network at that point, the best
option may be to see if we can mount a USB key (or external USB drive)
and store the output of dmesg and some other commands on that. Are you
comfortable enough with Unix shells to do so? The rough steps would be:
* At the prompt, attach a USB key/drive.
* Run dmesg to see what new device was recognized... should be something like
sda or sdb, such as:
[ 8072.023195] sdb: sdb1
* In this case, sdb1 is the new attached device. Mount that new device:
mkdir /mnt
mount /dev/sdb1 /mnt
* Then try running:
ls -l /dev > /mnt/dev.txt
dmesg > /mnt/dmesg.txt
cat /proc/modules > /mnt/modules.txt
umount /mnt
After that you should be able to reboot into your working kernel and re-
attach the key/disk and attach the 3 files (dev.txt, dmesg.txt,
modules.txt) to this bug.
--
Update from 2.6.24-12 to -14 or -15 results in changed uuid for root partition
https://bugs.launchpad.net/bugs/213308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
