[Bug 1285312] Re: Setting up mdadm (3.2.5-5ubuntu3) freezes after calling grub1's update-grub from postinst

[dino99]

No more supported ubuntu versions  use grub legacy, and the affected
ones here have received fixes. Grub legacy upstream is also stopped,
only receiving possible random fixes locally

** Changed in: grub (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: mdadm
       Status: New => Invalid

** Changed in: grub
       Status: New => Invalid

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

Title:
  Setting up mdadm (3.2.5-5ubuntu3) freezes after calling grub1's
  update-grub from postinst

Status in GRand Unified Bootloader:
  Invalid
Status in mdadm - Tool for managing linux software RAID arrays.:
  Invalid
Status in grub package in Ubuntu:
  Invalid
Status in mdadm package in Ubuntu:
  Fix Released
Status in grub source package in Trusty:
  Won't Fix
Status in mdadm source package in Trusty:
  Fix Released
Status in mdadm source package in Utopic:
  Fix Released

Bug description:
  [Impact]

   * Upgrading to mdadm/trusty package fails, if the machine is using
  grub1

  [Test Case]

   * Install grub1 - package grub (I've installed 8.04 LTS from old-
  releases.ubuntu.com first and upgraded to each consecutive LTS release
  up to 14.04)

   * Upgrading to mdadm/trusty should not stall & should not execute
  grub1's update-grub & should succeed normally

  [Regression Potential]

   * This bug does not affect installations that use grub2, default
  since 9.04

  [Other Info]

  ========================= ATTENTION! =========================
  All users who have not yet upgraded to grub2 are urged to upgrade following instructions at:
             https://help.ubuntu.com/community/Grub2/Upgrading
  ========================= ATTENTION! =========================

  [Original bug report]

  I'm unable to upgrade my Dell PowerEdge T105 from Saucy to Trusty
  because madm freezes during the update grub process during setup. This
  system was originally installed in April of 2009 with Hardy 8.04 and
  has successfully upgraded from revision to revision since then. This
  is the first time madm has failed to upgrade.

  Yesterday evening I ran do-release-upgrade -d and it froze at:

  Setting up libdevmapper1.02.1:amd64 (2:1.02.77-6ubuntu2) ...
  Setting up libdevmapper-event1.02.1:amd64 (2:1.02.77-6ubuntu2) ...
  Setting up lvm2 (2.02.98-6ubuntu2) ...
  Installing new version of config file /etc/lvm/lvm.conf ...
  update-initramfs: deferring update (trigger activated)
  Setting up mdadm (3.2.5-5ubuntu3) ...
   Removing any system startup links for /etc/init.d/mdadm-raid ...
  update-initramfs: deferring update (trigger activated)
  update-grub is /usr/sbin/update-grub
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /boot/vmlinuz-3.13.0-12-generic
  Found kernel: /boot/vmlinuz-3.11.0-17-generic
  Found kernel: /boot/vmlinuz-3.11.0-15-generic
  Found kernel: /boot/vmlinuz-3.11.0-14-generic
  Found kernel: /boot/vmlinuz-3.11.0-12-generic
  Found kernel: /boot/vmlinuz-3.11.0-7-generic
  Found kernel: /boot/memtest86+.bin
  -- 0:trusty -- time-stamp -- Feb/25/14 17:04:19 --
  -- 0:trusty -- time-stamp -- Feb/25/14 17:11:58 --

  -- 0:trusty -- time-stamp -- Feb/25/14 17:14:00 --
  -- 0:trusty -- time-stamp -- Feb/25/14 17:27:48 --

  It sat there for about half an hour so I canceled the do-release-
  upgrade and tried to recover with the usual steps after cleaning out
  some stale kernels:

  root at kami:~# apt-get update
  [...] output removed
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
  root at kami:~# apt-get -f install
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
  root at kami:~# apt-get dist-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
  root at kami:~# sudo dpkg --configure -a
  Processing triggers for initramfs-tools (0.103ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-3.13.0-12-generic
  Setting up mdadm (3.2.5-5ubuntu3) ...
   Removing any system startup links for /etc/init.d/mdadm-raid ...
  update-initramfs: deferring update (trigger activated)
  update-grub is /usr/sbin/update-grub
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /boot/vmlinuz-3.13.0-12-generic
  Found kernel: /boot/vmlinuz-3.11.0-17-generic
  Found kernel: /boot/vmlinuz-3.11.0-15-generic
  Found kernel: /boot/memtest86+.bin

  At this point mdadm setup still just sits forever. If I hit Ctrl-C:

  ^Cdpkg: error processing package mdadm (--configure):
   subprocess installed post-installation script was interrupted
  Processing triggers for initramfs-tools (0.103ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-3.13.0-12-generic
  Errors were encountered while processing:
   mdadm
  root at kami:~#

  root at kami:~# fdisk -l /dev/sda

  Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x000918ae

     Device Boot      Start         End      Blocks   Id  System
  /dev/sda1   *          63    39070079    19535008+  fd  Linux raid autodetect
  /dev/sda2        39070080  1953520064   957224992+   5  Extended
  /dev/sda5        39070143    46877669     3903763+  fd  Linux raid autodetect
  /dev/sda6        46877733  1953520064   953321166   fd  Linux raid autodetect

  root at kami:~# fdisk -l /dev/sdb

  Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
  255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x000455d6

     Device Boot      Start         End      Blocks   Id  System
  /dev/sdb1   *          63    39070079    19535008+  fd  Linux raid autodetect
  /dev/sdb2        39070080  1953520064   957224992+   5  Extended
  /dev/sdb5        39070143    46877669     3903763+  fd  Linux raid autodetect
  /dev/sdb6        46877733  1953520064   953321166   fd  Linux raid autodetect

  root at kami:~# cat /proc/mdstat
  Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
  md2 : active raid1 sdb6[1] sda6[0]
        953321088 blocks [2/2] [UU]

  md0 : active raid1 sdb1[1] sda1[0]
        19534912 blocks [2/2] [UU]

  md1 : active raid1 sdb5[1] sda5[0]
        3903680 blocks [2/2] [UU]

  unused devices: <none>

  root at kami:~# vgscan
    Reading all physical volumes.  This may take a while...
    Found volume group "KamiVG01" using metadata type lvm2

  root at kami:~# lvscan
    ACTIVE            '/dev/KamiVG01/chippoke' [50.00 GiB] inherit
    ACTIVE            '/dev/KamiVG01/nas-office' [850.00 GiB] inherit

  (additional data and logs will be added soon)

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1285312/+subscriptions