I am trying to backup three separate movies using the BR drive in my Mac which is running 10.9, the drive in question is this model:
GGW-H20L with firmware YL03
The three movies in question, appear to backup fine until that final 3% or so of the backup when an audible clicking sound can be heard coming from the drive, this goes on for anywhere from 5-20 minutes until the process fails. I don't have logs handy, but will try again and post them.
All of these are newly purchased discs, so they have no scratches, and I cannot believe that they are defective?
Does anyone have an ideas?
The films in question are:
Dan in Real Life
Batman Begins
French Kiss
Issues with certain movie BR discs.
Issues with certain movie BR discs.
Last edited by ashman on Thu Jan 02, 2014 2:33 pm, edited 1 time in total.
Re: Issues with certain movie BR discs.
Here is the log which results in the failure.
Using direct disc access mode
Evaluation version, 23 day(s) out of 30 remaining
Downloading latest SVQ(s) to /Volumes/Storage 2 ...
Loaded 34 SVQ file(s)
Processing BD+ code, please be patient - this may take up to few minutes
Processing BD+ code using disc-specific SVQ from builtin/dsall.svq
BD+ code processed, got 1 FUT(s) for 1 clip(s)
Title #00720.mpls has length of 35 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00800.mpls was added as title #0
Title #00020.mpls has length of 77 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00012.mpls has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title 00850.mpls is equal to title 00800.mpls and was skipped
Title #00122.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00123.m2ts has length of 15 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00720.m2ts has length of 17 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00600.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00200.m2ts has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00601.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00870.m2ts was added as title #1
Title #00021.m2ts has length of 38 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Operation successfully completed
Saving 1 titles into directory /Volumes/Storage 2
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8209956864'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8210282496'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8213102592'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8268546048'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8268546048'
Failed to save title 0 to file /Volumes/Storage 2/French_Kiss_t00.mkv
0 titles saved, 1 failed
Using direct disc access mode
Evaluation version, 23 day(s) out of 30 remaining
Downloading latest SVQ(s) to /Volumes/Storage 2 ...
Loaded 34 SVQ file(s)
Processing BD+ code, please be patient - this may take up to few minutes
Processing BD+ code using disc-specific SVQ from builtin/dsall.svq
BD+ code processed, got 1 FUT(s) for 1 clip(s)
Title #00720.mpls has length of 35 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00800.mpls was added as title #0
Title #00020.mpls has length of 77 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00012.mpls has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title 00850.mpls is equal to title 00800.mpls and was skipped
Title #00122.m2ts has length of 11 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00123.m2ts has length of 15 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00720.m2ts has length of 17 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00600.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00200.m2ts has length of 7 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00601.m2ts has length of 0 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00870.m2ts was added as title #1
Title #00021.m2ts has length of 38 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Operation successfully completed
Saving 1 titles into directory /Volumes/Storage 2
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8209956864'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8210282496'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8213102592'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8268546048'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8268546048'
Failed to save title 0 to file /Volumes/Storage 2/French_Kiss_t00.mkv
0 titles saved, 1 failed
Re: Issues with certain movie BR discs.
The drive is telling the operating system that it can't read parts of the disks.
If this happens with particular disks, but not others, it could be the disks themselves. Cleaning them would be the next step. They could also be poorly mastered; if they're new, I'd suggest getting them replaced.
If it happens with a LOT of disks, there could be a hardware reason for it, as in a problem with the drive itself.
If this happens with particular disks, but not others, it could be the disks themselves. Cleaning them would be the next step. They could also be poorly mastered; if they're new, I'd suggest getting them replaced.
If it happens with a LOT of disks, there could be a hardware reason for it, as in a problem with the drive itself.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
Re: Issues with certain movie BR discs.
Thanks but this sounds like a canned response.
It doesn't make sense to me that I would have to clean a brand new, newly opened disc, what would there be to clean?
It also doesn't make sense to me that it could be poorly mastered, I have three BluRay movies, is each of them poorly mastered?
Why this program fails on just these tree discs and not the many others I have tried, I do not know, but the reasons you have provided do not make sense to me.
Thanks.
It doesn't make sense to me that I would have to clean a brand new, newly opened disc, what would there be to clean?
It also doesn't make sense to me that it could be poorly mastered, I have three BluRay movies, is each of them poorly mastered?
Why this program fails on just these tree discs and not the many others I have tried, I do not know, but the reasons you have provided do not make sense to me.
Thanks.
Re: Issues with certain movie BR discs.
You are right that this is a canned response, because your logs show a common problem:
Dirty or scratched disk. Solution: Clean it.
Disk that has internal flaws. Solution: Get it replaced.
Optical drive is failing. Solution: Replace drive.
Note that this error is at the OPERATING SYSTEM LEVEL. OSX said the disk is unreadable, and MakeMKV simply reported it to you. OSX didn't say why, because it probably doesn't know.
It is possible that, by increasing the number of retries MakeMKV does when it gets errors like this, eventually the disk will be read. You can try that; it's in the Tools->IO menu, "Read retry count". Default is 5. Set it as high as you want, but 10 tries is usually enough to say the drive isn't going to figure out what is on the disk. Give it 100 if you have time to wait for it and really believe there is nothing wrong with the disk or the drive.
So, what can cause the drive to have an error with the medium (the BD)?Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8209956864'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8210282496'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8213102592'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8268546048'
Error 'Scsi error - MEDIUM ERROR:1090' occurred while reading '/BDMV/STREAM/00882.m2ts' at offset '8268546048'
Dirty or scratched disk. Solution: Clean it.
Disk that has internal flaws. Solution: Get it replaced.
Optical drive is failing. Solution: Replace drive.
Note that this error is at the OPERATING SYSTEM LEVEL. OSX said the disk is unreadable, and MakeMKV simply reported it to you. OSX didn't say why, because it probably doesn't know.
It is possible that, by increasing the number of retries MakeMKV does when it gets errors like this, eventually the disk will be read. You can try that; it's in the Tools->IO menu, "Read retry count". Default is 5. Set it as high as you want, but 10 tries is usually enough to say the drive isn't going to figure out what is on the disk. Give it 100 if you have time to wait for it and really believe there is nothing wrong with the disk or the drive.
MakeMKV Frequently Asked Questions
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging
FAQ about BETA and PERMANENT keys.
How to aid in finding the answer to your problem: Activating Debug Logging