[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#354458: Kernel panic after upgrading initramfs-tools



Hi,

2006/3/15, maximilian attems <maks@sternwelten.at>:
> ok so that's the bug you hit, it's closed by 0.55b
> lilo doesn't grog that the initd.img changed without beeing rerun
> grub is much friendlier in those regards.

So I've read.

> yes you need
> a) proc from outside the chroot or maybe it's enough from inside
> mount /proc /chroot/proc -t proc

I mounted it from the inside, which seems to work.

> b) the devices from inside the chroot
> /etc/init.d/udev start

This doesn't work:

# /etc/init.d/udev start
/lib/lsb/init-functions: line 130: /dev/null: Permission denied
udev requires a mounted sysfs, not started.
/lib/lsb/init-functions: line 130: /dev/null: Permission denied
 failed!

so I did:

# mount /sys -t sysfs

AFter that, I get:
# /etc/init.d/udev start



It has been detected that the command

        /etc/init.d/udev

has been run from an interactive shell.
It will probably not do what you expect, so this script will wait
60 seconds before continuing. Press ^C to stop it.
RUNNING THIS COMMAND IS HIGHLY DISCOURAGED!

So, to be sure I'm asking: are you REALLY sure??

> now run lilo

I tried running lilo without the udev stuff, but that clearly didn't work::

 # lilo
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.01.04 (2005-08-02)(compat) and kernel driver
Fatal: open /dev/hda: Permission denied

> if lilo doesn't work out for you use from knoppix (adapt to your device)
> grub-install --root-directory=/mnt/hda1 /dev/hda

I'll first try with lilo if you can confirm that I should indeed run
udev as you said, ignoring the very strong warning.

--
Grtjs,

Manuel
PS: http://manuel.msxnet.org/



Reply to: