On my machine (two disks, no RAID, LVM), the boot process still hangs in
about 1 out of 5 boots. Strg+Alt+Del to reboot almost always works.
(Lucid with all updates as of yesterday, 64 bit.)
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Released = Confirmed
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We still experience this bug on lucid today. Bootchart shows that the
boot stalls on mountall.
The system boots in some cases, so it is possible to compare OK and KO
cases. Attached are:
* The two bootcharts (OK and KO) ;
* The two mountall --debug logs (OK and KO);
* Our /etc/fstab
The
Sorry I could only add one attachment, so here is a tarball with all the
attachments listed in the previous comment.
** Attachment added: Tarball with bootcharts, mountall debug logs and fstab.
http://launchpadlibrarian.net/45080028/bug527666_attachment.tar.gz
--
Waiting for /some/partition
Upon debugging further, it seems mountall is waiting for
/dev/HEBEX/WOO_BASE, and rightly so. After skipping with 'S' during
boot, here is what we see:
r...@malorent:~# lvscan
ACTIVE'/dev/HEBEX/WOO_BASE' [1.00 GiB] inherit
ACTIVE'/dev/HEBEX/WOO_LOG' [1.00 GiB] inherit
Update: the /dev nodes seem to only be missing when two LVM partitions
fail.
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Fri, 2010-04-23 at 09:49 +, Mathieu Alorent wrote:
We still experience this bug on lucid today.
No, this bug has been fixed. You are experiencing a different bug, I'd
appreciate it if you could open a new bug with ubuntu-bug mountall
which will some of the information we need from you.
Mathieu: actually, after reviewing the data you did attach, it's a high
probability you're experiencing bug #561390
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
mountall blocks on timeout waiting for a partition, rather than supplying
prompt and picking it up later
Seems like the problem does not occur consistently with every possible
setup, because I have a another laptop with 8 LVs that I upgraded to
Lucid yesterday and it has been booting without problems; just the usual
error messages for statd and ureadahead startup for having /var on a
separate
Same here, but sometimes everything works (about half the time):
I have /home under LVM:
/dev/cassini/cassini-home /home ext4errors=remount-ro 0 1
The boot process (sometimes) hangs with the following message:
The disk drive for /home is not ready yet or not present.
Continue to
Sorry, I meant at comment
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/561390/comments/3
Bug 561390 tracks this specific issue, it could be marked a duplicate if
that bug was reopened instead, depending on where Scott prefers to track
the issue.
--
Waiting for /some/partition [SM]
With following line in mountall.conf to fix permissions for LVs, everything
seems to work fine:
chown root:root /dev/mapper/*
But, I've discovered that on battery power things get even worse. The
boot seems to hangup about the same place, but I cannot obtain a
recovery shell and I have found no
With the change to fix de ownership issue of DM device nodes, things
seemed to be working, but then I started having problems again today
even with mains power. I second Thierry Carrez that the boot fails about
half the time. In fact the things have become worse, because sometimes
pressing M for
Works for me now !
- plymouth 0.8.2-2
- udev 151-12
- mountall 2.13
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Something is clearly resetting the permissions of /dev/shm - I don't
think it'll be udev, udev would have removed the t as well
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yesterday, I had posted a comment with details of the issue I am
experiencing since I upgraded to Lucid.
Lucid hangs up indefinitely with the Waiting for 'some partition'
error. The partitions that cause the problem are on LVs. Amit Kucheria
mentioned that at this point some of the LVs have
Further to above:
There is still a race condition in mountall, proabably due to teh
integration with plymouth boot screen.
Add/change events from udev are being dropped.
When I get the error, I press 'M', and sulogin. The links are there in
/dev/volume_group, so I believe that udev is getting
Still having the same problem as well, pulled down the latest packages
for install this morning. Attaching screenshot, fstab, mount after boot,
and LVM displays.
lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
apt-cache policy mountall
mountall:
I am experiencing exactly the same problem since I upgraded to Lucid
yesterday. I wonder if this is a udev problem, because I've also
discovered an issue with the permissions of /dev/shm.
Since, the upgrade to Lucid, boots hangup indefinitely. I have to execute the
following procedure to get to
Having this this same issue, mountall 2.12. Trying to debug it. Seems
like an 'add/change' event is not getting to mountall from udev, as
symlinks in /dev/vg are being created...
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification
I try same fresh install from 10.4b2 alternative i386 with home
reiserfs on LVM as before and 3 next reboots are ok.
On main system from version 2.11 mostly boot and from version 2.12 I not
see hang on boot.
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You
After update and install nvidia-96 driver, system hang on boot with same
symptom. On maintenance console I see home not mounted, mount -a forking
fine and after Ctrl-D system boot. Gdm after login hang and restart.
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You
Having this same issue, mountall version 2.11
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
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
I have my bug related to lost lvs/vg: #554478
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
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
I opened a new bug about the ownership issue : #557909.
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
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
I see 2 issues :
- mountall stop working while user is prompted to press S/M (corrected in
mountall 2.10, cf #58)
- the latest devices created in /dev/mapper is owned by root.disk instead of
root.root
On my machine, mountall --version returns 2.8 while apt-cache show
mountall returns 2.10 (and
On Tue, 2010-04-06 at 11:47 +, Arnulf Heimsbakk wrote:
Can the status of this bug be changed from Fix Released to Confirmed
since it is still an issue?
No.
If you are still having issues, you must have had a different bug to the
original reporter all along.
Please open a new bug.
Scott
Hi,
I'm having the same problem as orgoj and some of the others on this bug.
Did someone create a new bug for this, possibly different, bug which
looks like this one?
Thanks,
Tim
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification
similar to tamieu. But my /dev/mapper contains only one file - control
:((( Should I open new bug as well?
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
An 'grep swap' extract from /var/log/boot.log with mountall --debug:
local 6/6 remote 0/0 virtual 11/11 swap 0/1
try_mount: /dev/mapper/lucid-swap_1 waiting for device
try_udev_device: block /dev/mapper/lucid-swap_1
e26b43b0-7782-44da-9a8f-78c7955e3c74 (null)
try_udev_device:
On Wed, 2010-04-07 at 16:53 +, Tim Jones wrote:
I'm having the same problem as orgoj and some of the others on this bug.
Did someone create a new bug for this, possibly different, bug which
looks like this one?
If you could each create a new one using ubuntu-bug mountall, I would
really
I would also ask that everyone post back here with the new bug numbers
so that I and others will be able to track the trail to the other bugs
should we land here.
Thanks
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are
Can the status of this bug be changed from Fix Released to Confirmed
since it is still an issue?
Arnulf
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@arnulf: done
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Released = Confirmed
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
On Sat, 2010-04-03 at 08:35 +, orgoj wrote:
My boot.log
** Attachment added: boot.log
http://launchpadlibrarian.net/42957861/boot.log
Thanks, could you try again replacing --verbose with --debug
Also attach your /var/log/udev file
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
I don't have --verbose in /etc/init/mountall.conf.
I have only line:
exec mountall --debug --daemon $force_fsck $fsck_fix
My actual boot.log and udev.
orgoj
2010/4/4 Scott James Remnant sc...@canonical.com:
On Sat, 2010-04-03 at 08:35 +, orgoj wrote:
My boot.log
** Attachment added:
I can confirm that the mount issue still exists. I'm adding debug from
mountall and /var/log/udev. Note. I used [s] to skip waiting for /var
and /var/log. My test setup is as follows.
lvdisplay:
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
homelv rootvg -wi-ao 1.00g
My /var/log/udev
** Attachment added: udev-100404-ah
http://launchpadlibrarian.net/43084292/udev-100404-ah
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
After several restart I see that system sometimes booted, even if
appears message from inotify_add_watch.
Behavior of maintenance shell after pressing M is changed, system now
continue on booting. In version before 2.10 system did reboot.
In fstab I see all instaled mount point by UUID, but I
On Fri, 2010-04-02 at 20:25 +, orgoj wrote:
(a) Waiting for 5 min. and nothing hapen.
(b) GDM login appear, but /data not mounted.
(c) I see /data not mounted. mount -a mont /data. After ctrl-d system
booted normally.
Ok, these are all correct behaviours for an error mounting your /data
My boot.log
** Attachment added: boot.log
http://launchpadlibrarian.net/42957861/boot.log
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same here, the issue is not fixed. As I stated earlier, my /dev/mapper
/vg-opt is owned by root:disk, all the rest is owned by root:root. Only
/dev/mapper/vg-opt gives issues, this volume is never mounted. The other
volumes are mounted correctly. How can I (permanently!) change ownership
for this
Fixed for my since update to mountall 2.10. Big Thanks!
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
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
On Thu, 2010-04-01 at 22:18 +, orgoj wrote:
After update to 2.10 on main system, hang message is changed to:
The disk drive for /data is not ready yet or not present
Continue to wait; or Press S to skip mount or M for manual recover
And what happens if you:
(a) Continue to wait
(b)
During my reboot following today's updates, I saw the new message appear
briefly, then go away, and the system booted normally.
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(a) Waiting for 5 min. and nothing hapen.
(b) GDM login appear, but /data not mounted.
(c) I see /data not mounted. mount -a mont /data. After ctrl-d system
booted normally.
Behavior is similar as in version 2.8-9, only message changed.
orgoj
2010/4/2 Scott James Remnant sc...@canonical.com:
Yeah, latest updates have me in the same situation as orgoj. The disk
drive /home is not ready yet or not present. Waiting for several
minutes does no good. Skipping brings up GDM and I switch to VT1 and
manually mount the volume just fine.
Deven
On Fri, Apr 2, 2010 at 4:25 PM, orgoj
After update to 2.10 on main system, hang message is changed to:
The disk drive for /data is not ready yet or not present
Continue to wait; or Press S to skip mount or M for manual recover
/data is manually added to /etc/fstab reiserfs on lvm of /dev/sda4 and
/dev/sdb1 from karmic.
** Summary changed:
- multiple LVM volumes not mounted in Lucid
+ Waiting for /some/partition [SM]
** Changed in: mountall (Ubuntu Lucid)
Status: Confirmed = Triaged
** Changed in: mountall (Ubuntu Lucid)
Assignee: Canonical Foundations Team (canonical-foundations) = Scott
James
Well, this is very interesting. I instrumented mountall.conf and turned
off boot splash+quiet and rebooted. The system came back within
seconds. I've now backed out all the customizations and the system is
booting beautifully. No hang, no waiting... message.
I'm going to try one more fresh
Confirmed fixed after reinstall+upgrade+reboot.
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
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
Pardon my ignorance, but would this also cause a hang at boot like:
Init: ureadahead main process (...) terminated w/ status 5
I've learned in the past that when my system hangs on boot after a major
upgrade, it often revolves around LVM -- which I should probably have
never played with in the
I don't know for sure, but I suspect that those ureadahead errors are
unrelated to the boot freezes. I'll bet if you instrument
/etc/init/mountall.conf as described above, you'll see that it's
actually hanging in mountall.
--
Waiting for /some/partition [SM]
This bug was fixed in the package mountall - 2.10
---
mountall (2.10) lucid; urgency=low
* Rework the Plymouth connection logic; one needs to attach the client to
the event loop *after* connection otherwise you don't get disconnection
notification, and one needs to actually
The latest updates seem to have fixed my LVM mount issues too
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for all of the hard work!!!
Deven
On Wed, Mar 31, 2010 at 3:22 PM, Amit Kucheria
amit.kuche...@canonical.com wrote:
The latest updates seem to have fixed my LVM mount issues too
--
Waiting for /some/partition [SM]
https://bugs.launchpad.net/bugs/527666
You received this bug
56 matches
Mail list logo
