Hi Stanley, I think that you had another problem. There have been cases of grub-install not finding /boot when it is on a separate partition. This was fixed recently thoug, so pulling in the latest and greatest of grub2 and associated should solve that.
In my case grub does install right, but fails to load the kernel in memory (confirmed again yesterday after getting all upgrades but the kernel which is being held back). cheers Tom Stanley Ames wrote: > Had a similar problem with Ubuntu 9.10 Server. After clean install from > disk, the system failed to boot. Went back to disk and used Recovery > Mode to check around. Found that the /boot directory was completely > empty. No grub, no nothing. Searched around for a bit and found a work > around that did the trick to get me back up and booted again. > > mount -a > update-grub > grub-install /dev/sda #just installed to my master boot record > > Re-booted the system and things ran as normal with everything loading. > > Note that I run the Ubuntu server with a minimal Gnome gui installed as > a desktop system and NOT as an actual server. I like how snappy it > feels. I've only got some other basic packages put on--no bells and > whistles, just basic programming stuff and the stuff from Willow Garage: > ros.org. I'm not sure if this makes any difference but I thought I would > add it. > > I still don't what caused this but it is nice to have a work-around. > > Stan > > ** Attachment added: "system.info" > http://launchpadlibrarian.net/38848136/system.info > > -- fails to boot after clean install; memory allocation problem (older Compaq server) https://bugs.launchpad.net/bugs/513528 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
