Can you expound on what is needed and this "code" is or point me to more information? I'd be interesting in finding a solution to this. I'm not sure what the "parameter list" is with regard to ASC/ASCQ and where in the source things related to this might be. I tried to turn on SCSIPI debugging unsuccessfully.

I pulled the enclosure apart and found that the USB-to-ATA interface chip is an In-System/Cypress ISD300 ASIC. The 1394 400Mbps ports on the drive are driven by an Oxford OXF911 chip however I cannot use the firewire ports on this machine due to kern/37411.

Thanks,
- Jesse

On Sun,  2 Dec 2007 19:35:03 +0000 (UTC)
Manuel Bouyer <bouyer@antioche.eu.org> wrote:

>  The problem here is that the drive appear as SCSI to the system, while it's
>  really an ATAPI drive. A few things have to be handled differently between
>  SCSI and ATAPI drives, and in your case the wrong code is used.
>  I don't know how to handle it in the driver, as there's nothing to tell
>  us here that it's an ATAPI device in an enclosure that makes it appear as
>  SCSI. It would probably work if it was in an USB enclosure using the UFI
>  or ATAPI protocol ...