Yes, we have determined that between facebook and walgreen's picture upload site, she has 75% of the pictures I don't have local backups of. She inst' nearly as distraught as she was earlier today.Leisher wrote:Worst case scenario, you can send it to Ontrack.
Also, your wife posts LOTS of pictures, so she'll have copies of all those on FB.
I've had a hilarious week of computer problems
"Be bold, and mighty forces will come to your aid."
Disk image... imaged. 282 GB. Problem is, I don't think I have a spare drive in the house big enough to expand this into.
May have to wait to after vacation. I don't think I want to pay the premium at best buy for a new HD.
Edited By GORDON on 1410680208
May have to wait to after vacation. I don't think I want to pay the premium at best buy for a new HD.
Edited By GORDON on 1410680208
"Be bold, and mighty forces will come to your aid."
A server, containing vital information. . . . . And no data redundancy? I understand the performance aspect, you don't want your transfers to take 2 days. . . . If you can't afford to run 4+ hard drives to ensure the speed of stripping + the security of data redundancy, maybe go with the later of the two? May take a little longer to make those transfers, but at least you have the guarantee that when one fails, you have another containing the same data. . . . Raid 0, in my opinion is a bad option for a server. . . . Point being, when you get this server back up and running again, attempt a more secure raid before hand?
Edited By Trooper on 1411006101
Edited By Trooper on 1411006101
Thank you for the disaster recovery advice. 
I have already said I had triple backups and the first two layers failed, and I mistakenly had important data on a raid 0 drive.
And at this point I don't think the drives failed, the mobo did.
Edited By GORDON on 1411046050

I have already said I had triple backups and the first two layers failed, and I mistakenly had important data on a raid 0 drive.
And at this point I don't think the drives failed, the mobo did.
Edited By GORDON on 1411046050
"Be bold, and mighty forces will come to your aid."
So before vacation I ran a recovery program on the RAID 0 disks and it created a 300GB VHD file. The size is what it should be. I didn't yet have a hard drive on which to extract it so I put it on hold.
Now I have a hard drive.
I am looking at a couple VHD extraction tutorials on youtube, and they both say go into disk management, Actions --> Attach a VHD file, then it shows a virtual hard drive getting created, and it is automatically assigned a drive letter.
When I do it it is not automatically assigned a drive letter, and I can't do anything with it. Also, in the tutorials the virtual drive letter gets a blue bar at the top the same as the existing drives, and the one I get is black.
So.
What am I doing wrong.
Now I have a hard drive.
I am looking at a couple VHD extraction tutorials on youtube, and they both say go into disk management, Actions --> Attach a VHD file, then it shows a virtual hard drive getting created, and it is automatically assigned a drive letter.
When I do it it is not automatically assigned a drive letter, and I can't do anything with it. Also, in the tutorials the virtual drive letter gets a blue bar at the top the same as the existing drives, and the one I get is black.
So.
What am I doing wrong.
"Be bold, and mighty forces will come to your aid."