** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672964
Title:
2.6.32-26 unbootable: does not find root file system
To manage notifications about this bug go to:
https://bugs.l
This bug was fixed in the package udev - 162-2.2
---
udev (162-2.2) maverick-proposed; urgency=low
* debian/udev.initramfs-hook: If /sbin/udevadm.upgrade exists, copy that
into the initramfs instead of the shell script wrapper that we have during
udev upgrades. (LP: #672964)
This bug was fixed in the package udev - 151-12.3
---
udev (151-12.3) lucid-proposed; urgency=low
* debian/udev.initramfs-hook: If /sbin/udevadm.upgrade exists, copy that
into the initramfs instead of the shell script wrapper that we have during
udev upgrades. (LP: #672964)
Hello Jean-Baptiste,
Jean-Baptiste Lallement [2010-11-22 11:23 -]:
> I'm unable to reproduce the original issue with the provided test case.
> The diversion is removed and update-initramfs is run in the postinst
> script, copying the right udevadm to the initramfs.
Ah, you mean that calling t
I am suffering from this at present having upgraded from 2.6.32-25 (works) to
2.6.32-26 (gives above error). Is there anything I can do/provide to either
a) provide evidence
b) test solution?
Charles
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
verification for lucid and maverick.
I'm unable to reproduce the original issue with the provided test case.
The diversion is removed and update-initramfs is run in the postinst
script, copying the right udevadm to the initramfs.
But, if I run update-initramfs without removing the diversion first
** Branch linked: lp:ubuntu/udev
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
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
htt
> If you do "sudo update-initramfs -u -k all", does 2.6.32-26 boot then?
Yes.
> I'm pretty sure that the update here will prevent people from falling
into it in the first place, but so far we do nothing to repair it after
the fact.
I guess I'm not the right person to make the decision whether we
$ sudo update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-2.6.35-22-generic
update-initramfs: Generating /boot/initrd.img-2.6.32-26-generic
update-initramfs: Generating /boot/initrd.img-2.6.32-25-generic
I *think* that's what I saw, but only for 2.6.35-22, when I upgraded
ude
> David, do you still have the complete screen output by any chance?
No, sorry.
> I wonder which kernel you were running at the time when you did the
update, was it 2.6.35-22 or 2.6.32-26?
It was 2.6.32-25. (Currently I have 2.6.32-25, 2.6.32-26 and 2.6.35-22
installed. 2.6.32-26 doesn't boot.)
David, do you still have the complete screen output by any chance?
udev's postinst already calls update-initramfs -u. I wonder which kernel
you were running at the time when you did the update, was it 2.6.35-22
or 2.6.32-26? I suppose it was .35, since you said that .32 didn't boot.
If you do "su
I don't know exactly how to test this, but I did the following:
1) booted 2.6.32-25
2) sudo apt-get update && sudo apt-get dist-upgrade
3) rebooted 2.6.32-26
2.6.32-26 was still unbootable. I'm not sure it's related, but I noticed
a line saying something like "updating initramfs for 2.6.35-22" (wh
** Branch linked: lp:ubuntu/maverick-proposed/udev
** Branch linked: lp:ubuntu/lucid-proposed/udev
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Accepted udev into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
2.6
Lucid/Maverick SRUs uploaded as well, patches:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/udev/lucid/revision/177
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/maverick/udev/ubuntu/revision/2624
(same as the natty fix).
** Changed in: udev (Ubuntu Maverick)
Stat
** Branch linked: lp:ubuntu/lucid/udev
** Branch linked: lp:~ubuntu-core-dev/ubuntu/maverick/udev/ubuntu
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package udev - 164-3
---
udev (164-3) natty; urgency=low
* debian/udev.initramfs-hook: If /sbin/udevadm.upgrade exists, copy that
into the initramfs instead of the shell script wrapper that we have during
udev upgrades. (LP: #672964)
-- Martin Pitt
** Description changed:
When trying to boot 2.6.32-26, the following error occurs:
udevadm trigger is not permitted while udev is unconfigured.
Gave up waiting for root device.
/.. etc ../
ALERT! /dev/disk/by-uuid/0927db9a-0528-49c5-bdc5-ff3d5a9eb9c5 does not exist.
Dropping to a she
Thanks Colin. I removed the "verification-failed"/"regression-proposed"
flags.
** Tags removed: regression-proposed
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: udev (Ubuntu Lucid)
Status: Triaged => New
** Changed in: udev (Ubuntu Lucid)
Assignee: Steve Conklin (sconklin) => Colin Watson (cjwatson)
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
You received this bug notification
This is not a regression, but it is a latent bug that you were unlucky
enough to hit. Something (it's not clear what) ran update-initramfs
while udev was unconfigured; there are quite a few candidates and it's
not clear exactly what did it. It probably doesn't matter.
I think it would be best fo
** Attachment added: "dpkg.log.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/672964/+attachment/1731344/+files/dpkg.log.1
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
You received this bug notification because you are a member of Ub
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/672964/+attachment/1731342/+files/dpkg.log
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
You received this bug notification because you are a member of Ubuntu
I can confirm that this just happened to one of my machines and that re-running
update-initramfs makes the system bootable again. For some reason all of my
previous initrd's also were partially remade, so I had -24 and -25 with the
udevadm trigger message and -26 panic while trying to find the i
David - can this be corrected by running 'update-initramfs -u' after
booting the 2.6.32-25 kernel? Are you out of disk space in /boot ?
--
2.6.32-26 unbootable: does not find root file system
https://bugs.launchpad.net/bugs/672964
You received this bug notification because you are a member of Ubu
25 matches
Mail list logo
