Hello Following the Post launched, I had contact with @michael chiklis, who confirmed what was also said by Spildit, I take this opportunity to thank them for the attention to the case, the thing has gone on, but I'm afraid it is in a negative sense. I do a chronology, because maybe I can make the situation better understood. HDD from nothing, it is no longer recognized by the Win7 64bit OS. When restarted, the BIOS of my Asus Maximus VI Extreme does not recognize the disk. I try to unlock it with RS232 and Hyper Terminal, with the known procedure for 7200.11 discs. I did not know mine is 7200.12. Attempt done by isolating the PCB from the physical disk. But from the terminal I had the white screen, any command I tried to insert. The commands used are those described in previous posts. The disk was connected via RS232 (USB) to a notebook with Win7 and power from an external source. I tried both powering the disk before connecting it to the notebook, and later. Since I did not see anything on the Hyper Terminal, I made several attempts. In one of the attempts I only had a screen with type: LED: 00000047 FAddr: FFFFFFFE LED: 00000047 FAddr: FFFFFFFE LED: 00000047 FAddr: FFFFFFFE Repeated 3 times with a separation line between them. I only remember that they were with the word LED, but I'm not sure of the rest of the strings. After I connected the disk to the PC, with the SATA cable and the disk was visible from the BIOS, but with a capacity totally different from the real 2TB. Given the disk was recognized, but incorrectly, I tried to test with SeaTools, and as already written, SMART Test "Ok", Quick and Generic Test "Failed". So far, it would seem to be a problem of sector allocation. Just by doing a final test, connecting the disk via RS232 (USB) to the Notebook, starting Hyper Terminal, enter the link properties, just start the disk power (Without PCB isolation - Physical Disc), on Hyper Terminal I get out as follows:
Boot 0x40M Spin Up FAIL Servo Op = 0100 Resp = 0003 0100 0000 The rest all 0 ResponseFrame 1980 and then a series of hexadecimal numbers Then again FAIL Servo Op = 0100 Resp = 0003 0100 0000 The rest all 0 ResponseFrame 23C0 and then a series of hexadecimal numbers
The disk is not strange ticking. I hear the engine that makes 2 attempts to Boot as soon as I connect the power supply, but then it does not make any more noise. Since I have this problem, it has always behaved in this way. Will it really be a physical problem, or maybe a PCB problem?
|