← Back to team overview

touch-packages team mailing list archive

[Bug 1393899] [NEW] LVM devices not created during boot

 

Public bug reported:

During bootup, I get errors to say that the kernal cannot mount the
filesystems that are on an LVM. When I choose "M" for manual recovery,
it shows that no LVM devices have been created under /dev/mapper/* or
/dev/dm-*

It is easy to fix, and resume the boot by running "vgchange -v -a y" but
it is annoying that the system will not boot without manual
intervention, and if it happened to a less knowlegable user they would
be stuck.

On my system the root, and other volumes necessary for the system to run
are setup as normal partions on a small ssd. I have a large hard disc
setup as an LVM phisycal volume that contains logical volumes for media
files and the like that are not necesary for boot or basic system
operation, but are wanted for deskop usage.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lvm2 2.02.98-6ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Nov 18 18:23:45 2014
InstallationDate: Installed on 2014-10-18 (31 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lvm2 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1393899

Title:
  LVM devices not created during boot

Status in “lvm2” package in Ubuntu:
  New

Bug description:
  During bootup, I get errors to say that the kernal cannot mount the
  filesystems that are on an LVM. When I choose "M" for manual recovery,
  it shows that no LVM devices have been created under /dev/mapper/* or
  /dev/dm-*

  It is easy to fix, and resume the boot by running "vgchange -v -a y"
  but it is annoying that the system will not boot without manual
  intervention, and if it happened to a less knowlegable user they would
  be stuck.

  On my system the root, and other volumes necessary for the system to
  run are setup as normal partions on a small ssd. I have a large hard
  disc setup as an LVM phisycal volume that contains logical volumes for
  media files and the like that are not necesary for boot or basic
  system operation, but are wanted for deskop usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Nov 18 18:23:45 2014
  InstallationDate: Installed on 2014-10-18 (31 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1393899/+subscriptions


Follow ups

References