Thanks for the response. The bug was reported from a different PC so the (automatically generated) attachments are not relevant.
I built this PC unsuccessfully dozens of times - very frustrating. I usually got the initramfs shell. In the end what worked was only installing to a single / partition (now md0) and adding the swap and /home by hand to this minimal working system. The PC with the fault has been successfully built by hand. I have given you as much info about the errors are as I can - md0 is assembled incorrectly. In the initramfs shell, sdb, sda1 and sdb1 share a single UUID. iirc, sda had its own UUID (#2), sda2 and sdb2 have a third UUID. sda3 and sdb3 have a forth UUID. 2 physical devices and 6 logical devices are all identified by only 4 UUID's. Either the ubuntu text installer is goofing up the UUID's so mdadm can't assemble the raid devices or blkid id reporting the UUID's incorrectly. mdadm appears to be intentionally duplicating UUID's on component partitions. Duplicating an identifier that is intended to be unique is just wrong. No wonder it does not work Thanks. Deano ________________________________ From: Surbhi Palande <[email protected]> To: [email protected] Sent: Wed, September 15, 2010 6:31:23 AM Subject: [Bug 627056] Re: new install to raid0 array does not boot @Dean, what happens when you boot (do you get at any initramfs prompt or maintenance prompt)? How did you attach all the .txt files? (from a live cd or something?) Your dmesg says: Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=UUID=94bb4d17-cb02-45e4-ba2e-633f2ac41c45 ro quiet splash. Can you please try: the command line argument "debug" instead of "quiet"? and let us know what the errors are? ** Changed in: mdadm (Ubuntu) Status: New => Incomplete -- new install to raid0 array does not boot https://bugs.launchpad.net/bugs/627056 You received this bug notification because you are a direct subscriber of the bug. Status in “mdadm” package in Ubuntu: Incomplete Bug description: Binary package hint: mdadm Using the text installer, I installed 10.04 onto two 80G drives with the following partitioning scheme sda: sda1: 2G sda2: 5G sda3: remainder sdb: sdb3: remainder sdb2: 5G sdb1: 2G *the partitions are intentionally inverted in their physical order on the drive The following raid0 devices are then created: md0=sda1+sda2 - swap md1=sda2+sdb2 - / - ext4 md2=sda3+sdb3 - /home - ext4 This install works correctly. When I attempt to do the same thing using two 500G drives instead, the resulting machine will not boot and drops to the initramfs shell. The md0 device is assembled from sda1+sdb not sda1+sdb1 as specified. All partitions on sdb are absorbed into the odd, mismatched md0 whose size is reported as 500G instead of 4G. Grub2 is installed on sdb by the installer. At this time blkid reports that md0, sda1 and sdb have the same UUID and that my boot device of md1 can not be found by UUID. I am not sure if the raid packages or the grub2 installer is malfunctioning to break the partitioning scheme. As an aside, whose idea was it to re-use UUID's for raid array partitions? Also, why does mdadm refer to an md device by the UUID of the partitions contained within it instead of the one that the system uses to mount it? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mdadm 2.6.7.1-1ubuntu15 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Mon Aug 30 13:55:24 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) 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.sda3: Error: command ['/sbin/mdadm', '-E', '/dev/sda3'] failed with exit code 1: mdadm: cannot open /dev/sda3: 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.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.sdb2: Error: command ['/sbin/mdadm', '-E', '/dev/sdb2'] failed with exit code 1: mdadm: cannot open /dev/sdb2: Permission denied MDadmExamine.dev.sdb3: Error: command ['/sbin/mdadm', '-E', '/dev/sdb3'] failed with exit code 1: mdadm: cannot open /dev/sdb3: Permission denied MDadmExamine.dev.sdb5: Error: command ['/sbin/mdadm', '-E', '/dev/sdb5'] failed with exit code 1: mdadm: cannot open /dev/sdb5: 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 MDadmExamine.dev.sdc2: Error: command ['/sbin/mdadm', '-E', '/dev/sdc2'] failed with exit code 1: mdadm: cannot open /dev/sdc2: Permission denied MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=UUID=94bb4d17-cb02-45e4-ba2e-633f2ac41c45 ro quiet splash ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: mdadm dmi.bios.date: 04/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd04/14/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785-M:rvrRevX.0x: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 unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/627056/+subscribe -- new install to raid0 array does not boot https://bugs.launchpad.net/bugs/627056 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
