www.makemkv.com

Hi there,

since I got my external LG Bluray burner about 1 1/2 week ago, I am currently evaluating all those ripping solutions available including MakeMKV which is essential the tool I want to have because of Linux support

Most of the BDs I have been playing around were ripped perfectly with MakeMKV. There is just a strange behaviour I have run into on specific BDs of my collection. I am unsure what the reason for this behaviour is.

MakeMKV starts ripping the BD, slows down to something like a few hundred kB a second and then dies. MakeMKV on Win7 x64 does not play nicely. The console app dies without I am able to kill it in the task manager. Under Linux (Xubuntu 11.01 x64) I get a somewhat identical behaviour but more output. MakeMKV show SCSI errors for certain sectors an I also see I/O errors in my dmesg like that. The BDs are ok and completely clean. Ripping times indicated by MakeMKV are around 2-4 hrs per BD
BluRayCopy from FreeFab was able to copy the BDs within an hour without any hickup. So I suspect the BDs having some copy protections which either "corrupt" my BD drive or make MakeMKV "die".

So far I found Predator (Hunter Edition) and any BD of the Alien Anthology Box causing such behaviour. Let me know if I need to provide more infortations.

Has anyone experienced similar things on other BDs ?

TIA,
Holger

Edit: This is a typical message of MakeMKV under Linux:

Hi!

So far I found Predator (Hunter Edition) and any BD of the Alien Anthology Box causing such behaviour

Unless these are VERY new releases that MakeMKV hasn't yet addressed, I don't see that MakeMKV could be the cause of your problems.

Despite what you've said, I'd suggest you try once again thoroughly and carefully cleaning the problematic discs...

Hi,

thanks for your response !

Believe me ...I know how to clean any optical media with a microfiber cloth
And I also know when there are neither finger prints or any sort of dust on a media.

Plus: I have "Program A" which rips the same BDs in the same drive without hickups in about a quater of the time.
MakeMKV has worked nicely with most of my BDs though but I need a reliable option to backup any BD I purchase. I have no issues about waiting a few days until MakeMKV is able to rip it (since I own the BD and must not give it back to a rental store ).

I will give AnyDVD HD a shot tomorrow with my LG BD drive and report back. If AnyDVD HD also works, I think it is hardly deniable that something wrong in the combination MakeMKV, my LG BD burner and the named BDs if two (!) other programs are able to backup, right ?

A bit OT: Are you the setarip_old as over at D9 ?

Regards,
Holger

I'm running into the same issue and I believe the problem is related to a bad DVD ROM or too-warm server. Going to test those theories hopefully tomorrow.

joetesta,

thanks for your reply ! I spent quite some time on this topic but could not really determine what is causing this issues.
Over a month ago when I reported the issue here, most of the time I got the same replies:
- Defect disc
- Dirty disc
etc.

But my observations and the conclusions from them still remain the same:
- Discs were never dirty -> Similar to audio CDs I always clean my BDs and DVDs prior ripping to remove any finger prints
- Discs were ripped fine by either AnyDVD HD or DVD Fab BD Ripper without changing anything configuration-wise (BD drive, BD, host, etc).
I also tried MakeMKV under Linux on my other box (instead of Windows 7) to assure that the issue is not related to my Windows OS or the host.
Same issue here: MakeMKV starts ripping and "dies".

Since I do not have another BD drive to crosscheck, I came to the conclusion that somehow MakeMKV makes things different than AnyDVD or the DVDFab stuff does.
As a result of this it is not a reliable solution for my to backup my BDs and convert them for storing on my HTPC. I bought DVDFabs BD Ripper since it provides similar functionality (ripping BD to MKV with subtitles). One can now speculate if the problems are caused by MakeMKV and/or my BD drive but what counts for me is a reliable solution which is capable of ripping DVDs / BDs to MKV now and in future.

Lately I have been doing a friend of mine the favor to rip all his BDs (roughly 60) to MKV and store them on his NAS for later viewing via streaming client of his new PC. I took the opportunity and crosschecked between the most recent version of MakeMKV and DVDFab BD Ripper.

I experienced similar behaviour for several BDs as the end of last year when I ripped my own stuff:
- Some BDs rip extremely slow with MakeMKV (e.g. up to 4 hrs !) while with BD Ripper it takes only the usual 1 hour.
- Some BDs simply "dry out" during the ripping process with MakeMKV. Then I either killed MakeMKV or the usual errors occured (SCSI I/O error, media not present, bla bla bla...)

Once again: Any of the above mentioned BDs play back fine in a regular standalone player and ripped fine with the DVD Fab product.

I am not a developer, have no access to the sources of MakeMKV and BD Ripper and I guess I would not even understand how things work if I had the sources available. So for me all this remains a mistery but it is defininitely NOT an issue caused by dirty or corrupt disks.

