Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Seagate ST1000DM003 - not detected in Bios

August 10th, 2016, 6:26

Hi!
It's my first post here, sorry for my english :)

Seagate ST1000DM003
PN: 1ER162-300
FW: CC43
Board number: 100724095 rev A

The drive is not being detected by Bios. When connected to terminal, HDD allow me to log in to the console, I can switch between levels, but I can't do anything else. Drive doesn't respond to commands like SpinDown, Translator repair, etc:
Code:
Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
TCC:001F

SNOOOZZZZZZEEE Retry
EDAC Value = 0000F018E59EDCE4
SNOOOZZZZZZEEE Retry
EDAC Value = 0000F018E59EDCE4
SIM Error 2042 LBA 0000000000090FCA FD FC359028
RW Error 00000080
No HOST FIS-ReadyStatusFlags 0002A1A1
ASCII Diag mode

F3 T>/2

F3 2>Z

F3 2> - here the motor doesn't spin down

Reaction for translator rebuild is the same - no reaction and no anwser from the drive.

Am I missing something? I'm working without shorted "read channel" pins (I think there's no need if I can access the console, I don't even know, which pins should be short). Can this be a bad head or HSA problem? I don't get any LED errors, except the N1 command, wchich returns some (but I don't have any log).

Re: Seagate ST1000DM003 - not detected in Bios

August 10th, 2016, 6:48

Code:
F3 T>ctrl + x

?

Re: Seagate ST1000DM003 - not detected in Bios

August 10th, 2016, 9:57

This may be a model with locked terminal access. Do you have a current PC3K system?

Re: Seagate ST1000DM003 - not detected in Bios

August 11th, 2016, 2:41

jermy
No reaction, nothing happening when pressing keys.

lcoughey
I'm using only simple RS232TTL adapter with HyperTerminal.

I found, that I can't read any info from SA:
Code:
F3 T>V1

DiagError 00005104
DiagError 00005104
Invalid Diag Cmd Parameter

Same reaction for V2, V8, V10, V20, V40, V80, V100.
Only V4 returns some info:
Code:
F3 T>V4
Reassigned Sectors List Enabled
Entries: 0000, Alts: 0000, Removed: 002D,
Pending: 0000 Host Pending: 0000
Idx  LBA          PBA          LLLCHS of LBA Wdg PLPCHS of PBA SFI    Hours Msecs  Status   BBM Mask

Re: Seagate ST1000DM003 - not detected in Bios

August 12th, 2016, 13:13

Type CTRL+Z and you should see a prompt like this F3 T>
F3 T> Type /2 and press (enter). It should say F3 2>
F3 2> Type Z (enter)

Now you'll see something like that;
Spin Down Complete
Elapsed Time 0.137 msecs (the time won't be same as here)F3 2>

Now carefull remove piece of paper with drive still powered by SATA power cable and TX/RX lies connected.
Carefully screw PCB board back on HDD case. (make sure that the screws don't short the PCB board)
To start the motor, type U
F3 2>U (enter)

Now it should look something like this:
Spin Up Complete
Elapsed Time 7.129secs

To go to Level 1 type /1 and hit enter
F3 2>/1

Create S.M.A.R.T. sector
Type N1 (enter)


IMPORTANT Power off the drive, wait 10 seconds and now Power ON your drive.

Press CTRL+Z on terminal and type:(case sensitive!!!!)

F3 T>m0,2,2,,,,,22 (enter)

After 15-30 seconds, you should see something like:

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

Re: Seagate ST1000DM003 - not detected in Bios

August 13th, 2016, 5:53

Disk have locked terminal access - that's the reason of it's weird respond on commands. As I found, for now there's no way to unlock it at home - am I right?

Re: Seagate ST1000DM003 - not detected in Bios

August 13th, 2016, 22:30

ogryz wrote:Disk have locked terminal access - that's the reason of it's weird respond on commands. As I found, for now there's no way to unlock it at home - am I right?


Yep, as already mentioned lcoughey

Re: Seagate ST1000DM003 - not detected in Bios

August 14th, 2016, 3:35

Yes he did. I also found similar topic with identical drive, and I'm 100% sure now.

Thanks for all, especially for lcoughey for proper diagnose.
Post a reply