If you're experiencing rip errors, please read here first!

[Rockl]

If you've followed the procedures outlined at the beginning of this thread (cleaning disk mostly) and it still didn't help, there is the possibility of a mastering error. Especially if the error occurs at the same place on multiple copies of the disk.

Different drives have different tolerances for read errors, so they normally won't give an error at the exact same spot.

Thank for the insight Woodstock. I still have both commercial disks, and confirmed again this morning that the errors occur in the same location. Which BR drives are most tolerant of this kind of error? I've tried LG and Mathshita so far. One of the LG drives has downgraded firmware as well.

[Woodstock]

Same location on two disks in two different drives points strongly to a mastering (creating the disk master) or pressing (manufacturing) error, which is hard to "fix". If the location of the error changed with the disk, neither of which can be fixed on the consumer side.

Sometimes, though, the error can be skipped over by un-checking unneeded tracks within a title. That is, removing a subtitle or audio track from being ripped. If the removed track happens to be what was stored where the error occurs, MakeMKV won't try to read that sector.

Last week, I had a BD that had errors in a single episode of the series. On a whim, I tried ripping the "play all" title. The whole playlist, 9 episodes, ripped without error. And, after that, I could rip the single episode. Apparently, after as many tries as I made, the drive decided to read it. That doesn't help with movies, though.

And sometimes, I'm amazed by what WILL rip.

[rivirwind]

Im trying to rip 500 Days of Summer and i keep getting this error:

Code: Select all

The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144, attempting to work around
The source file '/BDMV/STREAM/00941.m2ts' is corrupt or invalid at offset 2052870144-2052876288, attempting to work around

Eventually if given enough time to run it faults and says file failed to open. I've tried ripping it throughEaseFab Lossless Copy as well and it only gets to 6% then stops progress never faults out even after being allowed to run for 30 + minutes.

[Woodstock]

The drive cannot read that part of the disk. As noted in the beginning of this topic, cleaning is the starting point, even if it "looks clean/brand new". The laser in the drive doesn't agree, and its opinion is really the only one that counts.

[Rockl]

If you've followed the procedures outlined at the beginning of this thread (cleaning disk mostly) and it still didn't help, there is the possibility of a mastering error. Especially if the error occurs at the same place on multiple copies of the disk.

Different drives have different tolerances for read errors, so they normally won't give an error at the exact same spot.

Yes, very strange that both drives experience the read errors at the same exact place on both disks. It's almost like a new form of copy protection...

[rivirwind]

If you've followed the procedures outlined at the beginning of this thread (cleaning disk mostly) and it still didn't help, there is the possibility of a mastering error. Especially if the error occurs at the same place on multiple copies of the disk.

Different drives have different tolerances for read errors, so they normally won't give an error at the exact same spot.

Yes, very strange that both drives experience the read errors at the same exact place on both disks. It's almost like a new form of copy protection...

Yeah, Im seeing the same thing. Two different blu rays both getting errors at the 7% mark every time, even after cleaning, and no visible smudges on disc before or after cleaning. Have tried ripping with different programs and same thing each time.

[Rockl]

If you've followed the procedures outlined at the beginning of this thread (cleaning disk mostly) and it still didn't help, there is the possibility of a mastering error. Especially if the error occurs at the same place on multiple copies of the disk.

Different drives have different tolerances for read errors, so they normally won't give an error at the exact same spot.

Yes, very strange that both drives experience the read errors at the same exact place on both disks. It's almost like a new form of copy protection...

Yeah, Im seeing the same thing. Two different blu rays both getting errors at the 7% mark every time, even after cleaning, and no visible smudges on disc before or after cleaning. Have tried ripping with different programs and same thing each time.

Thanks for confirming I'm not the only one experiencing this. Hopefully the makemkv developers will find a solution for this at some point... The same problem occurs with DVDfab as well, so it's not a Makemkv specific issue..

[Baggi0]

I'm getting troubles with the new World of Wong Kar Wai Bluray boxset. Most of the discs don't rip and they each behave the same way when they freeze. Often, MakeMKV leaves no message at all. When it does it's something about corrupt files. I know I'm not the only one getting these issues. New unsupported form of protection or should I replace the discs?

[Woodstock]

Do you have debug logging enabled in Preferences? That will usually provide more information when things fail.

[Baggi0]

Do you have debug logging enabled in Preferences? That will usually provide more information when things fail.

