I experienced the same issue on Mint 17.1 Cinnamon 64 after a power failure
during an update run.
Your methodology of booting a live cd, mounting the partitions, chroot, and
complete the updates worked for me and I was able to recover my system.
I posted my experience on the Mint forums here:-
** Branch linked: lp:~xnox/debian/sid/cryptsetup/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/358654
Title:
udevadm trigger is not permitted while udev is unconfigured
To manage
** Changed in: bcmwl (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/358654
Title:
udevadm trigger is not permitted while udev is unconfigured
To manage
** Branch linked: lp:~dmitrij.ledkov/ubuntu/quantal/lvm2/merge95
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/358654
Title:
udevadm trigger is not permitted while udev is unconfigured
To manage
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
** Branch linked: lp:ubuntu/lucid/kbd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/358654
Title:
udevadm trigger is not permitted while udev is unconfigured
To manage notifications about this bug
Me too .. dkpg --configure -a fails because udisks wants to run udevadm
trigger which fails. dpkg-reconfigure udev works fine ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/358654
Title:
Just installed ubuntu 10.10, installed the nvidia driver and updated
everything, first reboot and hit this.
Mounted / on /mnt using busybox, chrooted /mnt, started /bin/bash and
then did update-initramfs -a -k latest installed kernel which fixed
it.
but SEEESH. Really? REALLY? This should be a
I also had this problem. The solution was to stop grub from using UUIDs.
For me using Grub 2 this meant editing /etc/default/grub and setting
GRUB_DISABLE_LINUX_UUID=true. Unfortunately this does not fix the core
problem, but it does at least allow you to boot.
--
udevadm trigger is not
I have just encountered this problem too.
I am running Kubuntu 10.04 on VMWare Player 3.1.2 on a Windows XP Pro machine.
Kubuntu performed the updates and then I got the udevadm trigger... report.
I am facing issues with the various suggestions here and elsewhere though.
After the udevadm trigger
Hi there. I just had this issue when updating my 10.10 UNE install. So
it should be marked for Meerkat as well.
I fixed it using the sequence below:
sudo -i
# create a target mount point
mkdir /mnt/target
# mount root
mount /dev/sda5 /mnt/target
# into Meerkat
chroot /mnt/target/
# update
I installed Ubuntu 10.04.1 on a 64-bit machine. There is a fake-raid
configuration on my machine. All went well until I tried to update my
system. I run into the following error: kernel panic unable to mount
root fs on unknown-block. Nothing helped but re-installing my system.
After
The posted solution does work on this instance of 10.04 LTS Desktop. The
house of cards?
1) Beginning the bug killing at the bottom -- answers #125176 was a false start
and not necessary [fsck -f cleaned up /boot filesystem after #4) below].
2) Access to former rev 2.6.32-23 in /boot failed --
Just got exactly the same problem after installing the batch of updates
(accumulated for the 10 days of my absence) through Update Manager that
included the latest generic kernel update. Only could solve this by
running
sudo update-initramfs -u -k 2.6.32-24-generic
while booting another
I seem to be living in a house of cards here... I began 3 days ago
with this bug but made the not-so-good choice to work backwards starting
from the end ... does not exist message -- see question #125176. My
twist is to find /dev/sdb partition table garbled-or-missing. Today I
fail to boot a
Just happend to me with my Aspire one netbook. I was running Ubuntu netbook
edition also updating. Will try to do the live cd recovery proposed.
Agree with a coment above: what if it is your only PC? pretty bad stuff to
happen on an update.
There is Busybox 1.13.3 anything that can be
forgot to add it was on the LTS and I keep it updated on a mothly (if not
weekly) basis. Thought it had to do with my 16GB USB left in.
More hardware notes: it is an aspire one with SSD.
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You
Tried what was shown in post:
http://ubuntuforums.org/showpost.php?p=9796852postcount=10
I could load grub and load a previous kernel but after running the comands
(2.6.32-24-generic
or 2.6.32-23-generic) it still comes up with the same bootup problem.
Seems there is no need for liveCD as I
Just discovered this issue with 32 bit 10.04 LTS (upgraded from 8.04 LTS
in Aug) (20100908). Boot stopped exactly as described in bug
description. System normally runs for weeks at a time without reboot,
and several upgrades/changes/new programs were applied before restarting
--unfortunately not
** Tags added: kj-triage
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
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
System broken after update !
sudo update-initramfs -u -k 2.6.32-24-generic restored a working boot.
Why don't you save the previous kernel + initramfs when updating image ?
I am glad I had another working kernel + initramfs.
How are you supposed to even find this page if you are not an
this happened to me after I left the room while the update was
proceeding. I did not see any error messages upon return and rebooted.
It is the first time Update manager has failed me. I am not an
experienced user. I do have the Live 64 bit CD. Could someone please
post the exact code I would
LL Phillips: You might want to see
http://ubuntuforums.org/showpost.php?p=9796852postcount=10
for StewartM's step-by-step solution if you have previous kernel images
that you can reboot from.
If you do not have a previously working kernel, you might have to do
what Andrux101 has suggested at
Chandra, I followed your directions to the letter and my main machine is
now running and even has today's updates done. Thank you so much I
must now do my second machine as I held off on its updates til I could
successfully get at least one machine in the house able to get onto the
internet. I
The solution given at the top appears to have worked for me. Many thanks
for the help!
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same here.
We got this one on a machine after a fresh update from lucid-proposed.
None of the usual workaround (reconfiguring, reinstalling udev) fixed
the situation. Only a complete rebuild of the initramfs images did the
trick.
- chroot in your broken install from a liveUSB/CD
- sudo
Just got this bug from updating to lucid-proposed.
Had to use the old image and check synaptic's history find what packages
caused the problem.
Rolling back the uDev packages did nothing, though once I rolled back
the linux-image and linux-headers pakages, everything is fine again.
** Also
I think this is not an issue for lvm2, as it depends on dmsetup, which
depends on initramfs-tools. Or does apt try to get sneaky, and we need
a direct depend on initramfs-tools in lvm2 as well?
** Changed in: lvm2 (Ubuntu)
Status: Triaged = Invalid
--
udevadm trigger is not permitted
This bug was fixed in the package plymouth - 0.8.2-1
---
plymouth (0.8.2-1) lucid; urgency=low
[ Steve Langasek ]
* New upstream release.
* debian/plymouth.plymouth-stop.upstart: trust the new kdm to stop plymouth
for us, too. LP: #540177.
* plymouth needs to depend on
I had the same problem with lucid. Shouldn't plymouth and lvm2 also
depends on initramfs-tools? This is the output of the script:
bcmwl-kernel-source
fuse-utils
lvm2
plymouth-theme-fade-in
plymouth-theme-kubuntu-logo
--
udevadm trigger is not permitted while udev is unconfigured
ok, opening new tasks for the affected packages.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu)
Status: New = Triaged
** Changed in: plymouth (Ubuntu)
Importance: Undecided = Medium
** Changed in: plymouth (Ubuntu)
** Branch linked: lp:ubuntu/plymouth
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I was most displeased to experience the exact same problem as described
by Jimmy above. May be worth mentioning I also tried to update my video
drivers while the update process was ongoing and had to cancel it due to
an error (I figured it was because I was already running an upgrade
window)
I
Same issue on a Karmic Fresh install. Ran the updates, restarted as
prompted and was left with an unbootable kernel.
My solution was to simply boot into the older kernele and run
sudo dpkg --configure -a
--
udevadm trigger is not permitted while udev is unconfigured
Had some problem in ubuntu 9.10 after apt-get update when kernel
package was updated to 2.6.31-17.55~ppa7 version. I was boot old kernel,
installed on my laptop and fixed it with that commands:
sudo dpkg-reconfigure udev
sudo dpkg-reconfigure linux-image-2.6.31.17-generic
--
udevadm trigger is
** Branch linked: lp:ubuntu/devmapper
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Had same problem upgrading from ubuntu 8 to ubuntu 9.10. I managed to
boot the system using alternative kernel image selection from GRUB boot.
(Generic kernel boots ok, while pae karnel had issues describe at the
beginning).
Hope this helps - since this way there was no need to download live
i had the same issue as the previous two posters, if i did sudo dpkg-
reconfigure udev, it only updated the -9-rt kernel, and not the
-14-generic kernel, i fixed it by running:
sudo dpkg-reconfigure udev
sudo update-initramfs -u -k 2.6.31-14-generic
this fixed the problem, so i beleve that udev
I'm having this problem. I can't boot with the newest kernel. udevadm
trigger... message. Karmic 64
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I ran into the same problem with karmic-beta
after update to kernel 2.6.31-14.47 (2.6.31-14.xx before)
the rt kernel 2.6.31-9.152 (newly installed with the same update) boots
I guess sudo update-initramfs -u -k VERSION would be the fix but i
hope update to 2.6.31-14.48 will do that anyway
--
Many thanks, all -
Tobias's suggestion brought my world back too.
It's a bit scary just how far we still are from having a system suitable
for normal users :-(
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug
** Branch linked: lp:ubuntu/karmic/watershed
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubuntu/karmic/cryptsetup
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I seem to have a similar setup to 'mjhorsnell' (Ubuntu Studio Jaunty).
When I execute $ sudo dpkg-reconfigure udev /sbin/udevadm will be deleted.
After doing $ sudo aptitude reinstall udev it shows up again.
So for me the fix was to run aptitude reinstall udev and then update-
initramfs -u -k
I've seem to have run into the same problem described here with updating
my samsung nc10 to the latest version of Jaunty. The proposed solutions
did not solve this problem.
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug
I had recently upgraded to Jaunty beta. Yesterday, after updating via
synaptic (mark all updates - smart upgrade), I didn't immediately reboot
and did another smart upgrade. Also, after all updates, i did 'apt-get
clean`. Now I have the same problem as mentioned in the first post, but
the proposed
My fix was to run dpkg-reconfigure udev (which recreates
/sbin/udevadm) and then rerun mkinitramfs.
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Kees, b solution fixed my problem. I passed all as the
version and let it rebuild for all my kernels.
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still not fixed even with all packages above upgraded.
Output of
for i in $(grep update-initramfs
/var/lib/dpkg/info/*.{post,pre}{rm,inst} | cut -d: -f1 | perl -pe
's/\.(post|pre)(inst|rm)//' | sort -u | awk -F/ '{print $NF}'); do apt-
cache show $i | grep Depends | head -n1 | egrep -qv
After getting the latest packages, you should verify:
a) /sbin/udevadm is a real file not the during-update-shell-script
b) rebuild your initramfs for all kernels (since you're booted on a different
kernel)
If a above isn't fixed, that's a new bug.
For b, you'll want sudo update-initramfs -u -k
** Package changed: initramfs-tools (Ubuntu) = ntfs-3g (Ubuntu)
** Package changed: linux (Ubuntu) = fuse (Ubuntu)
--
udevadm trigger is not permitted while udev is unconfigured
https://bugs.launchpad.net/bugs/358654
You received this bug notification because you are a member of Ubuntu
Bugs,
These are the package on my system that do not show depends on
initramfs-tools:
cryptsetup
dmsetup
fuse-utils
initramfs-tools
kbd
ntfs-3g
watershed
** Description changed:
I've just finished helping a German user diagnose a failed-boot issue
after the system had been updated. The failure
** Changed in: ntfs-3g (Ubuntu)
Importance: Undecided = Medium
** Changed in: ntfs-3g (Ubuntu)
Status: New = Fix Released
** Changed in: ntfs-3g (Ubuntu)
Assignee: (unassigned) = Kees Cook (kees)
--
udevadm trigger is not permitted while udev is unconfigured
for i in $(grep update-initramfs
/var/lib/dpkg/info/*.{post,pre}{rm,inst} | cut -d: -f1 | perl -pe
's/\.(post|pre)(inst|rm)//' | sort -u | awk -F/ '{print $NF}'); do apt-
cache show $i | grep Depends | head -n1 | egrep -qv 'initramfs-tools'
echo $i; done
Ignoring fuse-utils for now since it
This bug was fixed in the package watershed - 4
---
watershed (4) jaunty; urgency=low
* debian/control: Depend on initramfs-tools so system is not potentially
rendered unbootable (LP: #358654).
-- Kees Cook k...@ubuntu.com Thu, 09 Apr 2009 12:32:54 -0700
** Changed in:
This bug was fixed in the package cryptsetup - 2:1.0.6-7ubuntu7
---
cryptsetup (2:1.0.6-7ubuntu7) jaunty; urgency=low
* debian/control: Depend on initramfs-tools so system is not potentially
rendered unbootable (LP: #358654).
-- Kees Cook k...@ubuntu.com Thu, 09 Apr 2009
This bug was fixed in the package devmapper - 2:1.02.27-4ubuntu5
---
devmapper (2:1.02.27-4ubuntu5) jaunty; urgency=low
* debian/control: Depend on initramfs-tools so system is not potentially
rendered unbootable (LP: #358654).
-- Kees Cook k...@ubuntu.com Thu, 09 Apr 2009
This bug was fixed in the package kbd - 1.14.1-4ubuntu4
---
kbd (1.14.1-4ubuntu4) jaunty; urgency=low
* debian/control: Depend on initramfs-tools so system is not potentially
rendered unbootable (LP: #358654).
-- Kees Cook k...@ubuntu.com Thu, 09 Apr 2009 12:31:48 -0700
**
58 matches
Mail list logo
