On Wed, Dec 3, 2008 at 3:45 PM, Sean Hildebrand <silverwraithii@xxxxxxxxx> wrote: > On Wed, Dec 3, 2008 at 3:21 PM, NeilBrown <neilb@xxxxxxx> wrote: >> On Thu, December 4, 2008 2:43 am, Sean Hildebrand wrote: >>> blkid reports that all five disks have the same UUID. >>> >>> Specifying disks by UUID results in "mdadm: no devices found for >>> /dev/md0". >>> >>> Specifying disks based on their positions, /dev/sd[abcef]1 in this >>> case, results in "mdadm: superblock on /dev/sda1 doesn't match others >>> - assembly aborted" and it'll continue doing that with [bcef]1 if a is >>> removed. >>> >>> mdadm --detail --scan outputs nothing. >>> >>> I've tried assembling the original three disks sans the two new ones >>> to no avail. >> >> Please: >> git clone git://neil.brown.name/mdadm >> cd mdadm >> make >> >> and try the 'mdadm' that creates. >> If that still doesn't work, please report the output of >> mdadm -E /dev/sd[abcdef]1 >> and >> mdadm -Avv /dev/md0 /dev/sd[abcdef]1 >> >> NeilBrown >> >> > > That did it. Built, mounted and back to rebuilding. > > Thanks. > Having an issue right now, I am unsure of what's going on. When I resized my array from 5 disks to 3 some months ago, the filesystem was automatically made smaller. I'd assume the same happens when growing the array. However, conky and my file manager report that the partition is 1.35TB. fdisk and gparted output the correct 2.73 TB. Does mdadm automatically resize the partition when increasing the number of disks? -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
