[Bug 652327] Re: mdadm update is scaring me: "YOUR SYSTEM IS NOW UNBOOTABLE!"

[Craig Hansen]

On many of my systems, the assignment of drives to letters depends on a
number of unpredictable factors, so it's much safer to use the UUID to
define arrays than /dev/sd[a-z]1.

Running "sudo mdadm --detail --scan" usually gets you pretty good ARRAY
lines to put into your mdadm.conf file.

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

Title:
  mdadm update is scaring me: "YOUR SYSTEM IS NOW UNBOOTABLE!"

Status in “mdadm” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mdadm

  I just updated mdadm, during update it gave me a scary warning:
  W: mdadm: the array /dev/md0 with UUID 21fd4b98:0c4a255f:d4c030d5:a9b8b27a
  W: mdadm: is currently active, but it is not listed in mdadm.conf. if
  W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
  W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
  W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.

  I rebooted my system without making changes; nothing happened....
  raid array md0 is is running:
  cat /proc/mdstat
  Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
  md0 : active raid1 sdb1[0] sdc1[1]
        471041728 blocks [2/2] [UU]

  unused devices: <none>

  This is my mdadm.conf:
  # mdadm.conf
  #
  # Please refer to mdadm.conf(5) for information about this file.
  #

  # by default, scan all partitions (/proc/partitions) for MD superblocks.
  # alternatively, specify devices to scan, using wildcards if desired.
  #DEVICE partitions
  DEVICE /dev/sdb1 /dev/sdc1

  # auto-create devices with Debian standard permissions
  CREATE owner=root group=disk mode=0660 auto=yes

  # automatically tag new arrays as belonging to the local system
  HOMEHOST <system>

  # instruct the monitoring daemon where to send mail alerts
  MAILADDR root

  # definitions of existing MD arrays
  ARRAY /dev/md0 devices=/dev/sdb1,/dev/sdc1

  # This file was auto-generated on Wed, 03 Jun 2009 03:42:25 +0200
  # by mkconf $Id$

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: mdadm 2.6.7.1-1ubuntu16
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu Sep 30 20:50:59 2010
  EcryptfsInUse: Yes
  MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: cannot open /dev/sda: Permission denied
  MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: cannot open /dev/sda1: Permission denied
  MDadmExamine.dev.sda2: Error: command ['/sbin/mdadm', '-E', '/dev/sda2'] failed with exit code 1: mdadm: cannot open /dev/sda2: Permission denied
  MDadmExamine.dev.sda5: Error: command ['/sbin/mdadm', '-E', '/dev/sda5'] failed with exit code 1: mdadm: cannot open /dev/sda5: Permission denied
  MDadmExamine.dev.sda6: Error: command ['/sbin/mdadm', '-E', '/dev/sda6'] failed with exit code 1: mdadm: cannot open /dev/sda6: Permission denied
  MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: cannot open /dev/sdb: Permission denied
  MDadmExamine.dev.sdb1: Error: command ['/sbin/mdadm', '-E', '/dev/sdb1'] failed with exit code 1: mdadm: cannot open /dev/sdb1: Permission denied
  MDadmExamine.dev.sdc: Error: command ['/sbin/mdadm', '-E', '/dev/sdc'] failed with exit code 1: mdadm: cannot open /dev/sdc: Permission denied
  MDadmExamine.dev.sdc1: Error: command ['/sbin/mdadm', '-E', '/dev/sdc1'] failed with exit code 1: mdadm: cannot open /dev/sdc1: Permission denied
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=190948a5-a920-409e-aea4-7a0e94974738 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcMDstat:
   Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
   md0 : active raid1 sdb1[0] sdc1[1]
         471041728 blocks [2/2] [UU]

   unused devices: <none>
  SourcePackage: mdadm
  dmi.bios.date: 03/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd03/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'

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