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

[Qun Mang]

Thanks, but this log was from just today, using my new internal LG drive. There should be no going offline with the SATA LG drive- at least I would hope not.

[Woodstock]

True, an internal SATA should not experience this, assuming a normal power supply - only a "smart" supply would fold back power to accessories without crashing the whole machine, and a BD drive should never draw enough power to do that, anyway.

But your drive IS going off-line as far as Windows is concerned, mid-rip. The normal error sequence for a bad disk would be repeated read errors, not "STATUS_DEVICE_DATA_ERROR".

It is possible that it is still trying to read the disk and ignoring Windows' repeated request for status. That is not SUPPOSED to happen, but I have seen it.

Did the drive allow you to eject the disk when this happened? If it is still trying to read it, most will ignore the software eject command, and might not respond to a button push, but I haven't had an LG drive refuse the button push, even if it is still spinning doing a rip (a problem with two-drive ripping and one needs a new disk, but NOT the one on which you hit the button).

[Qun Mang]

I only tried to eject once in the middle and the tray did open, after which I closed it again. After doing that caused Windows 10 to BSOD, I did not repeat this experiment. It did that before with the other drive, but since that was USB and this new one SATA I decided to try it the one time and as I wrote, it still crashed Windows. The power supply should definitely be sufficient- I upgraded that when I upgraded my video card a couple years ago. Maybe I should check that the cables are tightly connected.

[Qun Mang]

Jiggling the cords and making sure they were pushed in didn't help on the ones I couldn't do, but I did try a couple more and finally had some success. The thing is the two successful ones were smaller in size. Rather than start on, say, an hour in the time left field, these two were more like 10-20 minutes and they did finish relatively quickly. Still have to try them on Gear VR, but BD3D2MK3D read and converted MakeMKV's videos without an issue. Is there any reason Windows may have a fit with the longer (ripping time) videos but not shorter ones?

[Woodstock]

That I can't tell you. Did you try the "flash speed limiter" trick, just in case it is something Windows is having a problem with due to rip speed?

[Qun Mang]

I would have to get a large-sized flash drive to try out your recommendation. I have 8GB sticks lying around, and a couple 16GB SD cards, but anything larger is already in use in Android and game devices. I suppose I could borrow the µSD card from my tablet and stick it in my SD card reader.

[Qun Mang]

So I tried your recommendation using the 64GB µSD card from my tablet (with an adapter & the built-in SD card reader on my computer) but it didn't work. I also tried a different method- I installed the latest DVDFab, and after reading just how to use their free HD decrypter, attempted to copy a couple of the blu-rays to isos on my computer. It's probably no surprise to you that I got read errors and even selecting ignore errors (bad idea I know even if it worked) didn't help. Welp, I guess that means either 80% of the blu-rays I try to rip are bad, or I git a bum deal on this drive. I guess I should try to write a couple of blurays and play a couple movies (not that I have a player installed, so maybe not) as well to see if the drive is at fault.

Anyway, thanks for your help.

EDIT 12/23/17: I just want to add that I have had some other successes since. The source of these discs has been the library so in fact the 3D discs could have had a higher fail rate even if most didn't watch that particular disc but rather the normal blu-ray disc also included. Before anyone asks, no I am not ripping these to keep them but rather to watch on my Gear VR since I don't have a 3D-capable TV. I watch them while I have the disc checked out then delete the file when I return the disc. Since most movies no longer have a 3D version, this will become unsustainable as the discs they do have get older. What I really want is a way to rent 3D movies right from my Gear VR. However, as of yet they offer no such solution- only outright purchase. I also consider it a grey (moral, not legal) area downloading a movie while I have the disc (even non-3D version) on hand, watching, then deleting them as I return the discs but I am heading toward that direction.

[Woodstock]

Follow-up information on "disk looks perfect".

Today, I was ripping a number of disks, and the third disk from a particular series had a LOT of errors, like:

Code: Select all

