I'm on version 1.8.1.
Never had problems before and I suddenly can't rip anything.
Failing on Cars 2 and Brave at the moment.
Anyone else having general issues like this?
Drive 1
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00935.m2ts' at offset '129024'
Error 'Scsi error - MEDIUM ERROR:L-EC UNCORRECTABLE ERROR' occurred while reading '/BDMV/STREAM/00935.m2ts' at offset '129024'
DEBUG: Code 0 at lA.FKs*#NH`Lv*@1-t6M:121262739
DEBUG: Code 0 at )_F9@t.i+5EP hd[Y[Es:121261888
DEBUG: Code 0 at lA.FKs*#NH`Lv*@1-t6M:213130743
DEBUG: Code 63 at lA.FKs*#NH`Lv*@1-t6M:29393332
DEBUG: Code 0 at ;"9ae[J@v:ZPMnh/XZ9*3:121266120
DEBUG: Code 0 at ;"9ae[J@v:ZPMnh/XZ9*3:213134676
DEBUG: Code 0 at :pK[*%U<V7@Ptp"I8u6d:213139115
Drive 2 (a brand new drive)
Error 'Scsi error - HARDWARE ERROR: TRACKING SERVO FAILURE' occurred while reading.....
Suddenly getting hardware errors on 2 different drives?
-
- Posts: 1
- Joined: Fri May 03, 2013 6:43 am
Re: Suddenly getting hardware errors on 2 different drives?
Yes, I'm getting exactly the same problem since installing 1.8.1 yesterday. On every Blu-ray I've tried in on, including ones I've successfully converted before.
Support - Could you urgently provide a link to download the previous version? I've never experienced upgrade issues before, so foolishly didn't bother to backup my existing version first.
I'm running on OS X Mountain Lion latest release.
Support - Could you urgently provide a link to download the previous version? I've never experienced upgrade issues before, so foolishly didn't bother to backup my existing version first.
I'm running on OS X Mountain Lion latest release.
Re: Suddenly getting hardware errors on 2 different drives?
/download/old/
Home Theater PC: Assassin HTPC, XBMCbuntu 12.0 (Frodo), Intel i5 3570k 3.4 GHz Ivy Bridge w/ HD 4000, LG BD-ROM
Playback Devices: Mede8er MED600X3D, MyGica EnjoyTV 120, Xtreamer SideWinder 3, Crystal Acoustics MediaMatchBox
Playback Devices: Mede8er MED600X3D, MyGica EnjoyTV 120, Xtreamer SideWinder 3, Crystal Acoustics MediaMatchBox
Re: Suddenly getting hardware errors on 2 different drives?
thanks crowfax, much appreciated
Re: Suddenly getting hardware errors on 2 different drives?
Did rolling back a version fix your issue?
Home Theater PC: Assassin HTPC, XBMCbuntu 12.0 (Frodo), Intel i5 3570k 3.4 GHz Ivy Bridge w/ HD 4000, LG BD-ROM
Playback Devices: Mede8er MED600X3D, MyGica EnjoyTV 120, Xtreamer SideWinder 3, Crystal Acoustics MediaMatchBox
Playback Devices: Mede8er MED600X3D, MyGica EnjoyTV 120, Xtreamer SideWinder 3, Crystal Acoustics MediaMatchBox
Re: Suddenly getting hardware errors on 2 different drives?
Here I have exactly the same problem, but not only starting with 1.8.1. Once I was at 1.7.6 and was successfully importing all the BD I tried so far. Then I upgraded almost every version as soon as it was available. However I observed that more and more I got problems importing BDs. This went so far, that one BD I recently bought and wanted to import (Red Riding Hood) could not even be opened. As I did not find any hint what the cause was I continued to upgrade until today when I was upgrading from 1.8.0 to 1.8.1 in the hope this would solve the issue. But now its even worse, as the OP said with 1.8.1 not even BDs that I have imported with 1.7.6 (e.g. Inception) could be even opened. I have here two systems (Lion and Mountain Lion) and two different BD-ROM drives (Lite-On) but with no combination I had any success. So after reading this post I switched back to 1.7.6 and my problems are solved.
Before doing further tests (with e.g. versions in between 1.7.6. and 1.8.1) I would like to ask the author to investigate what could have caused these increasing problems with BD (is it the new BD+ engine??). I'm willing to support with debug, tests and various BDs.
Before doing further tests (with e.g. versions in between 1.7.6. and 1.8.1) I would like to ask the author to investigate what could have caused these increasing problems with BD (is it the new BD+ engine??). I'm willing to support with debug, tests and various BDs.
Re: Suddenly getting hardware errors on 2 different drives?
Yes crowfax, I rolled back to 1.8.0 and it fixed the problem immediately. Thanks again for the link.
Re: Suddenly getting hardware errors on 2 different drives?
Just to be clear: nothing at all ripped with 1.8.1, but now with 1.8.0 you can rip again?
Home Theater PC: Assassin HTPC, XBMCbuntu 12.0 (Frodo), Intel i5 3570k 3.4 GHz Ivy Bridge w/ HD 4000, LG BD-ROM
Playback Devices: Mede8er MED600X3D, MyGica EnjoyTV 120, Xtreamer SideWinder 3, Crystal Acoustics MediaMatchBox
Playback Devices: Mede8er MED600X3D, MyGica EnjoyTV 120, Xtreamer SideWinder 3, Crystal Acoustics MediaMatchBox
Re: Suddenly getting hardware errors on 2 different drives?
I was also having problems with 1.8.1 and Pioneer drive, won't read disc or gets stuck halfway into process of reading a BD. Going back to 1.8.0 doesn't help, so I'm trying 1.7.6 next.
But so far very disappointing I can't import any BDs with latest version.
But so far very disappointing I can't import any BDs with latest version.
-
- Posts: 4075
- Joined: Wed Nov 26, 2008 2:26 am
- Contact:
Re: Suddenly getting hardware errors on 2 different drives?
I can't think of any possible changes that could cause hardware errors to appear. Can you copy files from the disc without MakeMKV, i.e. with Finder / Explorer?
Re: Suddenly getting hardware errors on 2 different drives?
Yeah, all other programs are working as should with the drive and can still make ISO files of the disc. I had to completely remove any trace of 1.8.1 and 1.8.0 and reinstall 1.7.6. Of course, I'm now forced to use AnyDVD to bypass encryption on newer discs and then make MKV files.
Later, I'll upgrade to 1.8.0 and see if the same issue returns.
Later, I'll upgrade to 1.8.0 and see if the same issue returns.
Re: Suddenly getting hardware errors on 2 different drives?
Upgraded to 1.8.0 and everything works good again.
Re: Suddenly getting hardware errors on 2 different drives?
My has fatal error when trying to open program, went back to version 1.80 and works just fine, something has changed and it is not for the good, hope this is solved soon