If all your disks are connected, simply try a:
mdadm –assemble –scan
This should find and activate all your RAID systems 
Recent Comments
- c0ffee on Tuning Ubuntu mdadm RAID5/6
- WoW on WordPress: Image could not be processed. Please go back and try again.
- 54sa.net on ImportError: No module named trac
- Opera on Getting more traffic to your blog
- Liviu on HttpClient: Target host must not be null, or set in parameters
- alfonso on Tuning Ubuntu mdadm RAID5/6
- Gareth on HttpClient: Target host must not be null, or set in parameters
- Blake on WordPress: Image could not be processed. Please go back and try again.
- hjhh on WordPress: Image could not be processed. Please go back and try again.
- Tor Henning Ueland on HttpClient: Target host must not be null, or set in parameters
Tags
Android apt bug cron data protector Desire disk div exception asadmin firewall glassfish cluster google GPFS GWT HTC Iran javascript kvm Linux mdadm munin MySQL Nagios node-agent performance PHP raid raid6 Request Tracker RPM RT SLES spotify ssd sysrq tape The pirate bay tuning Twitter UPS vim windows windows 7 wordpress YumArchives
- February 2012
- January 2012
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- November 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
Last time I reinstalled my fileserver, it found all my raids by it self… Didn’t have to do anything.
How about error checking your command before publishing?
–assembe vs. –assemble 
Sorry about that, fixed now!