Re: Error executing backup: Error (65280) executing cdrecord command to get properties.

[Kenneth Pronovici <kenneth.pronovici@cedar-solutions.com>]

This is what I see on my development system (Debian etch, kernel
2.6.18-3-k7). when I run the various scanbus commands:

# cdrecord -scanbus dev=ATA
scsibus1:
      1,0,0   100) 'LITE-ON ' 'DVDRW SOHW-1673S' 'JS02' Removable CD-ROM
      1,1,0   101) *
      1,2,0   102) *
      1,3,0   103) *
      1,4,0   104) *
      1,5,0   105) *
      1,6,0   106) *
      1,7,0   107) *

# cdrecord -scanbus dev=ATAPI
scsibus0:
      0,0,0     0) 'LITE-ON ' 'DVDRW SOHW-1673S' 'JS02' Removable CD-ROM
      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) *

Now, previously, I would have told you that this means I should use
one of these SCSI ids in Cedar Backup configuration:

      <target_scsi_id>ATA:1,0,0</target_scsi_id>
      <target_scsi_id>ATAPI:0,0,0</target_scsi_id>

However, wodim doesn't support method "ATAPI", and says it's deprecated.

      # cdrecord -prcap dev=ATAPI:0,0,0
      Warning, the ATAPI: method is considered deprecated on modern kernels!
      Mapping device specification to dev=0,0,0 now.
      To force the old ATAPI: method, replace ATAPI: with OLDATAPI:
      cdrecord: Invalid argument.
      Cannot open SCSI driver!
      For possible targets try 'wodim -scanbus'.
      For possible transport specifiers try 'wodim dev=help'.
      For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
      the wodim documentation.

I've checked, and I can successfully write a disk with either
"dev=ATA:1,0,0" or "dev=OLDATAPI:0,0,0" or "dev=/dev/cdrom" on my
development system.

However, wodim's behavior presents a bit of a problem, because Cedar
Backup 2.8.2 doesn't allow the "OLDATAPI" SCSI method.  So, first, I'm
going to loosen this restriction and allow *any* SCSI method --
basically anything followed by a ":" before the (scsibus,target,lun).
This way, Cedar Backup doesn't need to change if the tools suddenly
start supporting a different method in the future.

Second, I'm going to make the <target_scsi_id> parameter completely
optional.  If you don't configure a <target_scsi_id>, then the
<target_device> will be used when talking to cdrecord.  I've
introduced a new internal abstraction called hardwareId on the
CdWriter class, which will represent the value to use when talking to
cdrecord.

I've made the code changes and reworked the related regression tests,
and this all seems to work fine.  I just need to update the user
manual and other documentation, and then I'll put another release out
there (2.9.0) for you to try.  Hopefully that will be later tonite,
but it might be tomorrow evening if I run out of time.

KEN

--
Kenneth J. Pronovici <pronovic@ieee.org>
http://www.cedar-solutions.com


-- 
To unsubscribe, send mail to cedar-backup-users-unsubscribe@cedar-solutions.com.