[Bug 527666] Re: Waiting for /some/partition [SM]
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 bootcharts clearly show that mountall is the process blocking the boot with LVM (until we press 'S' or 'M'). In the KO case, the mountall debug logs read: Received SIGUSR1 (network device up) try_mount: /WOO waiting for device which seems to be blocking all the depending mounts. ** Attachment added: Bootchart OK http://launchpadlibrarian.net/45079910/bootchart_ok.png -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 ACTIVE'/dev/HEBEX/WOO' [5.00 GiB] inherit ACTIVE'/dev/HEBEX/WOO_PROG' [2.00 GiB] inherit ACTIVE'/dev/HEBEX/VAR_LOG' [3.00 GiB] inherit r...@malorent:~# ls -l /dev/mapper/ total 0 brw-rw 1 root disk 251, 4 Apr 23 14:57 HEBEX-VAR_LOG brw-rw 1 root disk 251, 2 Apr 23 14:57 HEBEX-WOO brw-rw 1 root disk 251, 1 Apr 23 14:57 HEBEX-WOO_LOG brw-rw 1 root disk 251, 3 Apr 23 14:57 HEBEX-WOO_PROG crw-rw 1 root root 10, 59 Apr 23 14:57 control r...@malorent:~# ls -l /dev/HEBEX/ total 0 lrwxrwxrwx 1 root root 23 Apr 23 14:57 VAR_LOG - ../mapper/HEBEX-VAR_LOG lrwxrwxrwx 1 root root 19 Apr 23 14:57 WOO - ../mapper/HEBEX-WOO lrwxrwxrwx 1 root root 23 Apr 23 14:57 WOO_LOG - ../mapper/HEBEX-WOO_LOG lrwxrwxrwx 1 root root 24 Apr 23 14:57 WOO_PROG - ../mapper/HEBEX-WOO_PROG r...@malorent:~# lvdisplay /dev/HEBEX/WOO_BASE /dev/mapper/HEBEX-WOO_BASE: open failed: No such file or directory /dev/mapper/HEBEX-WOO_BASE: open failed: No such file or directory --- Logical volume --- LV Name/dev/HEBEX/WOO_BASE VG NameHEBEX LV UUID1an8Zg-aYse-AkF3-NGs2-0BGF-4mfO-1m3wUA LV Write Accessread/write LV Status NOT available LV Size1.00 GiB Current LE 256 Segments 1 Allocation inherit Read ahead sectors auto So LVM finds the missing device internally, but the device is not created by udev. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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. Scott -- Scott James Remnant sc...@ubuntu.com ** Changed in: mountall (Ubuntu Lucid) Status: Confirmed = Fix Released ** Summary changed: - Waiting for /some/partition [SM] + mountall blocks on timeout waiting for a partition, rather than supplying prompt and picking it up later -- mountall blocks on timeout waiting for a partition, rather than supplying prompt and picking it up later 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 partition. I've uninstalled ureadahead for fixing the error messages with ureadahead which apparently does not work with /var n a separate partition, but the statd error messages are still there. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 wait; or Press S to skip mounting or M for manual recovery I press M # mount /home # exit and then the boot proceeds. See my mountall logs at comment 3. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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] 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: 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 way to get a running system. I am not sure if this is another bug somewhere else or the bug is related. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 manual recovery does not work and the only way to get the system to boot is to reboot over and over again to get a working session. As far as I can gather Lucid boot process is failing completely for many people that have multiple filesystems on LVM. I've been using Ubuntu since with LVM since 7.04, and all the upgrades up to 9.10 worked without problems. Judging by the comments of other the problem is not limited to upgrades either, This bug really seems to be a show-stopper, because a system that was working perfectly, does not even get to a login prompt with Lucid. I will be glad to help to identify a solution, but I do not know how. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 root:root ownership whereas others have root:disk ownership, and apparently the LVs that hang are the ones with root:disk ownership. Simply changing the owner ship of the device node in /dev/mapper is a no fix, because the permissions are not persistent through reboots. So, I went ahead and added the following line in mountall.conf before the line that launches the daemon with exec: chown root:root /dev/mapper/* Adding this line fixed the problem completely. This test seems to confirm that the problem is with the ownership of the LVM device nodes, but I have no idea why some nodes end up having the root:disk ownership, while others have root:root in the first place. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 its job done, and letting mountall know about it. two things should be done: 1) add code to try 2 mount attempts before giving up on a file system in /etc/fsta on boot. 2) Find the race and fix it. 1) is the belt and braces - not mounting file systems on boot is a SERIOUS problem. Condition can be debugged when a machines running by creating a volume group with about 10 logical volumes, deactivating it with 'vgchange -a n /dev/volume_group, and then activating it. mountall would have to be running in a separate window, not issuing events to upstart init. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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: Installed: 2.13 Candidate: 2.13 Version table: *** 2.13 0 500 http://apt-dev/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status ** Attachment added: Manual skipping of LVM filesystems to boot fully http://launchpadlibrarian.net/44844018/ubuntu-1004-skip-LVM-527666.JPG -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 the GDM screen: 1. Enter M (for Manual Recovery) 2. Execute mount -a which mounts all filesystems on LVM without problems. 3. CTRL-D to close the shell and continue with the reboot. After login to Gnome Session, launching Google Chrome fails, because /dev/shm has permissions rw-r--r-t. Google Chrome starts working normally after setting /dev/shm permissions manually to rw-rw-rwt, but the permissions do not survive a 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 apt-get tells my I already have the latest version). Maybe this 2.10 package contains a mistake ? Waiting for the dm device to be mounted is pointless, only changing permissions on /dev/mapper/logicalvolume can make Lucid to boot correctly. This is easy to do, but not really clean. thamieu -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 -- Scott James Remnant sc...@ubuntu.com ** Changed in: mountall (Ubuntu Lucid) Status: Confirmed = Fix Released -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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: /dev/mapper/lucid-swap_1 by name run_fsck: /dev/mapper/lucid-swap_1: no check required activating /dev/mapper/lucid-swap_1 spawn: swapon /dev/mapper/lucid-swap_1 spawn: swapon /dev/mapper/lucid-swap_1 [1021] swapon: /dev/mapper/lucid-swap_1: swapon failed: Device or resource busy mountall: swapon /dev/mapper/lucid-swap_1 [1021] terminated with status 255 mountall: Problem activating swap: /dev/mapper/lucid-swap_1 mounted: /dev/mapper/lucid-swap_1 swap finished local 6/6 remote 0/0 virtual 11/11 swap 1/1 Just a guess here... If each of the mountall discovered FSs are mounted in the background by a spawned process (assumed from the logging) then as /home is generally the largest mount on a default install and is going to take the longest, could it be possible that it just happens that as the swap mount has failed all but the /home has mounted ok but mountall has given up waiting due to the failure and killed off the spawned mounts? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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 appreciate that. It's quite possible that you each have a different problem at this point. Scott -- Scott James Remnant sc...@ubuntu.com -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
@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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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: 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 ** Attachment added: boot.log http://launchpadlibrarian.net/43077967/boot.log ** Attachment added: udev http://launchpadlibrarian.net/43077970/udev -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 loglv rootvg -wi-a- 2.00g optlv rootvg -wi-ao 1.00g tmplv rootvg -wi-ao 2.00g varlv rootvg -wi-a- 2.00g fstab: proc/proc procnodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=d5e5232c-0357-454e-8cb4-2fca244f4f42 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=1b4eae89-00cd-42d3-a9a3-0e08c885a1f1 noneswapsw 0 0 UUID=414e0c6d-29b0-446f-bde2-6540af2c73ae /home ext4defaults 01 UUID=816b3834-02a7-4cb1-b591-cab186c2502d /optext4defaults 01 UUID=35f9fad7-e5a0-48d7-8b29-50c9fd096054 /tmpext4defaults 01 UUID=40767f37-c576-42f6-82ab-80aa31f85617 /varext4defaults 01 UUID=e1ae56e7-0cd0-42bf-9079-690c5711461d /var/logext4 defaults0 1 I have also discovered, that if I move /usr to an lvm partition then I get the message error: file not found. on my console when/right after the kernel boots. I have no idea where that comes from or if it is related to this problem. Tips for debugging is appreciated. Arnulf ** Attachment added: mountall.debug-100404-ah http://launchpadlibrarian.net/43084241/mountall.debug-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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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 manually add mount point by path: /dev/mapper/data-data1 /datareiserfs defaults0 4 orgoj -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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 partition. It waited forever for it (it never showed up I assume), and you were able to skip it. Could you try appending --debug to the mountall exec line in /etc/init/mountall.conf and attach /var/log/boot.log after waiting a short time then skipping. Scott -- Scott James Remnant sc...@ubuntu.com -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 volume? And why does it have a different owner than the other logical volumes? I assume it is caused by the fact that I created /dev/vg/opt after installation The other volumes were either already present before installation, or created during installation. If you want, I can post my boot.log 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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) Press S (to skip mounting that one) (c) Press M (for manual recovery) Could you try each one in turn, and let us know what changes/what you see. Scott -- Scott James Remnant sc...@ubuntu.com -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
(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: 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) Press S (to skip mounting that one) (c) Press M (for manual recovery) Could you try each one in turn, and let us know what changes/what you see. Scott -- Scott James Remnant sc...@ubuntu.com -- -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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 michael.h...@gmail.com 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. Behavior is similar as in version 2.8-9, only message changed. orgoj 2010/4/2 Scott James Remnant sc...@canonical.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) Press S (to skip mounting that one) (c) Press M (for manual recovery) Could you try each one in turn, and let us know what changes/what you see. Scott -- Scott James Remnant sc...@ubuntu.com -- -- Waiting for /some/partition [SM] https://bugs.launchpad.net/bugs/527666 You received this bug notification because you are a direct subscriber of the bug. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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. /dev/mapper/data-data1 /datareiserfs defaults0 4 r...@telatko:~# pvdisplay -C PV VG Fmt Attr PSize PFree /dev/sda4 data lvm2 a- 220,71g0 /dev/sdb1 data lvm2 a- 298,09g0 I noticed message on boot if system hang: udevd-work[70]: inotify_aff_watch(6, /dev/sdb1, 10) failed: No such file or directory -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
** 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 Remnant (scott) ** Description changed: - When booting up in Lucid, often times the bootsplash screen will stop at - Waiting for /home. The only reason I can think of for this delay is - that the LVM2 modules/subsystem have not loaded yet. My home directory - is on an LVM2 volume so that I can mirror and resize easily as time - passes. + This bug describes the fault where during booting you will see the + message Waiting for /some/partition [SM] + + That may be LVM, it may be encrypted, or it may simply be on a slower + disk. The key point is that the message is intelligible, and never goes + away on its own. + + In effect, boot hangs because a drive takes more than 2s to become ready ** Changed in: mountall (Ubuntu Lucid) Status: Triaged = Fix Committed -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 install, but right now I'm going to have to agree that the bug is fixed. I don't know why it hung right after install+apt-get upgrade. Is it possible the disk didn't have its morning coffee yet? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 first place. (I searched for the above error and couldn't find anything conclusive.) -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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] 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: 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 actively disconnect in the disconnection handler. * For safety and sanity reasons it becomes much simpler to create the ply_boot_client when we connect, and free it on disconnection. Thus the presence or not of this struct tells us whether we're connected or not. LP: #524708. * Flush the plymouth connection before closing it and exiting, otherwise updates may be pending and the screen have messages that confuse people while X is starting (like fsck at 90%). LP: #487744. * Replace the modal plymouth prompt for error conditions with code that continues working in the background while prompting. This most benefits the old Waiting for message, which can now allow you to continue to wait and it can solve itself. LP: #527666, #545435. * Integrate fsck progress updates into the same mechanism. * Allow fsck messages to be translated. LP: #390740. * Change fsck message to be a little less alarming. LP: #545267. * Add hard dependency on Plymouth; without it running, mountall will ignore any filesystem which doesn't show up within a few seconds or that fails to fsck or mount. If you don't want graphical splash, you simply need not install themes. * Improve set of messages seen with --verbose, and ensure all visible messages are marked for translation. LP: #446592. * Reduce priority of failed to mount error for remote filesystems since we try again, and this just spams the console. LP: #504224. * Keep hold of the dev_t when parsing /proc/self/mountinfo, then after mounting /dev (or seeing that it's mounted) create a quick udev rules file that adds the /dev/root symlink to this device. LP: #527216. * Do not try and update /etc/mtab when it's a symbolic link. LP: #529993. * Remove odd -a option from mount calls, probably a CP error from the fsck code long ago. LP: #537135. * Wait for Upstart to acknowledge receipt of events, even if we don't hang around for them to be handled. * Always run through try_mounts() at least once. LP: #537136. * Don't keep mountall running if the only remaining unmounted filesystems * -- Scott James Remnant sc...@ubuntu.com Wed, 31 Mar 2010 19:37:31 +0100 ** Changed in: mountall (Ubuntu Lucid) Status: Fix Committed = Fix Released -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527666] Re: Waiting for /some/partition [SM]
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527666] Re: Waiting for /some/partition [SM]
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 notification because you are a direct subscriber of the bug. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
