All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 85 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next
Author Message
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: December 31st, 2015, 20:25 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
What do you think then ?

Replace MCU ? I don't think it would be MCU/PCB related.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: December 31st, 2015, 20:39 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
I mean sytuaution when backup rom module's and rom. Initialization mcu Exceeded timeout. Reaction same PCB is very slowly.

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: December 31st, 2015, 22:58 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 14945
Location: Australia
pikus_09 wrote:
O Hello Frank, so are you suggesting that it may be fault ROM code?
No, my own program was faulty. It wasn't able to detect the code modules in the second half of the ROM. I have since fixed the problem and all the checksums are OK.

BTW, I'm not sure I understand your problem. You appear to be saying that your drive is OK but WDMarvel doesn't give you access to the SA. So is your question just a technical one rather than a data recovery issue or a HDD performance issue?

If so, and assuming that WDMarvel does not have a bug, ISTM that either the ROM code or a particular SA module is locking you out of the SA (by disabling VSCs?). IIUC, Moltke replaced the ROM code with a version which he believed was not locked, but you were still unable to access the SA, so this would point to an SA module as the culprit. The next line of attack was to hide the SA from the ROM by displacing SA regions 0 and 1 by +1 sector in module 0x20B. Would it not have been advisable to also adjust the location of module 01 by -1 sector? In this way the ROM would still find module 1 but would not be able to find the others.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 4:28 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
Frank, he can access SA.
What he can't do is RUN ARCO (calibration that he needs to do prior to self scan).
He is trying to self-scan the drive an he can't but he can read modules ok.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 4:34 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
I would say WD changed something on the ARCO procedure and now you can't start it with WDMarvel, same as when they changed SS so it requires unlocking.
Test with drive from the exact same model.
If it doesn't work then WDMarvel can't run ARCO on those drives. If it does work then the problem is with your specific drive.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 9:21 
Offline

Joined: October 24th, 2005, 17:04
Posts: 254
fzabkar wrote:
Would it not have been advisable to also adjust the location of module 01 by -1 sector? In this way the ROM would still find module 1 but would not be able to find the others.

shifting regions we have access to the service area under the loader.
we need to analyze all modules, not just the 01h. how to do it in wdmarvel I do not know, and better to consult the author
since the ROM module are read without an error (experiment with only one controller) , the block comes from SA


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 10:56 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
Moltke wrote:
shifting regions we have access to the service area under the loader.
we need to analyze all modules, not just the 01h. how to do it in wdmarvel I do not know, and better to consult the author
since the ROM module are read without an error (experiment with only one controller) , the block comes from SA

In this situation I think it is helpful to take a backup of Reg 0 and reg 1 because the WD Marvel does not allow you to edit modules from the level SA Editor, or block loading firmware, then access to SA from the level DIR Modules. Understand me?
Spildit wrote:
I would say WD changed something on the ARCO procedure and now you can't start it with WDMarvel, same as when they changed SS so it requires unlocking.
Test with drive from the exact same model.
If it doesn't work then WDMarvel can't run ARCO on those drives. If it does work then the problem is with your specific drive.
Arco procedure can be run on my disk, without unlocking, tests 6A, 6B are going perfectly, while Zone TPI and Head Qual no longer have access to the User Area, based on previous test results and what is revealed DISK_DAM_ERROR on all the heads, the same way ARCO 46 All DISK_DAM_ ERROR on all heads.
Self Test also does not require unlocking.
Spildit wrote:
Frank, he can access SA.
What he can't do is RUN ARCO (calibration that he needs to do prior to self scan).
He is trying to self-scan the drive an he can't but he can read modules ok.
Exacly, but
by the end it is not, when regions SA are original, is accses for SA, all modules from the level DIR can read, write all access from the DIR there is no time when regions are on head 0 and 1 are changed, you must then using editor, which does not have the WD marvel. Understand me?

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 11:18 
Offline

Joined: October 24th, 2005, 17:04
Posts: 254
pikus_09 wrote:
. Understand me?

no. now the modules can be read or not ?! :spy: the reason (calibrator or selfscan) do not interest me. only the type of lock


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 11:38 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
Moltke friend no. Can't access to modules. Only 370F=FM_ERR_HEADER_II_SIGNATURE_INVALID

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 11:58 
Offline

