www.makemkv.com

Posted: **Mon Nov 27, 2023 1:53 pm**

MetAlbertR wrote: ↑
Sun Nov 26, 2023 11:00 pm
Currently ripping 3CB4, but got 1 HashCheck Error when it was loading up the disc, relating to 00441.m2ts.

Not sure if that will cause problems, but I’m at 75% without further issues.

I ripped fine and got the following message when it assessed the disc:

Title #00441.m2ts has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped

Posted: **Mon Nov 27, 2023 2:13 pm**

htpc_rookie wrote: ↑
Mon Nov 27, 2023 1:53 pm

MetAlbertR wrote: ↑
Sun Nov 26, 2023 11:00 pm
Currently ripping 3CB4, but got 1 HashCheck Error when it was loading up the disc, relating to 00441.m2ts.

Not sure if that will cause problems, but I’m at 75% without further issues.
I ripped fine and got the following message when it assessed the disc:

Title #00441.m2ts has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped

I actually set my minimum title length to 0, so I wouldn't get that message. Anyway, that's a different thing altogether than a HashCheck error and nothing to worry about.

I've discovered the HashCheck errors are seemingly random, as I re-inserted the disc and it came up with errors on different files, then no errors when I tried again. Regardless, it rips sucessfully without any issues.

Posted: **Mon Nov 27, 2023 5:39 pm**

MetAlbertR wrote: ↑
Sun Nov 26, 2023 11:00 pm
Currently ripping 3CB4, but got 1 HashCheck Error when it was loading up the disc, relating to 00441.m2ts.

Not sure if that will cause problems, but I’m at 75% without further issues.

Its a 7s disclaimer video, don't see why you would care about that.

Posted: **Mon Nov 27, 2023 5:40 pm**

Also can confirm 3CB4 works, HMV (UK) sourced disk, no read issues whatsoever.

Posted: **Mon Nov 27, 2023 7:41 pm**

Amazon disk ripped ok today.

Posted: **Mon Nov 27, 2023 11:29 pm**

H3cxDev wrote: ↑
Mon Nov 27, 2023 5:40 pm
Also can confirm 3CB4 works, HMV (UK) sourced disk, no read issues whatsoever.

Same here

Posted: **Tue Nov 28, 2023 4:07 am**

9DF6 still ain’t ripping

Posted: **Thu Nov 30, 2023 4:17 pm**

3CB4 still not working for me

Pioneer BD-RW BDR-UD04 drive with Firmware version 1.14

Posted: **Thu Nov 30, 2023 6:13 pm**

trespoolrepair wrote: ↑
Thu Nov 30, 2023 4:17 pm
3CB4 still not working for me

Pioneer BD-RW BDR-UD04 drive with Firmware version 1.14

Depending on what MakeMKV reports, there can be complications....

Fixing Volume Key is Unknown

hkdata.crabdance.com or hkdata.fairuse.org not found

hkdata.fairuse.org is no longer used!

Posted: **Thu Nov 30, 2023 10:01 pm**

d00zah wrote: ↑
Thu Nov 30, 2023 6:13 pm

trespoolrepair wrote: ↑
Thu Nov 30, 2023 4:17 pm
3CB4 still not working for me

Pioneer BD-RW BDR-UD04 drive with Firmware version 1.14
Depending on what MakeMKV reports, there can be complications....

Fixing Volume Key is Unknown

hkdata.crabdance.com or hkdata.fairuse.org not found
hkdata.fairuse.org is no longer used!

Ok so I tried it again to see the exact error message again and now it works with no issues.

Posted: **Sat Dec 02, 2023 5:10 pm**

3 separate attempts to rip my 4k disc (with various methods of cleaning) all led to a single hash check error in the exact same spot of 00294.m2ts (the main feature). Usually if it's a dirty disc or drive the read/hash errors will be in similar places, but not the exact same place over and over. I suspect some kind of physical issue with the disc. Opened an Amazon return, but unfortunately it looks like it will be >1 month to get a replacement what with stock out everywhere.

It's unfortunate; I have hundreds of 4k discs and most of them ripped fine, but lately brand-new shrink-wrapped discs from Amazon have had something like a ~20% failure rate. I wonder if one of the small number of major duplication plants out there has some kind of QC issue.

Posted: **Sat Dec 02, 2023 6:31 pm**

