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

[MartyMcNuts]

Hey all, just thought I would post a recent experience I've had to add to the conversation here.

First of all, I had to redo my Plex server who trashed it's config a couple weeks back due to some things I was testing, and the result didn't work as it usually does. Anyway because of this, I decided to wipe my Plex drive and start over with a different filesystem. Anyway I initially had an LG BP50NB40 that I had flashed several years ago to the last firmware which was 1.0.3 Anyway I had always been able to use this drive without issue connected to my iMac directly using the main connector of the Y plug as the iMac has USB 3.0, and the drive even worked for a short time on my Anker 60W powered USB 3 hub. Suddenly while re-ripping discs, the LG started flipping out, going into seek loops and having to be power cycled to stop. Along with this I started getting read errors and failures for discs that had previously worked fine on the same drive, the first time around of ripping.

It got to the point where the drive wouldn't even come online where the mac would recognize it, but it had power to spin up a disc, and sometimes it would come online and then disconnect a few minutes later. So, if it was a power issue, it's most likely due to something in the drive failing as it was several years old, and it now has the same behavior regardless of port, or computer, or cable used.

Anyway I bought I pioneer drive off Amazon to replace it: https://www.amazon.com/PIONEER-External ... 0C367V1QW/ and it works perfectly and it's extremely fast. It also has it's own power supply, and works over USB 3.0 speeds. Question, I still have one disc that WON"T rip regardless of what I do, even cleaned it, it's the older disc of Stargate Extended cut with ACSv3 and it's also a gold disc, and I know some players have issues with Gold discs, the particular issues with this one are like described in the other thread regarding this title, it hangs at analyzing seamless segments, and in backup mode, it copies all but the movie, and fails with hash error. Since it's a 20+ year old disc now, I was wondering if the newer release of the movie is more reliable to rip. I could get another LG drive as a backup as the disc works in that model drive, but I'd rather stick to one drive if I can, since just about all my discs have worked in the pioneer. I rarely have issues with MakeMKV, or ripping, so that's why you don't hear from me much. I just thought I would share this experience, provide a link to the drive I got, and ask about the disc releases, to see what people thought.

I'm running MakeMKV v1.17.7 on a late 2015, 27" 5K iMac, with Monterey 12.7.5. I also had issues with Indiana Jones and the Dial of Destiny, but after giving the disc a good clean, and then doing a backup, I was able to re-rip from backup. That also was a strange disc, I bought it May 9th of this year, and it ripped first time out of the box with the LG drive. The second time around, it failed on both drives with the typical medium read error messages, but then the LG drive died. So, at least I was able to get a new rip with the new drive.

Anyway, thanks for the good info here, and hope this post can help someone else. Have a great day!

