On Sat, Dec 3, 2011 at 1:11 PM, NeilBrown <neilb@xxxxxxx> wrote: > On Sat, 3 Dec 2011 10:58:43 -0600 Kenneth Emerson <kenneth.emerson@xxxxxxxxx> > wrote: > >> > >> > > I will do this conversion; but I will backup my data as best I can first, >> > > just in case. >> > > I still have the 5 1TB drives and my data should fit on there, just a PIA >> > > to do it. >> > > (Ahh, that's what weekends are for, right?) >> > > After the RAID6 is repaired and running OK, I believe I will rebuild the >> > 2 >> > > RAID1 arrays >> > > as that will be an easy project (since I have 5 copies of everything) >> > which >> > > will get rid of >> > > all vestiges of previous raid arrays. Do I need to anything special >> > other >> > > than zeroing >> > > the superblocks (--zero-superblock)? Also, shouldn't I do that on the >> > > RAID6 array before >> > > doing the create or is that done automagically? >> > >> > It is done automatically. When you use "--create", mdadm will zero any >> > superblocks it finds of any format that it recognises, then write the new >> > metadata it wants. >> > >> > I am still waiting for my replacement Hitachi drive. My RAID6 >> configuration is made up of a total of 5 drives and I am currently running >> degraded (missing one drive). Can I recreate this raid set, changing the >> metadata version missing one drive or should I just be patient and wait for >> the replacement to arrive? >> >> -- Ken Emerson > > Yes, you can re-create the raid set as degraded. > When you list the devices in the "mdadm --create" command, use the word > "missing" for the device which is missing. > > NeilBrown So I finished my backup and attempted to recreate the array using: root@mythtv:/home/ken# mdadm -C /dev/md3 --metadata=1.0 --chunk=64k --level=6 --raid-devices=5 missing /dev/sdb4 /dev/sdc4 /dev/sda4 /dev/sdd4 --assume-clean and received the error: mdadm: invalid chunk/rounding value: 64k What do I do now? -- Ken E. -- 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
