El Capitan Setup not Working

The place to discuss Mac OS X version of MakeMKV
Post Reply
erica
Posts: 2
Joined: Sun Oct 11, 2015 5:25 pm

El Capitan Setup not Working

Post by erica »

I wish I could be more specific. All was fine under Yosemite using a Macbook Pro/27" Thunderbolt Display with Firewire 800 connection to OWC Mercury Pro 16X External Blu-ray Burner...

Under El Capitan - I get:

1) Generally unreliable (never successful) BluRay access, reboots required, drive lock ups, MakeMKV hangs, etc. Tried new cables, moving things around, etc. I am suspecting firmware on the repackaged LG device at the moment (I am at latest now: v1.02) or the drivers for the Firewire interface on the display. Will be calling OWC tomorrow.

2) I have tried enabling and disabling DASPI (with sudo nvram boot-args="kext-dev-mode=1")... It may be that I need DASPI and that it is not behaving under El Capitan... I have used it all along. Anyone know for sure whether it is required for this drive and any luck under El Cap with another setup?

After a couple hours - I have yet to repeat any behavior twice.... That's why I am suspecting firmware or drivers. Any thoughts or advice is appreciated. Eric.

SOME LOGS BELOW:
Debug log started at Sun Oct 11 03:04:40 2015 , written by MakeMKV v1.9.7 darwin(x86-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.9.7 darwin(x86-release) started
001004:0000 Debug logging enabled, log will be saved as /Users/ericandresen/MakeMKV_log_1.txt
001003:0020 DEBUG: Code 4 at #f/6Pv_~i>!`8D_o:213139690
005042:0000 The program can't find any usable optical drives.
Application exited at Sun Oct 11 03:05:06 2015

Debug log started at Sun Oct 11 03:36:54 2015 , written by MakeMKV v1.9.7 darwin(x86-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.9.7 darwin(x86-release) started
001004:0000 Debug logging enabled, log will be saved as /Users/ericandresen/MakeMKV_log.txt
002010:0000 Optical drive "BD-RE HL-DT-ST BD-RE WH16NS40 1.02d" opened in OS access mode.
001003:0020 DEBUG: Code 100663296 at #f/6Pv_~i>!`8D_o:121269731
001003:0020 DEBUG: Code 100663296 at #f/6Pv_~i>!`8D_o:121269731
001003:0020 DEBUG: Code 100663296 at #f/6Pv_~i>!`8D_o:121269731
001003:0020 DEBUG: Code 100663296 at #f/6Pv_~i>!`8D_o:121269731
001003:0020 DEBUG: Code 100663296 at #f/6Pv_~i>!`8D_o:121269731
001003:0020 DEBUG: Code 100663296 at #f/6Pv_~i>!`8D_o:121269731
001003:0020 DEBUG: Code 100663296 at #f/6Pv_~i>!`8D_o:121269731
001003:0020 DEBUG: Code 117506160 at WzF6m,"O-'="L=Cle{:213132100
001003:0020 DEBUG: Code 117506160 at WzF6m,"O-'="L=Cle{:29393930
002003:0000 Error 'Internal error - Operation was cancelled (112)' occurred while reading 'BD-RE HL-DT-ST BD-RE WH16NS40 1.02' at offset '69632'
001002:0020 LIBMKV_TRACE: UDF mount: reading in reserve VDS extent
001003:0020 DEBUG: Code 117506160 at WzF6m,"O-'="L=Cle{:213132100
001003:0020 DEBUG: Code 117506160 at WzF6m,"O-'="L=Cle{:29393930
002003:0000 Error 'Internal error - Operation was cancelled (112)' occurred while reading 'BD-RE HL-DT-ST BD-RE WH16NS40 1.02' at offset '23948886016'
001002:0020 LIBMKV_TRACE: UDF mount: error reading volume space
001003:0020 DEBUG: Code 117506160 at WzF6m,"O-'="L=Cle{:213132100
001003:0020 DEBUG: Code 117506160 at WzF6m,"O-'="L=Cle{:29393930
002003:0000 Error 'Internal error - Operation was cancelled (112)' occurred while reading 'BD-RE HL-DT-ST BD-RE WH16NS40 1.02' at offset '32768'
001003:0020 DEBUG: Code 0 at O82.E'#QNb/8esPxaLr:213129777
Application exited at Sun Oct 11 03:43:54 2015
erica
Posts: 2
Joined: Sun Oct 11, 2015 5:25 pm

Re: El Capitan Setup not Working

Post by erica »

After posting - I wanted to try a couple more things (that I probably should have tried before posting) - I connected the drive directly to Macbook Pro USB 3 port with USB 3 on the BluRay... It worked. I then connected the drive over Firewire 800 with an adapter direct to Thunderbolt port on Macbook Pro. It worked.

It's all the display firewire drivers that are broken under El Capitan... I use the Display because of the ease of connectivity, being able to daisy chain devices with FW 800, etc. That is obviously a problem now... Back in business with MakeMKV - sorry for the self answering post - but maybe this helps someone...
Mango3
Posts: 3
Joined: Tue Dec 08, 2015 4:38 pm

Re: El Capitan Setup not Working

Post by Mango3 »

I have a similar situation but the drive is connected directly to my iMac (late 2015).

About a weeks ago, ripping started to fail, sometimes immediately, sometimes halfway trough. Sometimes the drive locks up requiring the drive to be disconnected and reconnected before the disk can be ejected. First I thought the disks where scratched or dirty but they are not. And all blu-ray disks are now failing. I tried changing cables and I tried connecting the drive to another computer. Nothing helped. I assumed the drive was broken so I bought a new. The new drive behaves the same way. The old one was an LG USB3 BD-ROM/DVD-writer combo and the new an Asus USB2 BD-ROM/DVD-writer combo.

Attached are two logs, one using the Asus drive connected to an iMac and the other using the LG drive connected to a MacBook Pro (2013?). Both Macs are running El Capitan OSX 10.11.1. MakeMKV is 1.9.7.

DVD disks seems to work ok.

The thing that I can not understand is why both drives start out with OS mode and then switch to direct access mode.

002010:0000 Optical drive "BD-ROM ASUS SBC-06D2X-U D201d" opened in OS access mode.
003007:0000 Using direct disc access mode

002010:0000 Optical drive "BD-ROM HL-DT-ST BDDVDRW CT30F YT04d" opened in OS access mode.
003007:0000 Using direct disc access mode

Isn't MakeMKV supposed to use OS mode on all drives now automagically?
Attachments
MakeMKV_log_LG.txt
(54.15 KiB) Downloaded 507 times
MakeMKV_log_Asus.txt
(16.57 KiB) Downloaded 530 times
Woodstock
Posts: 10331
Joined: Sun Jul 24, 2011 11:21 pm

Re: El Capitan Setup not Working

Post by Woodstock »

On the LG:
002003:0000 Error 'OS error - (ipc/send) invalid destination port' occurred while reading '/BDMV/STREAM/00372.m2ts' at offset '4367843328'
This error is normally seen on a USB-connected and powered drive, when it starts spinning too fast (read rate too high) for the available USB power. The drive motor takes up too much power, and drive "turns off" mid-read. The cure is to make sure that full power is available to the drive, either by making sure it is plugged into the computer itself, or a POWERED USB hub.

On the Asus:
002003:0000 Error 'Scsi error - HARDWARE ERROR:TRACK FOLLOWING ERROR' occurred while reading '/BDMV/STREAM/00372.m2ts' at offset '0'
This one indicates that the drive tried to move to the start of file 00372.m2ts, and never found it. This can be an issue with the disk, or the drive. If it is happening with all disks (try it with a DVD), then I would suspect the drive itself is failing, or has something blocking the follower mechanism.
Mango3
Posts: 3
Joined: Tue Dec 08, 2015 4:38 pm

Re: El Capitan Setup not Working

Post by Mango3 »

Thank you very much for your quick reply. Much appreciated. I will double check the power for the LG and do some more tests on the Asus with different discs. But what about that direct access mode, how come it always falls back to that in stead of using OS mode?
Woodstock
Posts: 10331
Joined: Sun Jul 24, 2011 11:21 pm

Re: El Capitan Setup not Working

Post by Woodstock »

Direct access mode gets around some operating system restrictions. For example, the operating system may try to enforce access restrictions that you're trying to get around. :)
Mango3
Posts: 3
Joined: Tue Dec 08, 2015 4:38 pm

Re: El Capitan Setup not Working

Post by Mango3 »

Ok, I thought OS mode was used for "everything" but this explains why I'm still seeing direct access mode. Thanks.
kindredex
Posts: 4
Joined: Sat Dec 05, 2015 12:51 am

Re: El Capitan Setup not Working

Post by kindredex »

Woodstock wrote:On the LG:
002003:0000 Error 'OS error - (ipc/send) invalid destination port' occurred while reading '/BDMV/STREAM/00372.m2ts' at offset '4367843328'
This error is normally seen on a USB-connected and powered drive, when it starts spinning too fast (read rate too high) for the available USB power. The drive motor takes up too much power, and drive "turns off" mid-read. The cure is to make sure that full power is available to the drive, either by making sure it is plugged into the computer itself, or a POWERED USB hub.
I have tried plugging mine in directly in every single USB port on my iMac AND also tried every port on my POWERED USB 3.0 hub. Still getting failures 100% of the time.
Post Reply