If you can get past the udev inotify storm there's a quick way to remove the "watch" entries instead of reverting the package:
sudo -i for rule in /lib/udev/rules.d/*; do sed -i 's/watch//g' $rule; done /etc/init.d/udev restart exit I'm attaching a udev_log=debug captured via serial console at boot. This is from a test-bed system configured with: sda1 /boot (ext3) sda2 swap sda3 / (ext3) sda4 LVM vgroup Ubuntu In the LVM is /dev/mapper/Ubuntu-home (ext3) which has an entry in /etc/fstab UUID=a3522871-8fae-4b77-8800-8fad4297987a /home ext3 defaults,errors=remount-ro 0 1 When the system was first created lvm2 wasn't installed (the LVM was created from a live-CD session and I initially forgot to install lvm2 to the target chroot!). The first time the installed system started there was no problem with udev. I installed lvm2 and rebooted it and instantly it hit the event storm. ** Attachment added: "Gzipped boot log with udev_log=debug" http://launchpadlibrarian.net/22975568/boot-log-udev-debug.log.gz ** Attachment removed: "Gzipped boot log with udev_log=debug" http://launchpadlibrarian.net/22975568/boot-log-udev-debug.log.gz -- [jaunty] doesn't boot anymore after udev upgrade 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
