Ominous looking syslog messages
Logcheck picked up the following:
Feb 17 12:25:28 d_baron kernel: hdb: status error: status=0x00 { }
Feb 17 12:25:28 d_baron kernel: hdb: status error: error=0x00
Feb 17 12:25:28 d_baron kernel: hdb: status error: status=0x00 { }
Feb 17 12:25:28 d_baron kernel: hdb: status error: error=0x00
Feb 17 12:25:28 d_baron kernel: hdb: status error: status=0x00 { }
Feb 17 12:25:28 d_baron kernel: hdb: status error: error=0x00
Feb 17 12:25:28 d_baron kernel: hdb: status error: status=0x00 { }
Feb 17 12:25:28 d_baron kernel: hdb: status error: error=0x00
Feb 17 12:25:28 d_baron kernel: hdb: DMA disabled
Feb 17 12:25:28 d_baron kernel: hdb: ATAPI reset complete
Feb 17 12:25:28 d_baron kernel: hdb: status error: status=0x00 { }
Feb 17 12:25:28 d_baron kernel: hdb: status error: error=0x00
( the last two repeat three more times)
Feb 17 12:25:28 d_baron kernel: hdb: ATAPI reset complete
Feb 17 12:25:28 d_baron kernel: hdb: status error: status=0x00 { }
Feb 17 12:25:28 d_baron kernel: hdb: status error: error=0x00
(the last repeat three more times)
Feb 17 12:25:28 d_baron kernel: hdb: ATAPI reset complete
(this pattern recurs several more times)
Feb 17 12:25:29 d_baron kernel: hdb: status error: status=0x00 { }
Feb 17 12:25:29 d_baron kernel: hdb: status error: error=0x00
Feb 17 12:25:34 d_baron kernel: hda: status timeout: status=0x80 { Busy }
Feb 17 12:25:34 d_baron kernel:
Feb 17 12:25:34 d_baron kernel: hda: DMA disabled
Feb 17 12:25:34 d_baron kernel: hda: drive not ready for command
Feb 17 12:25:34 d_baron kernel: ide0: reset: success
There was nothing immediately before these indicating what initiated whatever
brought this on.
/dev/hda's DMA was indeed set off. hparm -d1 put it on again.
hdb is a CD drive. No disk in it
hda has two vfat partitions on it for Windows
Linux in on hdc (which also has one vfat). There is a second CD on hdd
Disks are of recent vintage.
Reply to: