kernel does not recognize my hard drive after upgrade to linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb

I have problems with 2.6.22-14.47 to and my pc don't boot now.

I don't have the SIS5513 so this is a more common problem.

It turned out, in my case, that grub toyed around with root=... parameter in /boot/grub/menu.lst

I have the root filesystem on /dev/md3, this is noted in /etc/fstab and used to be noted in /boot/grub/menu.lst

However, after that upgrade, now everywhere 'root=/dev/md2', no idea why.

I edit menu.lst by hand and it boots fine.

If I install a new kernel (for instance -server, just to test) all /dev/md3 turn into /dev/md2 again.

Funny thing is, I never got an error form the kernel as to unable to mount root filesystem or such. Not an error at all. It just seemed to stop at either the cd-rom driver, the usb driver or some other driver. Which is probably just an issue of timing ?

Anyway, please check your /boot/grub/menu.lst (you can use a 7.10 alternate cd in rescue mode, or you can check this by pressing 'esc' during boot and then choose your kernel and then press 'e' for edit and check if root=... is correct.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Ace - Could you please attach your '/boot/grub/menu.lst' to the bug report? Thanks in advance.

I solved this problem by changing

# kopt=root=/dev/md2 ro

to

# kopt=root=/dev/md3 ro

But how an upgrade ever changed that option, is way beyond me.

For completeness, attached my menu.lst, but I think you already know where to look now.

The problem is still there after updating to linux-image-2.6.22-14-386_2.6.22-14.52_i386.deb.

P.S. The problem reported by Ace Suares is not the same as mine and should had been placed as a separate bug.

dima - When in the initramfs prompt please execute 'cat /proc/cmdline' and add the full results of that command to your bug report. I suspect that your system is trying to use the wrong UUID for root. You could temporarily resolve this by modifiying your boot options to 'root=/dev/sda2' where sda2 is the root partition for your Ubuntu install. Then you should update '/boot/grub/menu.lst' with the correct UUID for the root partition. You can learn a bit more about this at https://wiki.ubuntu.com/UsingUUID .

cat /proc/cmdline says
root=UUID=09e11862-4afc-47e0-a715-585b8c29236e ro
I've also tried root=/dev/sda2, but I've got an error
ALERT! /dev/sda2 does not exist. Dropping to a shell.

I neither have any sda nor hda devices in my /dev/ directory.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!