[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#752381: marked as done (initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM)

Your message dated Sun, 18 Jan 2015 15:25:52 +0000
with message-id <1421594752.31046.154.camel@decadent.org.uk>
and subject line Re: initramfs-tools: does not activate logical volume - two obversations
has caused the Debian Bug report #752381,
regarding initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
752381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752381
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: initramfs-tools
Version: 0.115~bpo70+1
Severity: important

What did I do:

Today I installed backports version of open-vm-dkms and upgraded to most
recent 3.14 backport kernel from a previous version of it I installed due
to using BTRFS with skinny meta data on one partition.


Current results:

After this the machine failed to boot. It didn´t find the root filesystem
by its UUID. I typed "vgchange -ay" in initramfs and then Ctrl-D and then
it booted. This used to work without manual interaction before.

To make it boot consistently I added as a work-around:

mondschein:~> cat /etc/initramfs-tools/scripts/local-top/lvm-manual 
#!/bin/sh

PREREQ="lvm"
prereqs()
{
        echo $PREREQ
}

case $1 in
prereqs)
        prereqs
        exit 0;
esac

. /scripts/functions

log_begin_msg "Activitating logical volumes (as it does not seem to be done automatically at the moment)."

vgchange -ay

log_end_msg


which I had handy as I use a similar workaround for enabling BTRFS RAID 1
boot on my laptop, which does not work as default.

This worked after actually chmod'ing +x it :)


Expected results:

Machine boots without manual adaptions to InitRD.


Additional information:

The machine still boots from an Ext4 filesystem. The BTRFS filesystem is
mounted later on by fstab.

There is a lvm and a BTRFS script in InitRD already, but the lvm script did
not seem to work properly:

mondschein:~> lsinitramfs /boot/initrd.img-3.14-0.bpo.1-686-pae | grep script
scripts
scripts/functions
scripts/nfs
scripts/init-bottom
scripts/init-bottom/udev
scripts/init-bottom/ORDER
scripts/local-premount
scripts/local-premount/btrfs
scripts/local-premount/resume
scripts/local-premount/ORDER
scripts/local
scripts/local-top
scripts/local-top/lvm-manual
scripts/local-top/lvm2
scripts/local-top/ORDER
scripts/init-top
scripts/init-top/blacklist
scripts/init-top/keymap
scripts/init-top/udev
scripts/init-top/ORDER
scripts/init-top/all_generic_ide


I thought it was an update to initramfs-tools causing this, but these have
been upgraded last week already:

Start-Date: 2014-06-12  11:46:49
Commandline: apt-get install -t wheezy-backports linux-image-3.14-0.bpo.1-686-pae linux-headers-3.14-0.bpo.1-686-pae btrfs-tools
Install: linux-headers-3.14-0.bpo.1-686-pae:i386 (3.14.5-1~bpo70+1), linux-image-3.14-0.bpo.1-686-pae:i386 (3.14.5-1~bpo70+1), linux-compiler-gcc-4.6-x
86:i386 (3.14.5-1~bpo70+1, automatic), btrfs-tools:i386 (3.14.1-1~bpo70+1), liblzo2-2:i386 (2.06-1, automatic), linux-kbuild-3.14:i386 (3.14-1~bpo70+1,
 automatic), linux-headers-3.14-0.bpo.1-common:i386 (3.14.5-1~bpo70+1, automatic)
Upgrade: initramfs-tools:i386 (0.109.1, 0.115~bpo70+1)
End-Date: 2014-06-12  11:48:06


And there rebooting the machine worked out of the box.

So maybe something in open-vm-tools or open-vm-dkms from wheezy-backports
interacts with InitRD script stuff in a way that breaks boot. But OTOH
I see no open-vm related scripts in above lsinitramfs output.

Thanks,
Martin

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 13M Jun 23 09:58 /boot/initrd.img-3.14-0.bpo.1-686-pae
-rw-r--r-- 1 root root 11M Jun 23 09:58 /boot/initrd.img-3.2.0-4-686-pae
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.14-0.bpo.1-686-pae root=UUID=a8e69cdf-f016-4f07-8d2d-d975881d2095 ro

