31 Jan
2010
31 Jan
'10
2:23 p.m.
Hi,
If you're running Debian testing (squeeze) then you may have noticed
complaints from the install scripts of udev saying that your kernel
still has CONFIG_DEPRECATED_SYSFS enabled and you need to turn it
off before upgrading udev.
Don't force udev to be upgraded if this happens to you. It *will*
result in an unbootable system.
You can instead switch to the upstream kernel package which now has
support for running under Xen. The package you want is
linux-image-2.6.32-trunk-686-bigmem.
Before booting though, check some other things. Firstly, be sure
that you haven't upgraded to grub 2 (the current version of the
grub-pc package in testing is grub 2). The config format is not yet
supported by pygrub which BitFolk uses, so you would end up getting
the old kernel list from your /boot/grub/menu.lst. Instead make
sure you have grub-legacy for now. Run "update-grub" to see which
kernels it finds.
Next, the upstream kernels don't need the clocksource=jiffies kernel
command line any more either. In fact it can make things break. So
check in your menu.lst that that isn't there. Do an update-grub if
you changed anything.
After booting into 2.6.32-trunk-686-bigmem you can safely upgrade
udev.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
3 Feb
3 Feb
5:45 p.m.
On 31/01/10 14:23, Andy Smith wrote: Instead make
sure you have grub-legacy for now. Run
"update-grub" to see which
kernels it finds.
When I do that, I get:
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?
4 Feb
4 Feb
5:31 a.m.
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
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"It is I, Simon Quinlank. The chief conductor on the bus that is called
hobby." -- Simon Quinlank
1:24 p.m.
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
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
13 Feb
13 Feb
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
14 Feb
14 Feb
2:51 a.m.
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)
2:56 a.m.
On Sun, Feb 14, 2010 at 02:51:39AM +0000, Andy Smith wrote:
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.
Actually thinking about it more, it's probably far easier to just
alter the config so that xvda1 becomes xvda and xvda2 becomes xvdb.
That will need me to fix up your grub config, maybe fstab too, but
that's only going to take a few minutes of downtime.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"Whoever is responsible for this stunning design failure deserves continuous
cockpunches." -- jwz
10:39 a.m.
On 14/02/10 02:56, Andy Smith wrote:
On Sun, Feb 14, 2010 at 02:51:39AM +0000, Andy Smith
wrote:
Sounds good to me.
Thanks,
Stuart
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.
Actually thinking about it more, it's probably far
easier to just
alter the config so that xvda1 becomes xvda and xvda2 becomes xvdb.
That will need me to fix up your grub config, maybe fstab too, but
that's only going to take a few minutes of downtime.
Cheers,
Andy
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
5424
days inactive
5438
days old
7 comments
2 participants
participants (2)
-
Andy Smith -
Stuart Swindells