WD2000JD problem

[louis]

4 - I don't understand how that tool works.

zmist was a virii opening new horizons at its time. when naiming it the russian author was inspired by a book called "With Morning Comes Mistfall".

as example I could say..

with head swap comes misalignment

with that tool you play with the HSA spindle's ox-y-z price: 500$ (but when you charge 1500 for a dr..it's nothing; the price doesn't reflect it's components value..but the money the users makes with it. and when you make easy money..at a large scale..bubble appears. dot com ...real estate...etc. btw dja and sp500 are on top of the bubble so soon we will have another global crash and more recession to come, but this time it will strike even harder)

@Nebojsa_28 maybe you have passed a link or something which was interpreted as spam.

[louis]

it's not a plan..it's a possibility I'm thinking

but what I'm talking about...at this moment I don't even have a valid donor. I'm tracing ebay for it.

by the way

How Many Sectors are on Your Hard Drive?

Code:

HDDs of exactly    10 GB  have:    19,531,250  sectors.
HDDs of exactly    20 GB  have:    39,062,500  sectors.
HDDs of exactly    30 GB  have:    58,593,750  sectors.
HDDs of exactly    40 GB  have:    78,125,000  sectors.
HDDs of exactly    60 GB  have:  117,187,500  sectors.
HDDs of exactly    80 GB  have:  156,250,000  sectors.
HDDs of exactly  100 GB  have:  195,312,500  sectors.
HDDs of exactly  120 GB  have:  234,375,000  sectors.
HDDs of exactly  140 GB  have:  273,437,500  sectors.
HDDs of exactly  160 GB  have:  312,500,000  sectors.
HDDs of exactly  180 GB  have:  351,562,500  sectors.
HDDs of exactly  200 GB  have:  390,625,000  sectors.
HDDs of exactly  250 GB  have:  488,281,250  sectors.
HDDs of exactly  300 GB  have:  585,937,500  sectors.
HDDs of exactly  320 GB  have:  625,000,000  sectors.
HDDs of exactly  500 GB  have:  976,562,500  sectors.

HDDs of exactly  640 GB  have: 1,250,000,000  sectors.
HDDs of exactly  750 GB  have: 1,464,843,750  sectors.
HDDs of exactly  860 GB  have: 1,679,687,500  sectors.
HDDs of exactly   1.0 TB  have: 1,953,125,000  sectors.
HDDs of exactly   1.5 TB  have: 2,929,687,500  sectors.
HDDs of exactly   2.0 TB  have: 3,906,250,000  sectors.
HDDs of exactly   3.0 TB  have: 5,859,375,000  sectors.

this should match also the LBA.

by the way...GB means giga multiple of 1000...not 1024 as it is supposed to be in bit's world. why? dont know.
ie: 200GB means 200 000 000 000...divide by 512bytes (a sector)...means 351,562,500 sectors/ lba?

so if I cut 1 head..the final max LBA should be set to 3/4 of 200GB = 150GB = 292,968,750 sectors?

[louis]

Just on thing, are you sure you didn't flash back the ROM with PUIS enabled to ignore jumper on the drive you say it's "bricked" ?
.

checked all that things. usually ..in puis mode the drive respond to commands with errors. now it doesn't change a register. entirely bricked

Off Topic - When you aquired the donor drive on ebay did you bother to check the seller feedback ?

yes. 44 negatives at 9000 items it's not so bad. the model it'd very rare. I had to risk.

Regarding ROM :

Assuming that you falshed a working ROM using 3.0 i can't see a reason why the PCB is briked now, unless you flashed a file that was not a ROM something else ...

the programmer has arrived to country. usually due to the bad system it will take one week to get it. as I said, I believe I flashed the patient's rom. maybe some errors during flashing operations not detected by the 3.0. I don't have any other roms at hand..but donor's and patient's...in those dir's where I dumped, because from there I selected.

one good option to my app it will be to automatically checking the flash after writing!! which means to download the newly flashed rom and compare to what we've written. don't know if it's possible because after flash write it could enter in reset mode automatically....but it's an option to investigate. this way if the images write/read after..doesn't match..and the kernel didn't already rebooted...you will have the chance to flash again until correct result.

