Preface: I recently replaced my motherboard in my main system with a Gigabyte GA-G22M-S3L due to several problems including random reboots, faulty RAM slots, and optical drive problems (DMA mode could not be enabled). My problem: After replacing my motherboard, I am now getting audio cd autoplay when there is no disc in the drive. Once the device shows it is possessed with this phantom audio cd, I cannot eject the drive and I certainly can't play the audio cd since there is not truly a disc in the drive. This happens on one or both drives and at varying amounts of time. Sometimes 15 minutes and sometimes 3+ hours. Error messages: Code: #dmesg ide: failed opcode was: unknown hdb: drive not ready for command hdb: status error: status=0x48 { DriveReady DataRequest } ide: failed opcode was: unknown hdb: drive not ready for command hdb: status error: status=0x48 { DriveReady DataRequest } ide: failed opcode was: unknown hdb: drive not ready for command hdb: status error: status=0x48 { DriveReady DataRequest } ide: failed opcode was: unknown hdb: drive not ready for command Code: #cat /var/log/messages Aug 9 13:05:08 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:08 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:08 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:08 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:08 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:08 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:08 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:08 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:08 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:08 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:10 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:10 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:10 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:10 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:10 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:10 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:10 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:10 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:10 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:10 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:12 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:12 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:12 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:12 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:12 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:12 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:12 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:12 galactus kernel: ide: failed opcode was: unknown Aug 9 13:05:12 galactus kernel: hdb: status error: status=0x48 { DriveReady DataRequest } Aug 9 13:05:12 galactus kernel: ide: failed opcode was: unknown Ejecting gives no feedback Code: #eject /dev/hdb # System Information - Will post additional info as needed GIGABYTE GA-G33M-S2L IDE optical drives of varying brand 2.6.23.17.hwf.core2.01 I've Tried Tested with Jumper settings at both Master/Slave and Cable Select Replaced the optical drives Replaced IDE cable with brand new cable Rebooted way too many times I know it is a bit lengthy, but I'd rather just give the info up front. Anyone know what's going on?
I haven't flashed the BIOS at all since I got the motherboard (its been about 24 hrs). I'm at work, but when I get home, I will check what version is available vs what version I'm running and I will get back to you. Are there any particular logs you wanted to see, AT? *edit* The first time I tried to eject the "audio cd" I got an error, but I didn't get an error when I tried to replicate this problem for the post.
On the /dev/hda (this drive currently does not have the "audio cd" problem), nothing changed in any logs when a disc (data DVD) was inserted. /dev/hdb (drive with problem) would not eject though GUI. Had to eject using button. When the disc was inserted, this was the result of tail /var/log/debug Code: Aug 9 23:38:58 galactus kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 Aug 9 23:38:58 galactus kernel: ISO 9660 Extensions: RRIP_1991A Next, I simply tried to access the drive in konqueror and got the error "Could not read /dev/hdb" After these things occured, I thought to check /var/log/messages. Here are the new errors I receivced: Code: Aug 9 23:41:06 galactus kernel: ATAPI device hdb: Aug 9 23:41:06 galactus kernel: Error: Medium error -- (Sense key=0x03) Aug 9 23:41:06 galactus kernel: "28 00 00 00 00 40 00 00 04 00 00 00 00 00 00 00 " Aug 9 23:41:06 galactus kernel: end_request: I/O error, dev hdb, sector 64 Aug 9 23:41:13 galactus kernel: hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } Aug 9 23:41:13 galactus kernel: hdb: media error (bad sector): error=0x30 { LastFailedSense=0x03 } Aug 9 23:41:13 galactus kernel: ide: failed opcode was: unknown Aug 9 23:41:13 galactus kernel: ATAPI device hdb: Aug 9 23:41:13 galactus kernel: Error: Medium error -- (Sense key=0x03) Aug 9 23:41:13 galactus kernel: "28 00 00 00 04 e0 00 00 04 00 00 00 00 00 00 00 " Aug 9 23:41:13 galactus kernel: end_request: I/O error, dev hdb, sector 1248 Aug 9 23:41:19 galactus kernel: hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } Aug 9 23:41:19 galactus kernel: hdb: media error (bad sector): error=0x30 { LastFailedSense=0x03 } Aug 9 23:41:19 galactus kernel: ide: failed opcode was: unknown Aug 9 23:41:19 galactus kernel: ATAPI device hdb: Aug 9 23:41:19 galactus kernel: Error: Medium error -- (Sense key=0x03) Aug 9 23:41:19 galactus kernel: "28 00 00 00 04 00 00 00 04 00 00 00 00 00 00 00 " Aug 9 23:41:19 galactus kernel: end_request: I/O error, dev hdb, sector 1024 Aug 9 23:41:19 galactus kernel: UDF-fs: No partition found (1) Aug 9 23:42:02 galactus kernel: hdb: packet command error: status=0x51 { DriveReady SeekComplete Error } Aug 9 23:42:02 galactus kernel: hdb: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 } Aug 9 23:42:02 galactus kernel: ide: failed opcode was: unknown Aug 9 23:42:02 galactus kernel: ATAPI device hdb: Aug 9 23:42:02 galactus kernel: Error: Illegal request -- (Sense key=0x05) Aug 9 23:42:02 galactus kernel: "42 02 40 01 00 00 00 00 10 00 00 00 00 00 00 00 " After this, it is back to the old error: Code: Aug 9 23:45:36 galactus kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } Aug 9 23:45:36 galactus kernel: ide: failed opcode was: unknown And now I can't open the drive using the button. I will get a "Cannot open tray" error. For some reason, I must go the command line and "eject /dev/hdb" *edit* After ejecting the disc in /dev/hdb the "audio cd" goes away and so do the error messages. I now must await the error to pop up again. No changes to /var/debug or /var/messages **edit #2** I looked up updates for my BIOS and I dont believe it will be necessary to update my BIOS to the latest. The fixes are for newer CPU recognition.
Have you tried putting each drive on its own IDE channel? Both would be jumpered to master in that situation, and each should be at the end of the cable.
No, I have not.... this motherboard only has one IDE channel. I could try only having the master on the chain. The problem hasn't occured since I ejected the drive through the CLI last night (though I have confidence if I rebooted it would come back). The thing is, if I keep only one on IDE at a time I wont know for sure if it is "cured" for hours or possibly days. And sometimes both drives do it, other times only one drive. I dont know if it makes a difference to this possible experiment, this problem has happended on two different sets of drives and two different IDE cables. *edit* I just got home from work and I removed /dev/hdb from IDE and power. I will report back if/when I get error messages.
Balls, should have noticed that, sorry. My mobo only has one IDE channel too; one of my optical drives is IDE, the other's SATA. OK, I'm interested to see how this works out.
No phantom audio cds yet, but this morning I checked the logs to find the following under dmesg Code: hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. There is nothing under /var/log/messeges or /var/log debug though. *edit* Same errors occur under /var/log/syslog but do not provide any additional errors/information
I'm still not getting the audio cd problem, but there are still errors. New errors: Code: #tail /var/log/messages Aug 12 07:29:04 galactus kernel: bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0 Aug 12 07:57:07 galactus -- MARK -- Aug 12 08:04:12 galactus kernel: cdrom_pc_intr, write: dev hda: type=d, flags=1088 Aug 12 08:04:12 galactus kernel: Aug 12 08:04:12 galactus kernel: sector 0, nr/cnr 0/0 Aug 12 08:04:12 galactus kernel: bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0 Aug 12 08:17:07 galactus -- MARK -- Aug 12 08:37:07 galactus -- MARK -- Aug 12 08:43:52 galactus kernel: hda: packet command error: status=0xd0 { Busy } Aug 12 08:43:52 galactus kernel: ide: failed opcode was: unknown Code: #tail /var/log/syslog Aug 12 08:04:12 galactus kernel: cdrom_pc_intr, write: dev hda: type=d, flags=1088 Aug 12 08:04:12 galactus kernel: Aug 12 08:04:12 galactus kernel: sector 0, nr/cnr 0/0 Aug 12 08:04:12 galactus kernel: bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0 Aug 12 08:04:12 galactus kernel: hda: cdrom_pc_intr: The drive appears confused (ireason = 0xd0). Trying to recover by ending request. Aug 12 08:13:10 galactus kernel: hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. Aug 12 08:17:01 galactus /USR/SBIN/CRON[19562]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 12 08:28:48 galactus kernel: hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. Aug 12 08:43:52 galactus kernel: hda: packet command error: status=0xd0 { Busy } Aug 12 08:43:52 galactus kernel: ide: failed opcode was: unknown Code: #dmesg hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. cdrom_pc_intr, write: dev hda: type=d, flags=1088 sector 0, nr/cnr 0/0 bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0 hda: cdrom_pc_intr: The drive appears confused (ireason = 0xd0). Trying to recover by ending request. cdrom_pc_intr, write: dev hda: type=d, flags=1088 sector 0, nr/cnr 0/0 bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0 hda: cdrom_pc_intr: The drive appears confused (ireason = 0xd0). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. hda: packet command error: status=0xd0 { Busy } ide: failed opcode was: unknown Hoping some of this new info helps. I'm also getting to the point of considering reinstalling the OS, but if this is a hardware problem and not software, then I'm stuck with the same problem, but having to reconfigure my system. Any thoughts on that aspect of my issue?
