gvinum raid5 cannot find file system superblock after removing a disk

[Edward Sutton]

I had a disk that had been in a down state in the past, marking its raid5 plexes as stale. After determining which disk was the one connected to the stale data (ad8), I rebooted to a freebsd on a nonraided freebsd drive that did not have geom_gvinum loaded. I made a dd of the first 64mb on ad8 and used sysinstall to repartition the drive. The main system has failed to mount or fsck all raid5 partitions since. gvinum still says the untouched pieces are in the 'up' state and restoring my ad8 dd made that disk listed again but still cannot boot. I have not yet tried to rebuild the disk from the other 2 since it is unable to boot from them. Is there a chance that the daya is no longer being called with the 
correct offset or from the correct disk? is there a way i can experiment with the data from each disk to rebuild it using different orders and offsets to create another disk containing nonstriped data to try to find the filesystems?
I am running a stable6 system updated about 3 days ago and haven't found any postings indicating trouble from there. Any information as to what went wrong and suggested steps from here to bring this data back online would be greatly appreciated. I will try to provide any requested information, but at present wukk be manually copying it fro one computer to the next in most cases.
Thanks again for any information,
Ed Sutton
_________________________________________________________________
Help yourself to FREE treats served up daily at the Messenger Café. Stop by today.
http://www.cafemessenger.com/info/info_sweetstuff2.html?ocid=TXT_TAGLM_OctWLtagline