Yeah, it's a near 20 year old disc and has probably degraded just enough to cause read issues. I've had a couple of blu-ray discs from 2007 (the first one's I ever bought) do this. I just repurchased the movie and the new discs ripped perfectly fine.

[iFrog]

Yeah, it's a near 20 year old disc and has probably degraded just enough to cause read issues. I've had a couple of blu-ray discs from 2007 (the first one's I ever bought) do this. I just repurchased the movie and the new discs ripped perfectly fine.

Stargate 1994, was never re-released in 4k / HDR was it?, I could wait until it is / if it will be, and get my new copy that way. They usually come with a standard Blu-ray as well.

[dcoke22]

I think all the Stargate fans are waiting for a 4K release of the movie. You would think a 30 year anniversary would be a good time to do it, but it doesn't seem like it.

There was a 15th anniversary release that had a better transfer than the original release.
https://www.blu-ray.com/movies/Stargate-The-Movie-Blu-ray/6569/#Review
If you're going to buy it again, might as well get that version.

[iFrog]

Hey all, I was able to get Stargate ripped. I couldn't find a copy on Amazon that didn't look like a scam to be based on the jacked up prices and names of the third party sellers. The main issue, was the new Pioneer drive wouldn't read the main title on disc, but everything else was. So I got a new LG WP50NB40 drive from Amazon and that drive was able to handle the disc. Now I have the two drives that I use multiple discs at the same time to cut down on time to rip, and I have found already that some discs won't work in one drive, but will work in the other.

With this said, I have a question about the LG drive(s). My initial drive was the LG BP50NB40. The new one is the WP50NB40. When I looked up the drives online, the most I could find was the BP50NB40 was intended for the European market while the WPP50NB40 is for the US. If this is the case, why was the BP50NB40 sold at a Best Buy here in the US? If anyone has additional info in addition to what I was able to find, please share.

Thanks

[cloaked1]

So, this is strange. I am trying to rip a bd I purchased at the store. When I run makeMKV on it, it fails, but there are no error message and no hints as to why it failed.

Screenshot 2024-09-26 at 11.15.39.png (310.32 KiB) Viewed 3211 times

I've enabled debug logging and seeing if that provides any additional clues. More to come. But if anyone has any thoughts on this or if they've seen this before, much would be appreciated. I'm using a purchased license. At first figured there might be something wrong with the disc. I was able to watch the entire movie from the same drive in which I'm ripping the film. So now I'm not sure what the problem is.

== update ==

I got an interesting debug output after enabling debug logging:

Screenshot 2024-09-26 at 15.39.13.png (214.29 KiB) Viewed 3174 times

[Woodstock]

The error is saying it couldn't save the file, and the lack of any intervening messages from the read often means that something blocked the write. You've tested the write to that path, correct?

[ember1205]

The error is saying it couldn't save the file, and the lack of any intervening messages from the read often means that something blocked the write. You've tested the write to that path, correct?

If it isn't permissions, then it's lack of space.

[cloaked1]

The error is saying it couldn't save the file, and the lack of any intervening messages from the read often means that something blocked the write. You've tested the write to that path, correct?

I have. Moreover, MakeMKV is able to create the directory just fine. I have plenty of space on the file system. I'll check a few other things. A clearer error message would have been nice, though.

[ember1205]

The error is saying it couldn't save the file, and the lack of any intervening messages from the read often means that something blocked the write. You've tested the write to that path, correct?

I have. Moreover, MakeMKV is able to create the directory just fine. I have plenty of space on the file system. I'll check a few other things. A clearer error message would have been nice, though.

Create the file locally then move it to the NAS. See if that works. If it does, there could some sort of file locking issue on the NAS when it reaches the point where it attempts to close the file.

[chip2ner]

I'm backing up some discs, and after backing up one of them I received the message "Encountered 7 errors of type 'Read Error'", and following that is the message ""Backup done".

Nowhere during the backup process does it tell me it's encountering any errors or hash check errors, it only tells me about the read errors after the entire disc finishes backing up. I assume these errors were able to be corrected and that's why the backup completed?

When I convert the disc backup to MKV, I receive no errors at all and the MKVs seem fine. Should I be worried that this is a bad disc?

[dcoke22]

I'm backing up some discs, and after backing up one of them I received the message "Encountered 7 errors of type 'Read Error'", and following that is the message ""Backup done".

Nowhere during the backup process does it tell me it's encountering any errors or hash check errors, it only tells me about the read errors after the entire disc finishes backing up. I assume these errors were able to be corrected and that's why the backup completed?

When I convert the disc backup to MKV, I receive no errors at all and the MKVs seem fine. Should I be worried that this is a bad disc?

Generally speaking, if MakeMKV produces output files, they're good. MakeMKV does retry when a read fails so it is possible that there can be read failures but still have a clean rip.

[jbrip]

I don't think anyone has found a solution to this? I'm currently going through the same thing with MAKEMKV ripping 0 title, 1 failed. Tried making backup ISO and using all protection settings from cell-trim, walk, full and auto. Nothing works. Any ideas anyone? This is so annoying. Common makemkv devs help us.

[ember1205]

I don't think anyone has found a solution to this? I'm currently going through the same thing with MAKEMKV ripping 0 title, 1 failed. Tried making backup ISO and using all protection settings from cell-trim, walk, full and auto. Nothing works. Any ideas anyone? This is so annoying. Common makemkv devs help us.

You need to look at the details of WHY it's failing. Odds are, you are experiencing read failures which is almost certainly related to a bad disc, a bad drive, or the combo of the two not working well together. The 'fix' for read errors is to correct them - that isn't something software can do for you.

[flojo]

Generally speaking, if MakeMKV produces output files, they're good.

On error, maybe generally at best.

I had a rip fail to complete 4 times, but on a 5th attempt it completed stating "Read Error". Did the 5th attempt rip all files correctly? Completion rate: 0.2, Error Free: 0. Without better error reporting, you have to give that 5th attempt 0 confidence, even if it did rip correctly. Now if those first 4 attempts didn't exist... I'd still like better error reporting :-/

This is the final line in my log after completion on the 5th attempt.

Code: Select all

65536MSG:2023,131072,3,"Encountered 1 errors of type 'Read Error' - see http://www.makemkv.com/errors/read/","Encountered %1 errors of type '%2' - see %3","1","Read Error","http://www.makemkv.com/errors/read/"MSG:5070,128,0,"Backup done","Backup done"MSG:5081,260,0,"Backup done.","Backup done."

[jbrip]

I don't think anyone has found a solution to this? I'm currently going through the same thing with MAKEMKV ripping 0 title, 1 failed. Tried making backup ISO and using all protection settings from cell-trim, walk, full and auto. Nothing works. Any ideas anyone? This is so annoying. Common makemkv devs help us.

You need to look at the details of WHY it's failing. Odds are, you are experiencing read failures which is almost certainly related to a bad disc, a bad drive, or the combo of the two not working well together. The 'fix' for read errors is to correct them - that isn't something software can do for you.

No it's not a bad disc. The disc is not dirty or greasy. It's 100 percent absolutely new and shrink wrapped and cleaned with a microfiber wito zero scratches and scuffs. Other Blu-ray players play the entire movie perfectly fine. And on the computer (same disc) plays the movie in pristine perfection on VLC.

The issue is Makemkv. It doesn't create a dump for me to send to devs. The only thing it gives are error messages and debug codes. In which no one has helped with. I have tried to Google, "0 title saved, 1 failed" and all have said "your disc is dirty" or try cell walk, full, auto. None of those work.

In my opinion I think this is copyright protected issue that no one has been able to crack. Perhaps other protections have been cracked but not some. And maybe a rare case of use.