gpg: Signature made Sun Feb 14 02:51:39 2010 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 Stuart,
On Sat, Feb 13, 2010 at 05:16:54PM +0000, Stuart Swindells wrote:
> I managed to get 2.6.32-trunk-686-bigmem to install by remove /dev/xvda*
> and manually inserting the right lines in /boot/grub/menu.lst
> (grub-update didn't seem to pick up on the new kernel and automatically
> update menu.lst).
Hmm, I think this did work for me.
> It boots fine, but /dev/xvda1 and /dev/xvda2 reappear.
> If I then try to remove linux-image-2.6.26-1-xen-686, apt chucks:
>
> Removing linux-image-2.6.26-1-xen-686 ...
> Searching for GRUB installation directory ... found: /boot/grub
> warning: grub-probe can't find drive for /dev/xvda1.
> grub-probe: error: Cannot find a GRUB drive for /dev/xvda1. Check your
> device.map.
You can probably hack around it by removing the postrm scripts for
that package in /var/lib/dpkg/info/linux-image-2.6.26-1-xen-686.*
If you want I am happy to set up your VPS again using /dev/xvda as a
block device directly which will avoid all this. Will require up to
about 30 mins of downtime.
Another thing we could do is, I could give you a /dev/xvdb and you
put /boot on it, that would probably be enough to make the package
scripts happy.
I can also try to set up a squeeze test vps with the old disk
layout that you've got and see if I can find a workaround, but this
may take some time.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"I'd be happy to buy all variations of sex to ensure I got what I wanted."
-- Gary Coates (talking about cabling)
