SCSI Error when opening MakeMKV

Everything related to MakeMKV
Post Reply
Message
Author
newtonuk
Posts: 10
Joined: Wed Dec 08, 2010 8:23 pm

SCSI Error when opening MakeMKV

#1 Post by newtonuk » Tue Apr 12, 2011 7:31 pm

When I launch MakeMKV I get the following text in the window:

Code: Select all

Debug log started at Tue Apr 12 19:23:11 2011 , written by MakeMKV v1.6.7 darwin(x86-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.6.7 darwin(x86-release) started
001004:0000 Debug logging enabled, log will be saved as /Users/htpc/MakeMKV_log.txt
002014:0000 Optical drive "DVD+R-DL PIONEER DVD-RW  DVR-K06 Q617" opened in DASPI v1.2 mode.
002014:0000 Optical drive "BD-RE PIONEER BD-ROM  BDC-202 1.07" opened in DASPI v1.2 mode.
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:INVALID COMMAND OPERATION CODE' occurred while issuing SCSI command 46020..00140 to device 'DASPI:IODASPIService:15beed6a0c55a4fa:'
001003:0020 DEBUG: Code 0 at 39c]U=R!S2$5#W}<:213137183
002014:0000 Optical drive "BD-ROM WD Virtual CD 070A 1032" opened in DASPI v1.2 mode.
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:INVALID COMMAND OPERATION CODE' occurred while issuing SCSI command 46020..00140 to device 'DASPI:IODASPIService:15beed6a0c55a4fa:'
001003:0020 DEBUG: Code 0 at 39c]U=R!S2$5#W}<:213137183
Can anybody tell me what the SCSI errors mean?

TIA

mike admin
Posts: 4075
Joined: Wed Nov 26, 2008 2:26 am
Contact:

Re: SCSI Error when opening MakeMKV

#2 Post by mike admin » Wed Apr 13, 2011 8:34 am

newtonuk wrote:When I launch MakeMKV I get the following text in the window:

Code: Select all

Debug log started at Tue Apr 12 19:23:11 2011 , written by MakeMKV v1.6.7 darwin(x86-release)
Using 524544KB for read cache.
001005:0000 MakeMKV v1.6.7 darwin(x86-release) started
001004:0000 Debug logging enabled, log will be saved as /Users/htpc/MakeMKV_log.txt
002014:0000 Optical drive "DVD+R-DL PIONEER DVD-RW  DVR-K06 Q617" opened in DASPI v1.2 mode.
002014:0000 Optical drive "BD-RE PIONEER BD-ROM  BDC-202 1.07" opened in DASPI v1.2 mode.
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:INVALID COMMAND OPERATION CODE' occurred while issuing SCSI command 46020..00140 to device 'DASPI:IODASPIService:15beed6a0c55a4fa:'
001003:0020 DEBUG: Code 0 at 39c]U=R!S2$5#W}<:213137183
002014:0000 Optical drive "BD-ROM WD Virtual CD 070A 1032" opened in DASPI v1.2 mode.
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:INVALID COMMAND OPERATION CODE' occurred while issuing SCSI command 46020..00140 to device 'DASPI:IODASPIService:15beed6a0c55a4fa:'
001003:0020 DEBUG: Code 0 at 39c]U=R!S2$5#W}<:213137183
Can anybody tell me what the SCSI errors mean?

TIA
It means that your cd-rom emulator "BD-ROM WD Virtual CD 070A 1032" in fact doesn't emulate a BD-ROM device properly. Are you running you Mac in a VM? What is this emulator?

If you need to open ISO files, MakeMKV can open them directly, from File menu.

newtonuk
Posts: 10
Joined: Wed Dec 08, 2010 8:23 pm

Re: SCSI Error when opening MakeMKV

#3 Post by newtonuk » Wed Apr 13, 2011 8:48 am

Hi, no I'm running MakeMKV on a Mac Mini and the BD-ROM is connected via USB, just as it has always been.

I'm doing nothing differently than I used to do, the only change I have made is to update MakeMKV to the latest version and connect a WD external hard drive which has a WD Smart Drive thing on it. I wonder if it is that which is causing the error.

I'll try unplugging that and see if I get the same error.

Strangely it doesn't seem to stop me from backing up my blu-ray discs, but if MakeMKV is reporting an error I would like to understand it.

newtonuk
Posts: 10
Joined: Wed Dec 08, 2010 8:23 pm

Re: SCSI Error when opening MakeMKV

#4 Post by newtonuk » Wed Apr 13, 2011 4:13 pm

I can confirm that the error is caused by Western Digitial's WD Smartware drive that comes along with their Passport portable drives.

m234897
Posts: 2
Joined: Sun Aug 14, 2011 8:55 am

Re: SCSI Error when opening MakeMKV

#5 Post by m234897 » Sun Aug 14, 2011 8:59 am

Yes that is entirely right the WD drive software upsets things. If you temporarily disconnect the drive NOT just eject then all works fine. Reconnect when done.

Post Reply