Andrew Nelson wrote: > Frank Blendinger wrote: > >>On Thu, Feb 16, 2006 at 11:31:06AM -0600, Andrew Nelson wrote: >> >> >>>>It's probably not your fault - blame /dev/hde! This sounds like a bad >>>>error on the disk - you should really get a new one, and try to copy >>>>/dev/hde to the new disk (with dd_rescue for example). This _might_ save >>>>the data. >>>> >>>>Then you can try to create the array with the new disk and hope that >>>>it will work. >>> >>> >>>I thought the whole idea of a raid 1 was that if one drive went bad I could just >>>plug a new drive in and the raid would rebuild without problems. >> >> >>That is certainly right. I just wanted to tell you, that your /dev/hde >>probably has a serious hardware error, and that you should replace it! >> >>Of course you can just throw it out, put in a new drive, rebuild the >>array with your other drive and the new one, and then resync. This >>should work just fine. >> >>I guess my first answer was quite confusing, sorry. It's absolutely not >>necessary to copy the old hde with dd_rescue. >> >> >>Greetings, >>Frank > > > Is it possible to assemble the array with just /dev/hdg? I swear I saw an > option somewhere that allowed just such a thing but now I can't find it anywhere. > > //andy > Never mind I figured it out. mdadm -AR /dev/md0 /dev/hdg1 So far this seems to work. Thanks for all the help. I'll replace hde ASAP :). //andy - 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
