I have been fighting my Giga PC for about 11 hours now... including a 3 hour call to Microsoft in New Dehli - and I am no further along than when I started. I thought about jumping, but my studio is on the 3rd floor, and I'd probably just hurt myself.
The PC is a P4/2.4 (yes, it's underpowered, but still works fine) w/ 1.5 gigs ram. Win XP pro SP2. GS3 3.12;
This morning, I was updating some files, a developer sent me some .art files, etc... all was fine. I started working... and one of the files that I had added this morning was not in the QS database, so I did a quick update... still not there... so I initiated a full QS database rebuild. About 50% done - and the PC crashed. Not stalled, not paused, but dead. Had to pull the plug to restart it. Now, after restart, my F: drive (the drive with all the .gig files) shows up, but can not be accessed.
The F: drive is actually (2) WD 160 gig 7200rpm/8mb drives (about 4 months old), striped in a RAID 0, using the raid controller built into my motherboard. It is the Promise 133 FastTrack controller -- has been working just fine. It continues to report "functional" on startup (in the BIOS). However, once we get into WinXP, the F: drive is "offline" - winxp thinks the drive is a removable and the tray is open or something like that...
chkdsk can not see it. disk management can not see it. we started up with the winxp cdrom and tried a few things -- nada."The drive is not ready for use; its door may be open. Please check drive and make sure that a disk is installed and that the drive door is closed"
In "my computer" - the drive appears as "local disk F:" and if I click on it, I get an error: "The device is not ready"
I pulled a pair of new drives from the shelf and swapped it out and made a new raid 0 - it works fine. I can say that I have no issues with the raid controller and it appears to be working.
The raid controller reports the F: drive (the raid 0) as functioning at boot - if I go into the raid utility in the BIOS, I can see the individual drives, and all checks out OK. Only when I get to Winxp that I get the "can not access" error messages. The F: drive appears in the list of drives, but is "offline".
I tried pulling one drive, and the RAID got mad... until both drives were plugged in, in the correct order, with the correct cabling (A to A, B to B, etc..) the RAID wasn't happy and would return error messages. Once I cabled it up correctly, the RAID reported "funtional" at boot... but Winxp would not mount or access it.
97% of the data on the drive(s) are from commercial DVDs and CD-ROMs that I have -- except many have been updated with .art files for GS3 (VSL) and SISC -- and since I was one of the early VSL purchasers, my DVDs are hit and miss... many errors and I have accumulated about a dozen more CDs with VSL fixes. I figure it will take me 12-15 hours to rebuild this array. Yes, I'm backed up, but DDS4 is painfully slow for a full restore over the network. 280gigs will be faster from the DVD drive. Fortunately, all my perf files are on my C: drive and fully backed up.
I tried a variety of data recovery utils, such as GetDataBack - and of course all of microsoft's utils... it can't even see the drive.
So: my questions....
1. Any hard drive rocket scientists out there who may know how I can salvage this raid?
2a. Let's assume that I will not be able to salvage the data... I will then buy a brand new PC for Giga... is it worth building my own when I can buy something like Sonica Audio Labs -- I already own a RME HDSP9652, so maybe the price will be adjusted? I'll call them in the morning.
2b. If you were building a new PC right now for GS3, what hardware would you go after? I need this yesterday -- so I don't want to deal with long shipping times or backorders.... if you build PCs, please contact me. I'm in NYC.
3. Could GS3 have anything to do with this, or is it simply a fluke that the drive(s) failed during a QS database update?
4. If you were me, what would you do: a) try to fix it; b) buy a new rig; c) jump?
Thanks to all for reading this and to the experts who may have a solution.