Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Fog_Watch d...@exemail.com.au wrote: On Wed, 27 May 2009 22:26:34 +1000 Fog_Watch d...@exemail.com.au wrote: snip cdrecord: No such device or address. Cannot send SCSI cmd via ioctl. cdrecord: No such device or address. prevent/allow medium removal: scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 200s The same error is returned with the more recent 2.01.01_alpha57. # uname -r 2.6.24-gentoo-r8 Any clues as to the cause of the error. Remember this one? I used two solutions for this. The first solution was to purchase an old SCSI writer: # cat /proc/scsi/scsi | grep Vendor Vendor: PLEXTOR Model: CD-R PX-W1210S Rev: 1.06 I am not sure about the reason for your mail... You are wuoting another mail in a way that makes it impossible to understand your problem and your current mail does not contain any information that could be related to your problem ...well if you have really strange problems, it always makes sense to look at hald (and kill it) as hald often interupts things on Linux. If you really have a problem, please send enough information to allow to understand your problem. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
On Wed, 27 May 2009 22:26:34 +1000 Fog_Watch d...@exemail.com.au wrote: snip cdrecord: No such device or address. Cannot send SCSI cmd via ioctl. cdrecord: No such device or address. prevent/allow medium removal: scsi sendcmd: fatal error CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 200s The same error is returned with the more recent 2.01.01_alpha57. # uname -r 2.6.24-gentoo-r8 Any clues as to the cause of the error. Remember this one? I used two solutions for this. The first solution was to purchase an old SCSI writer: # cat /proc/scsi/scsi | grep Vendor Vendor: PLEXTOR Model: CD-R PX-W1210S Rev: 1.06 The second solution I used was to change the IDE driver on the burner machines to libata: # cat /proc/scsi/scsi | grep CD-RW Vendor: SONY Model: CD-RW CRX175E Rev: 1.0j There is a strange unexpected aspect to the second solution. With: cdrecord dev=REMOTE:rs...@remote-host:0,1,0 -data dsl-4.4.10.iso driveropts=burnfree When: # grep rscsi /etc/passwd rscsi::1000:1000::/home/rscsi:/usr/sbin/rscsi The disk burns fine and is then able to be mounted afterwards on either SCSI or libata/ATAPI drives. When: # grep rscsi /etc/passwd rscsi::1000:1000::/home/rscsi:/bin/bash The disk burns fine and is then only able to be mounted afterwards on my SCSI drive. Interesting? Solved. Regards Fog_Watch. # uname -r 2.6.29-gentoo-r5 -- Lose wait. Get Gentoo. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Joerg Schilling wrote: Rob Bogus ro...@tmr.com wrote: Unsupported, undocumented, self-written, run as root... for problems any method which provides useful information is appropriate. This is not I am sorry to see that you seem to be interested to further increase the confusion. Let me try to help to reduce confusion. Thomas Schmitt unfortunately caused confusion by asking the OP to check /proc/ although this is unrelated to cdrtools. But it may be related to solving the poster's problem. You seem to have it both ways, any problem could not be in cdrecord so it must be in Linux, but any investigation of the Linux characteristics if confusing because it isn't cdrecord. Do you not see how you are contradicting yourself? Thomas Schmitt unfortunately caused confusion by asking the OP to test dev= parameters that are ducumented to be wrong. Thomas Schmitt unfortunately caused confusion by introducing cdrskin although the OP is interested in rscsi. rscsi is a protocol that is part of libscg. Software that makes use of the collaboration in the OSS community and uses libscg may work on any OS platform and gets the ability to use rscsi for free. cdrskin does not use libscg. Rob Bogus added a lot of other unrelated things. Cdrecord depends on a correctly working kernel and correctly working drivers. Had you said that rather than commenting on some vanilla kernel I would not have gotten into this, but the truth is that there isn't a standard compilation configuration, and virtually all vendor kernels have at least some patches applied which haven't made it to stable. If the OP replaces the ugly but working PATA HDD driver by ide-scsi that may not work correctly on his Linux version, then the OP needs to be prepared for a non working cdrecord. There are many reasons for using ide-scsi, but I agree that recent kernels seem to do burners for optical media fine without ide-scsi. It still seems desirable to use it for certain ide tape drives, and for ZIP and LS120 ide drives. There are basically two methods to fix this problem. 1) fix ide-scsi or let it be fixed by the linux kernel folks 2) use the supported PATA HDD driver (i.e. remove ide-scsi) Again we agree, I would like to see (1), but (2) is easier. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Hi, ... # cdrecord dev=0,0,0 -dao -data dsl-1.1.iso # 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 Strange. On my system the first component of the *:*:*:* address corresponds to the bus number as listed by cdrecord (a39): scsibus28: 28,0,0 2800) 'HL-DT-ST' 'BD-RE GGW-H20L ' 'YL03' Removable CD-ROM /sys/bus/scsi/devices/28:0:0:0/block:sr1 /sys/bus/scsi/devices/28:0:0:0/scsi_device:28:0:0:0 /sys/bus/scsi/devices/28:0:0:0/scsi_generic:sg2 So how come you can address 1:0:0:0 by dev=0,0,0 ? Did you ever try dev=1,0,0 ? http://lists.debian.org/cdwrite/2008/06/msg00026.html Did it work finally ? Yes. In retrospect it was the kernel upgrade(?) that lead to ide-scsi not working. Looks like the times of ide-scsi are over. Shrug. cat dsl-1.1.iso | ssh ... 'cdrecord dev=ATA:0,1,0 -tao -' I hadn't thought of that. I'll explore this option. Did you already disable ide-scsi and try dev=REMOTE:u...@host:ATA:0,1,0 dev=REMOTE:u...@host:/dev/hdb Maybe it works ... Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
On Sat, 30 May 2009 11:50:13 +0200 Thomas Schmitt scdbac...@gmx.net wrote: Did you already disable ide-scsi and try dev=REMOTE:u...@host:ATA:0,1,0 dev=REMOTE:u...@host:/dev/hdb Maybe it works ... $ cdrecord dev=REMOTE:rs...@hostname:0,1,0 -scanbus Cdrecord-ProDVD-ProBD-Clone 2.01.01a51 (i686-pc-linux-gnu) Copyright (C) 1995-2008 Jörg Schilling scsidev: 'REMOTE:rs...@hostname:0,1,0' devname: 'REMOTE:rs...@hostname:0,1,0' scsibus: 0 target: 1 lun: 0 Warning: Using remote SCSI interface. cdrecord: No such file or directory. Cannot open '/dev/pg1'. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Have a nice day :) Thomas Thanks for the help, Thomas. Regards Fog_Watch. -- Lose wait. Get Gentoo. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Ian d...@exemail.com.au wrote: On Fri, 29 May 2009 08:40:24 +0200 Thomas Schmitt scdbac...@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 Why do you check this? It is completely unimportant for the functionality of cdrtools. Did cdrecord dev=/dev/sr0 show any other behavior than dev=0,0,0 ? No Well it is not expected to give different results in special as dev=/dev/sr0 is unsupported. cdrecord works with all known Linux kernels, did you test this with an official unmodified Linux Kernel? You could try cdrskin instead of cdrecord. Same arguments as with cdrecord (but no rscsi). Possibly different error messages. cdrskin does not implement rscsi. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Fog_Watch d...@exemail.com.au wrote: On Sat, 30 May 2009 11:50:13 +0200 Thomas Schmitt scdbac...@gmx.net wrote: Did you already disable ide-scsi and try dev=REMOTE:u...@host:ATA:0,1,0 dev=REMOTE:u...@host:/dev/hdb Maybe it works ... $ cdrecord dev=REMOTE:rs...@hostname:0,1,0 -scanbus Cdrecord-ProDVD-ProBD-Clone 2.01.01a51 (i686-pc-linux-gnu) Copyright (C) 1995-2008 JÃ?rg Schilling scsidev: 'REMOTE:rs...@hostname:0,1,0' devname: 'REMOTE:rs...@hostname:0,1,0' scsibus: 0 target: 1 lun: 0 Warning: Using remote SCSI interface. cdrecord: No such file or directory. Cannot open '/dev/pg1'. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Is it possible that you have the broben wodim installed at the remote side? wodim is completely broken! You of course need a _working_ rscsi at the remote side cdrecord dev=REMOTE:rs...@hostname: -scanbus will work if you have a correctly working rscsi installed and_ configured at the remote side. rscsi must be installed at: /opt/schily/sbin/rscsi Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Hi, for me as bystander and programmer of burn software this is an interesting drama to watch. It might well be a futile effort, though. Especially since i do not know how crucial remote drive addressing is to you resp. whether remote burn program execution is an alternative for you. Whatever: $ cdrecord dev=REMOTE:rs...@hostname:0,1,0 -scanbus According to README.rscsi, -scanbus should be accompanied by a dev option without particular device address - dev=REMOTE:u...@host: or dev=REMOTE:u...@host will allow you to do SCSI bus scanning while you log in as user For a particular drive i'd try -inq rather than -scanbus. But that's several experiments in one, anyway. If not yet frustrated enough, would try: - What do these locally with ide-scsi enabled ? cdrecord dev=0,0,0 -inq cdrecord dev=1,0,0 -inq After disabling ide-scsi on the machine which hosts the burner: - What do these locally ? cdrecord dev=/dev/hdb -inq cdrecord dev=ATA:0,1,0 -inq (I assume /dev/hdb is the address of the burner without ide-scsi.) - What do these remotely ? cdrecord dev=REMOTE:rs...@hostname -scanbus cdrecord dev=REMOTE:rs...@hostname:ATA -scanbus - What do these remotely ? cdrecord dev=REMOTE:rs...@hostname:/dev/hdb -inq cdrecord dev=REMOTE:rs...@hostname:ATA:0,1,0 -inq ... the same with eventual addresses from above -scanbus ... Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Thomas Schmitt scdbac...@gmx.net wrote: for me as bystander and programmer of burn software this is an interesting drama to watch. It might well be a futile effort, though. Especially since i do not know how crucial remote drive addressing is to you resp. whether remote burn program execution is an alternative for you. There is nothing cruical... After disabling ide-scsi on the machine which hosts the burner: - What do these locally ? cdrecord dev=/dev/hdb -inq cdrecord dev=ATA:0,1,0 -inq (I assume /dev/hdb is the address of the burner without ide-scsi.) - What do these remotely ? cdrecord dev=REMOTE:rs...@hostname -scanbus cdrecord dev=REMOTE:rs...@hostname:ATA -scanbus - What do these remotely ? cdrecord dev=REMOTE:rs...@hostname:/dev/hdb -inq cdrecord dev=REMOTE:rs...@hostname:ATA:0,1,0 -inq ... the same with eventual addresses from above -scanbus ... Could you explain me the reason why you try to confuse the OP? Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Joerg Schilling wrote: Thomas Schmitt scdbac...@gmx.net wrote: Hi, Fog_Watch: cdrecord using ide-scsi returns an error that I don't understand. ... cdrecord: No such device or address. Cannot send SCSI cmd via ioctl. Joerg Schilling: This is a Linux kernel problem, please ask the related people. 2.6.24-gentoo-r8 Well, ide-scsi is said to be deprecated with kernel 2.6. This is not a helpful reply. One should at least find out a bit more before exposing oneself at LKML. What do you get from this command ? cdrecord -scanbus If the OP did create an own rotten kernel this will not help. Custom does not imply rotten many people build kernels without support things for hardware they lack and features they avoid. ide-scsi seems to be buggy and unmaintained in newer Linux releases. I would say lightly tested for sure, based on one machine still using that feature, it seems to work using a ZIP100 drive as a scsi disk. cdrecord -scanbus on a _vanilla_ Linux kernel will work as well as There *is* no vanilla kernel, virtually every distribution and developer picks different configuration options to build the kernel, even though the code base is the same. just calling cdrecord ... _without_ dev= parameter Most users have only one drive and in this case, cdrecord will automagically search for the right device. I doubt your assumption is right about most users, but in the case where only a single drive is present the application does identify it and use it. This is how the typical output from a cdrecord -scanbus call looks on a vanilla 2.6.13 Linux kernel: cdrecord -scanbus Cdrecord-ProDVD-ProBD-Clone 2.01.01a60 (i686-pc-linux-gnu) Copyright (C) 1995-2009 Jörg Schilling Linux sg driver version: 3.5.27 Using libscg version 'schily-0.9'. scsibus0: 0,0,0 0) 'QUANTUM ' 'ATLAS10K2-TY184L' 'DA40' Disk 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus1001: 1001,0,0 100100) 'MITSUMI ' 'CD-ROM FX4830T!B' 'R02J' Removable CD-ROM 1001,1,0 100101) * 1001,2,0 100102) * 1001,3,0 100103) * 1001,4,0 100104) * 1001,5,0 100105) * 1001,6,0 100106) * 1001,7,0 100107) * As you see, there is no need to hand craft e linux kernel - cdrecord works around the oddities in the Linux device addressing ;-) The usual reason for trimming the configuration is to get a compile done before the next revision of the kernel comes out. Related question: does cdrecord do the right thing if the only burner is on rscsi? -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Joerg Schilling wrote: Thomas Schmitt scdbac...@gmx.net wrote: cdrecord -scanbus Full record. Something like this ? scsibus0: 0,0,0 0) 'TSSTcorp' 'CDDVDW SH-S203B ' 'SB00' Removable CD-ROM 0,1,0 1) * .. (This is a SATA attached drive. It appears as SCSI without ide-scsi emulation.) eject /dev/sr0 Yes. Then try cdrecord dev=/dev/sr0 -dao ... rather than cdrecord dev=0,0,0 -dao ... Is there any reson to recommend _unsupported_ command line usage? Unsupported, undocumented, self-written, run as root... for problems any method which provides useful information is appropriate. This is not endorsement for production use, only a suggestion for characterizing the problem. Note, I don't say solving but do imply understanding. cdrecord works just fine out of the box if you either _don't_ use dev= at all or id you use the official SCSI device syntax. It works fine out of the box providing I want to use the burner it chooses. Having more than one is no longer unusual, a number of systems come with a reader and a burner these days. As to official, I have no doubt that you can cite some organization which says to do things the way you do, and you have decided they do it your way and so are official. I'm old enough to remember SCSI back when, and where were always four numbers, not the three you choose to support. These were the slot number, the bus number, the device number and the LUN number, and that was back when device number was 0..7 and LUNs often selected 556bpi tape drives. If it does not work this way, there is a bug in the kernel code. Jörg -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Rob Bogus ro...@tmr.com wrote: Unsupported, undocumented, self-written, run as root... for problems any method which provides useful information is appropriate. This is not I am sorry to see that you seem to be interested to further increase the confusion. Let me try to help to reduce confusion. Thomas Schmitt unfortunately caused confusion by asking the OP to check /proc/ although this is unrelated to cdrtools. Thomas Schmitt unfortunately caused confusion by asking the OP to test dev= parameters that are ducumented to be wrong. Thomas Schmitt unfortunately caused confusion by introducing cdrskin although the OP is interested in rscsi. rscsi is a protocol that is part of libscg. Software that makes use of the collaboration in the OSS community and uses libscg may work on any OS platform and gets the ability to use rscsi for free. cdrskin does not use libscg. Rob Bogus added a lot of other unrelated things. Cdrecord depends on a correctly working kernel and correctly working drivers. If the OP replaces the ugly but working PATA HDD driver by ide-scsi that may not work correctly on his Linux version, then the OP needs to be prepared for a non working cdrecord. There are basically two methods to fix this problem. 1) fix ide-scsi or let it be fixed by the linux kernel folks 2) use the supported PATA HDD driver (i.e. remove ide-scsi) Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Hi, However, when legacy /proc/scsi support is enabled in a fresh kernel the performance and returned error remains the same. That /proc/scsi stuff is for diagnostics. So no remedy was to be expected. But what do you get now from this ? cat /proc/scsi/scsi And from this ? 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 ) Did cdrecord dev=/dev/sr0 show any other behavior than dev=0,0,0 ? 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 -' 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 ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Fog_Watch d...@exemail.com.au wrote: On Thu, 28 May 2009 10:26:13 -0700 Dave Platt dpl...@radagast.org wrote: Possibly the user's kernel was configured without the legacy /proc/scsi support feature being enabled? Correct. However, when legacy /proc/scsi support is enabled in a fresh kernel the performance and returned error remains the same. You do not need prov/scsi but if you have a recent kernel where ide-scsi does not work, you must not use it. See my other mail from yesterday Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
On Fri, 29 May 2009 08:40:24 +0200 Thomas Schmitt scdbac...@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. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Hi, cdrecord -scanbus Full record. Something like this ? scsibus0: 0,0,0 0) 'TSSTcorp' 'CDDVDW SH-S203B ' 'SB00' Removable CD-ROM 0,1,0 1) * .. (This is a SATA attached drive. It appears as SCSI without ide-scsi emulation.) eject /dev/sr0 Yes. Then try cdrecord dev=/dev/sr0 -dao ... rather than cdrecord dev=0,0,0 -dao ... This is deprecated too. But maybe it works. I understand that cdrecord uses /dev/sg* if you give it dev=0,0,0. (We have a wealth of SCSI drivers in Linux.) eject /dev/scd0 Don't have one. That's normal. There are two sects of distro makers. Yours are in favor of sr, others prefer scd, generous ones provide both. [...] find . | grep scsi cat sys/dev/scsi/logging_level ./sys/dev/scsi ./sys/dev/scsi/logging_level That is really strange. I got 15 files below /proc/scsi. Like: ./scsi/usb-storage ./scsi/sg ./scsi/scsi I do not have a system with no (pseudo-)SCSI devices. So i cannot tell whether the lack of /proc/scsi is normal. (On the other hand /dev/sr0 works for eject. So somehow the system knows the drive as SCSI.) Do you have any USB device attached ? Usually they should show up like /proc/scsi/usb-storage/85 /proc/scsi/usb-storage/28 /proc/scsi/usb-storage/21 What do you see if you boot without ide-scsi ? Do you get a directory /proc/scsi then ? (Could it be ide-scsi confuses /proc ?) Well, if no more insight can be gained, it is time to ask some kernel people. I would first try at Gentoo, because as said: ide-scsi is not advised for 2.6 kernels. At least one can ask why /proc shows no signs of scsi info. (If you meet unwillingness to deal with cdrecord, i could offer my own burn program cdrskin for testing.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Thomas Schmitt scdbac...@gmx.net wrote: cdrecord -scanbus Full record. Something like this ? scsibus0: 0,0,0 0) 'TSSTcorp' 'CDDVDW SH-S203B ' 'SB00' Removable CD-ROM 0,1,0 1) * .. (This is a SATA attached drive. It appears as SCSI without ide-scsi emulation.) eject /dev/sr0 Yes. Then try cdrecord dev=/dev/sr0 -dao ... rather than cdrecord dev=0,0,0 -dao ... Is there any reson to recommend _unsupported_ command line usage? cdrecord works just fine out of the box if you either _don't_ use dev= at all or id you use the official SCSI device syntax. If it does not work this way, there is a bug in the kernel code. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Hi, me: Then try cdrecord dev=/dev/sr0 -dao ... [...] This is deprecated too. But maybe it works. Joerg Schilling: Is there any reson to recommend _unsupported_ command line usage? For a test: yes. After all, eject was able to send a LOAD/UNLOAD MEDIUM command to the drive. If the SCSI transport was totally unusable then this would not have succeeded either. Actually the kernel people strongly recommend not to use /dev/sg* for CD burning. So if Fog_Watch interfaces to those people then this might be an issue. cdrecord works just fine out of the box if you either _don't_ use dev= at all That is a further test proposal. Fog_Watch, please try this too. If it does not work this way, there is a bug in the kernel code. Something appears wrong, indeed. The /proc tree seems truncated. I try to provide the necessary knowledge on the burn side of the problem. The kernel side will need other expertise. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Thomas Schmitt scdbac...@gmx.net wrote: Then try cdrecord dev=/dev/sr0 -dao ... [...] This is deprecated too. But maybe it works. Joerg Schilling: Is there any reson to recommend _unsupported_ command line usage? For a test: yes. Sorry but it does not help at all if you give speudo advise without explaining the background. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
On Thu, May 28, 2009 at 11:49:13AM +0200, Thomas Schmitt wrote: Something appears wrong, indeed. The /proc tree seems truncated. My guess is he built his own custom kernel and left out a lot of drivers that he needs. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
If it does not work this way, there is a bug in the kernel code. Something appears wrong, indeed. The /proc tree seems truncated. Possibly the user's kernel was configured without the legacy /proc/scsi support feature being enabled? The help data says In Linux 2.6 this has been superseded by files in sysfs but many legacy applications rely on this. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Hi, Dave Platt wrote: Possibly the user's kernel was configured without the legacy /proc/scsi support feature being enabled? The help data says In Linux 2.6 this has been superseded by files in sysfs but many legacy applications rely on this. Being such a legacy entity myself i will now have to explore /sys/bus/scsi/devices Ahum ... lots of files ... $ ls /sys/bus/scsi/devices 0:0:0:0 2:0:0:0 21:0:0:0 28:0:0:0 85:0:0:0 $ cat /sys/bus/scsi/devices/28:0:0:0/model BD-RE GGW-H20L $ ls -d /sys/bus/scsi/devices/28:0:0:0/scsi_generic* /sys/bus/scsi/devices/28:0:0:0/scsi_generic:sg2 $ ls -d /sys/bus/scsi/devices/28:0:0:0/block* /sys/bus/scsi/devices/28:0:0:0/block:sr1 Where would one find an overview of available info in /sys/bus/scsi/ ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Ahum ... lots of files ... lots, plethora, overabundance... yeah. $ ls /sys/bus/scsi/devices 0:0:0:0 2:0:0:0 21:0:0:0 28:0:0:0 85:0:0:0 $ cat /sys/bus/scsi/devices/28:0:0:0/model BD-RE GGW-H20L $ ls -d /sys/bus/scsi/devices/28:0:0:0/scsi_generic* /sys/bus/scsi/devices/28:0:0:0/scsi_generic:sg2 $ ls -d /sys/bus/scsi/devices/28:0:0:0/block* /sys/bus/scsi/devices/28:0:0:0/block:sr1 Where would one find an overview of available info in /sys/bus/scsi/ I'm not sure that one exists, other than to say Use the source, Luke!. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Thomas Schmitt scdbac...@gmx.net wrote: Hi, Fog_Watch: cdrecord using ide-scsi returns an error that I don't understand. ... cdrecord: No such device or address. Cannot send SCSI cmd via ioctl. Joerg Schilling: This is a Linux kernel problem, please ask the related people. 2.6.24-gentoo-r8 Well, ide-scsi is said to be deprecated with kernel 2.6. This is not a helpful reply. One should at least find out a bit more before exposing oneself at LKML. What do you get from this command ? cdrecord -scanbus If the OP did create an own rotten kernel this will not help. ide-scsi seems to be buggy and unmaintained in newer Linux releases. cdrecord -scanbus on a _vanilla_ Linux kernel will work as well as just calling cdrecord ... _without_ dev= parameter Most users have only one drive and in this case, cdrecord will automagically search for the right device. This is how the typical output from a cdrecord -scanbus call looks on a vanilla 2.6.13 Linux kernel: cdrecord -scanbus Cdrecord-ProDVD-ProBD-Clone 2.01.01a60 (i686-pc-linux-gnu) Copyright (C) 1995-2009 Jörg Schilling Linux sg driver version: 3.5.27 Using libscg version 'schily-0.9'. scsibus0: 0,0,0 0) 'QUANTUM ' 'ATLAS10K2-TY184L' 'DA40' Disk 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus1001: 1001,0,0 100100) 'MITSUMI ' 'CD-ROM FX4830T!B' 'R02J' Removable CD-ROM 1001,1,0 100101) * 1001,2,0 100102) * 1001,3,0 100103) * 1001,4,0 100104) * 1001,5,0 100105) * 1001,6,0 100106) * 1001,7,0 100107) * As you see, there is no need to hand craft e linux kernel - cdrecord works around the oddities in the Linux device addressing ;-) Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
On Thu, 28 May 2009 10:26:13 -0700 Dave Platt dpl...@radagast.org wrote: Possibly the user's kernel was configured without the legacy /proc/scsi support feature being enabled? Correct. However, when legacy /proc/scsi support is enabled in a fresh kernel the performance and returned error remains the same. -- Lose wait. Get Gentoo. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
Fog_Watch d...@exemail.com.au wrote: cdrecord using ide-scsi returns an error that I don't understand. The burner can be used with dev=ATA:0,1,0, so I can't see how it is a device problem. I am using ide-scsi for rscsi compatibility and remote burning. The error follows: # cdrecord dev=0,0,0 -dao -data dsl-1.1.iso Cdrecord-ProDVD-ProBD-Clone 2.01.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2007 JÃ?rg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.5.34 Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'SONY' Identifikation : 'CD-RW CRX230E ' Revision : 'QYS1' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Starting to write CD/DVD/BD at speed 4 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. Turning BURN-Free off cdrecord: No such device or address. Cannot send SCSI cmd via ioctl. cdrecord: No such device or address. write_g1: scsi sendcmd: fatal error CDB: 2A 00 FF FF FF 89 00 00 1F 00 cmd finished after 0.000s timeout 200s This is a Linux kernel problem, please ask the related people. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
Re: ide-scsi - write_g1: scsi sendcmd: fatal error
On Wed, 27 May 2009 16:43:44 +0200 Thomas Schmitt scdbac...@gmx.net wrote: snip Well, ide-scsi is said to be deprecated with kernel 2.6. One should at least find out a bit more before exposing oneself at LKML. Sound ominous, but it looks like that is where I am heading. What do you get from this command ? cdrecord -scanbus Full record. Does it work with programs which use the SCSI block device ? eject /dev/sr0 Yes. eject /dev/scd0 Don't have one. (I assume it is your only CD drive. Yes Else try also 1, 2, ...) What do you get from this ? cat /proc/scsi/scsi cat /proc/sys/dev/cdrom/info # pwd find . | grep scsi cat sys/dev/scsi/logging_level /proc ./sys/dev/scsi ./sys/dev/scsi/logging_level 0 Nothing untoward I would have thought. Have a nice day :) Thomas Thanks for the replies. -- Lose wait. Get Gentoo. -- To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@other.debian.org
