2,251

sarami wrote:

Tell me please.

This is the main one I noticed, though OP doesn't say what drive s/he's using.
http://forum.redump.org/topic/22712/pc- … sion-help/

Looking back, I found that the other threads I saw are ~5 years old or not using DIC, so aren't really relevant.

2,252

Madroms wrote:

TDDDEMO-logs.rar

Try this.

DiscImageCreator.exe cd g ISO\TDDDEMO\TDDDEMO (1).bin 8 /c2 100 /s 2
Madroms wrote:

Three Dirty Dwarves demo disc with scratches that make c2 errors.

I think you should remove scratches. (Disc should be polished.)

2,253

I have this PC Coverdisc that is multisession: 1st session contains audio tracks, 2nd session contains data track.
I dumped it both as a PC disc and as a Multisession disc. Result was the same: I get scm, img and bin files as if successful; however there are 4496 errors.
The disc has no scratches; however there is a ring. Not sure if it marks the multisession or if it is some kind of protection.

Logs:
https://mega.nz/#!PvhU2SbT!Lnz32Nm_21m5 … 8JbulQyBcs
https://mega.nz/#!TjgElCrT!kr3VpXwBuGWQ … -1ssU5QdOk

2,254 (edited by Madroms 2019-11-18 20:26:32)

sarami wrote:

Try this.

DiscImageCreator.exe cd g ISO\TDDDEMO\TDDDEMO (1).bin 8 /c2 100 /s 2

It works: for the log if you want to check it for the /s 2 param: TDDwith_s2-logs.rar

but still some scratches do not let me dump it without c2 errors. The disc seems to have been already polished, but the scratches that are still there produce c2 errors. I will see later what to do.
But for now, /s 2 did the trick for the internal error.

Saturn Database {-} Retro Deals search engine that helps you find stuff (plextor drives, games, etc.) easily on eBay {-} My Redump Logs

2,255

pool7 wrote:

however there are 4496 errors.

It's error of the lead-in area. Almost all lead-in are unreadable for Plextor.
DIC is padding this area by zero except 1st 16 bytes like this. 1st 16 bytes are generated manually.

LBA[072175, 0x119ef] Read error. padding [2352byte]
========== LBA[072175, 0x119ef]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 17 84 25 61   ..............%a

Lead-in area of this disc is mode 1. Mode 1 disc has edc/ecc but DIC is padding by zero, so EccEdc.exe reports errors.
As a result, 4496 errors can be ignored.

Madroms wrote:

but still some scratches do not let me dump it without c2 errors

Why not get another one if it is possible? C2 errors are problem of the disc, not DIC. DIC (and other dumping tool) is not perfect for hard-damaged disc.

2,256

sarami wrote:

Why not get another one if it is possible? C2 errors are problem of the disc, not DIC. DIC (and other dumping tool) is not perfect for hard-damaged disc.

It is a very rare demo disc, that I never saw for more than 15 years collecting Sega Saturn stuff. So, there is very little chance to find another one for sale. It is not so hard-damaged, just a few scratches not on the good place sad
I will see if I can combine multiple ways to dump it.

Saturn Database {-} Retro Deals search engine that helps you find stuff (plextor drives, games, etc.) easily on eBay {-} My Redump Logs

2,257

Madroms wrote:

It is not so hard-damaged, just a few scratches not on the good place

But DIC reports 1206 C2 errors. It's a lot of errors. Not only scratches but other factor give the damage to disc. (e.g. humidity, heat, sunlight, and so on)

2,258

Try a different drive as well. Are you sure there's no scratches on the data part?

2,259

Thee are some spots and some linear scratches from center to outer. But I think the c2 errors are also due to how the disc was (badly) polished by the previous owner ( so the laser may be not reflected correctly ?).

2 different plextor drives gave me approx the same amount of c2 errors (with no luck with reread). I was able to dump the disc with isobuster with a non plextor drive with only a few low errors in the ecc/edc fields (all that could be repaired with cdmage).
So, something to try in the future for this disc, with multiple drives.

Saturn Database {-} Retro Deals search engine that helps you find stuff (plextor drives, games, etc.) easily on eBay {-} My Redump Logs

2,260

The previous resurface might need to be carefully smoothed out. Very doable with care. dangerboy (Game-Rave) resurfaced a few of his ultra-rare discs from super scratched to safety with a cheapy at home one, so i'm sure a decent resurfacer would do a great job on some light scratches.

2,261

This is something I might try in the future, yes.

Saturn Database {-} Retro Deals search engine that helps you find stuff (plextor drives, games, etc.) easily on eBay {-} My Redump Logs

2,262 (edited by user7 2019-11-21 04:09:18)

