Today worked on 2 Ares.
Both were (BAD!) - - - for plist, glist and dmcs
and copies all bad - fixed this, but...

One drive recovered files and then...

2nd drive, data seems OK to about sector 4.8M
thereafter all sectors filled with identical 512 sector to
end of drive !

In drive write enable I was able to record and
read data correctly to/from some test sectors.

Any ideas. ?

Strange........... Only think maybe translator is slightly corrupted.... other than that I would need to see it

Even with translator possible corruption, I cannot see that
a sector can output anything other than what is in the sector.

On further checking there are some, quite a few identical blocks
within the first 4.8m - something is writing to the disc - must be
the bastard - because i use his utility a lot

Today worked on 2 Ares.
Both were (BAD!) - - - for plist, glist and dmcs
and copies all bad - fixed this, but...

One drive recovered files and then...

2nd drive, data seems OK to about sector 4.8M
thereafter all sectors filled with identical 512 sector to
end of drive !

In drive write enable I was able to record and
read data correctly to/from some test sectors.

Any ideas. ?

Do theese idenical sectors begin with "VELT_G00"?pepe

Does anybody have more info about "VELT_G00"?

The sectors begin with :

17 26 4B 37 7A E9 26 35


Hi guru, yes, I have original modules and screen print
of P-list before anything was done.


Here is what I did,

filled in clear g-list

OK

created new DMCS from #78 and first 2F bytes from identical drive
copied another's p-list and did trans regen.


created new DMCS or just corrected headers? MMmm why copy Plist from other drive and then to translator regen? Sounds like a big mess to me...

Why not just correct DMCS and Plist? Was glist corrupted at first??? eg NO_GLIST ???

Like I said, it's a big mess definetly translator problem. You need to reload original firmware and just correct DMCS, PLIST headers.

Did you make loader from duff drive after you used donor loader?



Guru


btw - I am certain that some time last year I got exactly the same
sectors with another drive. That time these sectors occurred from
about 2M to exactly middle point of drive.

Later today I will compare current mods with original and write
back originals.

Like I said, it's a big mess definetly translator problem. You need to reload original firmware and just correct DMCS, PLIST headers.

Today worked on 2 Ares.
Both were (BAD!) - - - for plist, glist and dmcs
and copies all bad - fixed this, but...

VELT_G00 (EVTLG_00) is the event log!

The sectors begin with :

17 26 4B 37 7A E9 26 35

Hello, again. I have seen this pattern also. At the factory they fill the entire area of theese drives not with zeroes, but this pattern sometimes. Maybe it depends on the model.
It is not surprising that You have it after 4.8M if You had NTFS on it, because it sometimes does not start with the data on the beginning of the partition.
So if You skip the portion filled with this pattern, You probably get to the area where valuable things are stored.

pepe

Hi guru,

yes seems like a mess, but I wrote this at start :



i.e. the glist, dmcs or plist and copies were all BAD! -
modules unreadable and copies unreadable.
no headers no KS no data - kaput

I will get back to this drive later....

Posted 16/11/2004, 03:41:


1. Original P-list shows errors uhrs0: 788 uhrs1: 400 uhrs2: 51
2. Current P-list shows errors uhrs0: 753 uhrs1: 35 uhrs2: 51.

re-wrote original #33 did regen and p-list as in 2.

re-wrote original #33 NO regen and got P-list as in 1. ... great

Now more and more sectors are correct but after 5.6M all
still faulty.

So the problem is definitely translator related.

I think problem might lie with first 3 rows of created DMCS,
I do not know what each byte means - who can tell ????