View topic - Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Page 8 of 10

[ 185 posts ]

Go to page Previous 1 ... 5, 6, 7, 8, 9, 10 Next

Previous topic | Next topic

Author

Message

viald

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 13:00

Joined: July 10th, 2009, 12:12
Posts: 7
Location: France

What was suspicious before, both HD were not referenced by segeate as defective and should not need a firmware upgrade.
But, they had stopped working at the same time with the LBA issue. Perhaps I should not upgrade the firmware !?

Top

BlackST

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 16:39

Joined: July 18th, 2006, 3:05
Posts: 7474
Location: ITALY

Sorry for being SO clear but this is what happened.

- The drive was showing 0 capacity
- You assumed that it was a problem that can be "fixed" with the stuff you have found on the internet
- You didn't diagnose exactly what the original problem was
- You couldn't and didn't backup all the drive firmware
- You applied the procedure found on the net (assuming you knew it is RISKY and DOES NOT ALWAYS APPLY - but there was no precise initial diagnose)
- The thing worked partially (the problem was elsewhere, now is perfectly clear) but you didn't realize UNTIL trying to access a particular zone of the user area
- At this point you applied a not necessary but theoretically harmless (FOR A DRIVE IN NORMAL OPERATING CONDITIONS) FW update
- The problem came out.

This could be avoided initially BY HAVING A PRO ANALYSING THE DRIVE (at cost). Now we have another problem beside the initial one that I think it was and it's elsewhere. Information, when not supported by strong theory and knowledge about HOW to work, can have side effects. Who to blame ?

Top

viald

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 16:50

Joined: July 10th, 2009, 12:12
Posts: 7
Location: France

You have right. But my question is not about the person to blame. I'm not responsible about the poor Seagate hardware quality.
Perhaps it's to late, but I'm asking people for help, hoping it still exists a solution.

Quote:

This could be avoided initially BY HAVING A PRO ANALYSING THE DRIVE (at cost)

No ! This could be avoiding by don't buying Seagate product !

Thank you.

Top

BlackST

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 16:54

Joined: July 18th, 2006, 3:05
Posts: 7474
Location: ITALY

Yes I have, but you have to send the drive and it's not for free, so it's like I don't have a solution. And hoping there is no further damage.

About Seagate quality, it's not always true. If you don't "scratch the nose" to these drives and let them operate in STANDARD conditions, with SPECIFIED power, they are not prone to fail more than other. But end users....are another story.

Last edited by BlackST on July 10th, 2009, 16:57, edited 1 time in total.

Top

zebong

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 16:56

Joined: December 24th, 2007, 16:08
Posts: 1420
Location: EUROPE

You say that is from a RAID 5, how many disk have the array ?

ZeBong

_________________
ZeBong
" что случилось в России - останется в России "
" Россия еще раз"

Top

viald

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 17:02

Joined: July 10th, 2009, 12:12
Posts: 7
Location: France

4 disks, including the 1T maxtor and seagate plus 1T Samsung and 1T Hitatchi.
I didn't know that Maxtor and Seagate was from the same manufacture. They crashed both at the same time, with the same issue ! Thank you Seagate !

Top

BlackST

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 17:44

Joined: July 18th, 2006, 3:05
Posts: 7474
Location: ITALY

Same time ? I would thank the power supply or something else HARDWARE RELATED, not Seagate.
We know exactly when the problem happens.

Top

pcimage

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 10th, 2009, 18:02

Joined: November 29th, 2006, 10:08
Posts: 7843
Location: UK

On this occasion I have to agree with BlackST, it's hardly Seagate's fault this one I think.

Seagate may have their problems with certain drives (7.01, 3.CAE, SD15 etc...) but even they cannot be blamed for 4 drives simultaneously failing, especially as one was a Samsung and another was a Hitachi :-)

Note I've not mentioned the notorious 7200.10 seized spindle issue, this 99/100 times would not happen if the user hadn't dropped the drive, so not strictly speaking entirely Seagates fault.

But 7.01/3.CAE IMHO are their cheap nasty Chinese factory problem, but getting them to admit it and recall them is another kettle of fish entirely!

Sean

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

Top

viald

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 11th, 2009, 2:25

Joined: July 10th, 2009, 12:12
Posts: 7
Location: France

pcimage wrote:

but even they cannot be blamed for 4 drives simultaneously failing, especially as one was a Samsung and another was a Hitachi :-)

Only Seagate and Maxtor has failed, the Hitatchi and the Samsung still running. I have an other RAID5 on the same server with 4 others disks (without Segeate and Maxtor). And this Raid5 still running too. It can't be a power issue.

pcimage wrote:

Note I've not mentioned the notorious 7200.10 seized spindle issue, this 99/100 times would not happen if the user hadn't dropped the drive, so not strictly speaking entirely Seagates fault.

I had not dropped the drives. They failed both when the server was running. Next reboot shows the disks with 0 LBA issue.