[louis]

What programmer did you aquire ? Did you get the soic 8 clip too ?
I think it would be great if you manage to figure out a way to turn on the modem function on the mcu to upload ROM using the terminal, that way you wouldn't need the programmer...

TL866CS with a soic8 clip.

I don't have the tools to investigate the x-modem way.

[Nesa]

My unpublished post:

hi Nebojsa_28. when I said "format"...I was talking about windows format....ntfs format

let's say that the old pcb didn't matched the adaptives for H1 in SA. (1)but why with its own pcb can't still read the H1 on SA? If some adaptives mods on SA are screwed...at least (2)with its internal mod47 all heads should be able to read SA.

can somebody tel what (3)"format" does in fact? not the windows one..which makes the drive visible to OS.

also, (4)how the firmware knows where to find the SA on the platters? I know about the Servo system...some marks written on the platters in factory...but does the firmware use an explicit servo cylinder where the SA should be?

I believe the LBA it's on the mod 02 -> SA, so what to modify in rom? the rom holds only basic info to access the SA...which holds the rest. SO if you can't access the SA...the rom it's bad..OR the read channel it's bad...bad preamp (all 4 head dead..or H1+H2 =SA-heads). If one head gives error on SA..then the MOD 47 in rom could be bad for that Head..or the head it's dead. But it's possible that the other adaptives mods on SA hold again the adaptive infos for the dead head...(5)so the reading of SA with the good head should fix the bad info in 47 for H1..and the head should work (assuming good adaptives for H1 in SA found), (6)which leads me to a dead H1.

- Yes, I know you did a format for user area.

1. Maybe because the mods/tracks are damaged because of bad saving with wrong adaptives.
2. Not if the SA or part of it is damaged
3. I don't know on what "format" you refer
4. Good start for this is in the article HDD_Tracks_and_Zones on hddscan.com
5. Mod 47 is important for successfull reading of the SA, not vice versa
6. In one of your tests H1 is good

[louis]

1. until i found the H1 problem, I did not saved anything to SA.
2 .ok
3. format function on a tool called wdr.
4. I know that article. it doesn't tell how the firmware knows where it's the SA starts among servo sectors.
5. read again. mod 47 holds adaptives for all heads in SA!!..if adaptive for head 1 are defective but the H0 reads fine SA...then if the adaptives exist again in mod 40...H1 could be fixed by reading from there the correct values data dac, mr etc.. SA exist in 2 copies..one on H0 (main used) and one in H1.
6. I'm not sure of that. I did some quick test when implementing the read pcs function in my software....don't know on which head did the tests.

I need more info about adaptives and don't know where to find.

[Nesa]

1. Drive itself saves while works
4. Sorry, that article really have no direct information about that
6. You have all heads test in wdr and they are ok

I don't know what happend during your work with drive so now H1 doesn't read at all.

[louis]

wdr reported all heads ok..even when H1 was broken. no trust in that tool.

[Nesa]

Why are you sure that H1 is broken?

[Nesa]

@Spildit:

Heads 0-3 in wdr test are good

[Nesa]

There are too many confusing infos!

[louis]

got my hands on a test drive. purchased it for 15$ to continue developing my app. the device has 160GB and was made in 2004. It's an old model firmware..which doesn't have any mods at the end of the firmware .

now I see that older models support fewer VSC commands. So things I can do to the drives I tested before..I can't do on this one.

my "backup all" function didn't worked on this model because the VSC command which reads modules returns bogus data when reading mod1 which gives me access to all the other mods in SA. perhaps it's another way to call it.

[louis]

wdr kinda suckz for me because every time you put me to test I must leave my win7 with may stuff in it..TV tuner etc..and reboot from USB. I don't like this

the model is WDC WD1600JD-00GBB0_02.05D0_WD-WMAES4018073

I now adapt my app to support it. Will test WDR later.

