2,276

sarami wrote:

I don't know now.

well i've got over a dozen of these things. is there anyone we can ask? should i buy another drive model to test with?

2,277

user7 wrote:

With LITE ON iHBS112-04 2 drive:

Try to update the firmware https://www.firmwarehq.com/Lite-On/iHBS … files.html

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: UDF logs

2,278

Thank you, I've redumped with updated firmware and new DIC as well as IsoBuster https://drive.google.com/file/d/15PSYB6 … sp=sharing

dic size: 34,139,484,160 bytes
isobuster: 34,138,947,584 bytes (same size as before)

2,279

DIC is having issues dumping an Enhanced CD. When reaching the second session and after the 20000 msec sleep, the drive seemingly stops, and after a bit the following errors are thrown and then the drive re-spins up:

Creating .scm (LBA) 302492/307699[F:ProcessReadCD][L:280] GetLastError: 121, The semaphore timeout period has expired.

LBA[302494, 0x49d9e]: [F:ProcessReadCD][L:280]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 02-04-01 = NOT_READY - LUN_NOT_READY - BECOMING_READY

The LUN_NOT_READY error then throws for every remaining sector of the disc. See attached logs for an example (the dump was cancelled as it would take ages to error through all the sectors): https://mega.nz/#!wE40jCCK!zniqKYJNtHsi … GaZxXt6RlE
Currently using a PX-5224TA through a USB IDE interface, tested on multiple Enhanced CDs to confirm similar results.

2,280 (edited by sarami 2019-12-03 07:50:18)

Resistiv wrote:

DIC is having issues dumping an Enhanced CD

No problem with my 5224TA  (also 4824TA and 755SA). If you have other plextor, try it.

2,281

sarami wrote:

No problem with my 5224TA  (also 4824TA and 755SA). If you have other plextor, try it.

I haven't got any other (functional) Plextor that can dump at the moment. Is there at least some indication of what's happening based on the logs?

2,282

I did a bushound capture when dumping Settlers III Mission CD with alcohol to see how it handles the errors in the rings without aborting or hanging forever. It seems to use a different mode according to RibShark when encountering medium errors. I am hoping you may find this useful to improve DIC to handle such errors better and not hang forever on them.

My hopes for this are because using the file skipping misses the protected areas readable sectors which cause the protection checks to fail. I think this disc uses laserlock or proring tech, I am not sure.

https://drive.google.com/open?id=1R0dZG … FLVkxmo5aq

I made a dump of the Ski-Doo X-Team Racing disc as well, but this one didn't provide anything interesting, I will try with clonecd to see if it's advanced sector scanner is more efficient.

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

2,283

Resistiv wrote:

Is there at least some indication of what's happening based on the logs?

Failed to get the pregap of 1st track of 2nd session.

Resistiv wrote:

I haven't got any other (functional) Plextor that can dump at the moment.

Then, try to change the other PC if you have.

Nexy wrote:

bushound

I don't understand how to see this log.

2,284

sarami wrote:

I don't understand how to see this log.

It's a text file that has logged all the scsi commands, search it for "medium error" to see what it does when encountering the sync errors.

I did try to dump with CloneCD too, it hangs forever in the same manner that DIC does. I am unable to capture how Daemon Tools handles it since they cloak the driver.

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

2,285

user7 wrote:

Thank you, I've redumped with updated firmware and new DIC as well as IsoBuster https://drive.google.com/file/d/15PSYB6 … sp=sharing

dic size: 34,139,484,160 bytes
isobuster: 34,138,947,584 bytes (same size as before)

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- added: Detect Anchor Volume Descriptor Pointer

2,286

Now we're seeing a new size... 34138929152

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

2,287 (edited by sarami 2019-12-04 14:35:27)

Your disc is UDF 2.50
UDF 2.50 says

NOTE: An AnchorVolumeDescriptorPointer structure shall be recorded in at 
least 2 of the following 3 locations on the media: 
• Logical Sector 256. 
• Logical Sector (N - 256). 
• N 

N is last sector.

_disc.txt

Detected Anchor Volume Descriptor Pointer: LBA 16669398

Perhaps, last LBA is 16669398 (size is 34138929152).

2,288

http://redump.org/disc/66810/ - why was the 2nd track misdetected as audio? Marked as data in the subs as usual, TOC in disc.txt also says the track type is Data.

Post's attachments

ROM^2 Karaoke Volume 5 (Japan).rar 2.86 mb, 2 downloads since 2019-12-04 

You don't have the permssions to download the attachments of this post.

2,289

F1ReB4LL wrote:

http://redump.org/disc/66810/ - why was the 2nd track misdetected as audio? Marked as data in the subs as usual, TOC in disc.txt also says the track type is Data.

Try to use latest test version.

2,290 (edited by user7 Yesterday 12:46:14)

sarami, good sign. my ps3 OEM drive dumps with the same results: https://drive.google.com/file/d/1fVoJi3 … sp=sharing

Thank you! I will submit these results.

How do you check UDF version of the disc? I'd like to make sure all my other PS4 kiosk BD-Rs are UDF 2.50, thanks.

2,291

It's written in "Logical Volume Integrity Descriptor"

========== LBA[000273, 0x00111]: Logical Volume Integrity Descriptor ==========

        Minimum UDF Read Revision: 0x250
        Minimum UDF Write Revision: 0x260
        Maximum UDF Write Revision: 0x260

2,292 (edited by user7 Today 04:52:59)

I tried with another one, I left it dumping on my PS3 OEM drive (logs here): https://drive.google.com/file/d/1bZMna_ … sp=sharing
It wrote out the full disc size, even though data only took up 32 gb or so.

Not sure how long this ^ took, but when I came home and tried dumping on my LG, the dump slowed way down after the data area (32 GB or so) and I canceled the dump: https://drive.google.com/file/d/10oD7w2 … sp=sharing

2,293

It looks like no UDF disc.

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: Use "Volume Space Size" if there is not UDF (when disc is BDR, BDRW, DVDRW).