argh! 'cdrecord --scanbus' hangs - "The drive appears confused"???

Sy Beamont sbeam at attbi.com
Sun Aug 15 15:32:29 UTC 2004


After upgrading to FC2 I tried k3b and then xcdroast which would hang 
when scanning for SCSI devices - finally narrowed it down to and 
scanning of the bus - 

$ cdrecord --scanbus
Cdrecord-Clone 2.01a34-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 
...snip..
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
<... nothing happens. ever....>

This proc shows up in ps with STAT "D" and 'kill -9' has no effect... 

in dmesg I have this:
================
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0x00
hdc: DMA disabled
hdc: drive not ready for command
hdc: ATAPI reset complete
=================

and then in /var/log/messages every minute I get one of these:
================
Aug 15 11:16:28 darkrum kernel: ide-cd: cmd 0x1e timed out
Aug 15 11:16:28 darkrum kernel: hdc: lost interrupt
Aug 15 11:16:28 darkrum kernel: cdrom_pc_intr, write: dev hdc: flags = 
REQ_STARTED REQ_PC REQ_FAILED
Aug 15 11:16:28 darkrum kernel: sector 0, nr/cnr 0/0
Aug 15 11:16:28 darkrum kernel: bio 00000000, biotail 00000000, buffer 
00000000, data 00000000, len 0
Aug 15 11:16:28 darkrum kernel: cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00
Aug 15 11:16:28 darkrum kernel: hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x02)
=================

This CR-W worked fine under FC1, I used it to burn the FC2 cd's. Anyone 
else have this problem? Please help, this sucks!

-Sy





More information about the users mailing list