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
August 29th, 2011, 17:56
Hello,
i'm new to this forum...
maybe someone can help me with the following error:
Rst 0x40M
RW: Disc Ctlr Initialization Completed.
MC Internal LPC Process
(P) SATA Reset
User Data Base 00991550
MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MC Seg Disc and Cache Nodes: 4011985C 4011796C
Seg Write Preamble VBM start: 000010A7 end: 000010CE
Footer - start: 000010D0 end: 000010F7
Seg Read Preamble VBM - start: 000010F9 end: 00001120
Footer - start: 00001122 end: 00001149
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 22E0
Nonvolatile MCMT sequence number 000B7C3E
[RSRS] 21EB
Reconstruction: EXCEPTION: Segment Overall Sequence Number Mismatch
000B7C2F 000B525B
[MCMTWS]
Reconstruction Fail: Burly Case
MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00005101
MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A
MCMainPOR: MCStateFlags = 00005101
MCMainPOR: Feature Disabled...
No HOST FIS-ReadyStatusFlags 0002A1E1
greetings from austria
netviewdm
August 30th, 2011, 3:02
Can you explain what's the drive beaviour?
August 30th, 2011, 9:58
From Ace website:
http://www.acelaboratory.com/pc3000.udma.ver4.5.4.phpWe have introduced a password removal mode via Terminal. This mode is important for 7200.12 hard disk drives and drives similar to them in which "No HOST Fis-ReadyStatusFlags" message appears in Terminal when service information is not available and HDD doesn't get ready state.
I just love Google!
August 30th, 2011, 10:33
Hello again,
sorry for my incomplete error description.
the problem ist, that the drive isn't recognized in the bios...
August 30th, 2011, 10:36
But it spins, doesn't spin? Heads knock, doesn't knock? Stops spindle or keeps running?
August 30th, 2011, 10:44
spins up, just the initial sound from the head - so i would say normal sound.
already tried to change the pcb - but also no detection with the other pcb...
August 30th, 2011, 11:17
Well, if you simply swap PCB, you don't have a chance, as ROM is unique for those drives, and you have to swap it also.
Do you have any experience on DR?
August 30th, 2011, 16:18
yes but its some time ago... (in those days where maxtor had stucking heads in the park position, manually repair mft and so on...)
but with the new drives not really - but i think i'd be able to do some work with the terminal modus, if this would help like the bsy trouble of other seagate hdd (ok, not really the challenge

)
August 31st, 2011, 3:17
Well, if you have you can start to swap PCB+ROM and check beaviour.
After that, try to check if you can access anything on SA like defect lists for example.
August 31st, 2011, 6:57
Since disk spins up but stays busy, why would you change PCB?
As Dick's post says, I think UDMA can handle this.
September 28th, 2012, 3:44
Hello,
I have the same drive with a similar problem. It spins up, starts initialization, several clicks and spins down. The strange thing is that it doesn't appear in terminal! I used the settings for for Barracuda 7200.11 and 7200.12. and the terminal connection is checked OK. Any suggestions?
September 28th, 2012, 4:56
If the drive is spinning down, most probably you have heads damaged.
September 28th, 2012, 5:27
dmarques wrote:If the drive is spinning down, most probably you have heads damaged.
Can this explain the lack of terminal connection?
September 28th, 2012, 11:56
That can be due to several things.
Terminal can be damaged, USB cable can be damaged or even the drive may have terminal locked.
September 29th, 2012, 3:54
Terminal is fine, no doubts about it. No USB cable.So what do you mean by
"the drive may have terminal locked" ?
October 1st, 2012, 3:05
There are certain drives where you can't access terminal log unless you short circuit the reading channel.
October 1st, 2012, 3:29
if the terminal is working properly so you have problem in HDD head.
October 1st, 2012, 3:39
dmarques wrote:There are certain drives where you can't access terminal log unless you short circuit the reading channel.
And some othere where it is not enough either
Powered by phpBB © phpBB Group.