This may require a new thread as its a completely separate problem. (pre-quil: http://www.linuxquestions.org/questi...o-i-do-646716/
After recovering with the alternate drive I grew the array by placing the 8 th drive back in the array and using the --grow option. All seemed fine after this was completed. mdadm -D /dev/md0 reported that it successfully grew the array and that the size of the array grew by the appropriate amount.
The additional space was not available however since i had not resized the file system, but the array ran without problems all weekend. Now this morning I attempted to resize, but could not since the filesystem was mounted. The raid array includes my '/' partition, so to resize the file system i booted to the ubuntu live CD. After installing mdadm, the array was recognized without a problem. And the --detail reported no problems, so I ran the file system check and resized the array. All seemed to work with no problems reported.
But after rebooting it was unable to assemble the array. I'm not sure if it was damaged, or what. Every time i try to assemble it it gives the error...
mdadm: /dev/md0 assembled from 1 drive - not enough to start the array.
when I run in verbose mode, all the correct partitions are identified as members of /dev/md0, but they are all identified as being slot 0. Any idea what could cause this and/or if its fixable? Can I manually set the slot numbers some how?