[Bug 1163406] Re: Device-mapper initialized before hardware-raid during system boot

[Steve Langasek]

>     UUID=[uuid-like-displayed-by-lvdisplay] /mnt/images ext4 default 0
1

Well, first off you should never do this.  Owing to LVM snapshotting,
UUIDs are not guaranteed to be unique for LVs.  You should reference
this via its device mapper path instead.

But beyond this, I don't see any explanation for the behavior you're
experiencing.  /lib/udev/rules.d/85-lvm2.rules runs for each block
device it finds of ID_FS_TYPE=LVM2_member, and calls 'vgchange -ay' each
time to ensure the volume group gets fully assembled on boot.

Please attach /var/log/udev from the affected system.

** Package changed: upstart (Ubuntu) => lvm2 (Ubuntu)

** Changed in: lvm2 (Ubuntu)
       Status: Confirmed => Incomplete

** No longer affects: upstart

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

Title:
  Device-mapper initialized before hardware-raid during system boot

Status in “lvm2” package in Ubuntu:
  Incomplete

Bug description:
  I set up a LVM on a freshly installed Ubuntu Server 12.04.2 LTS 64
  Bit. If I locate the LVM's physical volume on a partition residing on
  a hardware RAID-1 (dev/sdb), the logical volumes are in NOT available
  state after system start and have to be activated by the command
  vgchange -ay. As soon I locate the LVM's physical volume on the non-
  raid boot-drive (/dev/sda), the logical volumes are activated on
  system start and can even be mounted by an entry in /etc/fstab.

  Due to this behaviour I assume, that the hardware-raid is initialized
  AFTER the device-mapper is loaded. This way the LVM's logical volumes
  on the raid can not be initialized during system start. This is also
  indicated by the following logfile entry:

  /var/log/syslog
  ...
  Mar 29 15:02:01 ikarus kernel: [    0.470265] device-mapper: uevent: version 1.0.3
  Mar 29 15:02:01 ikarus kernel: [    0.470297] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel at redhat.com
  ...
  Mar 29 15:02:01 ikarus kernel: [    0.782506] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
  Mar 29 15:02:01 ikarus kernel: [    0.782937] 3w-9xxx: scsi6: ERROR: (0x06:0x000D): PCI Abort: clearing.
  Mar 29 15:02:01 ikarus kernel: [    0.812967] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
  ...

  System Configuration:
  -    Ubuntu Server 12.04.2 64 Bit
  -    Intel Core i5-3450, 16G RAM
  -    128 GB SSD as System disk (/dev/sda)
  -    3ware 9650SE-4LPML Raid-Controller, RAID1 with 2 TB capacity (/dev/sdb)
  -    Bootloader and root-partition located on /dev/sda
  -    For /var and /tmp two primary partitions on /dev/sdb are used
  -    The third (extended) partition of /dev/sdb is used as physical volume for the LVM
  -    The LVM only stores user-data, no system related information

  Steps leading to issue:
  -    Installed Ubuntu Server 12.04.2 64 Bit on /dev/sda without setting up LVM
  -    Partitioned /dev/sdb using fdisk and set partition type to '8e'
  -    Installed lvm: apt-get install lvm2
  -    Set up lvm with four logical volumes (physical volume residing on /dev/sdb5)
  -    Formatted logical volumes with ext4 using mkfs
  -    Command lvdisplay shows all logical volumes as available
  -    Created mount points for logical volumes
  -    Manual mount of logical volumes works
  -    Edited /etc/fstab to automatically mount logical volumes - example for one logical volume:
      UUID=[uuid-like-displayed-by-lvdisplay] /mnt/images ext4 default 0 1
  -   Rebooted system

  Problem:
  -   System displays the following message when booting up and waits for user action to skip mount commands:
  -    The disk drive for /mnt/images is not ready yet or present.
  -    Continue to wait, or press S to skip mounting or M for manual recovery
  -    When skipped the same message is shown for the next logical volume mount point
  -    After skipping the last mount point boot up proceeds until login screen
  -    When login in the logical volumes are not mounted and in status "NOT available" according to lvdisplay
      
  This bug is related to the following tread in the Ubuntu-Forum:
  http://ubuntuforums.org/showthread.php?t=2130232
  If I have a solution for this issue I will update the tread to make the information public to other Ubuntu-users.

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