Re: ide-scsi -> write_g1: scsi sendcmd: fatal error

[Ian <db5@exemail.com.au>]

On Fri, 29 May 2009 08:40:24 +0200
"Thomas Schmitt" <scdbackup@gmx.net> wrote:

>   ls -d /sys/bus/scsi/devices/0:0:0:0/*:*
> (it should tell the various addresses of
>  the burner: sg?, sr0, 0:0:0:0 )
# ls -d /sys/bus/scsi/devices/1\:0\:0\:0/*:*               
/sys/bus/scsi/devices/1:0:0:0/block:sr0
/sys/bus/scsi/devices/1:0:0:0/scsi_device:1:0:0:0
/sys/bus/scsi/devices/1:0:0:0/scsi_generic:sg0

> 
> Did  cdrecord dev=/dev/sr0  show any other
> behavior than dev=0,0,0 ?
No
> You could try cdrskin instead of cdrecord.
> Same arguments as with cdrecord (but no rscsi).
> Possibly different error messages.
> 
> -------------------------------------------------
> 
> If this all does not bring insight, then you will
> have to try living without using ide-scsi.
> How about remote commands like:
> 
>   cat dsl-1.1.iso | ssh ... 'cdrecord dev=ATA:0,1,0 -tao -'
I hadn't thought of that.  I'll explore this option.
> 
>   cat dsl-1.1.iso | \
>     ssh ... 'cdrskin dev=ATA:0,1,0 -dao -isosize padsize=300k -'
> 
> (According to man cdrecord, -isosize cannot be
>  used with stdin. cdrskin allows this for the
>  first track. So one can use -dao or -sao.)
> 
> Is it sure at all that rscsi will not work
> with "/dev/hdb" (concluded from "ATA:0,1,0")
> rather than "0,0,0" (plus ide-scsi) ?  
> 
> I see a discussion thread from last year:
>   http://lists.debian.org/cdwrite/2008/06/msg00026.html
> How far did you get with that ?
> Did it work finally ?
Yes.  In retrospect it was the kernel upgrade(?) that lead to ide-scsi
not working.
> 
> 
> Have a nice day :)
> 
> Thomas
Cheers.

-- 
Lose wait.  Get Gentoo.