Page 1 of 1

Toshiba 3tb DT01ACA300 Not reading ID

Posted: 04.09.19, 09:19
by odedshankar
Hi Guys,

I've got this Toshiba 3tb DT01ACA300(AAA, AA00/BB0) FW:0006MX6NBBB0 which is not ID'd, stays spinning and there are no noises so i am suspecting it is a firmware problem.
I tried to use the instructions as explained in the following post without luck:
https://www.data-medics.com/forum/hitac ... t1280.html

Would love to hear any insights you may have, and if you've got the firmware for this drive it would be great.

Thanks

Re: Toshiba 3tb DT01ACA300 Not reading ID

Posted: 27.07.22, 03:38
by elbote83
hello odedshankar, did you solved it?

Thanks

Re: Toshiba 3tb DT01ACA300 Not reading ID

Posted: 27.07.22, 04:14
by odedshankar
Hi Mate,
To be honest it was 3 years ago and i don't remember the case that much at this stage as i've seen hundreds of drives since.
If i remeber correctly it was resolved, but i'm not sure wht i did at the time.
As far as i remeber i had to use an Hitachi Utility in PC3K as it is a rebranded HGST drive by Toshiba, and after getiing through the Utility there twice i had access to the drive.
Sorry that i couldn't be more helpfull, hoepfully it helps.

Cheers

Re: Toshiba 3tb DT01ACA300 Not reading ID

Posted: 28.07.22, 02:41
by elbote83
hello, every information can be useful, thanks a lot

Re: Toshiba 3tb DT01ACA300 Not reading ID

Posted: 24.04.24, 09:56
by gameboybin
I'm curious about this case also. Got this Toshiba DT01ACA050. Drive was spinning without any noises. Cannot ID. Upon opening utility got this error messages
Attachments
436838360_1139876913710334_1432267282724754279_n.jpg
436838360_1139876913710334_1432267282724754279_n.jpg (91.04 KiB) Viewed 6471 times
435216302_707166278053171_4443854774300486801_n.jpg
435216302_707166278053171_4443854774300486801_n.jpg (84.22 KiB) Viewed 6471 times

Re: Toshiba 3tb DT01ACA300 Not reading ID

Posted: 28.12.24, 03:38
by XiaoShen
The firmware is damaged. After uploading the same version of firmware, the damaged hard drive firmware can be read. Some firmware offsets need to be manually processed