My LG WH16NS60 drive fails to rip most UHD discs. As an example, I was unable to rip the latest Puss In Boots movie but I had no trouble ripping SpiderMan No Way Home. I can only rip two of the 5 Jurassic Park movies in my boxed set.
I get errors like these until the rip finally fails. Is this a firmware issue? Would it help to clean the drive? The disc I use for my BluRay player won't work in the PC drive. Should I just buy a new drive?
Saving 1 titles into directory D:/Disc Rips
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
Hash check failed for file 00294.m2ts at offset 2336876544, file is corrupt.
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2354688000, attempting to work around
Hash check failed for file 00294.m2ts at offset 2354767872, file is corrupt.
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2354688000, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2336821248, attempting to work around
<And so on until...>
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2405627904, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2405627904, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2405627904, attempting to work around
The source file '/BDMV/STREAM/00294.m2ts' is corrupt or invalid at offset 2405627904, attempting to work around
Failed to save title 0 to file D:/Disc Rips/Puss in Boots- The Last Wish_00801-SEG_MainFeature.mkv
Encountered 6 errors of type 'HashCheck Error' - see http://www.makemkv.com/errors/hashcheck/...
0 titles saved, 1 failed
Here is the drive information:
Drive Information
OS device name: A:
Manufacturer: HL-DT-ST
Product: BD-RE WH16NS60
Revision: 1.00
Serial number: SIK9MH8SB313
Firmware date: 2117-04-25 17:56
Bus encryption flags: 17
Highest AACS version: 78
LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Original (unpatched)
Firmware version: 1.00
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes
No disc inserted
Drive doesn't reliably rip UHD discs
Re: Drive doesn't reliably rip UHD discs
I see that you asked the same question a week ago.
Errors ripping UHD discs
I also suggest gently cleaning discs that give you trouble.
This isn't a firmware issue. In fact, once you get a drive running in LibreDrive mode, you should leave it alone. Hopefully you learned this last July. I think I screwed up Folks with Pioneer drives are learning this lesson again now. Pioneer firmware update February 2023
Your errors do indicate that your drive is having trouble correctly reading the disc.
Gently cleaning the disc is the first step. Cleaning the drive is also possible. But, the drive might be wearing out and it might be worth considering another drive. The data density of UHDs is quite high and as a consequence, reading them is harder.
MakeMKV supports using more than one drive at the same time. If you add an additional drive that's more reliable at reading UHDs, you can still use your existing drive for easier to read things like DVDs and blu-rays.
-
- Posts: 2
- Joined: Mon May 31, 2021 2:45 pm
OS Error when Burning Puss and Boots
This is the error I am getting when I try to burn Puss and Boots the last wish blu ray. Can anyone help me with this?
Optical drive "BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UCd" opened in OS access mode.
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '524288'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '524288'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '1048576'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '1048576'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '32768'
Optical drive "BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UCd" opened in OS access mode.
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '524288'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '524288'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '1048576'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '1048576'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '32768'
Re: Drive doesn't reliably rip UHD discs
Have you CLEANED the disk to take care of the dirty spots? MakeMKV won't skip them like a BD player would.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
Re: OS Error when Burning Puss and Boots
Try rebooting your computer and unpowering/unplugging your optical drive and plugging it back in. The tiny computer inside your optical drive might beed to be rebooted.barneysmith wrote: ↑Fri Mar 10, 2023 3:54 amThis is the error I am getting when I try to burn Puss and Boots the last wish blu ray. Can anyone help me with this?
Optical drive "BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UCd" opened in OS access mode.
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '524288'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '524288'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '1048576'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '1048576'
Error 'OS error - (ipc/send) invalid destination port' occurred while reading 'BD-RE PIONEER BD-RW BDR-XD05 3.10 REDL079208UC' at offset '32768'
Re: Drive doesn't reliably rip UHD discs
Problem has been solved. I bought a new drive (WH16NS40) and got it to the right firmware version (1.02) and I'm not having any problems now. Puss in Boots worked fine and Jurassic Park (which used to fail) is ripping OK as I type. The drive I had was 7 years old so that might have been a lot of the problems.
P.S. Turns out the original drive was actually a WH14NS40. Perhaps the firmware up/downgrades I attempted changed to model that was being displayed? Weird.
Anyway, the important thing is that the new drive seems to be working.
P.S. Turns out the original drive was actually a WH14NS40. Perhaps the firmware up/downgrades I attempted changed to model that was being displayed? Weird.
Anyway, the important thing is that the new drive seems to be working.