gpg: Signature made Thu May 29 14:21:53 2008 UTC using DSA key ID BF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>"
gpg: aka "Andrew James Smith <andy@strugglers.net>"
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>"
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>"
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>"
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>"
Hi,
A recent update to the grub package in Debian Lenny (and perhaps
others) has introduced a call to grub-probe to find out the device
that /boot is on.
With the way the lenny image is set up, this will fail like this
when doing something that calls update-grub (like installing a
kernel):
Searching for GRUB installation directory ... found: /boot/grub
grub-probe: error: Cannot find a GRUB drive for /dev/xvda1. Check your device.map.
dpkg: error processing linux-image-2.6.24-1-xen-686:
subprocess post-install script returned error exit status 1
Errors were encountered while processing:
linux-image-2.6.24-1-xen-686
You will find yourself unable to completely install or remove a
kernel.
I have found that creating the /dev/xvda device node and telling
grub that (hd0) is xvda makes this go away. To do that, you'd do
something like:
sudo sh -c "echo '(hd0) /dev/xvda' > /boot/grub/device.map && cd /dev && mknod xvda b 202 0"
Debian(-like) images installed after today will be set up like this
from the start.
Please note that I haven't yet had chance to try out
linux-image-2.6.24-1-xen-686 or any of the other new kernels you may
be offered by your distribution. :)
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Encrypted mail welcome - keyid 0x604DE5DB
