6 Feb
2011
6 Feb
'11
10:53 p.m.
Hi Joseph,
On Sun, Feb 06, 2011 at 04:28:18PM +0000, Joseph Heenan wrote:
I've not found a solution for this yet, but
running
strace -- grub-probe -vvvv --device-map=/boot/grub/device.map -t device /
2>&1 | less
and browsing the output I noticed this line, which I presume is the issue:
open("/dev/xvda", O_RDONLY|O_LARGEFILE) = -1 ENXIO (No such device or
address)
I presume the older version of grub-probe was less fussy.
I think you could temporarily resolve it by also creating a device
node for /dev/xvda that looks like this:
rw-rw---- 1 root disk 202, 0 2010-06-18 17:24 /dev/xvda
We can permanently resolve it by changing your block device to be
xvda instead of xvda1. Actually as previously discussed the new
BitFolk standard layout is a partitioned xvda, but that will be a
bit of work.
Changing your block device name is just a matter of us
editing your config file then you shut down and boot again. Your VPS
comes up with / on xvda instead of xvda1 and it all still works as
long as you're booting and mounting by label or UUID instead of
device name.
If you want to go this way then it's probably best that we pick a
time to do it when we are both around so that any problems can be
rectified. So once you've checked that your VPS is going to boot and
mount its root filesystem by label or UUID, please put in a support
ticket and we'll sort it out.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting