*This is an automated response*
This bug report is being closed because we received no response to the
previous request for information. Please reopen this if it is still an
issue in the actively developed pre-release of Jaunty Jackalope 9.04 -
http://cdimage.ubuntu.com/releases/jaunty . To
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
This bug is all but solved. The problem and cause is known. Can we
close the loop and get some kind of resolution, even if that is just
this is how things are -- not fixing?
Note that there is a follow up issue I just filed in bug 190995.
Perhaps one of these should be a dup of the other, but I
This bug is still present on Gutsy release. I had no entry for the dm
disks in /dev/disk/by-uuid.
I tried removing evms, but then the init RAM disk could not be created
for some reason, which led to a locked situation (apt-get needs dpkg to
finish, but dpkg does not).
Note that RAM disk creation
In fact, it appears that dpkg was not locked, but udev got mad after I
removed evms and was using 100% CPU. I had to restart the service
manually...
--
EBUSY trying to mount unmounted /boot filesystem
https://bugs.launchpad.net/bugs/122568
You received this bug notification because you are a
This can be related to bug #115616
I was having the same symptoms described here, and I fix them removing evms.
If you can't remove evms there is also other less drastic solutions, check
https://bugs.launchpad.net/ubuntu/+source/evms/+bug/115616.
--
EBUSY trying to mount unmounted /boot
Same problem here after upgrading to gutsy and using 2.6.22 kernel.
The still installed 2.6.20 does not have this problem.
--
EBUSY trying to mount unmounted /boot filesystem
https://bugs.launchpad.net/bugs/122568
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same problem here.
Having just upgraded from Feisty to Gutsy, boot process goes to maintenance
root console because of fsck 'device busy' error. Swapon fails for the same
reason.
As suggested above, I am able to activate swap partition by refering to it as
/dev/dm-3. UUID or /dev/sda5 are
I have figured this problem out. Here is the cause:
$ ls -l /dev/mapper
total 0
crw-rw 1 root root 10, 63 2007-08-08 04:56 control
lrwxrwxrwx 1 root root 7 2007-08-08 04:56 hda1 - ../dm-0
lrwxrwxrwx 1 root root 7 2007-08-08 04:56 hda2 - ../dm-1
lrwxrwxrwx 1 root root 7
I've seen no update since I provided the requested information. Also
this bug is marked Incomplete. How is it? Have I not provided all of
the requested information?
I have just discovered that this problem affects no only my /dev/hda1
partition but my /dev/hda2 partition as well. In fact I
Hi,
Can you run lsof /boot and see if anything has an open file handle
there?
Cheers, Kyle
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Kyle McMartin
Status: New = Incomplete
--
EBUSY trying to mount unmounted /boot filesystem
On Wed, 2007-06-27 at 15:51 +, Kyle McMartin wrote:
Hi,
Can you run lsof /boot and see if anything has an open file handle
there?
Nothing:
# lsof /boot
[ no output ]
# lsof -n | grep /boot
[ again, no output ]
b.
--
My other computer is your Microsoft Windows server.
Brian J.
12 matches
Mail list logo
