[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

xmcd sometimes fouls up the cdrom drive



Hi,
	I have a NEC 4 disk cdrom drive.  Sometimes after using xmcd, the
drive seems to get all balled up.  It seems to get confused about whether
there are any CD's in any of the 4 slots and just keeps cycling through them
looking.  When it gets in this state, I can't play any more CD's

	If I quit xmcd, remove the audio cd and replace with a iso9660 cd, I
can't mount the CD.  I get the "bad super-block, device busy or wrong fs
type" message.  If I switch to single user mode the error message is more
verbose when trying to mount the cdrom drive:

------------------- error from single user mode ----------------
# mount /cd
hdb : tray open or drive not ready
hdb: code: 0x70  key: 0x02  asc: 0x06  ascq: 0x00
hdb: packet command error: status=0x51
hdb: packet command error: error=0x54
hdb: code: 0x70  key: 0x05  asc: 0x24  ascq: 0x00
hdb : tray open or drive not ready
hdb: code: 0x70  key: 0x02  asc: 0x06  ascq: 0x00
hdb : tray open or drive not ready
hdb: code: 0x70  key: 0x02  asc: 0x06  ascq: 0x00
hdb : tray open or drive not ready
hdb: code: 0x70  key: 0x02  asc: 0x06  ascq: 0x00
hdb : tray open
end_request: I/O error, dev 03:40, sector 64
isofs_read_super: bread failed, dev 03:40 iso_blknum 16 block 32
hdb: code: 0x70  key: 0x02  asc: 0x06  ascq: 0x00
mount: wrong fs type, bad option, bad superblock on /dev/hdb,
       or too many mounted file systems
hdb : tray open or drive not ready
hdb: code: 0x70  key: 0x02  asc: 0x06  ascq: 0x00
hdb: packet command error: status=0x51
hdb: packet command error: error=0x54
hdb: code: 0x70  key: 0x05  asc: 0x24  ascq: 0x00
hdb : tray open or drive not ready
hdb: code: 0x70  key: 0x02  asc: 0x06  ascq: 0x00
-------------------- end single user mode error message--------------

	I'm wondering if anyone knows what gives, and better yet, how I can
reset the device to regain control.  I've tried "rm /dev/hdb" followed by
"mknod -m 771 /dev/hdb b 3 64" but that does't help.  The only solution I've
found thus far is to reboot ( :¬( )

	Any ideas welcome.

	Gerald


Reply to: