Get the right drive capacity after depop

[diybit]

Hello, Im looking to know if my drive is really at his max capacity, or if I can gain those "missing" 250GB.

Drive is WD20EADS-00R6B0 with 8 heads, 4 platters, capacity 2TB.
The head 5 was failing, and was automatically depoped during a selfscan.
I'm ok with the depop, I was going to do it if the selfscan will not repair it.

But now, the drive is identified as WD15EADS with 1.5TB.
It seems using 7 heads, but the capacity is now like with 6 heads.
The model list module 0C does not shown any WD175, and is reporting 2930277168 LBA for 6 and 7 heads.

So is it possible to manually re-adjust the capacity to obtain 1.75TB? or I'm facing a wall?

Have tried to change the max LBA to 3418653168 with the WDMarvel option, but it give me error...
Very thanks for your help!

[pepe]

To be honest i never ran selfscan on these, but i think it adjusted itself to the nearest factory defined capacity, which is 1.5TB. I'm afraid this is not achieved just by lowering MaxLba but setting lower SPT on zones as well. At least that's what i saw on refurb drives. So increasing the capacity probably cannot be done just by changing MaxLba.
pepe

[BGman]

It's feasible by editing the F-list, but before the depop procedure.

[diybit]

Thank you! your answers are well appreciate...

Can you confirm me that the F-List is the module 0C.

So, I'm going to restore my backup with 8 heads, modify 0C for 7 heads, and then manually depop.

I'm also not 100% sure about the max LBA for 1.75TB, please if you can confirm my value.
My calc to "found" it is :
(3907029168-2930277168)/2 = 488376000 (250GB)
2930277168+488376000 = 3418653168 (1.75TB)

It's little strange because 3907029168/8 = 488378646 (250GB), but this calc will not match for the factory 6 heads.

[fzabkar]

HDD manufacturers use the IDEMA standard.

https://www.google.com/search?q=97696368+%2B+%281953504+x+%28enter_GB_here+-+50%29%29+in+decimal

So 1500GB -> 2930277168 LBAs

… and 1750GB -> 3418653168 LBAs

[diybit]

Thanks all I will try and tell you the result.

[BGman]

Can you confirm me that the F-List is the module 0C.

So, I'm going to restore my backup with 8 heads, modify 0C for 7 heads, and then manually depop.

I'm also not 100% sure about the max LBA for 1.75TB, please if you can confirm my value.
My calc to "found" it is :
(3907029168-2930277168)/2 = 488376000 (250GB)
2930277168+488376000 = 3418653168 (1.75TB)

It's not so simple. You have to check the results of ARCO tests first. The capacity on each head may differ from 250GB by a few GB. Some space is needed for spare pool also....

[diybit]

Here are the infos I have found on this WD15:

Code:

Drive config
Format version = 0x0101
DCM Selection = 0x0001
cur_stroke = 0x0001
phy_heads = 0x0008
used_heads = 0x0008
cur_capacity = 0x4E28
max_fmt_LBAs = 3908644992 - 2001Gb
target_capacity = 0x0001
max_target_LBAs = 3907029167 - 2000Gb
hq_capacity = 0x0001
max_HQ_LBAs = 3908644992 - 2001Gb
final_capacity = 0x0001
z0_dtpi = 0x0002E2AD
z0_kfci = 0x0000000F
cur_svo_TPI = 0x000395F8
cur_data_TPI_0 = 0x0003AB7B
cur_data_TPI_1 = 0x0003C82B
cur_data_TPI_2 = 0x0003C82B
cur_data_TPI_3 = 0x000408B7
cur_data_TPI_4 = 0x00038ECC
cur_data_TPI_5 = 0x0003CF57
cur_data_TPI_6 = 0x00038ECC
cur_data_TPI_7 = 0x0003AB7B
cur_data_TPI_8 = 0x00000000
cur_data_TPI_9 = 0x00000000
cur_KFCI_0 = 0x09C5
cur_KFCI_1 = 0x09C5
cur_KFCI_2 = 0x09C5
cur_KFCI_3 = 0x09C5
cur_KFCI_4 = 0x09C5
cur_KFCI_5 = 0x09C5
cur_KFCI_6 = 0x09C5
cur_KFCI_7 = 0x09C5
cur_KFCI_8 = 0x0000
cur_KFCI_9 = 0x0000
max_LBA_for_head_0 = 488580624 - 250Gb
max_LBA_for_head_1 = 488580624 - 250Gb
max_LBA_for_head_2 = 488580624 - 250Gb
max_LBA_for_head_3 = 488580624 - 250Gb
max_LBA_for_head_4 = 488580624 - 250Gb
max_LBA_for_head_5 = 488580624 - 250Gb
max_LBA_for_head_6 = 488580624 - 250Gb
max_LBA_for_head_7 = 488580624 - 250Gb
max_LBA_for_head_8 = 0 - 0Gb
max_LBA_for_head_9 = 0 - 0Gb
max_user_cyls_for_head_0 = 0x0003A72A
max_user_cyls_for_head_1 = 0x0003BB3B
max_user_cyls_for_head_2 = 0x0003BB3B
max_user_cyls_for_head_3 = 0x0003EF5E
max_user_cyls_for_head_4 = 0x00038606
max_user_cyls_for_head_5 = 0x0003D127
max_user_cyls_for_head_6 = 0x00039097
max_user_cyls_for_head_7 = 0x0003A6A6
max_user_cyls_for_head_8 = 0x00000000
max_user_cyls_for_head_9 = 0x00000000
max_virt_cyls_for_head_0 = 0x0003AD7D
max_virt_cyls_for_head_1 = 0x0003C220
max_virt_cyls_for_head_2 = 0x0003C220
max_virt_cyls_for_head_3 = 0x0003F67B
max_virt_cyls_for_head_4 = 0x00038CA5
max_virt_cyls_for_head_5 = 0x0003D86E
max_virt_cyls_for_head_6 = 0x00039760
max_virt_cyls_for_head_7 = 0x0003AD7D
max_virt_cyls_for_head_8 = 0x00000000
max_virt_cyls_for_head_9 = 0x00000000
rsvd_svo_cyls = 0x0180
rsvd_data_cyls = 0x00C0
max_user_svo_cyls = 0x0003A585
max_svo_cyls = 0x0003AC00
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 = 0x0E 0x16 0x16 0x1D 0x0F 0x04 0x06 0x0E
HdMap Capacity = 0x04 0x04 0x04 0x04 0x04 0x04 0x04 0x04