Top

BlackST

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 11th, 2009, 2:33

Joined: July 18th, 2006, 3:05
Posts: 7474
Location: ITALY

Yes it can - may be. Samsung is different. Sorry I can't help no more here.

Top

pcimage

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 11th, 2009, 3:52

Joined: November 29th, 2006, 10:08
Posts: 7843
Location: UK

Firstly, you never said that the Samsung and Hitachi were still working. So how were we to know?

Secondly, I wasn't actually implying that YOU had dropped the drives, just that people tend to complain about this common problem when they've brought about the problem themelves.

Thirdly, as you said that your drives were from an UNAFFECTED batch, then you have the diagnosis wrong and applied a fix for a specific problem that didn't exist on your drives. The "LED 000000CC" error as far as I know is the drive "locking" itself to prevent further harm when an issue has occurred.

What are the model and original f/w of your bad drives? (Maybe Doomer or someone else can confirm if they are indeed affected)

And you can categorically state that you have no power issue when two drives die simultaneously? I was trying to help, but I'm outta here now as you obviously know better than us guys. Good luck

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

Top

viald

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 14th, 2009, 13:57

Joined: July 10th, 2009, 12:12
Posts: 7
Location: France

pcimage wrote:

What are the model and original f/w of your bad drives? (Maybe Doomer or someone else can confirm if they are indeed affected)

Seagate ST31000340AS
Part: 9BX158-303
Serial: 9QJ0TCCC
Old Firmware: SD15

Maxtor STM31000340AS
Part: 9GT158-325
Serial: 5QJ074FB
Old Firmware: MX15
New one: MX1A

pcimage wrote:

And you can categorically state that you have no power issue when two drives die simultaneously?

Yes I'm sure

pcimage wrote:

I was trying to help

And I thank you.

Below smarctl information from the Maxtor:

Code:

=== START OF INFORMATION SECTION ===
Device Model:     MAXTOR STM31000340AS
Serial Number:    5QJ074FB
Firmware Version: MX1A
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Jul 12 12:01:06 2009 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                 ( 634) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 224) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103b) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   109   099   006    Pre-fail  Always       -       146094291
  3 Spin_Up_Time            0x0003   093   091   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1309
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   069   069   030    Pre-fail  Always       -       68885281470
  9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       8249
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       1
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1771
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       156
188 Unknown_Attribute       0x0032   099   099   000    Old_age   Always       -       65537
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   074   067   045    Old_age   Always       -       26 (Lifetime Min/Max 19/26)
194 Temperature_Celsius     0x0022   026   040   000    Old_age   Always       -       26 (0 19 0 0)
195 Hardware_ECC_Recovered  0x001a   041   041   000    Old_age   Always       -       146094291
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 162 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
       CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 162 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 50 ff ff ff 4f 00      05:19:40.996  READ FPDMA QUEUED
  60 00 c0 ff ff ff 4f 00      05:19:40.995  READ FPDMA QUEUED
  60 00 40 ff ff ff 4f 00      05:19:40.995  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:40.995  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:40.995  READ FPDMA QUEUED

Error 161 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 58 ff ff ff 4f 00      05:19:37.989  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:37.989  READ FPDMA QUEUED
  60 00 e8 ff ff ff 4f 00      05:19:37.988  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      05:19:37.988  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00      05:19:37.973  READ FPDMA QUEUED

Error 160 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 10 ff ff ff 4f 00      05:19:35.017  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:35.017  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      05:19:35.017  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      05:19:35.016  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00      05:19:35.016  READ FPDMA QUEUED

Error 159 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 d8 ff ff ff 4f 00      05:19:32.018  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:32.017  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:32.017  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:32.016  READ FPDMA QUEUED
  60 00 58 ff ff ff 4f 00      05:19:32.016  READ FPDMA QUEUED

Error 158 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.
 After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 58 ff ff ff 4f 00      05:19:37.989  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:37.989  READ FPDMA QUEUED
  60 00 e8 ff ff ff 4f 00      05:19:37.988  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      05:19:37.988  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00      05:19:37.973  READ FPDMA QUEUED

Error 160 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 10 ff ff ff 4f 00      05:19:35.017  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:35.017  READ FPDMA QUEUED
  60 00 20 ff ff ff 4f 00      05:19:35.017  READ FPDMA QUEUED
  60 00 e0 ff ff ff 4f 00      05:19:35.016  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00      05:19:35.016  READ FPDMA QUEUED

Error 159 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 d8 ff ff ff 4f 00      05:19:32.018  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:32.017  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:32.017  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:32.016  READ FPDMA QUEUED
  60 00 58 ff ff ff 4f 00      05:19:32.016  READ FPDMA QUEUED

