** Description changed:
+ SYMPTOMS
+
+ Early in the boot process (during initial ram-disk script processing)
+ the PC appears to stop although there may be a lot of repeated disk
+ activity, possibly accompanied by messages to screen of the form:
+
+ UEVENT[1235217664.944992] change
+ /devices/pci0000:00/0000:00:09.0/host0/target0:0:0/0:0:0:0/block/sda
+ (block)
+
+ This happens after an automatic package upgrade to udev to 138-1.
+
+ RECOVERY PROCEDURE
+
+ If the PC is unable to complete start-up, effectively locking you out,
+ this is how to regain control and install a work-around until a solution
+ is available.
+
+ 1. When the PC starts enter the GRUB menu.
+ 2. Select the Recovery entry and edit it (press "e") - this starts in
single-user mode with minimal services.
+ 3. Select the "kernel" line and edit it (press "e")
+ 4. Add " break=top" to the end of the line and press Enter.
+ 5. With the "kernel" line highlighted press "b" to boot using the edited
entry.
+
+ The boot process will stop when the initial ram-disk scripts begin and
+ you'll be faced with a busybox shell.
+
+ Edit the rules that contain the problematic "watch" and remove it:
+
+ for rule in /lib/udev/rules.d/*; do sed -i -e '/watch/s/watch//' $rule;
+ done
+
+ Modify the init script so the boot can continue:
+
+ sed -i -e '/run-init/s,${init},/bin/bash,' /init
+
+ Restart the boot process by pressing Ctrl+D
+
+ The system *should* now boot to a root prompt although there may still
+ be a delay. Once there, edit the non-initrd system rules:
+
+ for rule in /lib/udev/rules.d/*; do sed -i -e '/watch/s/watch//' $rule;
+ done
+
+ And rebuild the initial ram-disk image so you don't have to go through
+ this procedure at every boot:
+
+ To update just the kernel version that is currently running:
+
+ update-initramfs -u -k `uname -r`
+
+ or to update for all installed kernels:
+
+ update-initramfs -u -k all
+
+ Now restart the PC and hopefully the regular multiuser start-up should
+ go normally.
+
+ -- TJ
+
+ -----------------------------
Since todays upgrade of udev jaunty is not able to boot anymore
affects also recovery mode, of course.
I can see messages like
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda
(9367)
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda/sda2
(9366)
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda/sda2
(9365)
the messages appear in blocks of quite many, always repeating after 5
minutes or so and the number is counting up.
Harddisk LED is flashing rapidly but no hearable access to the hard disk
I think it has something to do with udev as this is in the last upgrade log
2009-02-20 20:59:24 upgrade libvolume-id1 137-2 138-1
2009-02-20 20:59:24 status unpacked libvolume-id1 138-1
2009-02-20 20:59:24 status unpacked libvolume-id1 138-1
2009-02-20 20:59:25 configure libvolume-id1 138-1 138-1
2009-02-20 20:59:25 status unpacked libvolume-id1 138-1
2009-02-20 20:59:25 status half-configured libvolume-id1 138-1
2009-02-20 20:59:25 status installed libvolume-id1 138-1
2009-02-20 20:59:26 upgrade udev 137-2 138-1
2009-02-20 20:59:27 status unpacked udev 138-1
2009-02-20 20:59:27 status unpacked udev 138-1
2009-02-20 20:59:34 upgrade libudev0 137-2 138-1
2009-02-20 20:59:34 status unpacked libudev0 138-1
2009-02-20 20:59:34 status unpacked libudev0 138-1
2009-02-20 20:59:41 configure udev 138-1 138-1
2009-02-20 20:59:41 status unpacked udev 138-1
2009-02-20 20:59:41 status unpacked udev 138-1
2009-02-20 20:59:41 status unpacked udev 138-1
2009-02-20 20:59:41 status unpacked udev 138-1
2009-02-20 20:59:41 status unpacked udev 138-1
2009-02-20 20:59:41 status unpacked udev 138-1
2009-02-20 20:59:41 status half-configured udev 138-1
2009-02-20 20:59:41 status installed udev 138-1
2009-02-20 20:59:47 configure libudev0 138-1 138-1
2009-02-20 20:59:47 status unpacked libudev0 138-1
2009-02-20 20:59:47 status half-configured libudev0 138-1
2009-02-20 20:59:47 status installed libudev0 138-1
--
udev repeatedly generates "change" events for the same block device(s)
https://bugs.launchpad.net/bugs/332270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
