Search options (Page 5 of 9)

Ok ^-^

sarami: It's going in a good direction but to speed things up you could also code sector range extraction from those discs. It's way faster to read specific 'n' sectors than entire cd, and merge command that merges single sectors - just like CDArchive does.

celebi:

========== OpCode[0xd8]: SubCode[0]: Check Drive + CD offset ==========
========== LBA[000000, 0000000]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 5C 7A B9 E3 32 C9 D5 96  DF 2E D8 1C 5A 89 FB 26   \z..2.......Z..&
0010 : C3 5A D1 FB 1C 43 49 F1  F6 C4 46 D3 72 DD E5 99   .Z...CI...F.r...
0020 : 00 FF FF FF FF FF FF FF  00 FF FF FF FF FF FF FF   ................
0030 : FF FF FF 00 01 82 00 61  00 28 00 1E 80 08 60 06   .......a.(....`.
0040 : A8 02 FE 81 80 60 60 28  28 1E 9E 88 68 66 AE AA   .....``((...hf..
0050 : FC 7F 01 E0 00 48 00 36  80 16 E0 0E C8 04 56 83   .....H.6......V.
0060 : 7E E1 E0 48 48 36 B6 96  F6 EE C6 CC 52 D5 FD 9F   ~..HH6......R...
0070 : 01 A8 00 7E 80 20 60 18  28 0A 9E 87 28 62 9E A9   ...~. `.(...(b..
0080 : A8 7E FE A0 40 78 30 22  94 19 AF 4A FC 37 01 D6   .~..@x0"...J.7..

I don't like this lines:
0020 : 00 FF FF FF FF FF FF FF  00 FF FF FF FF FF FF FF   ................
0030 : FF FF FF 00 01 82 00 61

D8 reads ok, but 'higher level' read commands fail. So my conclusion is that there's something either with Header or ECC/EDC.
It looks like these devices don't like such patterns?

That 'data' command looks ok.

To be 100% sure I would look at the resulting image under hex editor and cut end / paste start sectors to match 'cd' image if there are some inconsistencies. Or maybe this is not necessary at all.

Here's is some info for DVD and BD (correction codes): http://citeseerx.ist.psu.edu/viewdoc/do … p;type=pdf

DVDs have RSPC code and can contain bad sectors but this has to be done in factory. I don't know if home devices can burn discs with incorrect correction codes...

I'll look at it during the weekend. Should be possible...

231096 - 230946 = 150 = 2sec = pregap. Try to lower it by few hundred sectors. DIC dump is bugged if error range crosses tracks & pregap area...

Run EdcEcc with fixex command. It will replace them with 0x55 and retry...
I have OptiArc 7290.

LBA[230940, 0x3861c], mode 1
LBA[230941, 0x3861d], mode 1
LBA[230942, 0x3861e], mode 1
LBA[230943, 0x3861f], mode 1
LBA[230944, 0x38620], mode 1
LBA[230945, 0x38621], mode 1
LBA[230946, 0x38622], This sector has invalid sync
LBA[230947, 0x38623], This sector has zero sync
LBA[230948, 0x38624], This sector has zero sync
LBA[230949, 0x38625], This sector has zero sync
LBA[230950, 0x38626], This sector has zero sync
LBA[230951, 0x38627], This sector has zero sync
LBA[230952, 0x38628], This sector has zero sync
LBA[230953, 0x38629], This sector has zero sync
LBA[230954, 0x3862a], This sector has zero sync
LBA[230955, 0x3862b], This sector has zero sync
LBA[230956, 0x3862c], This sector has zero sync

Why those sectors are bad? I think EdcEcc will fix also this:
LBA[230946, 0x38622], This sector has invalid sync

I can introduce another command fixex2 which would fix sectors in specific range...

Hello,
   The steps are:

1) You need to get error range. Launch alcohol, set: ignore read error, fast error skip, ass (100 sectors step)
write down 2 values, when the error range starts and where it ends. Say error range is from sector begin=100 000,  end=120 000
2) Get DIC: DiscImageCreator_2018_02_29_Skip.rar
3) Launch disc ripping with DIC but add 2 extra parameters: /frs 99900 /fre 120100

