我刚刚完成了我的新的Ubuntu服务器10.4机器，用2×500 GB的SATA磁盘 – 我打算在raid1中configuration; 具体来说，这就是我在安装过程中所做的：
分区：
磁盘1 – sda：
sda1 – 500mb小学
sda2 – 99gb小学
sda3扩展
sda5 – 399gb扩展
磁盘2 – sdb：
SDB 1 – 500MB的主要
sdb2 – 99gb主要
sdb3扩展
sdb5 – 399gb扩展
数组：
md0 – sda1 + sdb1，raid1，ext2，/ boot
md1 – sda2 + sdb2，raid1，ext4，/
md2 – sda5 + sdb5，raid1，未格式化，在安装过程中未安装。
一切顺利，但是当我的新系统启动时，我就是这么看的：
/ was on /dev/md1 during installation UUID=cc1a0b10-dd66-4c88-9022-247bff6571a6 / ext4 errors=remount-ro 0 1 /boot was on /dev/md0 during installation UUID=7e37165c-ab1c-4bd4-a62b-8b98656fe1f1 /boot ext2 defaults 0 2 major minor blocks name 8 0 488386584 sda 8 1 487424 sda1 8 2 97265664 sda2 8 3 1 sda3 8 5 390631424 sda5 8 16 488386584 sdb 8 17 487424 sdb1 8 18 97265664 sdb2 8 19 1 sdb3 8 21 390631424 sdb5 9 2 390631360 md2 259 0 487424 md2p1 259 1 97265664 md2p2 259 2 1 md2p3 259 3 292876224 md2p5 9 1 97265600 md1 9 0 487360 md0
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 md2p1[0] 487360 blocks [2/1] [U_] md1 : active raid1 md2p2[0] 97265600 blocks [2/1] [U_] md2 : active raid1 sda[0] sdb[1] 390631360 blocks [2/2] [UU] [============>........] resync = 63.1% (246865856/390631360) finish=25.9min speed=92459K/sec unused devices: <none>
/dev/md0: Version : 00.90 Creation Time : Wed Jul 7 16:07:16 2010 Raid Level : raid1 Array Size : 487360 (476.02 MiB 499.06 MB) Used Dev Size : 487360 (476.02 MiB 499.06 MB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Wed Jul 7 17:13:58 2010 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : fefff930:8e4d661c:665cfb90:2bbaf5ad Events : 0.74 Number Major Minor RaidDevice State 0 259 0 0 active sync /dev/md2p1 1 0 0 1 removed
/dev/md1: Version : 00.90 Creation Time : Wed Jul 7 16:07:23 2010 Raid Level : raid1 Array Size : 97265600 (92.76 GiB 99.60 GB) Used Dev Size : 97265600 (92.76 GiB 99.60 GB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Wed Jul 7 17:38:19 2010 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 UUID : 68b86560:6150f422:6a741df7:3de5f08f Events : 0.460 Number Major Minor RaidDevice State 0 259 1 0 active sync /dev/md2p2 1 0 0 1 removed
/dev/md2: Version : 00.90 Creation Time : Wed Jul 7 16:07:31 2010 Raid Level : raid1 Array Size : 390631360 (372.54 GiB 400.01 GB) Used Dev Size : 390631360 (372.54 GiB 400.01 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Wed Jul 7 17:37:04 2010 State : active, resyncing Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Rebuild Status : 65% complete UUID : fc7dadbe:2230a995:814dd292:d7c4bf75 Events : 0.33 Number Major Minor RaidDevice State 0 8 0 0 active sync /dev/sda 1 8 16 1 active sync /dev/sdb
/dev/md2p1: Version : 00.90 Creation Time : Wed Jul 7 16:07:31 2010 Raid Level : raid1 Array Size : 487424 (476.08 MiB 499.12 MB) Used Dev Size : 390631360 (372.54 GiB 400.01 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Wed Jul 7 17:37:04 2010 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : fc7dadbe:2230a995:814dd292:d7c4bf75 Events : 0.33 Number Major Minor RaidDevice State 0 8 0 0 active sync /dev/sda 1 8 16 1 active sync /dev/sdb
/dev/md2p2: Version : 00.90 Creation Time : Wed Jul 7 16:07:31 2010 Raid Level : raid1 Array Size : 97265664 (92.76 GiB 99.60 GB) Used Dev Size : 390631360 (372.54 GiB 400.01 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Wed Jul 7 17:37:04 2010 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : fc7dadbe:2230a995:814dd292:d7c4bf75 Events : 0.33 Number Major Minor RaidDevice State 0 8 0 0 active sync /dev/sda 1 8 16 1 active sync /dev/sdb
/dev/md2p3: Version : 00.90 Creation Time : Wed Jul 7 16:07:31 2010 Raid Level : raid1 Array Size : 1 Used Dev Size : 390631360 (372.54 GiB 400.01 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Wed Jul 7 17:37:04 2010 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : fc7dadbe:2230a995:814dd292:d7c4bf75 Events : 0.33 Number Major Minor RaidDevice State 0 8 0 0 active sync /dev/sda 1 8 16 1 active sync /dev/sdb
/dev/md2p5: Version : 00.90 Creation Time : Wed Jul 7 16:07:31 2010 Raid Level : raid1 Array Size : 292876224 (279.31 GiB 299.91 GB) Used Dev Size : 390631360 (372.54 GiB 400.01 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Wed Jul 7 17:37:04 2010 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : fc7dadbe:2230a995:814dd292:d7c4bf75 Events : 0.33 Number Major Minor RaidDevice State 0 8 0 0 active sync /dev/sda 1 8 16 1 active sync /dev/sdb
看来，而不是构buildraid1数组：
md0 = sda1 + sdb1
md1 = sda2 + sdb2
像附加的“子arrays”已经build成：
md2p1 = sda1 + sdb1
md2p2 = sda2 + sdb2
这些“子数组”被configuration为md0和md1数组的一部分。 由于每个arrays只有2个磁盘（分区），因此mdadm会正确地从两个分区构buildmd2p1和md2p2，但是随后会启动主arrays：md0和md1，因为它们每个只包含1个“子arrays”。
现在我想知道 – 我做错了什么？ 或者，也许一切都好，我只是不明白这个configuration的一部分？ 但是看起来确实如此 – md0和md1明显标记为降级。 那么现在 – 我该怎么做才对？ 我必须重新安装系统吗？ 现在好了，就在安装之后，然后在我花了一些努力来configuration和保护之后。 但也许有一些很好的mdadm技巧只是为了使一切正常？ 请帮助:)谢谢！
cat /etc/mdadm/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 # 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 level=raid1 num-devices=2 UUID=fefff930:8e4d661c:665cfb90:2bbaf5ad ARRAY /dev/md1 level=raid1 num-devices=2 UUID=68b86560:6150f422:6a741df7:3de5f08f ARRAY /dev/md2 level=raid1 num-devices=2 UUID=fc7dadbe:2230a995:814dd292:d7c4bf75 # This file was auto-generated on Wed, 07 Jul 2010 16:18:30 +0200 # by mkconf $Id$
似乎是一个相当严重的错误：
修复将与Ubuntu 10.04.2一起发货 – 可能的解决方法，如启动板所述
https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/569900
我很难从这个问题试图得到一个适当的软RAID与500,1GB的硬盘驱动器运行。
所有作为bug的受害者所要做的就是在最后一个分区的末尾留出一些空间，一切都会好起来的:)。 所以不要select由partman错误计算的默认值。
经过两天的尝试，反编译和重新创build数组等，我终于不得不尝试一个干净的安装。 这次我只用了3个主分区，用于：/ boot，/和/ var，并且一切正常。 这不是一个实际的解决scheme，但它的工作原理。