I just found out that this might not be a kernel issue at all, and might be a grub2 issue. When booting from GRUB, when I removed the line that said
search --no-floppy --fs-uuid --set f7aea5f9-577b-40b0-ab63-f58240cc94e1 Ubuntu boots up just fine on both the mainline kernel and the updated kernel. When I boot with this line intact, the above error occurs with the updated kernel, and an "Out of partition" error occurs with the mainline kernel. So it seems like the search command is what is screwing around with the kernel on boot. For more details on what might exactly be the problem, I'll attach the grub.cfg file. In this system, the f7aea5f9-577b-40b0-ab63-f58240cc94e1 UUID is the /boot partition on sda2 and 4cff9e74-9091-425f-95e8-dee6b63da0f3 UUID is the root partition on sda3. I hope this issue can be resolved since it doesn't appear like most people have had this kind of problem. For the one in the few people who this might happen too, it might be a doozy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/647128 Title: Maverick Beta Kernel Panic - "VFS: Unable to mount root fs on unknown-block(0,0)" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
