Page 9 of 19
Re: If you're experiencing rip errors, please read here first!
Posted: Sat Dec 19, 2020 11:55 pm
by Woodstock
That method works as long as the disk itself is readable, but MakeMKV won't do a backup with read errors.
Re: If you're experiencing rip errors, please read here first!
Posted: Sun Dec 20, 2020 10:49 pm
by dcoke22
cstrasz wrote: Thu Dec 17, 2020 5:03 am
Would an alternate drive help at all to try in these situations? I'd love if I don't need to keep returning discs. If so - what would be a good one that's different enough from my current drive? (WH16NS60 running on revision 1.01).
I have both a WH16NS60 and an ASUS BW-16D1HT. Most of the time, between the two drives I can get things ripped. A LG BU40N seems to be a good drive as well.
viewtopic.php?f=16&t=19634
Re: If you're experiencing rip errors, please read here first!
Posted: Sun Dec 20, 2020 11:57 pm
by jonghotti
Yes having one of each, LG and ASUS makes it easy to try one if the disc won't read in the other.
As far as cleaning use LCD screen cleaner and a microfiber cloth. Spray on and wipe from center to outside of disc ACROSS the grain and never in a circular motion. Dry thoroughly then hold disc between thumb and middle finger, move the disc around and catch the light just right to see the entire disc surface and check for any remainging smudges, streaks, lint or micro-dust as I call it.
Re: If you're experiencing rip errors, please read here first!
Posted: Wed Dec 23, 2020 8:00 am
by cstrasz
Was really hoping an alternative drive would help, but sadly the new ASUS BW-16D1HT drive did no better on this Tenet UHD disc. In fact, it didn't even get as far as the WH16NS60 (which fails at at the last minute). Just various ILLEGAL REQUEST:INVALID FIELD IN CDB errors.
Next step is to swap it out for another disc.
Re: If you're experiencing rip errors, please read here first!
Posted: Fri Dec 25, 2020 8:40 am
by WildCat
possibility of not being able to extract mkv files from full bluray online (folders) Star Trek Tos, mainly hdd use powered by usb
Re: If you're experiencing rip errors, please read here first!
Posted: Fri Dec 25, 2020 8:54 am
by preserve
WildCat wrote: Fri Dec 25, 2020 8:40 am
possibility of not being able to extract mkv files from full bluray online (folders) Star Trek Tos, mainly hdd use powered by usb
The best place for your specific troubleshooting would be the
thread you previously posted so that those offering to troubleshoot can follow the entire conversation.
Re: If you're experiencing rip errors, please read here first!
Posted: Sun Jan 03, 2021 7:59 pm
by Planet____9
I've been ripping my movie collection lately and 2 Fast 2 Furious (Blu-ray copyright2013) is having trouble. about 10.1GB in my WH16NS40 just goes down below 1x and makes quiet yet rapid and random seeking sounds along with the status light stopping before it completely turns off at 10.2GB. There also is no error message, just this. I've left it here for hours, the drive occasionally starts doing something before giving up and trying again and again. When I end the operation I get this.
Code: Select all
DEBUG: Code 233 at ebpwB6kb22+hB36VcVfH09Ch:0
Operation successfully completed
Saving 1 titles into directory //atkinson/Orange/Ripper/MakeMKV windows/2 Fast 2 Furious
Error 'Internal error - Operation was cancelled (135)' occurred while reading '/BDMV/STREAM/00010.m2ts' at offset '11870269440'
DEBUG: Code 0 at sJ#I"~`g+<rs*>?GeyoK:29395471
DEBUG: Code 0 at h*CYV;I&#^aU54?q0v+l:29394068
DEBUG: Code 0 at sJ#I"~`g+<rs*>?GeyoK:213131157
DEBUG: Code 0 at sJ#I"~`g+<rs*>?GeyoK:121262647
DEBUG: Code 5796030 at sJ#I"~`g+<rs*>?GeyoK:121261773
DEBUG: Code 0 at 2I4y60PaCJvDqCn65m1lX:213137068
DEBUG: Code 0 at 2I4y60PaCJvDqCn65m1lX:213137068
LIBMKV_TRACE: Exception: Error in p->FetchFrames(1,false)
Failed to save title 0 to file //atkinson/Orange/Ripper/MakeMKV windows/2 Fast 2 Furious/2 Fast 2 Furious_t00.mkv
0 titles saved, 1 failed
Edit:
I've even tried to grab a plain .iso of the disk and the same problem happened with the disk drive shuting down.
Re: If you're experiencing rip errors, please read here first!
Posted: Wed Feb 10, 2021 5:17 pm
by WheelsOfConfusion
WheelsOfConfusion wrote: Tue Sep 08, 2020 9:15 pm
lordmortis wrote: Sat May 16, 2020 4:55 am
So I just got a read error on the australian version of Steven Universe Season 3. Turning debug on gave the following output:
Interestingly enough, I'm reasonably certain it's not the disc itself, as I _was_ able to do a decrypted backup and my kernel logs showed no read errors. I've also taken a look at the resulting output via mpv.io and it seems to play at roughly the same place. I'm compressing everything with handbrake now and will update when I know more.
I have the same problem with the Australian BR set, same disc.
Interestingly, I can get the bonus features just fine. Just not the main episodes.
FWIW, the issue seems to be resolved in MakeMKV 1.15.4.
I just attempted to rip the same disc again after updating, and it worked without a problem. It seems to have dumped all the contents of the disc as expected.
I was previously able to work around it by using MakeMKV to create a backup, and then feeding the backup file to another program to turn it into MKVs.
Re: If you're experiencing rip errors, please read here first!
Posted: Sat Feb 13, 2021 6:34 pm
by ericst1138
I am getting the message " The source file 'BD-RE PIONEER BD-RW BDR-XS06 1.10' is corrupt or invalid at offset 5266114560-5266116608, attempting to work around"
Anybody have a clue to what it means?
Re: If you're experiencing rip errors, please read here first!
Posted: Sat Feb 13, 2021 6:36 pm
by Woodstock
It means your drive cannot read parts of the disk. The first page of this topic covers the likely causes.
Re: If you're experiencing rip errors, please read here first!
Posted: Tue Feb 23, 2021 10:17 am
by sacolton
I'm using an external drive (Archgon:
https://www.amazon.com/gp/product/B07BC ... UTF8&psc=1)
So far I've had good success ripping 4K movies - except for ALIEN 40th Anniversary UHD. Always gives me errors despite cleaning it constantly.
Other 4K discs were no problem:
Watchmen Ultimate Cut
Harry Potter 1-7
Requiem for a Dream
Passengers
The Greatest Showman
I noticed on my Alien 40th Anniversary UHD disc that there are some light "marks" on the disc. Is this copy protection?
-sacolton
Re: If you're experiencing rip errors, please read here first!
Posted: Thu Mar 04, 2021 5:21 am
by DaveB
I am getting "debug: code 3221225664 at 2c&CcEh9JJZCpiE*:2939919 when I try to rip a disk. I also can have a good rip after I unplug and restart Makemkv a few times. But a couple of my Blu-rays just will not rip. Any help or information would be greatly appreciated.
Re: If you're experiencing rip errors, please read here first!
Posted: Tue Mar 09, 2021 6:46 pm
by Artie
I'm ripping a certain Blu-ray Disc and after multiple attempts it fails with M2TS hash check error. I managed to copy the disc to hard disc using an ordinary "Finder" copy command, which completed and did not complain. I was hopeful that this meant the disc was copied ok. Then I used the MakeMKV backup function to copy the disc, which failed to complete due to the same hash check errors, but provided me with the discatt.dat file. By copying the discatt.dat over to the disc image I made with finder and directing MakeMKV to open this file makeMKV happily started ripping the drive, but gave the same M2TS hash check error.
I accept that the disc is faulty (even though it looks fine). But is there a way to get MakeMKV to rip the disc image, ignoring M2TS hash errors? Maybe the video would turn to crap as it traversed the defective section, but that would be better than failing to rip it at all.
Re: If you're experiencing rip errors, please read here first!
Posted: Wed Mar 10, 2021 3:49 am
by Rockl
I'm getting this same read error when backing up a Heart concert blu-ray: 002003:0000 Error 'Scsi error - MEDIUM ERROR:UNRECOVERED READ ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '598407168'
The problem occurs with:
1) Multiple copies of the commercial disk.
2) Multiple LG drives, one with latest firmware, one downgraded.
3) USB-C External MATSHITA blu-ray
Full log:
Code: Select all
PS C:\WINDOWS\system32> Get-Content C:\Users\rockl.ROCKLNET/MakeMKV_log.txt -Tail 10 -wait
DEBUG: Code 0 at qmqssB3~Ko:r45Q`f:121264142
DEBUG: Code 0 at jot[uQ>o.oH&@FAI:121268604
No SDF v07e: MATSHITA_BD-MLT_UJ240ES_1.30_HL52__002269
DEBUG: Code 3 at 9q-Ny:M#8{Q?vWP<DgKETVU4:29395310
SDF id v07e: MATSHITA_BD-MLT_UJ240ES_1.30_HL52__002269
005072:0000 Backing up disc into folder "file://M:/Blu-Ray Music Videos/backup/EVB335609"
DEBUG: Code 2147483648 at t{@n|^%CllqZ~%h,:121264625
DAFD=PAAAADAAAAEABDQUEAQEBAQ==
DCE=mopxeUkYonRRZFzvQS7u38pBMnnTJdEU/MZ1gBosqjwo3Dw8dkFLd/2UQx8TweUIdDDjunjwQFot0b9YtkmxbErvJmMMRZ/YNpsF4QISGsbFL3taH2OecJSSz/Roc5BFwBP0IGha7OoDD90tdstKPz6byiD0SkwmOg==
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
001003:0020 DEBUG: Code 3221225628 at 9q-Ny:M#8{Q?vWP<DgKETVU4:121262371
001003:0020 DEBUG: Code 3221225628 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 3221225628 at 9q-Ny:M#8{Q?vWP<DgKETVU4:121262371
001003:0020 DEBUG: Code 3221225628 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 3221225628 at 9q-Ny:M#8{Q?vWP<DgKETVU4:121262371
001003:0020 DEBUG: Code 3221225628 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 3221225628 at 9q-Ny:M#8{Q?vWP<DgKETVU4:121262371
001003:0020 DEBUG: Code 3221225628 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
001003:0020 DEBUG: Code 100864256 at jot[uQ>o.oH&@FAI:213139667
001003:0020 DEBUG: Code 100864256 at *tqN*SKGN\l!cy/d:213130559
002003:0000 Error 'Scsi error - MEDIUM ERROR:UNRECOVERED READ ERROR' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '598407168'
005003:0000 Failed to save title /BDMV/STREAM/00000.m2ts to file M:/Blu-Ray Music Videos/backup/EVB335609/BDMV/STREAM/00000.m2ts
002023:0000 Encountered 29 errors of type 'Read Error' - see http://www.makemkv.com/errors/read/
error=0x06031100 count=29 name=Scsi error - MEDIUM ERROR:UNRECOVERED READ ERROR
Encountered 4 unclassified errors
error=0xC000009C count=4 name=OS error - STATUS_DEVICE_DATA_ERROR
005079:0080 Backup done but 1 files failed hash check
005082:0404 Backup done but 1 files failed hash check.
Is there any way to work around this problem?
Re: If you're experiencing rip errors, please read here first!
Posted: Thu Mar 11, 2021 8:20 pm
by Woodstock
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.