Joined: October 24th, 2005, 17:04
Posts: 254
pikus_09 wrote:
Moltke friend no. Can't access to modules. Only 370F=FM_ERR_HEADER_II_SIGNATURE_INVALID

wow. already not CA_FLUSH_ALL_GOT_CANCELED! :)

if you read 01h (pba or chs) it differs from the original 01h ?


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 12:25 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
Moltke do you remeber that SA regions changed +1? Then Can't access SA modules. :arrow: 370F=FM_ERR_HEADER_II_SIGNATURE_INVALID
CA_FLUSH_AL_GOT_CANCELED shows when an attempt is made to access the UserArea :arrow: then it blocked access to SA, ROM, All.
It is possible that the mod 01(it's content) is broken , because the whole is an original FW, FW nothing was changed.

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 13:56 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
DUUHHHHH !!!

If you CHANGE SA regions then you can't access SA by ID !!!

That is the idea.

If you return the SA Regions to initial value you can read modules, yes or no ?

If YES then SA is NOT LOCKED and the problem is with Arco/SS only.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 14:25 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
Place regions BACK as original state :

Image

Read modules.

You should be OK !

Tell us if you can read modules now.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 15:31 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
Back region to oryginal state and SA module's work look:
Attachment:
ffff.JPG
ffff.JPG [ 185.92 KiB | Viewed 18587 times ]
checked all modules Work, but contents mod 03, 0C is incorrect, mod 31, 33, 36 are empty :arrow:
which does not change the fact that access to UA should be, and it is not.
So we are at the point of entry, ie,SA working, but there is no access to the User Area.
In contrast, as presented current insight into the zone table:
Attachment:
xxxx.JPG
xxxx.JPG [ 160.73 KiB | Viewed 18587 times ]
:arrow: All heads are the same entries.
A current disk parameters immediately after the procedure Arco present themselves in this way:
Code:
Drive config
Format version = 0x0101
DCM Selection = 0x0001
cur_stroke = 0x0001
phy_heads = 0x0008
used_heads = 00008
cur_capacity = 0x4E20
max_fmt_LBAs = 3907709568 - 2000Gb
target_capacity = 0x0002
max_target_LBAs = 3907029167 - 2000Gb
hq_capacity = 0x0002
max_HQ_LBAs = 3907709568 - 2000Gb
final_capacity = 0x0002
z0_dtpi = 0x0003665C
z0_kfci = 0x00000014
cur_svo_TPI = 0x00038270
cur_data_TPI_0 = 0x00035F57
cur_data_TPI_1 = 0x00035F57
cur_data_TPI_2 = 0x00035F57
cur_data_TPI_3 = 0x00035F57
cur_data_TPI_4 = 0x00035F57
cur_data_TPI_5 = 0x00035F57
cur_data_TPI_6 = 0x00035F57
cur_data_TPI_7 = 0x00035F57
cur_data_TPI_8 = 0x00000000
cur_data_TPI_9 = 0x00000000
cur_KFCI_0 = 0x09C4
cur_KFCI_1 = 0x09C4
cur_KFCI_2 = 0x09C4
cur_KFCI_3 = 0x09C4
cur_KFCI_4 = 0x09C4
cur_KFCI_5 = 0x09C4
cur_KFCI_6 = 0x09C4
cur_KFCI_7 = 0x09C4
cur_KFCI_8 = 0x0000
cur_KFCI_9 = 0x0000
max_LBA_for_head_0 = 488463696 - 250Gb
max_LBA_for_head_1 = 488463696 - 250Gb
max_LBA_for_head_2 = 488463696 - 250Gb
max_LBA_for_head_3 = 488463696 - 250Gb
max_LBA_for_head_4 = 488463696 - 250Gb
max_LBA_for_head_5 = 488463696 - 250Gb
max_LBA_for_head_6 = 488463696 - 250Gb
max_LBA_for_head_7 = 488463696 - 250Gb
max_LBA_for_head_8 = 0 - 0Gb
max_LBA_for_head_9 = 0 - 0Gb
max_user_cyls_for_head_0 = 0x00000000
max_user_cyls_for_head_1 = 0x00000000
max_user_cyls_for_head_2 = 0x00000000
max_user_cyls_for_head_3 = 0x00000000
max_user_cyls_for_head_4 = 0x00000000
max_user_cyls_for_head_5 = 0x00000000
max_user_cyls_for_head_6 = 0x00000000
max_user_cyls_for_head_7 = 0x00000000
max_user_cyls_for_head_8 = 0x00000000
max_user_cyls_for_head_9 = 0x00000000
max_virt_cyls_for_head_0 = 0x00034101
max_virt_cyls_for_head_1 = 0x00034101
max_virt_cyls_for_head_2 = 0x00034101
max_virt_cyls_for_head_3 = 0x00034101
max_virt_cyls_for_head_4 = 0x00034101
max_virt_cyls_for_head_5 = 0x00034101
max_virt_cyls_for_head_6 = 0x00034101
max_virt_cyls_for_head_7 = 0x00034101
max_virt_cyls_for_head_8 = 0x00000000
max_virt_cyls_for_head_9 = 0x00000000
rsvd_svo_cyls = 0x0200
rsvd_data_cyls = 0x0100
max_user_svo_cyls = 0x00000000
max_svo_cyls = 0x00039780
trks_per_clstr_svo = 0x0080
trks_per_clstr_rsvd = 0x0000
trks_per_clstr_for_head_0 = 0x0000
trks_per_clstr_for_head_1 = 0x0000
trks_per_clstr_for_head_2 = 0x0000
trks_per_clstr_for_head_3 = 0x0000
trks_per_clstr_for_head_4 = 0x0000
trks_per_clstr_for_head_5 = 0x0000
trks_per_clstr_for_head_6 = 0x0000
trks_per_clstr_for_head_7 = 0x0000
trks_per_clstr_for_head_8 = 0x0000
trks_per_clstr_for_head_9 = 0x0000
HdMap TPI = 0x31 0x31 0x31 0x31 0x31 0x31 0x31 0x31
HdMap Capacity = 0x04 0x04 0x04 0x04 0x04 0x04 0x04 0x04
Head map TPI, and capacity, max LBA, CURRENT DATA TPI for all head is incorrect.

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 15:49 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
so The situation is during the procedure ARCO:
Attachment:
jiji.JPG
jiji.JPG [ 150.02 KiB | Viewed 18586 times ]



Regards, and thank you so much behind all replies :)

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 16:00 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
Try "Prepare Sa For Test" checkmark.
Try "Run Test Servo Calibration" Checkmark.
Try "Set Target Capacity" to 1.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 1st, 2016, 16:14 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
Oh spildit friend, I tried, and Nothing of that. Target capacity must be 2, because Plater condition in these drives do not allow you to set options 1.
I also tried the scripts I've written on your forum, but the scripts were other models even though they were from the same family drives.

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 2nd, 2016, 9:34 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
Anyone have any idea's? Regards friends :)

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 2nd, 2016, 11:46 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
1 - Get an eaqual drive or ask someone with equal drive to test that out.

