Page 1 of 1

Toshiba MK3265GSXV - G-List Error

Posted: 04.07.12, 17:19
by lcoughey
Drive slow to detect, but does show full model, serial, firmware and capacity.
Techno On............................... : Ok

Zone table.............................. : Ok
Cyl num................................. : 178 407
Head num................................ : 2
Vendor.................................. : TOSHIBA
Model................................... : MK6465GSXV
Microcode............................... : GH011M6


G-List reading error.................... : G-List read error; Device Error Detected 51/19 (AMN;;INF)

CP Avalable............................. : 33,34,44,56,92,95,98,9A,9B,9C,A2,A5,A8,A9,AA,AD,AE ,AF,B1,B3,B5,B6,BB,BD,C1,C4,C5,C6,C7,C8,C9,CB,CD,D 0,D1,D4,D6,D7,D8,D9,DA,DB,DD,E0,E1,E2,E3,F3,F5

Can save all the CP modules.

Modules BB(SH) and BD(SF) have Checksum errors.

We are working with donor heads. We cannot read any sectors.

Clear SMART fails.
Clear G-List works, but does not make any difference.

Any suggestions?

Re: Toshiba MK3265GSXV - G-List Error

Posted: 17.07.12, 06:05
by RescueDRL@gmail.com
there is a new tool for Toshiba G-List from Acelab in PC3K UDMA 5.1 update, i havent tried it yet (no drive to test on) but give it a try and let us know.

Re: Toshiba MK3265GSXV - G-List Error

Posted: 17.07.12, 15:40
by lcoughey
We had no luck with it and neither could they figure it out remotely. The project is now closed and gone.

Re: Toshiba MK3265GSXV - G-List Error

Posted: 19.07.12, 19:01
by Balvan
I just installed the latest update and tried it on a MK7559GSX. Same symptoms as Luke's drive and same result -- no fix.

Re: Toshiba MK3265GSXV - G-List Error

Posted: 18.09.12, 05:19
by hddstudio
I just got two data recovery cases with MK3265GSX. Both drives have same problem "G-List reading error". Model, serial, firmware and capacity detected normally but no access to sector at all.
Solution is : directly building head map in DE and copy success 99.9% with 4 insignificant bad sectors problem.

May be I was just lucky, or ?
I think solutions with G-List clearing would fail if drive suffers damaged head or media. One of patient's drive took more than 1200 ms to reach readiness after clearing G-List. But I still could clone all sectors in DE