Re: CD burning problems with SLES9 SP3

In article <1162204360.862826.202590@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Bernd Nies <bnies@xxxxxxxxxx> wrote:
Hello,

Are there other methods on SLES9 SP3 than cdrecord to burn CDs?

We have problems with cdrecord due to the endless private war between
Schilling and Suse and because the driver for the cd burner of the HP
Proliant ML350 server is in pre-alpha state:

If you like to see this SuSE initiated war to end, send as many
complaints to Suse as possible, I am helpless against the attacks against
usability that are a result of missing knowledge at Suse's side...

You always have the option to download a non-bastardized original
from
ftp://ftp.berlios.de/pub/cdrecord/alpha/

compile it by your own and install it suid-root. Note that in contrary what
many uninformed people from Linux distributors claim, cdrecord needs to be
installed suid-root on Linux in order to work correctly.


==CUT==
/usr/bin/cdrecord dev=ATAPI:0,0,0 speed=8 -eject /tmp/tgd_export.iso
/usr/bin/cdrecord: No write mode specified.
/usr/bin/cdrecord: Asuming -tao mode.
/usr/bin/cdrecord: Future versions of cdrecord may have different
drive dependent defaults.
/usr/bin/cdrecord: Continuing in 5 seconds...
scsidev: 'ATAPI:0,0,0'
devname: 'ATAPI'
scsibus: 0 target: 0 lun: 0
Use of ATA is preferred over ATAPI.
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
/usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no
error
CDB: 2A 00 00 00 00 00 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 0E 00 00 00 00 09 00 00 00 00 00 00
00 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x09 Qual 0x00 (track following error) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 9.209s timeout 40s
/usr/bin/cdrecord: A write error occured.
/usr/bin/cdrecord: Please properly read the error message above.
/usr/bin/cdrecord: Input/output error. close track/session: scsi

You are having the following problems:

- You did not read the documentation and thus used dev=ATA: instead of
dev=ATAPI:

- You have either a defective drive or defective media.
If you did read the messages, you should know about this....



--
EMail:joerg@xxxxxxxxxxxxxxxxxxxxxxxxxxx (home) Jörg Schilling D-13353 Berlin
js@xxxxxxxxxxxxxxx (uni)
schilling@xxxxxxxxxxxxxxxxxxx (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
.

Quantcast