Error 158 occurred at disk power-on lifetime: 8241 hours (343 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 58 ff ff ff 4f 00      05:19:29.026  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      05:19:29.026  READ FPDMA QUEUED
  60 00 d8 ff ff ff 4f 00      05:19:29.025  READ FPDMA QUEUED
  60 00 38 ff ff ff 4f 00      05:19:28.988  READ FPDMA QUEUED
  60 00 f0 ff ff ff 4f 00      05:19:28.988  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Top

frodo.baggins

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 28th, 2009, 4:09

Joined: July 6th, 2009, 11:55
Posts: 3
Location: italy

Hi all,

I've a Seagate Barracuda 500 Gb (ST3500820AS) not recognized by BIOS and I've tried to follow the guide but the result was:

Code:

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.146 msecs
F3 2>U

Error 1009 DETSEC 00006008
Spin Error
Elapsed Time 7 mins 17 secs
R/W Status 2 R/W Error 84150180
F3 2>

Is the HDD dead and the data lost forever?

Top

Russwinters

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 28th, 2009, 12:48

Joined: July 16th, 2008, 17:52
Posts: 489
Location: Long Beach, California

Quote:

Error 1009 DETSEC 00006008
Spin Error

This drive doesn't have firmware issue; this is mechanical. Probably spindle

Top

drc

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: July 28th, 2009, 13:10

Joined: August 12th, 2008, 13:11
Posts: 3235
Location: USA

For the love of god, make new threads...

_________________
You don't have to backup all of your files, just the ones you want to keep.

Top

Killerslug

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: August 2nd, 2009, 18:49

Joined: August 2nd, 2009, 18:41
Posts: 1
Location: Sweden

Hello. Just want to say that theese posts saved my day. I'm far from an expert but i'm an experienced user that have encounterd many known and unknown hardwareproblems out there. Seems to have bad luck that way but at least you get som experience with tinkering around untill you find the solution . I understanded the risks but found them exeptable. I got the equipment needed and followed the steps. And that saved me 700 Gb of data =) Couldn't have done it without this forum. Thanks alot :mrgreen:

Top

Junior0409

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: August 3rd, 2009, 22:23

Joined: March 27th, 2009, 3:10
Posts: 76
Location: Wisconsin

bigal.nz wrote:

prodata wrote:

the reason is so simple.

WILL A DOCTOR GIVE OR TEACH DIY MANUAL. SO EVERY USER CAN HEAL THEIR ILLNESS BY THEMSELF....???

I think the Doctor will.. But not a FULL one.. there is only some information and advice but not Fully direct the user to DIY...

To compare a doctor who holds a person life in there hands, and data recovery is unrealistic. What is at stake in your example is completely disportionate (sp), but to use your example:

If you were on a yacht at sea and you could not get to a doctor but had to preform say a trachotomy (akin to the person who has lost there data, but cant afford a DR expert) would the doctor then give instructions over a radio on how to perform the trachotomy to save the life? (akin to giving instructions here on the forum) YES of course the doctor would. The person may very well still die if the trachotomy is not done right (they may still loose there data if not done right) but in both cases they have nothing to loose because if they do nothing they die (loose data) anyway!

-Al

I saw very scenario on M*A*S*H once. :lol:

Top

itp

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: September 24th, 2009, 17:50

Joined: September 21st, 2009, 11:36
Posts: 6
Location: Lima, Peru

To return to the simple fact if it works or not: I consider myself a (minor) expert on DR and asked a friend to build this device for me. Costed me about $10, but I was happy to pay it. To prevent power-problems we used a second PSU to power it and used the lines suggested in other forums. A small test on a working drive did no damage, it is still running and the only drive in the computer I'm using to write this reply.

This small device already saved 2 drives of customers of mine, without using my SD-doctors. I agree, you really have to follow the instructions to the letter (capitals or not), because else the chance of F-ing up four drive are tremendous, but with me it worked wonders. Thanks very much for this option!

Top

dmac

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: October 2nd, 2009, 18:39

Joined: October 2nd, 2009, 18:34
Posts: 2
Location: Kansas City

I am having the LBA 0 error with my Seagate hard drive and I purchased this cable that your recommended. Does it require anything else other than connecting this cable correctly the the hard drive and supplying power to be able to use in Hyper Terminal to repair. I would appreciate any help you can offer.

Thank you,
Darrin

Top

N.C.

Post subject: Re: Tutorial: resolve 0 LBA,SEAGATE 7200.11 BIOS don't recognize

Posted: October 2nd, 2009, 18:48

Joined: March 28th, 2008, 7:52
Posts: 1466
Location: Europe, Hungary

Hi,

This tutorial is not for beginners.
If your data is important, ask somebody for do it for you, who have done this at least 1 time successfully.
If you make any mistake, you can render your drive unrecoverable.

Janos

results-the-yourself-solutions-t11912.html

Top

Page 8 of 10

[ 185 posts ]

Go to page Previous 1 ... 5, 6, 7, 8, 9, 10 Next

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 100 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum