WH16NS60 UHD Issues

[Stubborn5228]

I've been having a bunch of issues recently with ripping UHD discs. It had initially seemed like it might be specific discs at issue, but I'm now thinking the issue may be the drive itself. Most discs have ripped fine over the last few weeks, but a couple have been nonstop problems, Dunkirk UHD has been the worst example, and I've tried 5 different discs all with similar effects. I'm guessing at this point the only thing to do is try a new drive, but I'm hoping to get confirmation one way or another. Non-UHD discs have been fine.

Code: Select all

Drive Information
OS device name: B:
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE WH16NS60
Revision: 1.02
Serial number: M00M2L05504
Firmware date: 2118-10-29 19:36
Bus encryption flags: 17
Highest AACS version: 77

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 1.02
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

[zittrig]

You can try cleaning the lenses. But I think the error should occur with all discs if the lenses are dirty.

Basically some 3-layer discs could cause errors with the LG drives. I used my first 4k friendly drive (LG) for about two years without problems and then arrived the 4k Middle Earth Collection Box ...... Since this time I've a Pioneer drive for difficult discs as second drive.

[Stubborn5228]

Would I have it right that if Blu-rays are working generally, just UHD isn't consistently that would mean it's likely the issue with 3 layers discs and not a drive issue fixable by getting another of the same model?

Just gave a shot cleaning it, but first effort already failed.

Edit:
Also the movie that's been giving me, and Amazon by extension, the most grief is apparently 2 layer.

[Coopervid]

Would I have it right that if Blu-rays are working generally, just UHD isn't consistently that would mean it's likely the issue with 3 layers discs and not a drive issue fixable by getting another of the same model?

Just gave a shot cleaning it, but first effort already failed.

Wash the discs with liquid soap and warm water. Rinse and dry with paper towels. Wipe with a microfiber cloth as used for cleaning glasses.

[Stubborn5228]

That was step one haha, and outside of Dunkirk it seemed to work. That said, I've now got a pile of about 5 discs that haven't been successful cleaning or not.

Dunkirk I'm on disc 5 trying to get it going, and then to a lesser degree I've been hitting roadblocks with:
Justice League
AntMan and the Wasp
Infinity War
Sin City 2
The Expendables 1,2,3

I'm not seeing a commonality, and a number of the discs are brand new.

Try two post cleaning and it looks to be on its way to failing again:

Code: Select all

MakeMKV v1.17.8 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\Charles/MakeMKV_log.txt
Using LibreDrive mode (v06.3 id=7FA2657C7667)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
File 00100.mpls was added as title #0
File 00101.mpls was added as title #1
Title #00000.mpls has length of 8 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00121.mpls was added as title #2
Title #00120.mpls has length of 38 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00007.mpls was added as title #3
Title #00008.mpls has length of 30 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00009.mpls has length of 50 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00005.mpls has length of 23 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00015.mpls has length of 30 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00012.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00017.m2ts has length of 5 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00006.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00002.m2ts has length of 5 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00004.m2ts has length of 12 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00003.m2ts has length of 19 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00020.m2ts has length of 4 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00005.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00063.m2ts has length of 28 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00010.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00064.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00000.m2ts has length of 1 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00900.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00018.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00067.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00068.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00009.m2ts has length of 4 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00021.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00016.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00015.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00019.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00001.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00026.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00007.m2ts has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00025.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00024.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00023.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00022.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00999.m2ts has length of 4 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00901.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00014.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00013.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Operation successfully completed
Saving 2 titles into directory I:/Video/Dunkirk
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 100941314 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 100941314 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 100941314 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 100941314 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 100941314 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 100941314 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 100941314 at e2ZHo%(J'4phL9N]&.:213131502
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
DEBUG: Code 0 at MUklj]%J8Q@ \s=`g8hm:29395793
DEBUG: Code 0 at >{`y(>CqW-`Fca0ypbVz:29394068
DEBUG: Code 0 at MUklj]%J8Q@ \s=`g8hm:213131157
DEBUG: Code 0 at MUklj]%J8Q@ \s=`g8hm:121262647
DEBUG: Code 9292350 at MUklj]%J8Q@ \s=`g8hm:121261773
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00061.m2ts' at offset '19030732800'
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502
Error 'OS error - The I/O device reported an I/O error' occurred while reading '\Device\CdRom0' at offset '19030732800'
DEBUG: Code 3221225861 at e2ZHo%(J'4phL9N]&.:213131502

[dcoke22]

It has been my experience that the same disc in a different drive sometimes produces different results. Not always, of course, but often.

The single biggest improvement in my success rate for ripping discs was added a second, different drive.

[Stubborn5228]

Hoping to try a different drive soon, but continuing to have these issues. Attaching a debug log below.

[dcoke22]

Code: Select all

004004:0000 The source file '/BDMV/STREAM/00061.m2ts' is corrupt or invalid at offset 39739133952, attempting to work around
005076:0000 Hash check failed for file 00061.m2ts at offset 39739189248, file is corrupt.

The optical drive is unable to correctly read a spot on the disc. The standard advice is to gently clean the disc and try again.

[Stubborn5228]

I'm open to the idea that I'm doing something wrong in my cleaning, but I'm also on the 6th of these discs, they are all exhibiting the same errors, and that seems a bit unlikely to be cleaning as the root cause. Same disc, pulled it out, cleaned it with soap and water and then a DVD cleaning spray, restarted the computer, and now it's getting the following error not 2 minutes into reading, whereas last time it made it to something like 40 of 44gb.

Code: Select all

DEBUG: Code 1 at t]^(x8^lFx_Y[hXb+]{lF:121262371

[Coopervid]

Pioneer drives have better error correction. Tell us your country of residence if you want to get one.

[Stubborn5228]

I'm US based, I've done some window shopping, but beyond the pre-flashed ones listed here, I've had a hard time finding a good candidate drive. I'd definitely appreciate any guidance.

[Grzybeek]

I've been having a bunch of issues recently with ripping UHD discs. It had initially seemed like it might be specific discs at issue, but I'm now thinking the issue may be the drive itself. Most discs have ripped fine over the last few weeks, but a couple have been nonstop problems, Dunkirk UHD has been the worst example, and I've tried 5 different discs all with similar effects. I'm guessing at this point the only thing to do is try a new drive, but I'm hoping to get confirmation one way or another. Non-UHD discs have been fine.

Code: Select all

Drive Information
OS device name: B:
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE WH16NS60
Revision: 1.02
Serial number: M00M2L05504
Firmware date: 2118-10-29 19:36
Bus encryption flags: 17
Highest AACS version: 77

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 1.02
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Maybe try updating the firmware or re-patching it before swapping out the drive. If that doesn’t work, then yeah, might be time for a new one.