[Bug 615186] Re: md_d0 array fabricated, prevents mounting md0 partitions

Christian Hudon 615186 at bugs.launchpad.net
Mon Aug 8 16:49:40 UTC 2011


Any reason why the following patches haven't been folded into Ubuntu
10.04 LTS? I had a similar problem (create md0 RAID1 array with one
device missing, after reboot it comes up as md_d0 instead) and these
patches (installed from the two packages in the PPA) fix that. It would
have saved me a couple of hours of work.

-- 
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/615186

Title:
  md_d0 array fabricated, prevents mounting md0 partitions

Status in “mdadm” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: mdadm

  I've had this problem happen a few times in the past with previous versions of Ubuntu. (I'm now on Lucid) I forget how I got rid of it then. What happened now is a just added a couple of eSATA disks (/dev/sdd and /dev/sde) (they function like regular SATA disks.) I had setup my /dev/md0 array from /dev/sdb and /dev/sdc months ago. Now all of a sudden it fabricates a /dev/md_d0 array somehow (based on /dev/md0p1) and the system fails to mount /dev/md0p1. This is the output from cat /proc/mdstat:
  mike at hegemon:~$ cat /proc/mdstat
  Personalities : [linear] [raid1] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] 
  md_d0 : inactive md0p1[1](S)
        245111616 blocks
         
  md0 : active raid1 sdc[1] sdb[0]
        245117312 blocks [2/2] [UU]
        
  unused devices: <none>
  My workaround for now is to manually remove /md_d0 every time I reboot the system as follows:
  mike at hegemon:~$ sudo mdadm --manage --stop /dev/md_d0
  mdadm: stopped /dev/md_d0
  I can then run mount -a and it successfully mounts /dev/md0p1
  I get this output after deleting the array, I believe it is the same as before I delete it:
  mike at hegemon:~$ sudo ls /dev/md*
  /dev/md0    /dev/md_d0	  /dev/md_d0p2	/dev/md_d0p4
  /dev/md0p1  /dev/md_d0p1  /dev/md_d0p3

  /dev/md:
  d0  d0p1  d0p2	d0p3  d0p4

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: mdadm 2.6.7.1-1ubuntu15
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic x86_64
  Architecture: amd64
  Date: Sun Aug  8 21:05:33 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda.
  MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda1.
  MDadmExamine.dev.sda2: Error: command ['/sbin/mdadm', '-E', '/dev/sda2'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda2.
  MDadmExamine.dev.sda3: Error: command ['/sbin/mdadm', '-E', '/dev/sda3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda3.
  MDadmExamine.dev.sda5: Error: command ['/sbin/mdadm', '-E', '/dev/sda5'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda5.
  MDadmExamine.dev.sdd: Error: command ['/sbin/mdadm', '-E', '/dev/sdd'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd.
  MDadmExamine.dev.sdd1: Error: command ['/sbin/mdadm', '-E', '/dev/sdd1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd1.
  MDadmExamine.dev.sde: Error: command ['/sbin/mdadm', '-E', '/dev/sde'] failed with exit code 1: mdadm: No md superblock detected on /dev/sde.
  MDadmExamine.dev.sde1: Error: command ['/sbin/mdadm', '-E', '/dev/sde1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sde1.
  MachineType: Gigabyte Technology Co., Ltd. 965P-S3
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=6a13dd7d-05c7-4f03-af14-031d3821217b ro quiet splash
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcMDstat:
   Personalities : [linear] [raid1] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] 
   md0 : active raid1 sdc[1] sdb[0]
         245117312 blocks [2/2] [UU]
         
   unused devices: <none>
  SourcePackage: mdadm
  dmi.bios.date: 06/25/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: 965P-S3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-S3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-S3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 965P-S3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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/615186/+subscriptions




More information about the foundations-bugs mailing list