Saving 9 titles into directory Z:/Kuromukuro using profile 'New' from file 'C:\MakeMKVSVQ/New.mmcp.xml'
DEBUG: Code 0 at ^-Z=+1Gl vIjv^(<K:121266856
DEBUG: Code 0 at ^-Z=+1Gl vIjv^(<K:121266856
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '3351773184'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351773184'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '3351773184'
DEBUG: Code 100864261 at i*xOXNB02\B"BbfA8j:121262969
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '3351773184'
DEBUG: Code 100864261 at i*xOXNB02\B"BbfA8j:121262969
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '3351773184'
DEBUG: Code 100864261 at i*xOXNB02\B"BbfA8j:121262969
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '3351902208'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '3351969792'
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351969792'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351969792'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351969792'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351969792'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351969792'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351969792'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969
Error 'OS error - STATUS_DEVICE_DATA_ERROR' occurred while reading '\Device\CdRom3' at offset '3351969792'
DEBUG: Code 3221225628 at i*xOXNB02\B"BbfA8j:121262969

Interestingly, the location changed every few error reports, as MakeMKV did make it past the errors.

I eventually aborted the rip, and moved the "brand new and looks perfect" disk to a different drive... which found no read errors.

Bottom line - disks can look perfect to human eyes, but what counts is what the laser in a particular drive can pull off a disk. I have multiple BD drives, and occasionally have to move disks around to get a "perfect read" on a given BD. The lasers on "identical" drives will always have some slight variance in tolerance, which can make a given DVD or BD "good" or "bad".

[Krawk]

I just ripped the entire tv series Cheers (dvd) to my hard drive. Every Single disc had hand prints on them, all 43 of them. The discs are a UK set but the package said made in Mexico. Did this packing facility double as a lard factory? I cannot figure out how one set of hands could contain enough oil to smear 43 discs.

[drathbun]

My copy of Star Trek: The Next Generation was the same way (hand prints). Turned out to be counterfeit.

[pewn1]

I got the same error with my BD driver as well.
Disc was AACS v65.
Please help me.

MakeMKV Version 1.12.0

Driver

Manufacturer: HL-DT-ST
Product: BD-RE BH16NS40

Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..06964741EC3913E5A687634EF3F0E66BD28 to device 'SPTI:\Device\CdRom1'
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..03483585E7C61FC7A7344639030700499E0 to device 'SPTI:\Device\CdRom1'
...
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'SPTI:\Device\CdRom1'
Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive
Saved AACS dump file as .\MKB_v65_BDROM_4718.tgz
The volume key is unknown for this disc - video can't be decrypted
Backup failed

[Woodstock]

AACS v65 is new.

Saved AACS dump file as .\MKB_v65_BDROM_4718.tgz

This file should be sent to svq@makemkv.com so that Mike can get a new version of MakeMKV put together that deals with the new AACS version.

Edited to add: New version of MakeMKV deals with this: /download/

[jonghotti]

.

[xt550]

so im ripping game of thrones and having problem with S6D2:

Hash check failed for file 00064.m2ts at offset 82765824, file is corrupt.
Too many hash check errors in file 00064.m2ts.
Hash check for /BDMV/STREAM/00064.m2ts : 6.72% corrupt, 93.25% correct, 99.97% checked.Hash check failed for file 01093.m2ts at offset 463005696, file is corrupt.
Too many hash check errors in file 01093.m2ts.
Error 'Scsi error - ILLEGAL REQUEST:ILLEGAL MODE FOR THIS TRACK' occurred while reading '/BDMV/STREAM/01093.m2ts' at offset '466219008'
DEBUG: Code 0 at %C3&6N(a/?Hj~qv`{Cq:213134653
DEBUG: Code 0 at %C3&6N(a/?Hj~qv`{Cq:29397564
DEBUG: Code 0 at 4K>[g,.i~V;JL.4X{o)k:213133319
Encountered 22 errors of type 'Read Error' - see /errors/read/
Encountered 115 errors of type 'HashCheck Error' - see /errors/hashcheck/...
Backup failed

So i copyed to the HDD and then looked at the links in the log:

The simple workaround is to copy all files from the disc to the hard drive manually, without MakeMKV running. If you succeed in this, there is a fast and simple way to convert such copy into encrypted MakeMKV backup that can be opened by MakeMKV later. See our forum for details.


Where do i find this in forum link please

Then after looking around the files im intrested of is 00075.m2ts and 00074.m2ts not the files whit all offset errors
is there aworkaround for this

[Woodstock]

Assuming you were able to get the files to copy without error (and that's a big assumption given that your drive reported multiple read errors), you can try the method outlined by Mike in this thread: http://makemkv.com/forum2/viewtopic.php ... 87&p=60530