Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

The Solution for Seagate 7200.11 HDDs

- - - - -

  • Please log in to reply
4755 replies to this topic

#3626
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag


[*]once the drive is unbricked (and WITHOUT ANY firmware upgrade) it won't re-brick itself spontaneously for at least three months of daily use (six to twelve month being proven to be the most likely cases)

I can not agree with this. Just unbricked my drive last week for the 4th time. I undbricked it the last time two months ago.

Well, maybe not strictly "at least" three months, but if your hdd bricked three more times in the 14 months since you fixed it the first time in Jan'10, it is 14/3=4.66 months. Thus on average it bricked every 4 months and twenty days which IS longer than the three months jaclaz said. It also depends on how many times you power cycle the drive and can't be exactly quantfied.

However, since I did not solve the Fujitsu Siemens firmware issue (and to be honest I'm not interrested to look further in this topic anymore),

Did you look here? http://support.seaga...e_check_en.html
Jack of all trades, master of none, though ofttimes better than master of one.


How to remove advertisement from MSFN

#3627
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,593 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Well, maybe not strictly "at least" three months, but if your hdd bricked three more times in the 14 months since you fixed it the first time in Jan'10, it is 14/3=4.66 months. Thus on average it bricked every 4 months and twenty days which IS longer than the three months jaclaz said. It also depends on how many times you power cycle the drive and can't be exactly quantfied.

Sure, three months is something intended as "NOT IMMEDIATELY" and "NOT TOMORROW" it may also depend on the number of (other) problems the drive may have AND by the actual number of entries written to the log.

Just as an example if a "good drive" writes just one entry in the log at each boot, if some other events writes at each boot other three events, and you boot once daily, you will reach a multiple of 256 earlier, like 256/4=64 days, that do sound a lot like two months.
Some hypothesis explaining the three months (or 106 reboots) possibilities:
http://www.msfn.org/.../page__st__1061
http://www.msfn.org/.../page__st__1065

jaclaz

#3628
Jamesblond

Jamesblond
  • Member
  • 4 posts
  • Joined 17-February 11
  • OS:Windows 7 x86
  • Country: Country Flag

That should mean that you did not manage to spin down. :blink:

See here:
http://vermeulen.ca/...harddrives.html

Try if this changes anything.

WHICH guide/method are you following?
I don't recall any "v4" command in the guides used :unsure:

jaclaz


Hello Jaclaz,
now i tried this from your link "http://vermeulen.ca/...arddrives.html"

After ...

F3 T>/8

F3 8>Z

Spin Down Complete
Elapsed Time 0.161 msecs
F3 8>

F3 8>U

Spin Up Complete
Elapsed Time 9.250 secs
F3 8>/1

F3 1>N1


I got allways the same words:

LED:000000CC FAddr:00243FCF

In my case : Is there any hope to solve the problem, or get it into the garbage ?

I google for the words :
DIAG Error 0000500E Process Effect List Error
R/W Sense 00000002 R/W Error 841C0087, List Offset 00000000, File Error 00000001

And i found on "http://forum.hddguru...in-t13900.html" the v4.....

#3629
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86

Barracuda 7200.11... do I have this same problem??

I have a internal Barracuda 7200.11...Firmware SD33 .... Manufac: 11/2008.....and for some reason it refuses to start up when connected via SATA at bootup..

I can hear the drive actually spinning to start with, then it seems to reset itself and try over again, on an endless unsuccessful cycle. it does not want to initiate...however im guessing i would not hear these sounds if it was not spinning up at all?...

this text seems to match my problem:

Reason for the Seagate 7200.11 Failure
This problem is caused by a firmware issue that sets the drive's "event log" pointer to an invalid location. This is detected by the drive during power-up initialisation, and the drive switches to fail-safe mode to prevent further corruption and loss of user data. Once the failure has occurred user data becomes inaccessible.
During power up, if the Event Log count is at 320, or any multiple of (320 + Nx256), and if a particular fill pattern is present in the factory reserved area of the drive, the firmware will incorrectly allow the Event Log pointer to increment past the end of the Event Log data structure.
This error is detected during initialisation and returns an "Assert Failure", which causes the drive to enter it's fail-safe mode. When the drive enters this mode further updates to the event log counter are impossible as the same results occur at each power-cycle.
The problem can only occur if a power cycle initialization occurs when the Event Log is at 320 or a multiple of 256 thereafter. Once a drive is in this state, the user will not be able to resolve/recover existing failed drives.

...but i am not sure...plus i dont know how to get a diagnosis?!?


The drive resides in a clean host system as a back-up drive for data, and has not been dropped or had any form of stress....it just stopped working and disappeared form my computer.

I have contacted Seagate but its an OEM so they will not help me any further....The OEM would not help as i beleive its out of waaranty and even if it was still under, then they would only offer a replacement...which of course, i do not want.....i need the data only - this drive has important stuff and for the record the £600GBP i have been qouted from data recovery is too much...

any help/advice is very much appreciated!!

Thanks in advance,

Corky :P



ok guys ive performed the fix as per listed here and now the drive is spinning more normally than before...

it loaded the drivers and said it was installed and the device was working properly

still no in My COmputer though...

however although its telling me in disk management that it is 'unknown' and 'Not initialized' this is strange as its obviously not a new disk...it ghas my data on it. is it ok to go ahead and initialize? it says something of partioning which worries me that it might overwrite my data or am i being a jack a** worrying there?!

Corky

#3630
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

ok guys ive performed the fix as per listed here and now the drive is spinning more normally than before...

it loaded the drivers and said it was installed and the device was working properly

still no in My COmputer though...

however although its telling me in disk management that it is 'unknown' and 'Not initialized' this is strange as its obviously not a new disk...it ghas my data on it. is it ok to go ahead and initialize? it says something of partioning which worries me that it might overwrite my data or am i being a jack a** worrying there?!


Normally after the fix, it is exactly as it was before it bricked with all the data and partitions like before . Did you get something like this:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful - Elapsed Time 0 mins 05 secs


Is it seen in BIOS now. and if it is, as what size?

How are you connecting to your computer now - still as an internal hdd via SATA or as an external USB? :unsure:

And NO, do not partition or overwrite anything now you are right to worry about that, let's first try to find out what is wrong.

Edited by BlouBul, 25 March 2011 - 02:25 PM.

Jack of all trades, master of none, though ofttimes better than master of one.

#3631
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86


ok guys ive performed the fix as per listed here and now the drive is spinning more normally than before...

it loaded the drivers and said it was installed and the device was working properly

still no in My COmputer though...

however although its telling me in disk management that it is 'unknown' and 'Not initialized' this is strange as its obviously not a new disk...it ghas my data on it. is it ok to go ahead and initialize? it says something of partioning which worries me that it might overwrite my data or am i being a jack a** worrying there?!


Normally after the fix, it is exactly as it was before it bricked with all the data and partitions like before . Did you get something like this:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful - Elapsed Time 0 mins 05 secs


Is it seen in BIOS now. and if it is, as what size?

How are you connecting to your computer now - still as an internal hdd via SATA or as an external USB? :unsure:

And NO, do not partition or overwrite anything now you are right to worry about that, let's first try to find out what is wrong.



no its not being seen at all in BIOS, and its connected as a internal HDD.

#3632
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

no its not being seen at all in BIOS, and its connected as a internal HDD.

That means the unbricking was unsuccessful :no:
Did you get something like this during the unbricking:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful - Elapsed Time 0 mins 05 secs


What exactly did you do to unbrick it?
Were there any strange error messages?
Do you have a log file of your HyperTerminal session?

Maybe repeat the whole procedure carefully again and save the log file.

Edited by BlouBul, 25 March 2011 - 03:01 PM.

Jack of all trades, master of none, though ofttimes better than master of one.

#3633
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86


no its not being seen at all in BIOS, and its connected as a internal HDD.

That means the unbricking was unsuccessful :no:
Did you get something like this during the unbricking:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful - Elapsed Time 0 mins 05 secs


What exactly did you do to unbrick it?
Were there any strange error messages?
Do you have a log file of your HyperTerminal session?

Maybe repeat the whole procedure carefully again and save the log file.


well, the drive was sent to a data recovery for a free examination....upon its return i have noticed that the firmware has been changed....this has meant as i put before that the behavious of the drive has changed a bit...does changing the firmware though mess the data?? why would they do that staright away??

i just didnt go with thier qoute to carry out the recovery as they wanted £300.

i figured could attempt the fix,
however, i have the right cables im assuming...the actual HDD wasn't powering up at all during the first part (the hyperterminal part)

#3634
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86

Ok, the drives are 100%. :w00t: :thumbup

I didn't loss anything, it went back to it were before BSY error (and I almost had a heart attack!).

This is a direct guide for BSY error, for details and more, check the 1st msg on this topic.

I received the stuff at 14:30h today as you can see here:
Posted Image

The one circled in red isn't necessary at all. In fact, is so tiny to connect those pins on Seagate, I was forced to give up on those plastics.

Here is the kit fully assembled it took me 20min, mounting those cables is really a pain:
Posted Image

Another angle:
Posted Image

With HDD connected (note I giving up on plastic connectores [circled in red on 1st photo):
Posted Image

The whole stuff complete to fire up:
Posted Image

And on this photo (above) is the TRICK here, see that little paper card (CR2032) ?

Yes! Just unscrew those around, and put a paper card or something to isolate the area (is the spin motor) like plastic, don't use anything that is an electric-conductor, after that you can turn ON everything.

You can work with just 1 screw, like on this photo (square in red):
Posted Image


On terminal you'll see nothing, just press CTRL+Z. And you'll get F3 T> prompt.

With PCB disconnected from HDA with a paper card (or similar), you'll see:

On terminal press CTRL+Z:

F3 T>

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.147 msecs
F3 2>

Wait 5sec and remove the paper card, this will connect the PCB to HDA (spin motor), but since is in Spin Down state (from cmd), you'll feel nothing.

Now screw just enough to make a good contact between PCB and HDA (be real careful here, don't drop the screw, just be calm, relax!).

Then press CTRL+Z again:

F3 2>U

Spin Up Complete
Elapsed Time 7.457 secs (if you get this msg you did everything fine until here)
F3 2>/1

F3 1>N1

F3 1>/T

F3 T> <<< At this step you'll need to POWER OFF your HD for 10sec, and then POWER ON again. By power off, remove the SATA power (not PCB!).

When done, press CTRL+Z.

F3 T>

F3 T>i4,1,22

F3 T>

F3 T>m0,2,2,,,,,22 <<< This command takes a little over a minute to complete!
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8

User Partition Format 5% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful - Elapsed Time 0 mins 05 secs

F3 T>

You did it! Congratulations! :ph34r:

Just turn off everything, and put your HDD on your lovely PC. :thumbup

Keep in mind TX and RX from Seagate are exactly like that, but on Seagate side.

Connect it this way:

PC (TX) > RX on Seagate
PC (RX) > TX on Seagate

The wires was inverted to me and I didn't get nothing, so I just reverted and finally got a terminal answer.

Gradius

http://www.kwikpiks...... topic/01.jpg
http://www.kwikpiks...... topic/02.jpg
http://www.kwikpiks....c/connector.jpg
http://www.kwikpiks...... topic/05.jpg
http://www.kwikpiks...... topic/04.jpg



As far as i know...i have all of the cables as Gradius instructed...but my problem is actually powering up the HDD....although i dont have the little battery in the pictures here.....just realised.... is there a way around not using the battery?

#3635
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

As far as i know...i have all of the cables as Gradius instructed...but my problem is actually powering up the HDD....although i dont have the little battery in the pictures here.....just realised.... is there a way around not using the battery?

<sigh> I thought you already did the procedure :no:
Let us start at the very beginning. Did you do a loopback test? See FGA no. 3 and 4. Just for good measure, you can also read the rest of the FGA as well as the Read-Me-First as you obviously missed quite a few important parts (#11 deals with powering the converter). Then also read the guide by CarterinCanada a few times. Next time you report that you did the fix, make sure you followed that guide and got the expected responses. I am really flabbergasted that you actually reported a fix before and now come with these questions :o :no:

PS. and next time you quote a post, don't quote the whole post (especially if it is a long post), but only the relevant parts.

Edited by BlouBul, 25 March 2011 - 06:22 PM.

Jack of all trades, master of none, though ofttimes better than master of one.

#3636
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

i figured could attempt the fix,
however, i have the right cables im assuming...the actual HDD wasn't powering up at all during the first part (the hyperterminal part)

Missed this post..
Did you plug in the SATA power?
I am assuming you did get a response in Hyperterminal (which you would not if no power was connected), what happened when you typed Z (enter) to spin down the drive and U (enter) to spin up the drive?.
Jack of all trades, master of none, though ofttimes better than master of one.

#3637
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86


As far as i know...i have all of the cables as Gradius instructed...but my problem is actually powering up the HDD....although i dont have the little battery in the pictures here.....just realised.... is there a way around not using the battery?

<sigh> I thought you already did the procedure :no:
Let us start at the very beginning. Did you do a loopback test? See FGA no. 3 and 4. Just for good measure, you can also read the rest of the FGA as well as the Read-Me-First as you obviously missed quite a few important parts (#11 deals with powering the converter). Then also read the guide by CarterinCanada a few times. Next time you report that you did the fix, make sure you followed that guide and got the expected responses. I am really flabbergasted that you actually reported a fix before and now come with these questions :o :no:

PS. and next time you quote a post, don't quote the whole post (especially if it is a long post), but only the relevant parts.



yeah my bad, after a very sleepless night we're attempting this today again, i'd also like to add that during the free examination by the data recovery co. they actually did change the firmware ......has been changed to ZZ7L ... i found this out using Seatools...where for the record the drive has also failed the SMART test.

will be posting later today the latest,

thanks bloubal

#3638
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

yeah my bad, after a very sleepless night we're attempting this today again, i'd also like to add that during the free examination by the data recovery co. they actually did change the firmware ......has been changed to ZZ7L ... i found this out using Seatools...where for the record the drive has also failed the SMART test.

will be posting later today the latest,

OK, let me just understand exactly what you did as the reports are very conflicting...

1. Did you do a loopback test?
2. Did you get a response in Hyperterminal when you issued commands?
If the response to these questions are "YES", then your converter is powered and your hdd as well and you do not need to worry about that. If not, we have to look for the problem.

Funny firmware version is not a major issue and can be flashed to SD1A/B after the fix.
http://www.msfn.org/...ndpost&p=892154

Edited by BlouBul, 26 March 2011 - 04:53 AM.

Jack of all trades, master of none, though ofttimes better than master of one.

#3639
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86


yeah my bad, after a very sleepless night we're attempting this today again, i'd also like to add that during the free examination by the data recovery co. they actually did change the firmware ......has been changed to ZZ7L ... i found this out using Seatools...where for the record the drive has also failed the SMART test.

will be posting later today the latest,

OK, let me just understand exactly what you did as the reports are very conflicting...

1. Did you do a loopback test?
2. Did you get a response in Hyperterminal when you issued commands?
If the response to these questions are "YES", then your converter is powered and your hdd as well and you do not need to worry about that. If not, we have to look for the problem.

Funny firmware version is not a major issue and can be flashed to SD1A/B after the fix.
http://www.msfn.org/...ndpost&p=892154



the latest strange development is that its showing no firware revision in seatools now..... the ZZ7L has disappeared?? not allowing any tests either!!

#3640
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

the latest strange development is that its showing no firware revision in seatools now..... the ZZ7L has disappeared?? not allowing any tests either!!

First tell us exactly what you committed with your hdd during the attempted fix. The more detailed info you give, the better the chance that we can understand what went wrong.
Jack of all trades, master of none, though ofttimes better than master of one.

#3641
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86


the latest strange development is that its showing no firware revision in seatools now..... the ZZ7L has disappeared?? not allowing any tests either!!

First tell us exactly what you committed with your hdd during the attempted fix. The more detailed info you give, the better the chance that we can understand what went wrong.


ok, here goes..

well having received the drive back from the 'free diagnosis' form the data recoverer, i connected the drive back to my PC as an internal and discovered that it spins up, although did not show in BIOS. it was identified through disk management but was 'unknown' and needed initializing.

now, my freind /neighbour is more technical than I am so we have all the cables and adaptor (inclusive of nokia modified cable) ready to attempt the BSY fix, or at least try and get something through hyperterminal as a first thing.

as a first attempt, we were not succesful in getting the HDD to power up, which could be a result in the fact it wasnt talking to our independant PSU???, which was being used from its red cable molex only, in orer to power it up...... he suggested we take a look again to see if the drive was appearing through BIOS, but on HIS pc instead of mine..... it was. however it was showing only a total of 7.87GB and of course the firmware as previously stated as ZZ7L.

This drive should be a total of 640GB and has near 423GB of my data on it!

(i'd like to point out again that the HDD had a firmware of SD33 Prior to its 'free diagnosis' ... they changed it during the week they had the drive...they also said that it WASN'T the BSY fix and that they quouted £300 to get my data back. )

here is what the recoverer has actually said:

'Your drive has multiple failures. It would appear that media issues have caused a firmware lockout, so one problem would have to be resolved before fixing the next one.'

during the session at my friends, we connected the drive using the RX and TX, and tried to check that we were getting the right connections. my freind set up hyperterminal and checked that this matched...however, the actual drive would not spin up.

My freind then suggested we just get the firmware update on the drive, and downloaded the 'Brinks' SD1 something or other firmware, however...he nearly messed his own PC up by this... so aborted.

I am now at home again and connected the drive to my PC, to have another look through Seatools...its firmware is now displaying nothing...blank. which makes me think did he actually wipe off the ZZ7L Firmware? is that possible?

looking forward to your feedback, i'll answer further questions as simply as i can.

Corky :unsure:

#3642
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag
Did you get any response from hyperterminal when you tried to fix it. Check the three links given earlier for help (FGA, Read-me-first, and guide by CarterinCanada).

Not sure what is exactly wrong, but you can't update the firmware on a bricked drive - you have to first do the whole procedure correctly before updating.

Just try everything again carefully. and report what goes wrong (or attach log file from hyperterminal)
Jack of all trades, master of none, though ofttimes better than master of one.

#3643
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86
ok latest is I've just looked for my drive in AIDA64......Heres what comes up.

remember my drive is a 640GB Capacity drive.

hopefully this listed info helps a little more to understand my case.


ATA Device Properties

Model ID : ST3640323AS

Serial Number : 9VK0CE3H

Revision : ZZ7L

Device Type : SATA-II @ JMicron

Parameters : 16383 cylinders,16 heads, 63 sectors per track, 512 bytes per sector

LBA Sectors : 0

Buffer : Unknown

Multiple Sectors : 16

ECC Bytes : 4

Unformatted Capacity : 8064 MB

ATA Standard : ATA8-ACS

#3644
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag
OK corkyblue,

Just try for once to answer specific questions. Each time I ask you a question, you come back with an answer for a different question :ph34r:
I am still trying to understand how far you came with the fix and what happen there, what error commands you got if any and if you actually had communication with your hdd through hyperterminal.
Please, just FIRST answer those questions and then we can look at the rest.

Edited by BlouBul, 27 March 2011 - 12:32 AM.

Jack of all trades, master of none, though ofttimes better than master of one.

#3645
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86

OK corkyblue,

Just try for once to answer specific questions. Each time I ask you a question, you come back with an answer for a different question :ph34r:
I am still trying to understand how far you came with the fix and what happen there, what error commands you got if any and if you actually had communication with your hdd through hyperterminal.
Please, just FIRST answer those questions and then we can look at the rest.


ok just spent several hours trying, but no comms between hdd and hyperterminal. checked the RX/TX leads, swapped and tried checked the loopback which seemed to report ok...but nothing.

tried covering the motor with piece of card, followed the instructions...but nothing doing...any suggestions?
for the record, i am 'seeig' the drive in disk management...but no data or any capacity.

#3646
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

ok just spent several hours trying, but no comms between hdd and hyperterminal. checked the RX/TX leads, swapped and tried checked the loopback which seemed to report ok...but nothing.

tried covering the motor with piece of card, followed the instructions...but nothing doing...any suggestions?
for the record, i am 'seeig' the drive in disk management...but no data or any capacity.

A couple more questions (try to answer them all)


1.So your loopback was successful?

2. What kind of converter did you use? Is it powered at 3.3V or 5V?

3. Did you put SATA power on your hdd?

4. Is it now seen in BIOS?

5. Did you have comms with your hdd before?

Edited by BlouBul, 27 March 2011 - 09:08 AM.

Jack of all trades, master of none, though ofttimes better than master of one.

#3647
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86



ok just spent several hours trying, but no comms between hdd and hyperterminal. checked the RX/TX leads, swapped and tried checked the loopback which seemed to report ok...but nothing.

tried covering the motor with piece of card, followed the instructions...but nothing doing...any suggestions?
for the record, i am 'seeig' the drive in disk management...but no data or any capacity.

A couple more questions (try to answer them all)


1.So your loopback was successful?

2. What kind of converter did you use? Is it powered at 3.3V or 5V?

3. Did you put SATA power on your hdd?

4. Is it now seen in BIOS?

5. Did you have comms with your hdd before?



1. loopback seemed to have success as the converter displays LED lights and also on hyperterminal as we typed it showed up as per the carterincanada explanation

2. convertor 3.3 powered from molex from PC PSU

3. SATA power on HDD yes...but not spinning up

4. yes seen in bios on freinds pc (his is XP) not on mine (mine is vista)

5. i dont think i had comms before (in what way do you mean) (through hyperterminal?)

#3648
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

1. loopback seemed to have success as the converter displays LED lights and also on hyperterminal as we typed it showed up as per the carterincanada explanation

2. convertor 3.3 powered from molex from PC PSU

3. SATA power on HDD yes...but not spinning up

4. yes seen in bios on freinds pc (his is XP) not on mine (mine is vista)

5. i dont think i had comms before (in what way do you mean) (through hyperterminal?)

Thanks :)
Now I have a better idea of what is going on. I was not sure if you did half a fix before and that was the reason for the strange things.

That said, there are a couple of strange things that I am not sure about. Let us do it one at a time.
The first one is that it is seen on your friends pc in BIOS and not on yours. One possibility is that your sata power cable is damaged (that would also explain why your converter is not seen by your hdd) Check all cables and connections thoroughly (use different cables if you can).
Jack of all trades, master of none, though ofttimes better than master of one.

#3649
corkyblue

corkyblue

    Newbie

  • Member
  • 27 posts
  • Joined 02-March 11
  • OS:Vista Home x86



1. loopback seemed to have success as the converter displays LED lights and also on hyperterminal as we typed it showed up as per the carterincanada explanation

2. convertor 3.3 powered from molex from PC PSU

3. SATA power on HDD yes...but not spinning up

4. yes seen in bios on freinds pc (his is XP) not on mine (mine is vista)

5. i dont think i had comms before (in what way do you mean) (through hyperterminal?)

Thanks :)
Now I have a better idea of what is going on. I was not sure if you did half a fix before and that was the reason for the strange things.

That said, there are a couple of strange things that I am not sure about. Let us do it one at a time.
The first one is that it is seen on your friends pc in BIOS and not on yours. One possibility is that your sata power cable is damaged (that would also explain why your converter is not seen by your hdd) Check all cables and connections thoroughly (use different cables if you can).



i can try the drive via usb enclosure if thats worthwhile too?

#3650
BlouBul

BlouBul

    Advanced Member

  • Member
  • PipPipPip
  • 409 posts
  • Joined 13-July 10
  • OS:Windows 7 x86
  • Country: Country Flag

i can try the drive via usb enclosure if thats worthwhile too?

Yes, see what happens :)
Jack of all trades, master of none, though ofttimes better than master of one.




12 user(s) are reading this topic

0 members, 12 guests, 0 anonymous users