On 08/08/2011 01:55 AM, Jeff Johnson wrote:
Joe / et-al, The '--assemble --update=uuid' appears to have done the trick. It is weird because the uuid in the config file matched the uuid of the raid volume shown with 'mdadm -D /dev/md3' and the uuid on each of the drives shown with 'mdadm -E /dev/sdc1'
Interesting.
The '--update=summaries' did not work. Assigning a new random uuid appears to have repaired whatever bit in the superblock was mucked up. Strange... Joe, thanks for your help. Find me at SC11, I'm buying you beers.
:) see you there -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: landman@xxxxxxxxxxxxxxxxxxxxxxx web : http://scalableinformatics.com http://scalableinformatics.com/sicluster phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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
