Bug#479056: grub: destroys /boot/grub/device.map

[Aurelien Jarno]

On Sat, May 03, 2008 at 03:52:26PM +0200, Robert Millan wrote:
> On Sat, May 03, 2008 at 12:37:28AM +0200, Aurelien Jarno wrote:
> > >   - grub-mkdevicemap doesn't grok virtio devices.  Could you confirm the
> > >     attached quick & dirty patch makes it work?  Also, is this device path
> > >     Linux-specific?
> > 
> > Yes that make it working. Currently virtio is only supported on Linux,
> > so the device patch is Linux-specific. But that may change in the future
> 
> Thanks.  That's enough for me to add it to grub-mkdevicemap.
> 
> > > > Searching for GRUB installation directory ... found: /boot/grub
> > > > grub-probe: error: Cannot find a GRUB drive for /dev/vda1.  Check your device.map.
> > > > 
> > > > Here is the contents of /boot/grub/device.map before it is destroyed:
> > > > (fd0)   /dev/fd0
> > > > (hd0)   /dev/vda
> > [...]
> > # grub-probe -t drive -d /dev/vda -v
> > [...]
> > (hd0)
> 
> Now what troubles me here is that grub-probe is working now, but my patch
> wasn't supposed to fix anything in it.  This seems to be inconsistent with
> your previous report.
> 
> Are you completely sure that with your /boot/grub/device.map being:
> 
> (fd0)   /dev/fd0
> (hd0)   /dev/vda
> 
> and grub-common being the pristine version, grub-probe failed and (in
> consequence) regenerated your device.map?
> 

I am sure about that. The only difference is that /usr/sbin/update-grub
does not uses the same command, but this one instead:

grub-probe --device-map=/boot/grub/device.map -t drive -d /dev/vda1

And this command:
1) fails
2) destroys /boot/grub/device.map

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32 at debian.org         | aurelien at aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net