grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Caseless UUID comparsion in search command


From: Arthur Marsh
Subject: Re: [PATCH] Caseless UUID comparsion in search command
Date: Tue, 07 Jul 2009 13:08:21 +0930
User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701)

Pavel Roskin wrote, on 07/07/09 11:28:
On Tue, 2009-07-07 at 10:41 +0930, Arthur Marsh wrote:

using grub-emu at the moment. I'll try in real grub when I reboot.

Could you please try booting Linux in grub-emu?  You can interrupt qemu
before the kernel tries to mount anything.  Or you can remove the
"linux" line.  What matters is whether the "search" command works.  That
would show if BIOS limitations play any role.

I haven't used grub-emu to boot linux.

In grub-emu I get:

sh:grub> ls -l
Device hd0: Partition table
Partition hd0,7: Filesystem type ext2, Last modification time 2009-07-07
 03:21:45 Tuesday, UUID 96c96a61-8615-4715-86d0-09cb8c62638c
        Partition hd0,6: Filesystem type fat, UUID 7417-5aff
        Partition hd0,5: Unknown filesystem
Partition hd0,1: Filesystem type ext2, Last modification time 2009-07-07
 03:23:54 Tuesday, UUID bfdeb6d6-0b77-4beb-a63d-bdc3e455b8ea

sh:grub> search -l ""
Segmentation fault
victoria:/home/amarsh04#



Partition hd0,1: Filesystem type ext2, Last modification time 2009-07-07
  00:49:27 Tuesday, UUID bfdeb6d6-0b77-4beb-a63d-bdc3e455b8ea

tune2fs -l /dev/hda1 |grep UUID
Filesystem UUID:        bfdeb6d6-0b77-4beb-a63d-bdc3e455b8ea

That means that the search command indeed fails to find a partition that
GRUB sees.

Since you are getting "device not found" with the refactor patch, it
means that grub_device_iterate() doesn't set grub_errno.

If --set is given, the iteration would stop as soon as the matching
device is found.  Unfortunately, grub lists partitions backwards (we'll
need to look at that), so a problem with a later partition could confuse
GRUB.

Please run "ls -l" in GRUB to see if it finds any problems.  Also please
try running the "search" command manually on the command line.  Maybe
the config file has some weird symbol somewhere.  You can also search by
label, even though it's empty:

search -l ""

In real grub:

ls -l

hd0: Partition table
Partition hd0,1: Filesystem cannot be accessed
Device hd1: filesysetm cannot be accessed
Device hd2: filesystem cannot be accessed
Device fd0: Filesystem cannot be accessed
error: no such disk

search -l ""

hd1,5 hd1,3

The /boot partition is on (hd0,1)

Regards,

Arthur Marsh.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]