[Bug 358654] Re: udevadm trigger is not permitted while udev is unconfigured
Launchpad Bug Tracker
358654 at bugs.launchpad.net
Wed May 2 20:10:23 UTC 2012
This bug was fixed in the package lvm2 - 2.02.88-2ubuntu1
---------------
lvm2 (2.02.88-2ubuntu1) quantal; urgency=low
* Merge from Debian unstable (LP: #726677), remaining changes:
- debian/patches/avoid-dev-block.patch: Prefer any other device name over
names in /dev/block/ since lvm.conf won't handle this.
- debian/rules:
- copy .po file to .pot file for Rosetta (Ubuntu specific).
- debian/{dmsetup,lvm2}-udeb.install:
- install initramfs and udev hooks in udebs (Debian bug 504341).
- auto-start VGs as their PVs are discovered (Ubuntu specific):
- add debian/tree/lvm2/lib/udev/rules.d/85-lvm2.rules: use watershed plus
the sledgehammer of vgscan/vgchange to turn on VGs as they come online.
- debian/tree/lvm2/usr/share/initramfs-tools/scripts/hooks/lvm2:
- add 85-lvm2.rules to the list of udev rules to copy.
- depend on udev.
- debian/control:
- add versioned Depend on watershed in lvm2 for udev rules.
- add versioned Depend/Breaks on udev in dmsetup for udev rules.
- add Depend on initramfs-tools in dmsetup so system is not potentially
rendered unbootable by out-of-order dpkg configuration. LP: #358654.
- debian/rules:
- do not install local-top scripts since Ubuntu mounts root using udev.
- do not install init scripts for lvm2, since udev starts LVM.
- debian/lvm2.postinst: handle missing lvm2 init script.
- debian/tree/dmsetup/lib/udev/rules.d/60-persistent-storage-dm.rules:
watch dm devices for changes with inotify
- add mountroot failure hooks to help fix bad boots (Debian bug 468115):
- debian/tree/lvm2/usr/share/initramfs-tools/scripts/init-premount/lvm2
- add packages for upstream event manager (Debian bug 514706):
- debian/control: define libdevmapper-event1.02.1 and dmeventd packages.
- debian/rules:
- enable dmeventd during configure.
- add build targets.
- fix shlibs invocation with a cleared DH_OPTIONS to get udeb shlibs.
- debian/dmeventd.{install,8,manpages}: install dmeventd files.
- debian/libdevmapper-event*.{install,symbols}: install dmeventd files.
- debian/libdevmapper-dev.install: install libdevmapper-event files.
- debian/patches/monitoring-default-off.patch: by default, do not
expect to talk to dmeventd. Monitoring can be done via "--monitor y".
- rename debian/clvm.defaults to debian/clvm.default so it is intalled
correctly.
- debian/control: add dmsetup-udeb to libdevmapper1.02.1-udeb recommends.
- lidevmapper-dev: move .so symlinks to /usr/lib where they belong
- debian/patches/rules-subdir.patch: removed as reordering will cause
build failure with dmeventd.
- debian/patches/libdm-event-static.patch: removed as other static libs
aren't being built anymore either.
- debian/rules: make sure dmsetup and lvm2 initramfs-tools scripts are
executable. When the Ubuntu-specific ones are added with a patch,
they may lose their executable bit.
- Add and install clvmd resource agent
- Add dependency on libudev-dev to libdevmapper-dev so that the .pc file
works.
- Make lvm2-udeb depend on watershed-udeb, since it has udev rules that
use watershed.
* Dropped changes, included in Debian:
- Build clvm with support for corosync, openais and cman
- debian/control: change to libreadline-dev for build.
* Dropped changes, included upstream:
- debian/patches/open-readonly.patch: do not open every device for
write, otherwise udev thinks they've all changed (see inotify above).
* Dropped changes, superseded upstream:
- debian/tree/dmsetup/lib/udev/rules.d/55-dm.rules: properly respond
to "add" events during boot. Upstream now distinguishes between
coldplug add events initial ones, so this is not supposed to be a
problem now.
* Update symbols for libdevmapper-event.
* Update libdevmapper-event, dmeventd descriptions to match Debian
boilerplate.
* Don't install documentation in udebs.
* Call dh_installman so that our dmeventd manpage actually gets installed
* Install the missing fsadm manpage.
lvm2 (2.02.88-2) unstable; urgency=low
* Enable corosync and openais support. (closes: #563320)
lvm2 (2.02.88-1) unstable; urgency=low
* New upstream version.
* Remove lvm-common conflicts and replaces.
* Remove grub-common breakage.
* Remove own quilt usage.
* Move cache file to /run/lvm. (closes: #562234)
- Remove old cache dir.
* Move lock files to /run/lock/lvm. (closes: #263148)
* Support status action in lvm2 init script. (closes: #643822)
* Remove Squeeze upgrade checks.
lvm2 (2.02.86-1) unstable; urgency=low
* New upstream version.
* Remove leading article from short description.
* Update udev rules.
lvm2 (2.02.84-3.1) unstable; urgency=low
* Non-maintainer upload.
* Replace libreadline5-dev build dependency with (conservatively)
libreadline-gplv2-dev, fixes an FTBFS. (Closes: #553807)
lvm2 (2.02.84-3) unstable; urgency=low
* Remove udev dependency from init script. (closes: #543163)
* Don't longer create device nodes in init script.
* Don't longer try to stop devices on shutdown.
lvm2 (2.02.84-2) unstable; urgency=low
* Fix development library symlinks. (closes: #614838)
* Update Standards-Version to 3.9.1, no changes needed.
lvm2 (2.02.84-1) unstable; urgency=medium
* New upstream version.
* Adopt upstream changes in udev rules. (closes: #603710)
lvm2 (2.02.66-5) unstable; urgency=low
* Remove old libdevmapper1.02 init script on upgrade. (closes: #549316)
* Conflict against libdevmapper1.02.
-- Steve Langasek <steve.langasek at ubuntu.com> Wed, 02 May 2012 07:48:42 -0700
** Changed in: lvm2 (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/358654
Title:
udevadm trigger is not permitted while udev is unconfigured
Status in “bcmwl” package in Ubuntu:
Triaged
Status in “cryptsetup” package in Ubuntu:
Fix Released
Status in “devmapper” package in Ubuntu:
Fix Released
Status in “fuse” package in Ubuntu:
Triaged
Status in “kbd” package in Ubuntu:
Fix Released
Status in “linux” package in Ubuntu:
Incomplete
Status in “lvm2” package in Ubuntu:
Fix Released
Status in “ntfs-3g” package in Ubuntu:
Fix Released
Status in “plymouth” package in Ubuntu:
Fix Released
Status in “watershed” package in Ubuntu:
Fix Released
Bug description:
I've just finished helping a German user diagnose a failed-boot issue
after the system had been updated. The failure means that although
udevd starts it doesn't do anything so no devices are populated.
Later, we found a forums post (also in the German language) with the
same issue which shows:
udevadm trigger is not premitted while udev is unconfigured.
Gave up waiting for root device. Common problems:
-Boot args (cat /proc/cmdline)
-Check rootdelay= (did the system wait long enough)
-Check root= (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/05d79451-0ad0-43fc-9f51-a2c98b4831f2 does not exist.
Dropping to a shell!
See: http://forum.ubuntuusers.de/topic/nach-update-bootet-laptop-
nicht-mehr/
It seems that the user was prompted to restart the system before the
system had been fully configured. I'm not sure how that could happen
and unfortunately we have no logs to look at, but this should at least
be on the radar.
The user reported he updates the system every day so in this case the
difference was between 8th April and 9th April.
Discussing it on 'ubuntu-devel kees suggested the best packages to
post this against since:
<kees> you could open it against both udev and linux :)
<kees> ...well both of those packages drop the "please reboot" file, so they likely both need to be fixed.
But Scott thought that wouldn't help and needs a cross reference check
of the postinst scripts against package depends:
<Keybuk> instead grep /var/lib/dpkg/info/*.postinst and look for calls to update-initramfs
<Keybuk> and check each of the packages to make sure they have Depends: initramfs-tools
<Keybuk> if you find some which don't, file bugs on them
For which the user needs to return to check their particular
installation, since they left in a hurry once the problem was finally
fixed.
However, the following shell script identifies some packages that
don't depend on initramfs-tools:
for ITEM in /var/lib/dpkg/info/*.postinst; do PKG=$(sed -n "/update-
initramfs/ s/.*/${ITEM##*/}/p" $ITEM | sort -u); [ ! -z $PKG ] &&
(apt-cache depends ${PKG%%.postinst} | grep Depends | grep -q
initramfs-tools || echo ${PKG%%.postinst}); done
For now I've assigned some of the packages this identifies whilst
discussion continues as to the extent of the issue.
----------
The solution is to use a live-CD to mount the system (or boot from a completely separate installation), mount the failed OS partition(s), and complete the update process:
e.g.
sudo -i
# create a target mount point
mkdir /mnt/target
# mount root
mount /dev/sda8 /mnt/target
# mount boot
mount /dev/sda9 /mnt/target/boot
# into Jaunty
chroot /mnt/target/
# update
dpkg --configure -a
# done
exit
#unmount
umount /mnt/target/boot
umount /mnt/target
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/358654/+subscriptions
More information about the foundations-bugs
mailing list