RWGap Calibration
Error Code = 0x00000000
Measured temp = 0x0000
Head 0 Zone calibrated = 0x0014
Head 0 Gap value = 0x0028
Head 1 Zone calibrated = 0x0014
Head 1 Gap value = 0x0029
Head 2 Zone calibrated = 0x0014
Head 2 Gap value = 0x0028
Head 3 Zone calibrated = 0x0014
Head 3 Gap value = 0x0029
Head 4 Zone calibrated = 0x0014
Head 4 Gap value = 0x0027
Head 5 Zone calibrated = 0x0014
Head 5 Gap value = 0x0027
Head 6 Zone calibrated = 0x0014
Head 6 Gap value = 0x0027
Head 7 Zone calibrated = 0x0014
Head 7 Gap value = 0x0027

TPI Calibration
Error Code = 0x00000000
Head 0 Tpi Code = 0x000E
Head 1 Tpi Code = 0x0016
Head 2 Tpi Code = 0x0016
Head 3 Tpi Code = 0x001D
Head 4 Tpi Code = 0x000F
Head 5 Tpi Code = 0x0004
Head 6 Tpi Code = 0x0006
Head 7 Tpi Code = 0x000E
Measured temp = 0x01
Zone count = 0x02

Is it those max_LBA_for_head_X that you are talking about BGman?

[BGman]

Yes. What tool did you use?

[diybit]

The tool is WDMarvel 4.0.0

Okay, so it seems that I'm surely ok with 3418653168 LBAs, I will try soon.

[BGman]

Don't forget to run internal format after the head depop!

[diybit]

Damn, the selfscan have reset the F-List values.
If anyone know how to avoid this...

Yes, I have try with the auto depop of selfscan...
That can be a good way if it have use and not reset my values...
Because we do not know how much defect there will be before a 1st selfscan, and if depoping is really needed.

So I have manually depop, and wow! I'm now getting 3418653168 LBAs with 1750GB identified.
I have little test the end of drive with a quick format, and it seems working!

Now restarted for a 3rd selfscan...
And it seems it do not touch at the depoped head, so I will surely not have the logs that show this head is defective...

I have little try to eventually done "a mix" of modules, but I'm afraid doing/missing something bad, maybe not so easy because of this head depop with LBA re-adjusted, and ARCO tests that are also modifying others modules...
Do you think I will be in an identical state (except LBAs) by just re-done the ARCO tests, and then copy my new P-List, and the heads defects logs modules.

Anyway, SS is restarted, but if you have some hints for my next drive to avoid double selfscan in case of depop with LBA re-adjust needed...

I hope it will not re-fall to WD15 this time...

[BGman]

Why did you decide to run selfscan?
I said internal format, not selfscan!

[diybit]

Because the drive have "tiny" sectors problems on others heads.

[diybit]

Final result is well good!
Have retest parts near those 3 orange sectors and they are finaly saying fine.

So I confirm you that the LBAs re-adjust is working.

Special thanks BGman, this tips is very useful!