Debug is activated. Tried again and got this log.
MakeMKV v1.16.0 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\nicob/MakeMKV_log.txt
The new version 1.16.3 is available for download at http://www.makemkv.com/download/
Using LibreDrive mode (v06.2 id=4FBA32AEC678)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
File 00001.mpls was added as title #0
File 00800.mpls was added as title #1
File 00021.mpls was added as title #2
Title #00230.m2ts has length of 0 seconds which is less than minimum title length of 30 seconds and was therefore skipped
Title #00231.m2ts has length of 20 seconds which is less than minimum title length of 30 seconds and was therefore skipped
File 00295.m2ts was added as title #3
File 00304.m2ts was added as title #4
File 00306.m2ts was added as title #5
Operation successfully completed
Saving 6 titles into directory C:/Users/nicob/Videos/Wong Kar Wai/HAPPY TOGETHER
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00274.m2ts' at offset '25792278528'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom0' at offset '25792278528'
DEBUG: Code 3221225628 at eN+MY-Xkg{d5{JGgt4:29395149
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom0' at offset '25792278528'
DEBUG: Code 3221225628 at eN+MY-Xkg{d5{JGgt4:29395149

[Woodstock]

This is a common error sequence when the drive has issues with power at high speed (USB-powered drives), or encounters an error that sends the drive into "try really really hard" mode, and stops responding to operating system commands.

USB power can be affected by what port(s) you plug into. Lowering the drive's top speed can fix it, and the latest versions of MakeMKV can also set a speed limit on many LibreDrive drives. The Info window will indicate if that's available for your particular drive.

"Try really really hard" can be as simple as cleaning the disk, because the drive thinks it can almost read the sector in question.

[henning65]

Hello
I would like to ask for some help with an error message. I simply don't understand how to proceed.
I cleaned the bd-disc with toothpaste - and the disc looks fine.
As you can see: I'm using a ASUS BW-16D1H1 - I got it flashed and it is located in a Vantec NexStar DX USB 3.0.
I'm running MacOS 10. 15.7 Catalina. I don't have a microsoft or linux machine available...
The drive is connected via USB directly to my iMac.

I would like to ask how to proceed: Do I have to get a new drive?

Thanks for helping
------------------

From the log:
MakeMKV v1.16.3 darwin(x64-release) started
Optical drive "DVD+R-DL HL-DT-ST DVDRW GX50N RR06d" opened in OS access mode.
Optical drive "BD-RE TSSTcorp BDDVDW SE-506CB TS02d" opened in OS access mode.
Optical drive "BD-RE ASUS BW-16D1HT 3.10d" opened in OS access mode.
Using LibreDrive mode (v06.2 id=0FA242DD4D0B)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
File 00020.mpls was added as title #0
Title #00011.mpls has length of 8 seconds which is less than minimum title length of 68 seconds and was therefore skipped
[…]
Title #00173.m2ts has length of 8 seconds which is less than minimum title length of 68 seconds and was therefore skipped
Operation successfully completed
Saving 13 titles into directory xxxxxxxxxx
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00205.m2ts' at offset '300810240'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00205.m2ts' at offset '470286336'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00205.m2ts' at offset '521404416'
Error 'Posix error - Input/output error' occurred while reading '/dev/rdisk4' at offset '521404416'
Error 'Posix error - Input/output error' occurred while reading '/dev/rdisk4' at offset '521404416'
Error 'Scsi error - STATUS_05' occurred while reading '/BDMV/STREAM/00205.m2ts' at offset '534380544'
Error 'Posix error - Input/output error' occurred while reading '/dev/rdisk4' at offset '534380544'
Error 'Posix error - Input/output error' occurred while reading '/dev/rdisk4' at offset '534380544'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00205.m2ts' at offset '546177024'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00205.m2ts' at offset '591790080'
[.....]
Error 'Posix error - Input/output error' occurred while reading '/dev/rdisk4' at offset '0'
Error 'Posix error - Input/output error' occurred while reading '/dev/rdisk4' at offset '0'
Error 'Posix error - Input/output error' occurred while reading '/dev/rdisk4' at offset '0'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00208.m2ts' at offset '0'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00208.m2ts' at offset '0'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00208.m2ts' at offset '0'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00208.m2ts' at offset '0'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00208.m2ts' at offset '0'
Error 'Scsi error - HARDWARE ERROR:TIMEOUT ON LOGICAL UNIT' occurred while reading '/BDMV/STREAM/00208.m2ts' at offset '0'
Failed to save title 9 to file xxxxxxxx
Error 'Internal error - Operation was cancelled (135)' occurred while reading '/BDMV/STREAM/00209.m2ts' at offset '0'
Failed to save title 10 to file xxxxxxxxx

[NullNix]

I cleaned the bd-disc with toothpaste - and the disc looks fine.

!! Toothpaste contains abrasives and a fairly strong alkali. I'm not sure that hitting a transparent surface that must remain transparent to laser light at a microscopic level with an alkali abrasive is going to do it too much good...

[dcoke22]

I would like to ask for some help with an error message. I simply don't understand how to proceed.
I cleaned the bd-disc with toothpaste - and the disc looks fine.
As you can see: I'm using a ASUS BW-16D1H1 - I got it flashed and it is located in a Vantec NexStar DX USB 3.0.
I'm running MacOS 10. 15.7 Catalina. I don't have a microsoft or linux machine available...
The drive is connected via USB directly to my iMac.

I would like to ask how to proceed: Do I have to get a new drive?

You can think of that error as the computer got tired of waiting for the optical drive to read the disc. You probably don't have to replace the drive unless things like that happen with most discs you try to rip. It is more likely the case that the disc is dirty or otherwise difficult for your drive for some reason. I've not seen people use toothpaste to clean an optical disc before, so I don't know if that would work. I usually use dish soap and warm water to gently clean a disc.

Personally, I have two different drives. When a disc doesn't want to work in the drive I usually use, I try it in my other drive. It usually works in the other drive and I rarely have to attempt to clean a disc.

I suggest first trying the disc in a different drive. If that doesn't work, then I'd maybe try getting another copy of the disc. Maybe a friend has a copy they could loan you?

[QuiGonLives]

I recently just bought the ASUS Blu ray writer and is unable to rip my Blu-ray through MakeMKV.
It can rip the special features but keeps timing out on the Movie it's self with a "error Device timed out". There is no issues with ripping DVDs.

Here is the actual Error message: (Error 'OS error - {Device Timeout} The specified I/O operation on hs was not completed before the time-out period expired' occurred while reading '/BDMV/STREAM/00057.m2ts' at offset '3578523648')

I have another Blu ray writer and this message comes up: (Error 'OS error - STATUS_DEVICE_NOT_CONNECTED' occurred while reading '/BDMV/STREAM/00057.m2ts' at offset '1113194496')
(Error 'OS error - A device which does not exist was specified' occurred while reading '\Device\CdRom1' at offset '1113194496')

The writer is installed on my computer, no issues.

Anyone know what the issue here could be and how to fix it?


Thanks.