3vj3 Posted July 10, 2010 Share Posted July 10, 2010 I was following a guide to get another RAID-0 array bootable and used the command: "diskutil eraseVolume "HFS+" "disk0s1" /dev/disk0s1" but since the last time I restarted the disk numbers changed so I erased the wrong one and now I can't access the array. Is there any way to fix this? I only erased disk0s1, the 200MB partition. Link to comment Share on other sites More sharing options...
justvisiting Posted July 10, 2010 Share Posted July 10, 2010 can you still boot the machine or was your install on the raid? Link to comment Share on other sites More sharing options...
3vj3 Posted July 10, 2010 Author Share Posted July 10, 2010 can you still boot the machine or was your install on the raid? I had cloned a working Snow Leopard installation from a single hd to a new RAID 0 array and was in the process of trying to get it to boot. My current boot drives (and backup drives) are running out of room so I stuck my porn on the new drives temporarily to get some space back until I could make the switch, since I don't consider it too important. Anyway I fixed it somehow (or it fixed itself). Diskutility told me that the RAID array had failed and then later wouldn't even show the partitions, just two empty drives. After some googling I found this partition recovery program called TestDisk that looked like it might be able to help. I ran it and it started scanning. When it hit 1% I quit it because it would've taken 34 hours to scan the entire hd. I logged out and when I logged back in later the RAID array mounted itself. I don't know if the program did anything or if my logging out and back in did it, but everything seems fine now. The porn is safe and all is right in the world. Link to comment Share on other sites More sharing options...
Recommended Posts