Well, I've lost everything. All of my toys. All of my research. My programming environment. The thousands of hours I've spend developing my audio mixing and mastering skills.
The story goes like this; I got this new (to me, not to the world) Sony DVD-writer which I think may be capable of reading the high density areas of Saturn discs and GDROMs. I've been holding on to it for a while, so today I decided I was going to finally install it. That's when I remembered that I needed to adjust the cables on my floppy drive (believe it or not. I need it for my T1000 anyways.) So I started to adjust it, when I heard a snap. Which was when I noticed that the SATA cable the HDD wasn't attached.
That tiny little nub of plastic that held the pins together broke off, along with the bottom of the socket.
But there's good news! None of the pins were broken, you see, so if I just put the cable by them, the contact should stay. It did work!
So I tore out the HDD from Werkzeug's nearly-identical twin, Stallion, and attached it to the second SATA plug. I didn't feel like waiting for a disc image to download and burn so I could partition the new drive. So I just put in the Vista disc. I figured that, since it was also a recovery disc, I could just use the partition editor on that.
Well, as it turns out, Vista's DiscPart is pretty much crap. It didn't know the difference between my two drives, so I ended up deleting the partitions on the old hard drive. I lost everything. I had an album ready to be released as soon as the album art was done, and was almost done with another album. Oh, and I don't have any of the years of work I put into building my system.
Well, the good news is that the data can theoretically be brought back to perhaps a full partition and filesystem restoration at little to no cost, depending on if you believe that time is money or not. Luckally, the new HDD had a (very old) version of Ubuntu. And GNU has this program called TestDisk (or something to that extent) which is supposed to be able to salvage data from a number of file systems, thankfully including NTFS.
So... I'll call you back if I have any good luck?
If not, I'll just steal your money and send the disk to a data recovery specialist.
BTW, DiskPart=another reason to hate Microsoft.
skip to main |
skip to sidebar
Searches this blog, the NFG sites, and insertcredit.
The fool who writes this
Labels
- music (9)
- misery (6)
- Linux (2)
- OS (2)
- Apple (1)
- Civil Rights (1)
- Development (1)
- Programming (1)
- review (1)
- video (1)
- website (1)
The FireFae Gazzette
Posts
custom search
Searches this blog, the NFG sites, and insertcredit.
FYI
I own the copyright to everything in this blog, excluding content from external sources (such as Google), which are copyright their owners. Also, Dennis Kucinich should have won the presidency. And Vista sucks.
2 comments:
first, tough break man, i just went through my third power supply, however, all my data is safe and i bout a second terabyte hdd.
second, your going to blame microsoft for your error, if you saw only one drive was showing up, you should have taken out your old drive just in case, same if YOU couldn't tell the difference.
You don't understand: every OS besides windows knows which HD is which, and that there's a difference between /dev/sda and /dev/sdb. Not being able to tell the difference between the two is just a bad design choice. Windows is even worse than that; it's choice of drive lettering doesn't follow any normal pattern, so if you have more than one Windows installation, you're going to be totally confused with which partition is mounted to G:. Even the whole drive-lettering idea is antiquated; the last OS to even use a colon was AmigaOS, and it wasn't limited to using a single letter.
But that's not the point I'm getting at. The fact is that issuing the same commands yielded different results, as disk0 didn't stay as disk0. That's a sign of defective design and implementation.
Post a Comment