1 Jun
2011
1 Jun
'11
10:28 p.m.
Hi Mathew,
On Wed, Jun 01, 2011 at 11:14:53PM +0100, Mathew Newton wrote:
Thanks Andy, and you others, for the comments.
By the time you have the squeeze version of update-grub though, none
of those workarounds will work. You absolutely have to have either a
filesystem directly on /dev/xvda, or a partitioned disk at
/dev/xvda. I haven't yet looked to see if this is the case for you.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
One thing I would say is that you probably want
to make sure that
your block devices are just xvda, xvdb, etc. instead of xvda1,
xvda2, etc. Otherwise you will run into difficulties doing
"update-grub" after installing squeeze's kernel.
I've just discovered an old post of yours
(http://lists.bitfolk.com/lurker/message/20080529.142153.954fedf4.el.html)
which is presumably what this issue is about. I've checked my
/boot/grub/device.map and it confirms xvda (and kopt in
/boot/grub/menu.lst uses a UUID).