[nmglug] Ubuntu 9.10 Grub2 "fix"

Le Nguyen lenguyen0 at gmail.com
Thu Dec 24 20:38:23 PST 2009


>
> Hi there Anthony,
>

First I wan't sure what you were talking about since I had just installed
Ubuntu 9.10,  Linux 2.6.31-14-generic.
I did have trouble booting since Grub2 doesn't deal with large disks very
well (mine is 500 GB).

I did find steps to work around that boot issue after some googling around.
Today my Ubuntu updated itself to Linux 2.6.31-16, and I got the same Grub2
boot issue.
These are the steps I took in both cases to work around the grub2 boot
problem.
Hopefully the following steps will help.

First, here's what I saw on my monitor right after the Ubuntu install (and
also right after the recent kernel update):
   Error: no such device:  xxxxxxxx-xxxxxxxx-...
   Failed to boot default entry
   Press any key to continue...

If that's what you also see, here's what I did (before you follow the steps
below, make sure you undo whatever you did so you end up with the same
Error: no such device above):

1. Press the reset button, and this time you should be presented with a
choice of Grub boot options.
2. Press the letter '*c*' (without the single quotes) to drop into console
mode
3. Type:  *set  root=(hd0,1) *and press the ENTER key
4. Type: *linux  /vmlinuz  root=/dev/sda1  ro*    and press the ENTER key
5. Type: *initrd  /initrd.img*   and press the ENTER key
6. Type: *boot*    and press the ENTER key
You should be able to log in. Once you log in, select
Application->Accessories->Terminal to bring up a command shell window.

Inside that window:
Enter this command line:   *uname  -a*
It should spit out several lines about your system, and you should be able
to verify that you're using the 2.6.13-16.generic kernel

Enter this command line:  *sudo  chmod   644  /boot/grub/grub.cfg*
This will make file /boot/grub/grub.cfg writeable by root

Enter this command line:  *sudo  gedit  /boot/grub/grub.cfg*
This will open up another edit  window, showing the contents of that file.
The file has different sections, typically a normal one for booting, and
another one for repair. There are 2 per version of the kernel, so you should
see 4 of those sections, two for 2.6.13-14 and two for 2.6.13-16
Locate the section for 2.6.13-16.generic (the normal boot case). Look for a
line which says something like:
*Search  -no--floppy  --fs-uuid  --set . . . .*
Put a pound sign (#) in front of that Search, so the line now looks like
this:
*#Search  -no--floppy  --fs-uuid  --set . . . .*
Do a File->Save, then File->Exit to get out of that edit window.  Go back to
the command shell window.

Enter this command line: *sudo  chmod  444  /boot/grub/grub.cfg*
This will change the file's permissions back to read-only for everyone.

If you did everything right, you should be able to reboot and the latest
version of Ubuntu will come up.
At least that worked for me. Your mileage may vary...
This should get you going until the next update of Ubuntu, or until grub2 is
fixed.
:-)

Merry Christmas, and Happy New Year!!!

Le Nguyen



---------- Forwarded message ----------
> From: a_kaluta <akaluta at taosnet.com>
> To: nmglug at nmglug.org
> Date: Mon, 21 Dec 2009 06:51:52 -0700
> Subject: [nmglug] Grub2
> After fresh Ubuntu 9.10 install,then followed install w/ package update
> which including change from "Linux 2.6.31-14-generic" to "Linux
> 2.6.31-16-generic",thereafter,boot would no get past splash screen.
>
> Limping along with the following mods:
> /etc/default/grub:  grub default changed from=0 to =saved.
> sudo grub-set-default "Linux 2.6.31-14-generic"
>
> Have not located the elegant solution,can anyone lend clarity,
> Thanks,Anthony
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nmglug.org/pipermail/nmglug-nmglug.org/attachments/20091224/2d9dc871/attachment.htm>


More information about the nmglug mailing list