13 Feb
2010
13 Feb
'10
5:16 p.m.
On 04/02/2010 13:24, Stuart Swindells wrote:
On Thu, 4 Feb 2010 05:31:04 +0000, Andy
Smith<andy(a)bitfolk.com> wrote:
That's the post I found before:
sswindells@ra:/dev$ ls -l xvda
brw-rw---- 1 root disk 202, 0 2010-01-31 14:47 xvda
If it helps any, if I run grub-probe /dev/xvda as root:
error: cannot open `/dev/xvda' while attempting to get disk size.
grub-probe: error: cannot find a device for /dev/xvda (is /dev mounted?).
Stuart
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
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). 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.
Hi Stuart,
On Wed, Feb 03, 2010 at 05:45:47PM +0000, Stuart Swindells wrote:
> 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.
Googling, I found the previous post about changing device.map, but it
seems to be set to what it should be:
(hd0) /dev/xvda
Something I'm missing?
http://lists.bitfolk.com/lurker/message/20080529.142153.954fedf4.el.html
Try creating /dev/xvda with mknod.
More recent setups just use /dev/xvda, xvdb, etc. directly and avoid
this.
Cheers,
Andy