As for system stability: My Quad-core is not overclocked and can run stable a 24/7 encoding week with all four cores maxed out by x264

I would be happy if your post the results of your investigations here

- Holger

These errors come from the drive when MakeMKV reads the data. I can't think of a single case when one program can read the data from blu-ray disc, and another fails. There should be something with the drive.

A simple test - can you just copy files from the problematic disc?

Mike,

thanks for replying ! I took the opportunity and verified the issues with one of the named BDs again.

I use Predator "Ultimate Hunter Edition" for my experiments. The BD was cleaned carefully using a micro fibre clothing to remove even the smallest finger print.

Test #1: Xubuntu 11.10 x64 / MakeMKV 1.7.9
MakeMKV "dies" during initialisation or more specific: I did not feel like waiting another 60 minutes until something happens. I couldn't even get MakeMKV to "rip" the BD.
Here is the part of the log window:
.......................................................
MakeMKV v1.7.9 linux(x64-release) gestartet
Die neue Version 1.7.10 ist unter /download als Download verf?gbar.
Direkter Zugriffsmodus wird verwendet
Fehler 'SCSI-Fehler - MEDIUM ERROR:1090' trat auf w?hrend des Auslesens von '/BDMV/CLIPINF/00101.clpi' bei Offset '0'
.......................................................

Test #2: Windows 7 x64 Professional / MakeMKV 1.7.10

Under Windows 7 x64 pretty similar things seem to happen. Here initialisation of the disk start slow but nicely. After selecting the main movie for ripping, the ripping time explodes to something like 6 hours ?!?

The external BD drive starts to make strange noises like you usually get when you rip DVDs / CDs which have scratches.

As under Linux I chanceled the ripping process to avoid unneccessary stress to the drive.

MakeMKV process still hangs in the background even after closing the Main window. Error messages in the log and drive behaviour seem to indicate a serious "I/O" problem. The GUI somehow freezes completely since the read rate stays at 3x.

I have attached the log file to this post.

Test #3: Windows 7 x64 / DVDFab BluRay Ripper 8.2.2.6
BluRay Ripper initialized the BD and ripped the main movie fine in mkv.remux profile. This is similar to what MakeMKV does.
Ripping was taking about 50 minutes. No strange sounds from the drive. No noticeable drop in reading speed.

Crosscheck: I created an ISO of the same BD via IMG Burn Tool to my HDD. 44 GB went to my HDD straight from the external LG BD drive without any notion of I/O error or something like that.

I have not bothered doing a full BD dump on my Linux box with dd but I would bet on it that this works as well.

Whatever causes this problem is related to the combination of MakeMKV and my BD drive.

-Holger

Ouch. What happens if you do a full disc backup with MakeMKV (as opposed to making a MKV file)?

Strange things happen here

Full dump under Windows with decryption worked fine. No issues...no strange drive sounds...no decrease in ripping speed.
Must I understand this ?

Driven by the success I retried MakeMKV under Linux using the console command to do also a full dump but then my system goes haywire:
Makemkvcon freezes and dmesg reveals "I/O errors": I am out of ideas now....may be (somehow) at least this specific BD has issues..

It's certainly a hardware error. You have a dying disc or drive.

Possibly...I will keep an eye on the BD. If similar behaviour happens again in MakeMKVs "MKV mode" I will try to rip the complete BD.

Thanks for your help !

HolgiB wrote:Hi there,

since I got my external LG Bluray burner about 1 1/2 week ago, I am currently evaluating all those ripping solutions available including MakeMKV which is essential the tool I want to have because of Linux support

Most of the BDs I have been playing around were ripped perfectly with MakeMKV. There is just a strange behaviour I have run into on specific BDs of my collection. I am unsure what the reason for this behaviour is.

MakeMKV starts ripping the BD, slows down to something like a few hundred kB a second and then dies. MakeMKV on Win7 x64 does not play nicely. The console app dies without I am able to kill it in the task manager. Under Linux (Xubuntu 11.01 x64) I get a somewhat identical behaviour but more output. MakeMKV show SCSI errors for certain sectors an I also see I/O errors in my dmesg like that.

Code: Select all

