grub-pc in gpt drive does not boot other drives

Bug #604743 reported by oldfred
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Fix Released
Medium
Unassigned
Lucid
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: grub2

grub-pc installed on gpt drive sdb boots Ubuntu install on sdb but will not boot windows in sda or other Ubuntu installs in sdc.
Since I was booting directly from sdb I tried changing drive numbers 0,1, & 2 in set root with same results.

Windows boot error:
error: no such device 046.... (correct UUID for win on sda1 NTFS)
error: invalid signature

Ubuntu boot error for install on sdc5
error: not such device 1174... (corrrect UUID for Ubuntu on sdc5)
error: you need to load the kernel first

Same as above for sdc7 with correct UUID for sdc7 shown.

fred@fred-DTgpt:~$ apt-cache policy grub-pc
grub-pc:
  Installed: 1.98-1ubuntu6
  Candidate: 1.98-1ubuntu6
  Version table:
 *** 1.98-1ubuntu6 0
        500 http://ubuntu.mirrors.tds.net/pub/ubuntu/ lucid-updates/main Packages
        100 /var/lib/dpkg/status
     1.98-1ubuntu5 0
        500 http://ubuntu.mirrors.tds.net/pub/ubuntu/ lucid/main Packages

fred@fred-DTgpt:~$ uname -a
Linux fred-DTgpt 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux
fred@fred-DTgpt:~$ lsb_release -d
Description: Ubuntu 10.04 LTS

fred@fred-DTgpt:~$ sudo grub-install /dev/sdb
Installation finished. No error reported.
fred@fred-DTgpt:~$ sudo update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.32-23-generic
Found initrd image: /boot/initrd.img-2.6.32-23-generic
Found linux image: /boot/vmlinuz-2.6.32-22-generic
Found initrd image: /boot/initrd.img-2.6.32-22-generic
Found linux image: /boot/vmlinuz-2.6.32-21-generic
Found initrd image: /boot/initrd.img-2.6.32-21-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Microsoft Windows XP Professional on /dev/sda1
Found Ubuntu 9.10 (9.10) on /dev/sdc5
Found Ubuntu 10.04 LTS (10.04) on /dev/sdc7
done

I was helping this user and he had the same issue. He converted drive to MBR and reinstalled.
http://ubuntuforums.org/showthread.php?t=1528910

Revision history for this message
Colin Watson (cjwatson) wrote : Re: [Bug 604743] [NEW] grub-pc in gpt drive does not boot other drives

I think this is a bug that was fixed upstream a couple of months ago,
and is now fixed in maverick. Could you try pressing 'c' to get the
GRUB command line, type 'insmod part_msdos', then press Escape and
select one of the menu entries that previously failed? If that works,
we can make it more permanent, but this test will do for now.

Revision history for this message
oldfred (oldfred) wrote : Fix Worked insmod part_msdos

I use c and at grub> prompt insmod part_msdos.

Both windows and Ubuntu then booted ok (a little slow it seemed in
switching to Ubuntu, windows is always slow so I could not tell any
difference.)

Glad you already had a fix. How would I have found this. I occasionally
review grub errors and other documentation.

Thanks,

Fred

Revision history for this message
Colin Watson (cjwatson) wrote :

Great, thanks for testing this. It would have been pretty difficult to find out for yourself without being quite familiar with GRUB development; filing a bug was the right thing to do.

To make this permanent, the simplest option for now is probably to edit /etc/grub.d/40_custom and add 'insmod part_msdos' at the very end of that file, after the comments.

Changed in grub2 (Ubuntu):
status: New → Fix Released
Changed in grub2 (Ubuntu Lucid):
status: New → Triaged
importance: Undecided → Medium
Changed in grub2 (Ubuntu):
importance: Undecided → Medium
Revision history for this message
oldfred (oldfred) wrote : Added to 40_custom & works

>
> To make this permanent, the simplest option for now is probably to edit
> /etc/grub.d/40_custom and add 'insmod part_msdos' at the very end of
> that file, after the comments.
>
I added insmod part_msdos to 40_custom & both windows on sda1 and Ubuntu
on sdc5 booted without any issues.

Thanks

Fred

Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in grub2 (Ubuntu Lucid):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.