DIC is overdumping PS4 kiosk demo (BD-R). This time i used the PS3 OEM drive
https://drive.google.com/file/d/1Ru-uco … sp=sharing

PS4 kiosk demos stall out on my LITE ON iHBS112-04 2 drive

---

by the way, your CD-R and DVD-R dumping fixes worked great. I tested tons of discs.

2,263

user7 wrote:

DIC is overdumping PS4 kiosk demo (BD-R).

TOC says

========== TOC ==========
      Data Track  1, LBA        0 - 23652351, Length 23652352
                                              Total  23652352

23652352 * 2048 = 48440016896

DAT says

    <rom name="2019 Summer Refresh - Game 89.iso" size="48440016896" crc="747e62f9" md5="1aca828231c4834fa632f87810ad648a" sha1="fad60cc0796f063c7dcba46ea41d38ef82e204b0" />

Is it really overdumping?

2,264 (edited by user7 2019-11-21 05:16:27)

Data size on finder level is about what isobuster dumps (34,138,947,584 bytes). I presume this means it has to be overdumping?

I'm going to dump with the same PS3 OEM drive with isobuster and see what happens.

2,265

I redumped the PS4 kiosk disc BD-R with the PS3 OEM drive this time and got size "48440016896". This number seems to be the ENTIRE size of the blu-ray disc, including where data isn't written. Can this be right? Shouldn't the dump end where the data ends?

The lite-on blu-ray dump isobuster iso matches the data size without padding (34,138,947,584 bytes). I'm inclined to believe this is correct.

Is there a definite answer?

2,266

1. DIC and PS3 OEM drive          => 48440016896
2. DIC and other drive                => ???
3. Isobuster and PS3 OEM drive => ???
4. Isobuster and other drive       => ???

2 is 34138947584? or 48440016896?
3 is 34138947584? or 48440016896?
4 is 34138947584? or 48440016896?

2,267

1. DIC and PS3 OEM drive          => 48440016896
2. DIC and other drive                => fails (goes super slow towards the end)
3. Isobuster and PS3 OEM drive => 48440016896
4. Isobuster and other drive       => 34138947584 (size of data on disc)

Would love to mail you one of these...

2,268

user7 wrote:

2. DIC and other drive                => fails (goes super slow towards the end)

Are there logs?

user7 wrote:

3. Isobuster and PS3 OEM drive => 48440016896
4. Isobuster and other drive       => 34138947584 (size of data on disc)

It looks like PS3 OEM drive problem...

2,269

sarami wrote:
user7 wrote:

2. DIC and other drive                => fails (goes super slow towards the end)

Are there logs?.

Yes, but i canceled so they're incomplete: https://drive.google.com/file/d/14gLO6N … sp=sharing

Dumping slows WAAAAAY down.

2,270

DIC and other drive are also 48440016896...

added READ CAPACITY log http://www.mediafire.com/file/eq80y20l9 … st.7z/file

user7 wrote:

Dumping slows WAAAAAY down.

It still exists but give me logs.

2,271

With LITE ON iHBS112-04 2 drive:

Somewhere around here: Creating iso(LBA) 16833824/23652352
the slowdown occurs, it becomes very slow...

https://drive.google.com/file/d/1aNOKPS … sp=sharing

2,272

ReadCapacity is also same as ReadTOC.

========== ReadCapacity ==========
    Max LBA + 1: 23652352 (0x168e800)

I can't fix this problem now. By the way, how about other BD-R?

2,273

sarami wrote:

I can't fix this problem now. By the way, how about other BD-R?

Same way. which size is correct? 33gb or 45gb? i can do more tests if necessary.

2,274

I am sure a good explanation exists, but thought to ask about it.
I just dumped a PS2 CD ROM: http://forum.redump.org/topic/25130/ps2 … to-no-ken/
At first pass, the dump came back with some C2 errors. However, final checksums of the dump with the errors were the same as the existing verified dump. I gave this disc a thorough wash with soap and it fixed the errors, resulting in same checksums again but this time with 0 C2 errors as expected.

I was wondering how a disc with C2 errors can still come back with the correct checksums? Theory says that C2 is uncorrectable error which *should* break the dump and cause wrong checksums, but probably I understand something wrongly here and would love to hear explanation from the experts. smile

Logs of the dump with C2 errors: https://mega.nz/#!30hAyAyB!eRiljbOBIBnf … pwpe5hgZ1Q
Logs of dump of same disc without C2 errors: https://mega.nz/#!v95wWYhJ!Pp7cAIze9SnG … hERx9f-gF4

2,275

Maddog wrote:

I was wondering how a disc with C2 errors can still come back with the correct checksums?

Due to rereading, all sectors with c2 errors turned no error sectors. See _c2Error.txt

user7 wrote:

which size is correct?

I don't know now.