This bug was fixed in the package devicekit-disks - 007-2ubuntu7
---
devicekit-disks (007-2ubuntu7) karmic-proposed; urgency=low
* Add devicekit-disks.prerm script which stops the devicekit-disks
daemon when devicekit-disks is removed. This fixes a problem with
the Karmic
** Tags added: verification-done
** Tags removed: verification-needed
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
https://bugs.launchpad.net/bugs/554718
You received this bug
Thanks Scott!
** Changed in: devicekit-disks (Ubuntu Karmic)
Status: Triaged = Fix Committed
** Tags added: verification-needed
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
** Branch linked: lp:ubuntu/karmic-proposed/devicekit-disks
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
https://bugs.launchpad.net/bugs/554718
You received this bug notification
Installed the karmic-proposed package onto my test Karmic image.
Upgraded successfully from Karmic-Lucid.
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
Scott, thanks a lot for your investigations, this makes a lot of sense.
To be honest I would be rather cautious with backporting the media
detection patch. A lot of other layers (gvfs, blkid, udev, etc.) have
changed since then, and it is not immediately obvious that this patch
would not cause
On Mon, 26 Jul 2010, Martin Pitt wrote:
so we can just copy the script and replace configure with remove. Do
you want to prepare an SRU/debdiff yourself, or want me to do it?
I haven't done one in a while, but I can take a crack at it.
Scott
--
[MASTER] package policykit-1 0.96-1 failed to
** Tags added: patch
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
https://bugs.launchpad.net/bugs/554718
You received this bug notification because you are a member of Ubuntu
Bugs,
Debdiff attached.
** Patch added: Debdiff for the as-discussed changes.
http://launchpadlibrarian.net/52562700/devicekit-disks_007-2ubuntu7.debdiff
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
OK, I think I finally have a reasonably good idea of what's going on
with this now. I had been focused on udev and udisks, but it turns out
that the bug appears to actually be in devicekit-disks. Here's a rough
timeline of what happens:
1. During the Karmic-Lucid upgrade, devicekit-disks
So I went ahead and backported the media detection change to devicekit-
disks. It is attached. My test system successfully upgraded from
Karmic-Lucid with the patched devicekit-disks in place.
** Patch added: Port of media detection logic in udisks to devicekit-disks
Scott Talbert [2010-07-19 4:00 -]:
UDEV [1277516625.070541] remove /devices/virtual/bdi/0:21 (bdi)
Hm, I'm not sure about this. I don't see anything in udev or udisks
which would issue events on bdi devices, and usually they originate
from the kernel. Does this also appear in udevadm
Yes, the bdi event does appear as a kernel event as well.
One thing I noticed tonight is that, when things go wrong, /dev/sda also
no longer exists. (/dev/sda1, /dev/sda2, and /dev/sda5 do still exist,
though.) I'll attach a log of udevd in debug mode when this occurs. I
couldn't see anything
One possibly interesting thing that I've noticed about this is when I
look at the output of 'udevadm monitor' while running the 'udevadm
trigger --subsystem-match=block --action=change' command which causes
/proc to go away, it shows this line (which it doesn't show if I run the
'udevadm trigger
I tried that on lucid (install devicekit-disks, devkit-disks --dump,
purge, and trigger), and /proc and /sys are still fine. How exactly did
you reproduce this? On karmic, before the upgrade? Any other steps than
I did?
On Karmic I did:
dpkg -r devicekit-disks --ignore-depends=devicekit-disks
Further narrowing it down, removal of the file /lib/udev/rules.d/95
-devkit-disks.rules followed by the udevadm trigger causes the empty
/proc.
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external
I tried that on lucid (install devicekit-disks, devkit-disks --dump,
purge, and trigger), and /proc and /sys are still fine. How exactly did
you reproduce this? On karmic, before the upgrade? Any other steps than
I did?
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
You're right - it was technically still mounted (per 'mount') but
/proc was empty. Ie, 'ls -l /proc' returns an empty directory.
That sounds seriously wrong. What is the exact output of mount and
cat /proc/mounts when this happens?
--
[MASTER] package policykit-1 0.96-1 failed to
On Mon, 28 Jun 2010, Martin Pitt wrote:
You're right - it was technically still mounted (per 'mount') but
/proc was empty. Ie, 'ls -l /proc' returns an empty directory.
That sounds seriously wrong. What is the exact output of mount and
cat /proc/mounts when this happens?
The output of mount
Further troubleshooting on this...the empty /proc /sys occurs during
the karmic-lucid upgrade when udevadm trigger --subsystem-match=block
--action=change is called AFTER the devicekit-disks package has been
removed. I can reproduce this outside the upgrade installer by manually
removing
Scott,
seems that wasn't a scenario where the udevadm trigger would cause /proc
to be unmounted -- in your mount output after trigger, /proc is still
mounted.
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run
So this bug could potentially live in either udisks itself (jjust in
case it does something really strange with /proc, but usually it doesn't
touch those virtual FSes at all), or in mountall (which I believe mounts
/proc and /sys in the first place).
Can someone who is able to reproduce this
On Sat, 26 Jun 2010, Martin Pitt wrote:
seems that wasn't a scenario where the udevadm trigger would cause /proc
to be unmounted -- in your mount output after trigger, /proc is still
mounted.
You're right - it was technically still mounted (per 'mount') but /proc
was empty. Ie, 'ls -l
** Attachment added: Output of 'mount' before udevadm trigger.
http://launchpadlibrarian.net/50929606/mount.before
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
** Attachment added: Output of 'mount' after udevadm trigger.
http://launchpadlibrarian.net/50929624/mount.after
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
** Attachment added: Output of 'udevadm monitor' while udevadm trigger runs.
http://launchpadlibrarian.net/50929644/udevadm.log
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
** Attachment added: fstab
http://launchpadlibrarian.net/50929658/fstab
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is run from
external card
https://bugs.launchpad.net/bugs/554718
You received this bug
Repeated my test on an upgrade from Hardy - Lucid on a USB Flash Drive.
This worked. So this appears to be a Karmic - Lucid only issue.
Continuing to investigate why /proc and /sys appear to be getting
unmounted somehow.
--
[MASTER] package policykit-1 0.96-1 failed to install/upgrade:
I experienced what I believe to be this same problem on my desktop
machine. My desktop machine is not running on an external card, but it
is running on a RAID controller which Ubuntu seems to think is
'removable.'
In any event, I have been able to replicate this problem by installing
9.10 on a
** Summary changed:
- package policykit-1 0.96-1 failed to install/upgrade: start-stop-daemon:
nothing in /proc - not mounted? when system is run from external card
+ [MASTER] package policykit-1 0.96-1 failed to install/upgrade:
start-stop-daemon: nothing in /proc - not mounted? when system is
30 matches
Mail list logo
