12-30-2008 08:30 AM
The circuit I built was successful in connecting to the drive, however I am using a custom built serial cable and I think there is something wrong with it. I can see the console, but the console is not accepting commands (I tried it on a few drives with the same result). I will be trying a different serial cable tonight and will let you know what happens.
Check back around 9:00PM MST
12-30-2008 08:36 AM
Just spoke to someone at 1-800-SEAGATE (732-4283) - he suggested that "the drive has failed" and he recommends I send it back for a replacement. He said that this is not a problem they're aware of!!
I suggest that everyone who is having this issue call Seagate at 1(800) 732-4283 and ask for a solution. Point out how many people online are experiencing the same issue and even the reviews on Newegg suggest that 20% of buyers have reported the same problems.
Remember - the squeaky wheel gets the grease!! Be sure to report back your results on here.
12-30-2008 12:54 PM
Does this issue only affect 500GB and 1TB drives? Are 750GB and 1.5TB drives suffering the same issue? (I am aware of the recent BIOS upgrade for the 1.5TB drives)
FYI - I also have a 1TB drive with firmware SD15 that does not show up in the BIOs after 2 months of use.
12-30-2008 06:25 PM
As I suspected, I had a bad serial cable. I am connected properly now. So far the commands I have sent have not solved the issue. I have to be careful with every command I send, so you can imagine the time it takes to try and figure out what every command does prior to sending it. It's not like there is a confirmation when you send a command in terminal mode I haven't sent anything yet that I am not sure what it does.
Any experts out there that want to point me in the right direction as to which F3 level and which commands I should be looking at, please PM me. You don't have to give me the answer, but a small pointer would be nice.
If anyone is wondering what the LED error looks like in the console, here you go:
By the way, I have tried:
F3 T>/2 F3 2>Z F3 2>U F3 2>/1 F3 1>N1
power reset (no dice)
12-30-2008 06:46 PM
Just like any of you guys, I am also a victim of a faulty ST3500320AS-SD15 which is made in Thailand. And just like mine, the HDD led is always on when i plug in the faulty hdd. So I am having the BSY status problem as well. I have been following this thread since it first posted and I am amaze by the progress made so far by Fatlip.
From the steps that you are taking did you tried:
First Ctrl-Z after the terminal boots up, then follow the command line below:
Reboot the PC and connect the hdd normally.
For those of you who want to try their hand on this solution please follow the steps below, (I hope this message is not deleted):
1. Google, hyperterminal seagate
2. Choose [PDF] Unlocking Tutorial Seagate ST310014ACE v0.1 by cyd0g (Should be the third link)
3. Good Luck Guys
P/S: I don't really understand why they need to connect through the jumper pins and not through the IDE/SATA.
12-30-2008 07:02 PM
I saw those commands awhile back but I couldn't track them down again, although I have been looking. Thanks!!!
There is a much easier way to connect via serial than what you mentioned Death.
PM me if you want the easier way.
12-30-2008 07:25 PM
12-30-2008 07:28 PM
Nice find on this link, but they are doing a different operation here by "unlocking" the drive that the symptom we are expereincing in the BSY state.
The operation they are describing is unlocking the drive for normal use if you dont have the encryption key, which is a little used feature, but it was used on the Xbox1 and the HD was locked to the console.
Still a good find though.....and to fatlip, you are making incredible progress!!!!! keep it up and please share every bit of your experience - theres a number of us who check this thread once a day or more I am sure!
12-30-2008 07:29 PM
The question is, how will you upgrade the firmware when your SATA port on the drive is locked?
Hopefully they figured something out, keep us posted!