Note that I extended a bit this range because I don't want Plextor to read near it
If you get any C2 errors before or after error range, extend it even more.
When ripping you might have to extend its beginning by 100 sectors and end by 5000! because Plextor is very bad at reading neer the ring.
In your case it would be /frs 99000 /fre 125000
The purpose of commands above is to fast skip error range and save the drive from rereading into this bad area

In next steps we'll be reading it with other tool and optiarc
4) Get CDArchive.rar
5) Execute: CDArchive.exe -x <driveNo> -d "<dir_where_sectors_are_dumped_to>" -e <rangeStart> <rangeEnd> <retries> <skipCount> <overread> <dir> "<bin_image_path>"

CDArchive.exe -x f -d "c:\Redump\PX\SECT" -e 90 210 10 3 10 fb "c:\Redump\PX\FXX.bin"
f = my OPTI drive
c:\Redump\PC\SECT - here it extracts sectors, this directory must exist
90 = range start, the same value as /frs
210 = range end, the same value as /fre
10 = sector read retry count
3 = if 3 consecutive sectors fail to read then drop reading in this direction
10 = sector overread count, leave 10 default
fb = read forward first, then backwards
c:\Redump\PX\FXX.bin - binary track 1 that is used as reference to check which sectors are bad and should be read by optiarc

6) Once process is complete you will have single sectors in c:\Redump\PX\SECT. Now it's time to merge them into image.

You do this by this command: CDArchive.exe -x f -d "c:\Redump\PX\SECT" -m "c:\Redump\PX\FXX.bin"

It's iterative process, you can once again run CDArchive.exe -x f -d "c:\Redump\PX\SECT" -e 90 210 10 3 10 fb "c:\Redump\PX\FXX.bin" to extract more sectors and later merge them with CDArchive.exe -x f -d "e:\Redump\PX\SECT" -m "c:\Redump\PX\FXX.bin"

After merging launch EccEdc with fixex command (argument is CUE file). This step is required as some sectors read by OptiArc might not be 100% fine. EccEdc will replace whem with 0x55, and you can retry step 6 until no sectors are read.

Make sure to delete contents of c:\Redump\PX\SECT after each iteration, as you don't want to merge the same sectors all the time.

Note #1:
It's very important to set skip value to at least 3-5 to eliminate case when there are few unreadable sectors and then some readable after those.

Note #2:
For discs with multiple rings like Laserlock you have to rip with DIC using biggest error range and repeat process with CDArchive with smaller error ranges as well as specifying valid ranges to extract good sectors!

Sorry for my english!

Jackal I also have disc (german coverdisk) that also gives me no read errors but essentially the data returned by non PX-device is bad. I bet this is some weird mastering error that only scrambled reader can handle.

Some drives incorrectly handle such sectors in firmware and return wrong data thus masking read errors!!

LBA[041489, 0x0a211], MSF[09:15:14], mode 1 User data vs. ecc/edc doesn't match
LBA[041490, 0x0a212], MSF[8d:a0:6c], invalid sync
LBA[041491, 0x0a213], MSF[8a:20:2e], invalid sync
LBA[041492, 0x0a214], MSF[09:15:17], mode 1

Option 2:

I have a disc that triggers some bug in Plextor firmware. Yes - Plextor firmware has bugs! The effect is the same as yours. Few sectors corrupted in the middle of the disc. I don't remember exactly which disc it was, but reripping solved the problem. Have you tried reripping your disc?

I think my disc returned some C2 errors & screwed 50-100 consecutive sectors without returning any C2 data.

Another Plextor bug: Some discs with -153 offset from 'takt' trigger a weird bug and return constant C2 data pattern 0F0F0F F0F0F0. 24 bytes in total corrupted.

ECC checker should not replace sectors for such discs with 0x55. For most cases it's just different mode sector perfectly readable by optical drive. Are you sure the differences stem from that single sector near the end of the disc?

EDIT: I have my custom tool for checking sectors for errors & custom fixer... I think it's time to release it...

It was Plextor 760A

BW-16D1HT - I think I'll buy this drive. Can it read lead-in and lead-out?