On Sat, 2008-03-22 at 13:30 -0400, Bill Davidsen wrote:
> Might I suggest that you
> - back up your mdadm.conf file
> - replace the list of components in the ARRAY description with the UUID
> of the array
> - change configure to use PARTITIONS and try them all
> - try the assemble with mdadm figuring out what goes where
>
> Your chances of getting something drastically wrong are lower. You may
> have to use --force to get the assembly, and should run fsck *with the
> -n option* first to see what you have.
I was using UUID :)
As you suggested, I changed DEVICES to 'partitions' as that was my
original intent.
Rather than just hope, I looked at the source for mdadm. A thousand
cheers for open source! =D
And discovered:
-v Would show how partitions were assigned.
mdadm -v -A /dev/md5 showed all was good.
--force updates the events first thing when assembling.
Solving my exact issue.
My array is now operational. And the rest is up to reiserfsck. :/
Thank you so much,
-Arthur
--
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
