im not sure, but looks the problem i have here is the same problem 14.04
gave up waiting for root device
common problems:
--boot arts (cat /proc/cmdline)
-check root delay (did the system wait long enough?)
-check root (did the system wait for the right device?)
-missing modules ls/dev
ALERT! /dev
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
I have this problem as well on my 14.04.2 Dom0 cloud1. The VG that
holds all VMs does not come up active on boot so no VMs set to autostart
are started. I have another 14.04.2 which is on matching hardware and
configured very similar to cloud1. It reboots and starts up the VMs
properly. like th
@Astara:
> Now, I've noticed when I am booting, it *does* take a bit of time to mount
> bring up and mount all of the lvs, but you can the root mount is NOT
> in an VG/LV -- It's on a "regular device" (numbers on left are w/kernel time
> printing turned on -- so they are in seconds after boot):
>
>
I don't get this bug.
I have at least 1 snapshot going on my "/home" partition all the time.
The VG that /home is in contains most of my partitions (26), with
2 more partitions on a separate (VG+PD's) VG.
Now, I've noticed when I am booting, it *does* take a bit of time to mount
bring up and mou
Turns out, the suggested --setactivationskip option is not present in
Utopic, as Utopic comes with an LVM version which dates back to 2012
(2.02.98(2) (2012-10-15)), while the feature was implemented in 2013.
Vivid will come with a newer LVM: 2.02.111(2) (2014-09-01).
Activation skip could be a n
Got an interesting reply from the Red Hat LVM mailing list:
https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html
Haven't tested the suggestion yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
With the knowledge that the hang is caused by snapshots, some googling has
brought up some duplicates:
https://bugs.launchpad.net/lvm2/+bug/360237
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645
It seems the issue was hanging around since 2009 or earlier.
In Trusty (or probably even e
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: hundredpapercuts
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396213
Title:
L
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Now I have some more info about this. What actually makes the VG
activation so long is that I have a snapshot. Activating the snapshot
takes very long, and bringing up the entire VG takes about 5 minutes.
This wouldn't be such a big problem, as I could just patiently wait for
the activation (with r
Alberto Salvia Novella, thanks for the QA, and helpful suggestion. From my
understanding, the Ubuntu Kernel Team prefers to mark reports like these High
(not sure why I marked it Medium initially, probably was on auto-pilot) as
defined in https://wiki.ubuntu.com/Bugs/Bug%20importances :
"Makes a
@ Christopher M. Penalver:
Because this bug renders the system temporally unusable, it looks like
it should have an importance of "critical".
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => Medium
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396213
Title:
LVM V
MegaBrutal, you may want to ping an lvm2 maintainer about this. As per
https://launchpad.net/ubuntu/+source/lvm2/+changelog the most recent
person to commit to this is Dave Chiluk .
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification becau
I've had a backup of my old Trusty system, and I've built an initrd for
3.16.0-23-generic in that environment. With that initrd, the kernel
booted properly. Note, still it takes several minutes for the VG to
activate, but it eventually comes up if the kernel waits enough with
"rootdelay=300".
Now,
Yeah, I was in hurry and didn't have the time to give you the reason why
I did this.
I sent the latest apport from a kernel with which I don't experience the
issue. The difference is that I see these messages:
[5.527952] bio: create slab at 1
[ 151.415509] bio: create slab at 2
[ 161.7178
MegaBrutal, just to reinforce
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/comments/22
you do not have to do any more apport-collect'ing at this time.
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, a
apport information
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
https://www.redha
MegaBrutal, just to advise, apport-collect'ing on the mainline kernel
doesn't provide any helpful information. As well, you don't have to
apport-collect further on this report unless asked.
Despite this, the next step is to fully commit bisect from kernel
3.13.0-37 to 3.16.0-23 in order to identif
I experience the same symptoms with the mainline kernel.
Note, if the problem is really with initrd scripts, then probably the
kernel version doesn't matter much. On the other hand, as I see, lvm2
initrd scripts haven't changed since Trusty, which would suggest it's a
kernel bug, after all. Hard t
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.18-rc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396213
Title:
LVM VG is not activated during system boot
To manage noti
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
https://www.redhat.com/archives/linux
MegaBrutal, could you please test the latest upstream kernel available
from the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream dev
apport information
** Tags added: apport-collected
** Description changed:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/
I've generated the report and I'm trying to use what the linked tutorial
suggests:
$ ubuntu-bug -c 1396213.apport -u 1396213
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
ubuntu-bug: error: -u/--update-bug option cannot be used together with
options for a new
MegaBrutal, could you please provide the requested information following
https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup
?
** Tags added: regression-release
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (U
I can't run apport-collect because Lynx doesn't send HTTP referrer to
Launchpad, and I don't wish to go through the ordeal of finding out how
to change this behaviour.
Furthermore, I'm not sure what logs would be collected. I can provide
logs you need manually, if you ask for them.
--
You receiv
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396213
Title:
LVM VG is not activated during system boot
To manage notifications
29 matches
Mail list logo