Marvell it's the MCU...the firmware it's the same inside, I mean..the VSC functions must follow the same specs. The code it's based on arm architecture. The ROYL on the WDR's menu doesn't spec anything different than the Marvel. The VSC functions are the same (it should act in the same way)..only the headers are different..and the structures returned. ROYL it's an enhancement to old firmware...supporting LBA accessing, greater LBA etc etc. But I believe you can't understand it well because you don't know how the code looks and what it does

so..the dumprom function work in my app.
also the "dump mod vsc" works...for all the mods except mod01. so I had to read it with read_track_cyl_sector() function....aka the raw way.
because I couldn't get the mod1..I couldn't get any mod...that's the way... I have to enumerate through mod's dir.

[louis]

I make progresses but to what..I don't know

look:

Code:

97 Modules found in the SA. Start downloading...
..blabla..
mod ID: 3C found in MOD DIR, points to another MOD ID: 23
mod ID: 38 found in MOD DIR, points to another MOD ID: 22
mod ID: 30 found in MOD DIR, points to another MOD ID: 1
mod ID: 34 found in MOD DIR, points to another MOD ID: 10
mod ID: 45 found in MOD DIR, points to another MOD ID: 46

mod ID: 1 found in MOD DIR, points to another MOD ID: 30
mod ID: 10 found in MOD DIR, points to another MOD ID: 34
mod ID: 22 found in MOD DIR, points to another MOD ID: 38
mod ID: 23 found in MOD DIR, points to another MOD ID: 3C
mod ID: 46 found in MOD DIR, points to another MOD ID: 45

so..when I search the mod's dir to find mods' name (to know what to download)..the mod's name indicated in the mod1...has other name when reading it from the SA.
as you see there are 5 mods which tell..hello I'm mod X..you find me there on track n, sect m size p...but when you go to read it..you find mod Y

when I use VSC_READ_MOD(0x1)..the vsc downloads interrnally mod01...at track-1, sector 0..and scrolls to find mod's 1 location...and from there downloads the mod 1...which in fact points to mod 30!! that's why I couldn't get the mod1 using VSC_READ_MOD.

very strange. now..how the heck should I handle this? how do I name the mod when I save it to hdd as backup, using the name from mod1 or the name found inside?

of curse I could try to rename them..save to SA and see if the firmware still works. this way I could find if the firmware uses VSC_READ_MOD if the firmware won't work..or else..it means that the firmware doesn't care about mod's name found in mod01..and builds its internal list with the mod's name read directly from each mod.

[rameez]

The drive you bought is an old drive older then marvel its structure is different .
These drives are known as 32bit drives .

[louis]

here's the device backup.

the directory mod it's not 0x01...but 0x41. more...it doesn't show itself in it

and more..yes...the H2 holds a copy of the H1 SA

didn't tested on 3.0

Attachments

WDC WD1600JD-00GBB0_02.05D0_WD-WMAES4018073-ORIG.zip

(629.29 KiB) Downloaded 388 times

[louis]

yes...the vsc are the same.

I had to adapt it to this situation.

just for fun..here's an image...sorry for the quality..it's all I could get under led light.

the MCU it's a WDC.

this device has PUIS enabled&controlled by PM2...tested it with the jumper set and doesn't spin at powerup. what's funny is that if I send a vsc when it's PUIS mode...and not started..it returns "VSC error code decoded: 0x0000 -->> SUCCESS" which is different from the other device I've tested which returned some errors

bw..what's the second mcu in size..at the right of the WDC? I mean..what does?

Attachments

[fzabkar]

It looks like the Read Channel.
http://www.users.on.net/~fzabkar/HDD/HD ... annel.html

[louis]

coded a device ident option for my app

wdt -did
outputs:

Code:

Model :            WDC WD1600JD-00GBB0
S/N :              WD-WMAES4018073
FW Rev :           02.05D0
Family:            ID_POLARIS (73)
Rom Frmw Rev :     02.1SD
Platter count:     3
Heads count:       6
Heads used:        4
Depop map: H0->Hn  1 1 0 0 1 1
Zones count:       21
Servo count:       180
SA cyl count:      32
Spindle rpm:       7200
Used cylinders:    87922
Format ver.:       1

[rameez]

Check depop map the information is incorrect .