*** This bug is a duplicate of bug 343919 *** https://bugs.launchpad.net/bugs/343919
****WAIT!***** Actually. since the title of this bug better *is* the problem I had I will post the solution here (to get the job done) and also in the ubuntu forums) so more can find it. >From my saved partition and chroot with Hardy 8.04 (you could use a live CD), this is how I fixed my Jaunty 9.04 fresh, beta install; where I could boot again. I look everywhere and tries everything. NONE of th buzybox commands worked for me. I do NOT have raid and their was no UUID or /dev naming error. Only the following worked for me and I still do not know why the newly installed kernal failed to boot after upgrading it. Perhaps it didn't upgrade or something because once I got back in using chroot, I had to run the apt-get fix command it recommends. Unless that was a limit of the chroot, I don't know. This was ugly and I almost gave up. In a terminal (we're using sudo for root here) Where "X" is your correct drive number, like /dev/sda2 for example sudo mount /dev/sdaX /mnt (You can cut and paste the commands below) sudo mount --bind /dev /mnt/dev sudo mount --bind /proc /mnt/proc sudo mount --bind /sys /mnt/sys sudo cp /etc/resolv.conf /mnt/etc/resolv.conf sudo chroot /mnt /bin/bash Then: apt-get install ................................................etc. I believe I did a: apt-get update (then the suggested fix command and...) apt-get upgrade While the kernel didn't appear to be different I not sure that it wasn't a newer fix. It booted. Now, after doing upgrades back in Jaunty again, I'm about to reboot and try the newest kernel (it just installed). I hope this helps you as much as it did me! -- alert! /dev/disk/by-uuid/be80cf42-e6f2-466c-bb73-7d664956a334 does not exist https://bugs.launchpad.net/bugs/315572 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