[14362.844278] sr 7:0:0:0: [sr1] Device not ready
[14362.844293] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14362.844306] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14362.844319] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14362.844336] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 5d 9c 00 00 3c 00
[14362.844361] end_request: I/O error, dev sr1, sector 39679600
[14362.847910] sr 7:0:0:0: [sr1] Device not ready
[14362.847925] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14362.847937] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14362.847950] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14362.847966] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 5d d8 00 00 3c 00
[14362.847991] end_request: I/O error, dev sr1, sector 39679840
[14362.852666] sr 7:0:0:0: [sr1] Device not ready
[14362.852681] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14362.852693] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14362.852707] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14362.852724] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 5e 14 00 00 0c 00
[14362.852750] end_request: I/O error, dev sr1, sector 39680080
[14363.496454] sr 7:0:0:0: [sr1] Device not ready
[14363.496470] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14363.496482] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14363.496495] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14363.496511] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 71 19 00 00 03 00
[14363.496537] end_request: I/O error, dev sr1, sector 39699556
[14363.539800] sr 7:0:0:0: [sr1] Device not ready
[14363.539816] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14363.539828] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14363.539841] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14363.539858] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 71 19 00 00 01 00
[14363.539884] end_request: I/O error, dev sr1, sector 39699556
[14363.629151] sr 7:0:0:0: [sr1] Device not ready
[14363.629166] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14363.629178] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14363.629192] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14363.629208] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 71 19 00 00 01 00
[14363.629233] end_request: I/O error, dev sr1, sector 39699556
[14363.673647] sr 7:0:0:0: [sr1] Device not ready
[14363.673662] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14363.673674] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14363.673687] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14363.673703] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 71 19 00 00 01 00
[14363.673729] end_request: I/O error, dev sr1, sector 39699556
[14363.761410] sr 7:0:0:0: [sr1] Device not ready
[14363.761426] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14363.761438] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14363.761451] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14363.761467] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 97 71 19 00 00 01 00
[14363.761493] end_request: I/O error, dev sr1, sector 39699556
[14378.373459] sr 7:0:0:0: [sr1] Device not ready
[14378.373474] sr 7:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[14378.373486] sr 7:0:0:0: [sr1]  Sense Key : Not Ready [current] 
[14378.373499] sr 7:0:0:0: [sr1]  Add. Sense: Medium not present
[14378.373515] sr 7:0:0:0: [sr1] CDB: Read(10): 28 00 00 01 ff a0 00 00 01 00

The BDs are ok and completely clean. Ripping times indicated by MakeMKV are around 2-4 hrs per BD
BluRayCopy from FreeFab was able to copy the BDs within an hour without any hickup. So I suspect the BDs having some copy protections which either "corrupt" my BD drive or make MakeMKV "die".

So far I found Predator (Hunter Edition) and any BD of the Alien Anthology Box causing such behaviour. Let me know if I need to provide more infortations.

Has anyone experienced similar things on other BDs ?

TIA,
Holger

Edit: This is a typical message of MakeMKV under Linux:

Code: Select all

Die Aufgabe wurde erfolgreich abgeschlossen
1 Titel werden in Verzeichnis ~/Filme/Alien gespeichert
Fehler 'SCSI-Fehler - NOT READY:MEDIUM NOT PRESENT' trat auf w?hrend des Auslesens von '/BDMV/STREAM/00985.m2ts' bei Offset '1572864'
Fehler 'SCSI-Fehler - NOT READY:MEDIUM NOT PRESENT' trat auf w?hrend des Auslesens von '/BDMV/STREAM/00985.m2ts' bei Offset '11962368'
Titel 0 in Datei ~/Filme/Alien/Alien_t00.mkv zu speichern schlug fehl
0 Titel wurden gesichert, 1 schlugen fehl

I've been using MakeMKV for a couple years now, and this has just started happening to me. Just got the Godfather Trilogy (Coppola Restoration version) and when I tried the first movie, this is exactly what happened. I'm using OS 10.8.2. The same thing happened when trying to rip Hugo this week. I am going to try a disc that formerly ripped fine for me and see how it goes.

Interesting....please post your results here.

One part of me tries to believe that everything can be explained by defect BDs and / or drive. But in general I see here way too many postings about identical or similar behaviour. It is hard to believe that they all share the similar issues (dirty, defect BDs, defect drives, etc).

I'm ripping a BD I've successfully ripped in the past right now - Superman Vs the Elite. Where Hugo and Godfather started out at a 2x read rate and slowly got slower and slower until it was 0.1x and then quit, this disc started at 2x and slowly sped up throughout the rip, topping out at 3.9x and finishing successfully. Could it be something about the size of the file? The Superman file was a little over 14G, while The Godfather was about 45G and while I don't remember what Hugo was, it was closer to the latter than the former. I also am using 1.7.6, since I haven't been able to complete a successful rip with any version released after that.

Well, I feel kind of stupid. I discovered my problem was that I recently added a new external HD to my network and these were the first two movies I tried to rip to it. I finally saw a message saying something along the lines that the BD drive was writing information too fast for the HD. I tried ripping Hugo and The Godfather to one of my other drives and it worked just like it had always worked.