bug-grub
[Top][All Lists]
Advanced

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

Re: grub-pc jumps straight to rescue and prints error: no such disk / fi


From: Colin Watson
Subject: Re: grub-pc jumps straight to rescue and prints error: no such disk / file not found
Date: Wed, 4 Aug 2010 14:53:22 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Wed, Feb 03, 2010 at 08:50:36PM +0100, Josip Rodin wrote:
> On Sat, Jan 02, 2010 at 03:00:39PM +0100, Josip Rodin wrote:
> > my autogenerated menu entry for the amd64 root partition seemed to have
> > the wrong UUID in the 'search' command. That sounds like a userland issue,
> > because:
> > 
> > % sudo grub-probe -d /dev/sda1 -t fs_uuid
> > 1460509560508002
> > % sudo grub-probe -d /dev/sda2 -t fs_uuid
> > 18515dea-973e-473b-bddf-74d1cb58e15a
> > % sudo grub-probe -d /dev/sda3 -t fs_uuid
> > 7e6cdce7-8136-41f0-8a66-997b89ea00fe
> > 
> > And yet after running the update-grub command on the amd64 machine
> > I still get:
> > 
> > % grep search /boot/grub/grub.cfg | sort -u
> >         search --no-floppy --fs-uuid --set 1460509560508002
> >         search --no-floppy --fs-uuid --set 
> > 7e6cdce7-8136-41f0-8a66-997b89ea00fe
> > 
> > It's supposed to detect the amd64 partition (sda2) at least once :)
> > but it seems to be fixating on the i386 one (sda3).
> 
> This behaviour seems to be a problem with grub-probe and its usage by the
> default config scripts, because the simple most straightforward test fails
> for one of the RAID devices:
> 
> % sudo tune2fs -l /dev/md0 | grep UUID
> Filesystem UUID:          18515dea-973e-473b-bddf-74d1cb58e15a
> % sudo grub-probe --device /dev/md0 --target=fs_uuid
> 7e6cdce7-8136-41f0-8a66-997b89ea00fe
> 
> % sudo tune2fs -l /dev/md2 | grep UUID
> Filesystem UUID:          222e0fc1-800d-4be4-89fa-96a876aca441
> % sudo grub-probe --device /dev/md2 --target=fs_uuid
> 222e0fc1-800d-4be4-89fa-96a876aca441
> 
> What it thinks to be /dev/md0 isn't actually what the rest of the system
> knows to be /dev/md0 (nor is it actually what grub sees as md0 on boot time,
> as it happens).

This all sounds awfully like the problems with array numbering which I
fixed recently.  Are you in a position to re-test with grub-pc
1.98+20100804-1 from unstable?

Thanks,

-- 
Colin Watson                                       address@hidden



reply via email to

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