[Bug 1421877] Re: boot fails with lvm root device in /dev/mapper not found after updates from proposed

[astro]

Hi Philip,

The system would not boot with any kernels with the message gave up waiting
for root device /dev/mapper/sysvg-lvroot1

>From the initramfs prompt there was no mapper listed under /dev but I could
mount  /dev/sysvg/lvroot1 in /root. However exiting the shell gave a kernel
panic. But I am not sure if I was supposed to bind dev, dev/pts, sys and or
proc before.

The problem is I don't have a copy of the original grub.cfg (I did not
think of doing that) since I have cleaned up the system by merging root
with a lvm snapshot  and force reinstalled the previous kernel which caused
grub.cfg to be overwritten. However grub.cfg is the only file that can have
caused the problem as it is the only difference under /boot (the only place
used before mounting the root device) except for the newer kernel (but I
could not boot any of the previous kernels so the newer kernel should not
have been the problem).

Unfortunately I cannot break my system again at the moment so I cannot test
it.
If the proposed updates get accepted, my system might break again. I will
try and provide more info (grub.cfg) if this happens.

Thank you,


On Mon, Feb 16, 2015 at 2:34 PM, Phillip Susi <psusi at ubuntu.com> wrote:

> What do you mean you could not find the /dev/mapper entry?
> /dev/sysvg/lvroot1 should just be a symlink to /dev/mapper/sysvg-
> lvroot1.  If you mount it in /root and exit from the shell does the
> system boot up normally?  If you suspect something changed in grub.cfg (
> and I don't see any reason to think that ), it would be helpful to
> attach a copy for analysis.
>
>
> ** Changed in: grub2 (Ubuntu)
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1421877
>
> Title:
>   boot fails with lvm root device in /dev/mapper not found after updates
>   from proposed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1421877/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1421877

Title:
  boot fails with lvm root device in /dev/mapper not found after updates
  from proposed

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  System:  Ubuntu 14.04 64 bits
  I have run a packages update/upgrade with synaptic. (Note that I had proposed-update repo enabled).
  Among other things a new kernel was installed and libc-bin was updated both likely from proposed-update since I didn't see them in my other box which doesn't use this source  (see attached dpkg.log for full list of recently installed packages. The culprit is probably at the end of that list).

  After the upgrade, I rebooted the system.

  I got the initramfs prompt with an error message saying that it gave up waiting for root devive /dev/mapper/sysvg-lvroot1
  I could not find the mapper entry under /dev but I could find /dev/sysvg/lvroot1 and mount it alright from the busybox prompt.

  Tried booting with 2 previous kernels to no avail: same problem with
  root device even though previous kernels worked fine.

  I booted from live usb, chrooted my ubuntu, merged my 10 days old
  sysvg-lvroot1 lvm snapshot, deleted last kernel from /boot (from last
  update)  and forced reinstalled previous kernel. Then I could boot
  alright and I have disabled proposed-update.

  The problem was with all kernels, hence the culprit is likely grub.cfg
  which is updated at each kernel update.  Between my previous snapshots
  and today failed boot something must have changed on my system which
  has resulted in the grub-mkconfig (or whatever tool is called to write
  grub.cfg when kernel is updated) producing a wrong config.

  Here is a filtered (I have removed what I think is irrelevant, the
  full list is in attachment) list of the packages last installed:

  bsdutils libblkid1 libc-bin libmount1 libuuid1 linux-generic linux-
  headers-3.13.0-46 linux-headers-3.13.0-46-generic linux-headers-
  generic linux-image-3.13.0-46-generic linux-image-
  extra-3.13.0-46-generic linux-image-generic linux-libc-dev mount
  ureadahead util-linux uuid-runtime

  I would say that blkid, uuid and mount are suspicious.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-03-24 (326 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323)
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Tags:  trusty
  Uname: Linux 3.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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