pkasting wrote: ↑
Sat Dec 02, 2023 5:10 pm
3 separate attempts to rip my 4k disc (with various methods of cleaning) all led to a single hash check error in the exact same spot of 00294.m2ts (the main feature). Usually if it's a dirty disc or drive the read/hash errors will be in similar places, but not the exact same place over and over. I suspect some kind of physical issue with the disc. Opened an Amazon return, but unfortunately it looks like it will be >1 month to get a replacement what with stock out everywhere.

It's unfortunate; I have hundreds of 4k discs and most of them ripped fine, but lately brand-new shrink-wrapped discs from Amazon have had something like a ~20% failure rate. I wonder if one of the small number of major duplication plants out there has some kind of QC issue.

It appears a decent bit of the Amazon discs have had issues. Not sure if this will be the case for your return but I started mine on the 26th and it says it will arrive tomorrow. The initial expected delivery was in January but just yesterday it updated. They might fulfil it faster than the initial expectation.

Posted: **Mon Dec 04, 2023 2:19 am**

Amazon isn't doing well with replacements. I got January for a replacement, then December 9, finally December 4. But tonight got the notice that replacement won't arrive til December 9 again.

Posted: **Mon Dec 04, 2023 2:32 am**

Replacement disc from Amazon. Still can't rip Oppenheimer. I don't have problems with other UHD discs. Is there a log file or other info I should submit?

Code: Select all

Saving 1 titles into directory C:/Users/~/Videos/Scratch/Movie 0 using profile 'Atmos 3D' from file 'C:\Users\~/.MakeMKV/Atmos 3D.mmcp.xml'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '30303252480'
DEBUG: Code 3221225488 at T*66mI"9R%2H!-6CI':213131502
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '30303252480'
DEBUG: Code 3221225488 at T*66mI"9R%2H!-6CI':213131502
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '30303252480'
DEBUG: Code 3221225488 at T*66mI"9R%2H!-6CI':213131502
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '30303252480'
DEBUG: Code 3221225488 at T*66mI"9R%2H!-6CI':213131502
Error 'OS error - The specified request is not a valid operation for the target device' occurred while reading '\Device\CdRom0' at offset '30303252480'
DEBUG: Code 3221225488 at T*66mI"9R%2H!-6CI':213131502
Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'
DEBUG: Code 101000192 at T*66mI"9R%2H!-6CI':213131502
Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'
DEBUG: Code 101000192 at T*66mI"9R%2H!-6CI':213131502
Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'
DEBUG: Code 101000192 at T*66mI"9R%2H!-6CI':213131502
Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'
DEBUG: Code 101000192 at T*66mI"9R%2H!-6CI':213131502
Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'
DEBUG: Code 101000192 at T*66mI"9R%2H!-6CI':213131502
Error 'Scsi error - ILLEGAL REQUEST:INVALID FIELD IN CDB' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'
DEBUG: Code 0 at %K{3+D<I-p.W2g)K$P73:29395471
DEBUG: Code 0 at >u+x)D9+i6!-r0Fh7!4O:29394068
DEBUG: Code 0 at %K{3+D<I-p.W2g)K$P73:213131157
DEBUG: Code 0 at %K{3+D<I-p.W2g)K$P73:121262647
DEBUG: Code 14796510 at %K{3+D<I-p.W2g)K$P73:121261773
DEBUG: Code 0 at 5#w%HEc@g}P<=`%X^J>Av:213137068
DEBUG: Code 0 at 5#w%HEc@g}P<=`%X^J>Av:213137068
DEBUG: Code 0 at 5#w%HEc@g}P<=`%X^J>Av:213137068
LIBMKV_TRACE: Exception: Error while reading input
Failed to save title 0 to file C:/Users/~/Videos/Scratch/Movie 0/Oppenheimer (2023)_t00.mkv
Encountered 6 errors of type 'Read Error' - see http://www.makemkv.com/errors/read/
0 titles saved, 1 failed

Posted: **Mon Dec 04, 2023 2:41 am**

ShoutingMan wrote: ↑
Mon Dec 04, 2023 2:32 am
Replacement disc from Amazon. Still can't rip Oppenheimer. I don't have problems with other UHD discs. Is there a log file or other info I should submit?
Code: Select all
Saving 1 titles into directory C:/Users/~/Videos/Scratch/Movie 0 using profile 'Atmos 3D' from file 'C:\Users\~/.MakeMKV/Atmos 3D.mmcp.xml'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00294.m2ts' at offset '30303252480'

0 titles saved, 1 failed

that error if its a usb drive usually mean its not getting enough power is the drive usb?
what dive is this?
probably time to try cleaning the drive
after that replace it with a pioneer

www.makemkv.com

Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)

Re: Oppenheimer (2023)