7 Feb
2011
7 Feb
'11
10:29 a.m.
Hello,
On Mon, Feb 07, 2011 at 09:24:55AM +0000, Joseph Heenan wrote:
No I think that covers it.
On 06/02/2011 22:53, Andy Smith wrote:
Oh so it is. Hmm, how annoying. This is the sort of thing that made
me change the layout again..
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
I've already tried
that - I think correctly, hence the above error is
ENXIO rather than ENOENT. 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.
Okay, that sounds like the way to go, thanks.
I think I'm okay on the label/uuid front - fstab looks like this:
LABEL=/ / ext3 defaults,noatime 0 1
LABEL=SWAP swap swap defaults 0 0
and the kopt line in /boot/grub/menu.list like so:
# kopt=root=UUID=e031dfea-0cda-43eb-a9d6-912fed215b99 ro console=hvc0
Are there any other places I need to check before raising a support ticket? (I presume my current system will reboot okay, as long
as the kernel
entry in menu.lst is correct?)
Yes, should do.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting