A question

Questions about Arch7 Repair Tool capabilities
Post Reply
User avatar
smyg
Posts: 835
Joined: 12 Nov 2019, 12:40
Location: Симферополь, Крым
Contact:

Re: Spindown time - WD40EZAZ-00SF3B0 (VENICE_R)

Post by smyg »

pujosm
Posts: 9
Joined: 07 Jun 2018, 14:57

Re: A question

Post by pujosm »

Trying to cut a head on a Kojn_RE drive = error 3714
FM_ERR_PARTIAL_FILE_BUF_OFFSET_EXCEEDS_EOF

it has mod 04

Someone has idea?
User avatar
Vlad
Разработчик
Posts: 5025
Joined: 13 Aug 2013, 07:53

Re: A question

Post by Vlad »

Usually, this mean corrupted 04 or 04 from another FW version
pujosm
Posts: 9
Joined: 07 Jun 2018, 14:57

Re: A question

Post by pujosm »

The Kojn_RE drive is a WD Black WD4001FAEX-32MJRA0, Firmware 07.J2E, Mod 04 size 14.0 MiB, head cut does not work.
I have another Kojn_RE drive, a WD Re WD3000FYYZ-01UL1B1, same Firmware 07.J2E, here Mod 04 size is 15.4 MiB and head cut works.
And a 3rd Kojn_RE drive, a WD Re WD3000FYYZ-01UL1B3, Firmware 09.D6E, Mod 04 size is 14.0 MiB and head cut does not work.

Writing 15.4 MiB mod 04 on the WD4001FAEX or WD3000FYYZ with 09.D6E Firmware and try head cut = same error 3714

Delete mod 04 on WD4001FAEX or WD3000FYYZ with 09.D6E and try head cut = same error 3714

So maybe it's something the drive checks before mod 04, when trying head cut. Maybe soemthing in ROM or another module.
I know mod 4F in ROM is important for head cut.
User avatar
Vlad
Разработчик
Posts: 5025
Joined: 13 Aug 2013, 07:53

Re: A question

Post by Vlad »

FM_ERR_PARTIAL_FILE_BUF_OFFSET_EXCEEDS_EOF - corrupted/wrong module
Unfortunately, FW doesn't report what exactly module cause the problem
If we talking about head cut, usually, problem with 04...
If you compare FW before and after head cut, you will find a lot of changed modules, and even more modules are read by FW in this process
We can quess many years, which module wrong)
User avatar
SRUTSSSSSSSS80
Posts: 1546
Joined: 01 Jan 1970, 00:00
Location: USxxR

Re: A question

Post by SRUTSSSSSSSS80 »

check modules by heads for correct reading and CS
pujosm
Posts: 9
Joined: 07 Jun 2018, 14:57

Re: A question

Post by pujosm »

Thank you very much for your answers.

If I find out, I'll post it.
pujosm
Posts: 9
Joined: 07 Jun 2018, 14:57

Re: A question

Post by pujosm »

On all 3 drives mod 6F Overlay and mod 24 SMART Log have invalid CRC. Must be normal (1 drive can cut head (from 2013), 2 drives not (from 2017 and 2018)
Other modules all are ok.
User avatar
SRUTSSSSSSSS80
Posts: 1546
Joined: 01 Jan 1970, 00:00
Location: USxxR

Re: A question

Post by SRUTSSSSSSSS80 »

this is normal for these modules, recalculate the CRC, they are updated online and the CRC is always wrong.

04 and other modules normal in all heads? read head 0/1

WD4000FYYZ-01UL1B1-07.J2E

what is the size of the 05 module?
try to register new 04 and 05 module in dir
pujosm
Posts: 9
Joined: 07 Jun 2018, 14:57

Re: A question

Post by pujosm »

All modules are normal on both heads.

05 is the same size as 04 = 28806

I tried 04 and 05 from the other drive with working head cut, sizes 31686
Registered correctly in dir, read both heads ok. But still same error

I tested the 28806 modules on the good drive instead of 31686 modules.
When head cut, there is no such error, so I don't think it's mod 04 or 05 that causes the error.
It's maybe some kind of head cut lock, I see it in all newer Vivaldi and Kojn_RE drives from 2017 or newer.
I need to change some other modules and try.
Post Reply