CD/DVD writer no longer works

Paul Schmehl pauls at utdallas.edu
Thu Dec 6 13:34:03 PST 2007


--On Thursday, December 06, 2007 19:14:51 +0100 Wojciech Puchar 
<wojtek at wojtek.tensor.gdynia.pl> wrote:

>> /home/pauls/Downloads/FreeBSD/6.2-RELEASE-amd64-disc1.iso fixate
>> burncd: ioctl(CDRIOCWRITESPEED): Input/output error
>> root at utd59514# mount /dev/acd
>> acd0  acd1
>> root at utd59514# mount /dev/acd1 /mnt/cdrom/
>> mount: /dev/acd1: Input/output error
>
> mount_cd9660 - unless you use FFS on CD/DVD.

Yeah, I knew that.  Just mistyped it.  The results are the same in either 
case - input/output error.

>> CDB:  00 00 00 00 00 00
>> status: 0x2 (CHECK CONDITION)
>> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 00 00 00 00
>> 00  00 00 00 00 00 00 00 00 00 00 00
>> Sense Key: 0x2 Not Ready, Segment 0
>> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
>> Sense flags: Blk 0 (not valid)
>> cmd finished after 0.000s timeout 40s
>> cdrecord: No disk / Wrong disk!
>>
>
> looks like your device is broken - reports no disk

Does this provide any additional information?
root at utd59514# atacontrol cap acd1

Protocol              ATA/ATAPI revision 5
device model          TSSTcorpCD-RW TS-H292B
serial number
firmware revision     DE03
cylinders             0
heads                 0
sectors/track         0
lba supported
lba48 not supported
dma supported
overlap not supported

Feature                      Support  Enable    Value           Vendor
write cache                    no       no
read ahead                     no       no
Tagged Command Queuing (TCQ)   no       no      0/0x00
SMART                          no       no
microcode download             no       no
security                       no       no
power management               yes      yes
advanced power management      no       no      0/0x00
automatic acoustic management  no       no      0/0x00  0/0x00

The result of this command doesn't change if there's a known good CD in the 
drive.  And are you saying that the *device* appears to be bad?  Or the 
*driver* appears to be bad?  Is there a way to confirm this (utility?  test 
process?)

-- 
Paul Schmehl (pauls at utdallas.edu)
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/



More information about the freebsd-questions mailing list