Similar, but not the same. In my case, an error occurs IF the array has been named, and I don't see this mentioned in those two bugs.
I've tried using the exact same array, the only difference it being named or unnamed and if it's named it fails, but when not, it works flawlessly. I've been using it ever since without error. Could you please explain what the workaround for those two bugs does? ** Description changed: Binary package hint: mdadm I installed Ubuntu 10.04 on a software (throughout the description I'm talking about softraid) raid1 array, with the alternate installer. It boots, it works, all's well. Now I wanted to create some new raid arrays and I experience the following: If I create it with the 1.2 superblock AND I give it a name "#mdadm --create /dev/md1 --metadata=1.2 --name=TEST --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1 -> the array is created - "#mdadm -Es | grep md1 >> /etc/mdadm/mdadm.conf" -> the array gets the name "TEST" and device name "/dev/md/TEST" and upon doesn't start. + "#mdadm -Es | grep md1 >> /etc/mdadm/mdadm.conf" -> the array gets the name "TEST" and device name "/dev/md/TEST" and upon reboot doesn't start. Instead an inactive array called md_d127 (further arrays are named md_d126, md_d125) appears, in /proc/mdstat grabbing one of the components. Trying to assemble the created array "#mdadm --assemble --name=TEST" (or --assemble /dev/md/TEST) results in a degraded array with only the other component in it. Stopping the md_d127 array and then assembling the TEST array usually works, but last time I tried it failed. The following device files are present in /dev (md0 has the system on it): # ls /dev/md* /dev/md0 /dev/md_TEST1 /dev/md_TEST3 /dev/md_d127 /dev/md_TEST2 /dev/md_TEST4 /dev/md: TEST TEST1 TEST2 TEST3 TEST4 If I create a default raid1 (I've tried naming it too, but I guess that's unavailable, with a v0.9 superblock), or one with a 1.2 superblock, but no name given, they all get assembled upon reboot. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mdadm 2.6.7.1-1ubuntu15 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 Date: Thu May 6 01:45:07 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) 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.sda3: Error: command ['/sbin/mdadm', '-E', '/dev/sda3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda3. MDadmExamine.dev.sda4: Error: command ['/sbin/mdadm', '-E', '/dev/sda4'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda4. MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb. MDadmExamine.dev.sdb3: Error: command ['/sbin/mdadm', '-E', '/dev/sdb3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb3. MDadmExamine.dev.sdb4: Error: command ['/sbin/mdadm', '-E', '/dev/sdb4'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb4. MachineType: Gigabyte Technology Co., Ltd. GA-MA78GPM-DS2H ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=88e1b6ce-dd96-4f24-b899-48bca4256fc7 ro quiet splash ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: mdadm dmi.bios.date: 04/14/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-MA78GPM-DS2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/14/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GPM-DS2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GPM-DS2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA78GPM-DS2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab' -- if array is given a name, a strange inactive md device appears instead of the one created upon reboot https://bugs.launchpad.net/bugs/576147 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