2 - Ask in general if people can run ARCO on those drives even with other tools.

3 - Test yourself with another drive.

- You must be sure if the problem is with your specific drive or with all drives from that model first.

Regards.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: CA_FLUSH_ALL_GOT_CANCELED - what's wrong?
PostPosted: January 2nd, 2016, 12:15 
Offline
User avatar

Joined: November 24th, 2013, 18:13
Posts: 438
Location: Poland
1 - Get an eaqual drive or ask someone with equal drive to test that out. :arrow: with this is a problem, because I have another WD Black for testing.

2 - Ask in general if people can run ARCO on those drives even with other tools. :arrow: WD Black drives are rare and the few it has, because of the price. ps. Newest PC3K certainly moves each WD BLACK, or sediv
3 - Test yourself with another drive. :arrow: self tests on other drives such as the ARCO on WD5000AAKX and on Zephyr WD7500BPVT over Seamlessly, WD15EADS SELFTEST module 28 Seamlessly,
- You must be sure if the problem is with your specific drive or with all drives from that model first. :arrow: the problem is not only in my case, viewing the forum I stumbled on another topic: WD20EZRX CA_FLUSH_ALL_GOT_CANCELED

Btw, solutions are 2.
Module 28 with the procedure arco, which is assigned to FW: 00050016F or higher, or a question WD MARVEL Autor to improved ARCO procedure for WD Black and higher. :(
PS, Franc or moltke he probably would have helped something, but first they had to analyze the firmware, but I doubt that they wanted to do :(

_________________
Hello everyone, sorry for my poor english, because i using google translator.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 85 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot], Google Adsense [Bot], michael chiklis and 70 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group