Redump Forum

user7 wrote:Is HL-DT-ST UH12NS30 still a drive that works

/viewtopic.php?t=10572 … ification/
I don't have this drive, but he reported this drive worked about scrambled and lead-in.

diego-rbb-93 wrote:Plextor-W4012TU im using here keeps reporting me this error:

Try using the latest firmware.

sarami wrote:Yes. Verbose rereading just occurs, surely real c2 errors may be fixed. Plz wait until I add the code.

Uploaded the test version. I haven't tested the protected disc except safedisc yet.

Thanks for the new test version - testing right now. Hopefully I can properly dump this problematic disc now and get matching checksums...

How much is ripping time increased because of this new feature?

It depends on the settings. For my first test run, I used 5 re-reads, but that missed about 20 sectors with unintentional C2 errors (verified against ripping with CloneCD with always creates 579 bad sectors - I guess CloneCD does re-reading right away).

With 5 re-readings, ripping time increased about 5 minutes using my Plextor W5224A at 24x reading speed.

If you want no ripping time increase, just use /sf /c2 0 to disable it.

Update: Test run with 25 re-reads went down to 581 sectors with C2 errors. Now trying with lower read speed and 100 re-reads... Still wonder why CloneCD seems to get past the unintentional C2 errors each and every run.

I did a few more runs on that problematic disc - it seems that it is in a condition that makes it unusable for proper dumping. I get not only random C2 errors (that get fixed by the re-readings, so the new feature works as expected), but also sync issues. Damn.


sarami, thank you for the fast implementation of this feature request!

Uploaded  test ver.
----
I confirmed the specific bit was error.
If your disc also has a specific value of error bit count, app can exclude the sectors which this value has. As a result, app can only reread unintentional c2 error sector.
Please upload the log of your all safedisc. (Because I have only 1 safedisc..)

sarami, thanks for the new test version.

Just trying with another known good safedisc disk - I'll see if checksums match with "old" stable version and latest test version. Hold on - logs will follow. Then I'll see if the new test version can do something about the bad safedisc disc.

I'll post the logs of the bad disc too... maybe I can finally get a good dump without any unintentional C2 errors.

The latest test version is only added the log message --- "Detected C2 error xxx bit". No need to dump full, I want to know "xxx" value of your all safedisc.

At least for one good safedisc disc I can confirm that *all* sectors with C2 errors are 312 bit.

Most of the sectors of my bad safedisc disc have 312 bit too, the random ones have random values. Logs of the bad disc attached. I'll try to confirm more good safedisc disks.

Logs of the bad disc after a full redump: https://www.sendspace.com/file/9i1ne5

I dumped 5 safedisc discs, ranging from Safedisc v1.x to 4.6.

Logs: https://www.sendspace.com/file/l7lxjq

C2 error is always 312 bit.