My setup:
Dual core X2, 2gb ram, sata hard disk (sdaX), etc.
A windows vista partition (came with laptop -rarely- used... 'when I have to')
A normal boot partition
An LVM partition
crypttab
rootvolume /dev/ubuntu/encryptedroot none luks,retry=1
homevolume /dev/ubuntu/encryptedhome none
The TJ fix did NOT fix anything for me. Same symptoms as most here:
Appears not to boot (within a reasonable time-frame) with 2.6.28-8,
spewing out dozens of messages of the form:
/sys/devices/pci:00/:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda/sda2
(9365)
to the console every five
jh, can you get in or chroot and run:
sudo dpkg -l udev
You should see this:
ii udev 138-2~tj~ppa2j
rule-based device node and kernel event manager
If you do, please run this: (I use -c since -u has broken the cryptsetup
I am seeing the same issue.
My setup is:
sda1: windows
sda2: ubuntu root FS
sda3: empty space for other OSes
sda4: EXTENDED
sda5-9: LVM PVs
/var, /var/cache, /usr, /home and swap are all on LVs.
Commenting out the watch-line in udev rules (as suggested in a
Scott, agreed on need to find root cause for this on, particularly as
workaround packages does not help me at all. ;-)
I have the same issue with up-to-date Kubuntu/Jaunty on HP n8440 laptop
running everything on LVM.
I have small /boot (/dev/sda1), the rest of the disk is LVM pvol (/dev/sda2).
Interesting, I don't remember if I tried commenting it out with the
first spin of the PPA package or the 138-1 version of the package.
Does installing the PPA version of the package fix it?
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You received
I am also seeing this on my laptop (Thinkpad X60). The system runs on an
encrypted filesystem.
** Attachment added: dpkg-l.txt
http://launchpadlibrarian.net/22971695/dpkg-l.txt
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You received this bug
** Attachment added: ls-sys-block.txt
http://launchpadlibrarian.net/22971700/ls-sys-block.txt
--
[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.
** Attachment added: lvm-pvs.txt
http://launchpadlibrarian.net/22971704/lvm-pvs.txt
--
[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.
--
** Attachment added: lvm-vgs.txt
http://launchpadlibrarian.net/22971716/lvm-vgs.txt
--
[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.
--
If you've -only- commented it out like in my prior post:
https://bugs.edge.launchpad.net/ubuntu/+source/udev/+bug/332270/comments/16
You -ALSO- need to update the initrd. The stale initrd will still have the bad
rulesets in it.
sudo update-initramfs -c -k all
gunzip -dc
More information to my earlier comment
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/332270/comments/32
I am using neither encrypted partitions nor a raid setup.
Attached you will find the requested info (in one tar ball).
** Attachment added: requested system information
MichaelEvans: Sorry, forgot to do that. After doing the initrmafs update
the -7 and -8 kernels boot again, too.
--
[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
Downgraded to 138-1
Copied auto-gen initrd to a temporary one and setup a grub line to boot
that.
Edited /lib/udev/rules.d/60-persistent-storage.rules to remove the
'watch' lines.
regenerated initrds (which then become the defaults).
Results:
ppa-2 == Boots (already inside it before I started
Is anyone that does -not- use LVM or RAID or other device-mapper items
effected?
(I believe the effect for this is that the device-mapper devices have
different names/patterns that are user selectable, and that other
devices are black-listed from the watch some other way, instead of
white-listing
Here are some probable blacklist lines.
# skip rules for inappropriate block devices
KERNEL==ram*|fd*|nbd*|gnbd*|dm-*|md*|btibm*, GOTO=persistent_storage_end
# never access non-cdrom removable ide devices, the drivers are causing event
loops on open()
KERNEL==hd*[!0-9], ATTR{removable}==1,
@MichaelEvans
# aptitude show udev
Package: udev
State: installed
Automatically installed: no
Version: 138-2~tj~ppa2j
Checked that a new initrd was generated as well.
Still broken as reported.
-jh
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You
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
** Attachment added: Gzipped boot log with udev_log=debug
http://launchpadlibrarian.net/22975815/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,
I'm seeing a bunch of lines like
/sys/devices/virtual/block/dm-0 ($NR)
appearing, where $NR has been 350 - I've left it running over night. When
I came back, a busybox prompt was running and a message like failed while
waiting for root device.
I have a RAID+cryptsetup+LVM setup.
**
I can get past the event storm. After 3 - 4 hours of waiting. But then
kernel panic: out of memmory. Can I boot my system without reinstalling?
I have everything on LVM2. And have installed a system a week ago and do
not have a different kernel to switch to :(
--
[jaunty] doesn't boot anymore
Attached are the requested info files.
Tweaking 60-persistent-storage.rules I found the disk activity only
occurs when a watch is added on a partition used for LVM.
Attached are the modified rules and the resulting watches
in /dev/.udev/watch.
** Attachment added: dpkgl.txt
Scott, I think it makes sense to provide an udev update, which includes a/the
workaround - unless a proper fix is not found already.
There should be enough info for debugging provided already and given the impact
of this bug, it makes not much sense to upset more users using the development
You can try an older kernel, there's a chance it's initrd isn't tainted
with a set of rules that has watch in it; you'll then be able to boot in
and fix it.
Alternatively you can get in to your system via chrooting. That's a
bit of console work though, and really depends on how you set things
Have you added any udev rules that use watch? You should be able to
grep the files...
sudo grep -ri watch /etc/udev
sudo grep -ri watch /lib/udev
Then comment out any watches like this one has been (from grep result)
/lib/udev/rules.d/60-persistent-storage.rules:#KERNEL!=sr*, OPTIONS+=watch
@MichaelEvans: Missed /lib/udev/rules.d/65-mdadm.vol_id.rules
removing WATCH from that (as well) and regenerating the initrd does
enable -8 to boot. Thanks.
-jh
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You received this bug notification because
TJ, can you add a patched mdadm to your PPA, too, please? (see comment
above)
--
[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
Might be because my laptop only has a single disc and all my systems
that use raid have either 8.10 or gentoo on them... Sorry.
As a bonus, I would say this qualifies anyone using raid as I suspected
(any device-mapper based storage).
@MichaelEvans: Missed
** Tags added: jaunty
--
[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
Michael, the grep stalled for me at grep: /lib/udev/devices/ppp: No such
device or address, the following works better:
$ find /lib/udev /etc/udev -type f | xargs grep -i watch
For me, watch is used in /lib/udev/rules.d/65-dmsetup.rules, too
(package dmsetup).
I hope the workaround will work
Odd, you shouldn't have a problem like grep: /lib/udev/devices/ppp: No
such device or address; that seems to indicate some kind of storage
corruption if I remember correctly. Though it may just be udev spamming
you.
--
[jaunty] doesn't boot anymore after udev upgrade
Same here on a Asus P5N7A-VM running on Jaunty amd64.
Using 2.6.28-6 the system boots within 1.5 minutes.
--
[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
Attached is another udev_log=debug captured via serial console. Only
lvm2 installed, and one partition with a VG in it. No boot devices are
mounted from the LVM.
** Attachment added: udev_log=debug via serial console
http://launchpadlibrarian.net/22981279/boot-udev_log%3Ddebug.log.gz
--
So far, debugging suggests that the event processing themselves is
causing the inotify change event. Disabling any processing for the
change event stops the events.
(ie. they don't show up in normal disk activity - thus udev is
responding to itself. With our custom LVM and mdadm rules, this
I've tried downloading both the Feb 19 and 20 ISOs, and they appear to
contain the 138-1 version of udev as well as the other upgraged
packages.
How can I downgrade? Are there other sources?
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You received
Greetings,
I also have this problem, and I think I might be able to shed some light
on what's going wrong.
I'm running a slightly unusual configuration -- my root filesystem on my
ThinkPad is on LVM, as it my home filesystem. Only a small /boot is
stored on a conventional DOS partition. When I
Same here, I used the prior kernel (-7 not -8) and was able to boot BUT
now udevd runs at ~50% of a core and spams messages like...
UEVENT[1235217664.735688] change
/devices/pci:00/:00:09.0/host0/target0:0:0/0:0:0:0/block/sda (block)
UEVENT[1235217664.759302] change
The problem seems to come from the watch option added in 60-persistent-
storage.rules.
1. Booting with break=premount drops me in busybox without problems. With
break=mount the disk activity already starts.
2. Booting with break=premount, then starting udevd and calling udevadm trigger
Looking at other bugs, like this one...
https://bugs.launchpad.net/ubuntu/+source/speechd-up/+bug/316511
Could this be a new udev rule?
Um... This doesn't quite look as complicated as my gentoo system or my
8.10 gateway server...
ls -lR /etc/udev/
/etc/udev/:
total 8
drwxr-xr-x 2 root root
The udev files were moved, and I glanced at them but I'm no expert on
udev files and nothing obviously related to
/devices/pci:00/:00:09.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
even stuck out.
Is there a guide to follow for troubleshooting this, logs that should be
collected, or tests
I've put a test package in my PPA that may resolve this:
https://edge.launchpad.net/~intuitivenipple/+archive/ppa/
udev (138-2~tj~ppa1j) jaunty; urgency=low
* Revert Revert rules: add watch option to dm and md rules to prevent
slow down due to inotify on dm devices (LP: #332270).
-- TJ
Unfortunately, installing libudev0, libvolume-id1, and udev
138-2~tj~ppa1j doesn't fix the problem for me.
--
[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
Workaround: I can boot to the desktop under kernel -7 (but not -8)--
albeit very slowly. Then, /etc/init.d/udev restart seems to stop the
disk thrashing.
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You received this bug notification because you are
In case the odd wrapping causes confusion, the lines said by others have
their nicknames in front, except when word-wrapped.
IntuitiveNipple Device nodes can be watched for changes with inotify with
OPTIONS=watch. If closed after being opened for writing, a change uevent
will occur.
- -
So...
20090221-12:13:33 IntuitiveNipple Sure... you do that, I'll do the
new package and test it in the VM
** Changed in: udev (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
Status: Confirmed = In Progress
--
[jaunty] doesn't boot anymore after udev upgrade
Tested, and works
albert23 IntuitiveNipple: you need to drop the OPTIONS+=watch line from
60-persistent-storage.rules. That's the one causing trouble with lvm. See
comment 10 in the bug.
IntuitiveNipple ok, I've found the commit that applies the watch: f24036d
IntuitiveNipple Device nodes
The updated fix is now available in my PPA. Instead of reverting
selected patches I reset to the commit before the watch rules were added
and then cherry-picked the two non-watch-rules:
udev (138-2~tj~ppa2j) jaunty; urgency=low
* Revert watch option rules to prevent slow down due to
Tested 138-2~tj~ppa2j on my dual-core laptop with LVM and crypto-root
home, etc.
Confirm the package also fixes it and boots with kernel 2.6.28-8.
For everyone still with 138-1; good luck getting inside of a prior
kernel or chroot setup to install the update.
--
[jaunty] doesn't boot anymore
This is not a correct fix.
Please do not recommend people install it.
Instead it would be much more helpful if we could understand why you are
getting such event storms
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You received this bug notification
** Changed in: udev (Ubuntu)
Importance: Undecided = Critical
--
[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
status incomplete
On Sat, 2009-02-21 at 11:21 +, David McBride wrote:
Reverting the use-inotify-to-watch-LVM-volumes addition to udev would
probably be a good idea until this can be sorted out. In the mean time,
I'm going to see if I can find a binary package to downgrade to...
No.
** Changed in: udev (Ubuntu)
Status: In Progress = Incomplete
--
[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
For me:
http://web.mit.edu/andersk/Public/lp-332270/dpkg_-l.txt
http://web.mit.edu/andersk/Public/lp-332270/ls_sys_block.txt
http://web.mit.edu/andersk/Public/lp-332270/lvm_pvs.txt
http://web.mit.edu/andersk/Public/lp-332270/lvm_vgs.txt
** Changed in: udev (Ubuntu)
Assignee: TJ
I got hit by this bug also. It rendered my system unbootable.
I had to boot 2.6.28-7, ctrl-alt-del during boot and comment out the line from
/lib/udev/rules.d/60-persistent-storage.rules to get the system bootable again
(still need to boot with 2.6.28-7 though).
Attached are my files.
**
** Attachment added: mdeslaur ls /sys/block
http://launchpadlibrarian.net/22968202/ls_sys_block.txt
--
[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
** Attachment added: mdeslaur lvm pvs
http://launchpadlibrarian.net/22968203/lvm_pvs.txt
--
[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.
--
** Attachment added: mdeslaur lvm vgs
http://launchpadlibrarian.net/22968211/lvm_vgs.txt
--
[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.
--
I have an encrypted swap file, if that makes a difference.
--
[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
reassigning this bug to package udev
** Changed in: udev (Ubuntu)
Sourcepackagename: None = udev
--
[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.
I've the same problem. After system was upgraded today hard drive is
working all the time and system doesn't boot anymore.
--
[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,
Okay, thank you.
Setting status to confirmed.
For future reference you can manage the status of your own bugs by
clicking on the current status in the yellow line and then choosing a
new status in the revealed drop down box. You can learn more about bug
statuses at
Okay, thank you.
Setting status to confirmed.
For future reference you can manage the status of your own bugs by
clicking on the current status in the yellow line and then choosing a
new status in the revealed drop down box. You can learn more about bug
statuses at
Confirmed same on Jaunty amd64, Lenovo ThinkPad T500. Jaunty *does*
eventually boot, but by a rough wall-clock, it takes 90mins +/- 5, and
the laptop's scorching afterward.
Disk check of some kind? I noticed there was a dmsetup upgrade, and I
was focused on that-- I'm using lvols for /, /var,
Me too. The problem goes away after downgrading dmsetup, libdevmapper-
event1.02.1, libdevmapper1.02.1 [2:1.02.27-4ubuntu4 →
2:1.02.27-4ubuntu3], and libudev0, libvolume-id1, udev [138-1 → 137-2].
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You
64 matches
Mail list logo
