If you have HubbleLT with dead head, you can use PCB from HubbleLT to run ARCO as LT, not LT2
A question
Re: A question
Why never? May be, someday, somebody will publish 04
If you have HubbleLT with dead head, you can use PCB from HubbleLT to run ARCO as LT, not LT2
If you have HubbleLT with dead head, you can use PCB from HubbleLT to run ARCO as LT, not LT2
Re: A question
I was just asking.Vlad писал(а):Why never? May be, someday, somebody will publish 04
If you have HubbleLT with dead head, you can use PCB from HubbleLT to run ARCO as LT, not LT2
I'm sure there's a possibility to get mod 04 in the future. Thanks for the info about using the HubbleLT PCB. I don't have a HubbleLT drive at this time. However, It's definitely nice to know this can be done.Re: A question
Thanks. I'll most likely get the whole drive in the future.Smyg писал(а):https://www.google.com/search?q=2060-771959-000Beamg писал(а):I don't have a HubbleLT drive at this time.
Re: A question
So,
I'm currently near the final ARCO steps (WriteWRRO) on an old 1TB WD10JPVT-55A1YT0 drive. I used the TREX FW for the Firebird drive. However, it only has created 372 modules. I have a donor FW for the same model which shows this model should have 476 modules. How do I go about getting the missing modules? Keep in mind I don't have the original modules. Only donor FW modules. I just would like to see if I can get the drive working again. It already shows it was sized down to 768GB after the Zone TPI calc test. This test alone took a over a day to complete.
I'm currently near the final ARCO steps (WriteWRRO) on an old 1TB WD10JPVT-55A1YT0 drive. I used the TREX FW for the Firebird drive. However, it only has created 372 modules. I have a donor FW for the same model which shows this model should have 476 modules. How do I go about getting the missing modules? Keep in mind I don't have the original modules. Only donor FW modules. I just would like to see if I can get the drive working again. It already shows it was sized down to 768GB after the Zone TPI calc test. This test alone took a over a day to complete.
Re: A question
No need to do something with modules, if ARCO and SelfScan will be completed without errors
Re: A question
Sorry to hijack thread but I have a related question.
I have a WD3200BEVT-11A03T0 with PCB 701609. I accidentally rewrote the ROM from another WD3200BEVT but different firmware version.
Now the drive will not spin up. There is no external ROM so PCB seems bricked.
Is there any way to rewrite the ROM using TTL for these PCBs?
I have a WD3200BEVT-11A03T0 with PCB 701609. I accidentally rewrote the ROM from another WD3200BEVT but different firmware version.
Now the drive will not spin up. There is no external ROM so PCB seems bricked.
Is there any way to rewrite the ROM using TTL for these PCBs?
Re: A question
in WDMarvel - no
Re: A question
Ok thanks Vlad.
I am trying to access data on a WD3200BEVT-11A03T0 (PCB 701609) with failed PCB. I have a donor working 701609 PCB from the same model drive, but the donor has a different ROM version, and I can't find a ROM that is compatible with the patient drive to get it to initialise properly.
Using the donor PCB, I can get the drive to a ready state and read all firmware, but drive shows as 0lba. The modules on the platters which usually contain the ROM modules are all Not Init, so I can't rebuild rom from firmware on the platters.
According to Module 11 the firmware version is 5002B. Does anyone have a ROM version 5002B from a WD3200BEVT-11A03T0 they'd be kind enough to share?
I am trying to access data on a WD3200BEVT-11A03T0 (PCB 701609) with failed PCB. I have a donor working 701609 PCB from the same model drive, but the donor has a different ROM version, and I can't find a ROM that is compatible with the patient drive to get it to initialise properly.
Using the donor PCB, I can get the drive to a ready state and read all firmware, but drive shows as 0lba. The modules on the platters which usually contain the ROM modules are all Not Init, so I can't rebuild rom from firmware on the platters.
According to Module 11 the firmware version is 5002B. Does anyone have a ROM version 5002B from a WD3200BEVT-11A03T0 they'd be kind enough to share?
Re: A question
Baraka you can rebulid from Module 40, ROM module 47. 4F you can adapt from donor ROM, 30 module tshi si Plist SA ypu can adapt from donor ROM.
And Same ROM you can via Terminal in boot code using china Soft on internet you can find it.
And Same ROM you can via Terminal in boot code using china Soft on internet you can find it.
Hello everyone, sorry for my english, because am using google translator.
Re: A question
So, I have a few more questions.
Vlad,
After ARCO and SelfScan pass with new factory FW, how do you enable the ATA security function again? I tried ticking the check box in config mod 02 to change security to supported.
However, it still won't accept passwords via ATA.
Also, what does ARCO error code 72ED mean? This error occurs during the RWGap Calibration test.
BTW, I just found the factory FW package for the HubbleLT2 500GB drive! Which contains mod04. Why were you hiding it? Currently testing it out.
Vlad,
After ARCO and SelfScan pass with new factory FW, how do you enable the ATA security function again? I tried ticking the check box in config mod 02 to change security to supported.
However, it still won't accept passwords via ATA.
Also, what does ARCO error code 72ED mean? This error occurs during the RWGap Calibration test.
BTW, I just found the factory FW package for the HubbleLT2 500GB drive! Which contains mod04. Why were you hiding it?
Currently testing it out.