-- resume
RESUME=/dev/sda2
-- /proc/filesystems
	btrfs
	ext3
	ext2
	ext4

-- lsmod
Module                  Size  Used by
coretemp               12734  0 
crc32_pclmul           12809  0 
crc32c_intel           12624  0 
vmw_balloon            12502  0 
irda                   90367  0 
parport_pc             25991  0 
crc_ccitt              12331  1 irda
parport                35207  1 parport_pc
aesni_intel            17934  0 
vmwgfx                142296  0 
ttm                    59829  1 vmwgfx
aes_i586               16647  1 aesni_intel
xts                    12583  1 aesni_intel
lrw                    12686  1 aesni_intel
gf128mul               12834  2 lrw,xts
ablk_helper            12508  1 aesni_intel
cryptd                 14125  1 ablk_helper
psmouse                85040  0 
drm                   198349  2 ttm,vmwgfx
evdev                  17172  0 
serio_raw              12737  0 
pcspkr                 12531  0 
i2c_piix4              12592  0 
i2c_core               23454  2 drm,i2c_piix4
battery                12949  0 
processor              27575  0 
button                 12824  0 
thermal_sys            22946  1 processor
ac                     12588  0 
shpchp                 30673  0 
ext4                  454558  4 
crc16                  12327  1 ext4
mbcache                12938  1 ext4
jbd2                   77040  1 ext4
crc32c                 12576  1 
btrfs                 852360  1 
xor                    25716  1 btrfs
raid6_pq               95207  1 btrfs
dm_mod                 78695  20 
sg                     25573  0 
sd_mod                 43628  5 
sr_mod                 21563  0 
crc_t10dif             12399  1 sd_mod
crct10dif_common       12340  1 crc_t10dif
cdrom                  34765  1 sr_mod
ata_generic            12450  0 
floppy                 52004  0 
pcnet32                34990  0 
ata_piix               29409  0 
libata                153279  2 ata_generic,ata_piix
mii                    12595  1 pcnet32
BusLogic               25480  3 
scsi_mod              155492  5 sg,BusLogic,libata,sd_mod,sr_mod

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
do_initrd = yes
do_bootloader = no


-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
btrfs
busybox
dmsetup
keymap
klibc
kmod
lvm2
resume
thermal
udev
vmxnet


-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.14-0.bpo.1-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initramfs-tools depends on:
ii  cpio               2.11+dfsg-0.1
ii  klibc-utils        2.0.1-3.1
ii  kmod               9-3
ii  module-init-tools  9-3
ii  udev               175-7.2

Versions of packages initramfs-tools recommends:
ii  busybox  1:1.20.0-7

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.0-1

-- no debconf information

--- End Message ---
--- Begin Message --- 
Control: notfound -1 0.115~bpo70+1

On Mon, 23 Jun 2014 10:34:02 +0200 Martin Steigerwald <Martin@lichtvoll.de> wrote:
> Hi!
> 
> I bzr diff on /boot/grub/grub.cfg revealed – but already from last week as I 
> upgraded to the newer backport initramfs-tools, where booting still worked
> okay:
> 
>  menuentry 'Debian GNU/Linux, mit Linux 3.2.0-4-686-pae' --class debian --
> class gnu-linux --class gnu --class os {
>         load_video
>         insmod gzio
> @@ -67,7 +90,7 @@
>         set root='(hd0,msdos1)'
>         search --no-floppy --fs-uuid --set=root [UUID]
>         echo    'Linux 3.2.0-4-686-pae wird geladen …'
> -       linux   /vmlinuz-3.2.0-4-686-pae root=/dev/mapper/mondschein-debian ro  
> +       linux   /vmlinuz-3.2.0-4-686-pae root=UUID=[UUID ro  
>         echo    'Initiale Ramdisk wird geladen …'
>         initrd  /initrd.img-3.2.0-4-686-pae
>  }
[...]

The 'UUID=...' syntax is not supported for root on an LV.  You *must*
use the /dev/mapper device name so that the lvm2 script can work out
which VG to activate.  (It is not safe in general to activate all
visible VGs.)

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: