Neil, Thanks for the reply, the --force worked great, md0 is syncing now, I will run testing against my database once the sync completes in 400 minutes.
Jim ---------- Original Message ----------- From: Neil Brown <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [email protected] Sent: Wed, 16 Nov 2005 10:16:22 +1100 Subject: Re: HELP 13 disk raid 5 not starting > On Tuesday November 15, [EMAIL PROTECTED] wrote: > > all, > > > > I have a 13 disk raid 5 set with 4 disks marks as "clean" and the > > rest marked as dirty. > > And important question to answer is 'how did this happen'? > > > When I do the following command > > to start the raid set (md0) I get an error. Any ideas on how to > > recover? > > Add '--force' to the 'mdadm --assemble' command. This tells mdadm to > try really hard to assemble the array, modifying info in the > super blocks if necessary. > Be aware that though doing this will normally give you a working > array, there may be data corruption within the array (it depends > somewhat on the answer to that first important question). > I would recommend at least an 'fsck' if that is practical. > > The array will be assembled degraded. You will need to add in a spare > if you are happy that the data is sufficiently intact. > > NeilBrown > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html ------- End of Original Message ------- - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
