touch-packages team mailing list archive

[cracket <931929@xxxxxxxxxxxxxxxxxx>]

Here same problem 3 years after releasing new version of Ubuntu. Today upgrading from 10.04 LTS to 12.04. Apart broken grub2 update, which I already worked around - system does not boot any more.  System configuration:   / at REVO Drive PCIe SSD, visible as fake raid (2x 115 GB) sdb & sdc, x86_64. Before upgrade in 10.04 it was recognised during boot as /dev/mapper/sil_biajabcecafc device, and root filesystem was mounted on it. 
Unfortunately after update to 12.04 LTS , and fixing broken grub2 "grub_xputs" failure from pendrive my system is still unusable, probably due to invalid/broken initrd/udevd:    
ALERT /dev/disk/by-uuid/3a11ac88-b86a-4500-a94a-737adf8b989e does not exist. 
Dropping to a shell!
And your hints are not very helpful, because my new initrd upgraded by fresh ubuntu installation contains only dmsetup and mdadm binaries. I would add dmraid happily to initrd if my first boot was successful! 

So problem #1 - how to create manually required device /dev/mapper/sil_biajabcecafc  from initrd
Problem #2 - how to update broken installation 12.04 so it would have proper fakeraid autodetection in initrd
Problem #3 - how to inform people willing to install/update to 12.04 that they will have serious problems?

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

Title:
  root on RAID:0 fails to boot

Status in dmraid:
  New
Status in tools for generating an initramfs:
  Confirmed
Status in udev - /dev/ management daemon:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Booting from RAID is often broken after upgrades or fresh
  installations of Ubuntu.

  initramfs is not activating RAID devices.

  Steps to reproduce:
  1. Upgrade or Install Ubuntu on a RAID
  2. Reboot
  3. Observe failure to find root drive and drop to busybox

  To work around this, when given the busybox prompt enter:

  dmraid -ay

  Verify that all of your raid devices are initialized, then enter:

  exit

  Booting should then continue.

  See comment #2 for a persistent (rebootable) workaround.

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