Comment 10 for bug 12581

Message-Id: <1107688315l.10508l.0l@tangerine-64>
Date: Sun, 06 Feb 2005 11:11:55 +0000
From: "Jean-Luc Coulon (f5ibh)" <email address hidden>
To: Marco d'Itri <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system
 unbootable

Le 06.02.2005 11:20:38, Marco d'Itri a =E9crit=A0:
> On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden>
> wrote:
>=20
>> I've redone the test, it is always the same. It begin to boot and the
>=20
>> stops displaying anything while there is still some activity. I didnt
>=20
>> manage to reach my box via the network: whine I can ping it, ssh is
> not
>> working.
>>=20
>> The latest displayed message are:
> This is not helping. Please reboot the system with init=3D/bin/bash,
> manually run:
>=20
> /etc/init.d/mountvirtfs start
> /etc/init.d/udev start
>=20
> and check what really happens.

I've to borrow an other keyboard: mine is usb and not initialised yet =20
at this level.

Anyway, I have got some arror message about the node for my root =20
filesystem (which is on lvm)

Anyway, when I've started the system with the new version of udev, I =20
gor the following error:

<<
The device node /dev/mapper/vg00-root_lv for the root filesystem is =20
missing, incorrect or there is no entry for the root filesystem in
/etc/fstab. The system is also unable to create temporary node in =20
/dev/shm to use as a work-around. This means that you have to fix this =20
manually.
>>=20

>=20
>> #BUS=3D"usb", SYSFS{idVendor}=3D"056a", SYSFS{idProduct}=3D"0011",
> NAME=3D"%k",
>> SYMLINK=3D"input/tablet"
>>=20
>> But the way, if I tried to enable this line, it creates first the
> right
>> symlink but it is overwritten later with every device in /dev/inout/
> to
>> finally stay with the latest found.
> I find hard to believe that such a bug is exposed only on your system.
>=20
>> To be able to boot, I've started the system on a live CD and the
>> download the previous debian package fro udev (0.050-6) from
> If udev breaks, you can disable it by disabling the init script.
>=20
> Or else, add to the top of the init script:
>=20
> if [ "$DISABLE_UDEV" =3D "yes" ]; then
> echo "udev disabled by a kernel parameter
> exit 0
> fi

Ok done, this save me from using a live cd to recover.

>=20
> and you will be able to disable it by adding DISABLE_UDEV=3Dyes to the
> kernel command line.
>=20
> --
> ciao,
> Marco
>=20

Jean-Luc