search for: datarequest

...es with identical hardware, both running Red Hat 7.3's stock SMP kernel (required due to third party software). Both have come down with the same symptoms after having run fine for a number of months. The initial errors were these: kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=54666719, high=3, low=4335071, sector=61720 kernel: end_request: I/O error, dev 03:09 (hda), sector 61720 kernel: journal_bmap_Rsmp_41b34d97: journal block not found at offset 7180 on ide0(3,9) kernel: Aborting journal on de...

...ma1 *mdma2 AdvancedPM=no Drive Supports : ATA/ATAPI-4 T13 1153D revision 13 : ATA-4 Now the logs about my problems, the fresh one from today ;) Jan 23 10:02:22 inspiron kernel: ide-floppy driver 0.97.sv Jan 23 10:02:23 inspiron kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } Jan 23 10:02:23 inspiron kernel: hda: drive not ready for command Jan 23 10:02:23 inspiron kernel: EXT3-fs error (device ide0(3,6)): ext3_readdir: bad entry in directory #892807: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 Jan 23 10:02:33 inspiron kernel: hda: tim...

...problem with my HVM testing. I using the i686 Centos + Bluecurve isntaller and I get the following error in the guest during disk formatting: <4>hda: dma_timer_expiry: dma status == 0x21 <4>hda: DMA timeout error <4>hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } <4> <4>ide: failed opcode was: unknown Not sure if there is a solution to this at present, or if some patches are still coming down the road. -Mike _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-d...

...veledged user can abuse the syslog facility in an interesting way. The following example is a good one that can put misleading information in the logs. ------------------------------- #include <syslog.h> void main(void){ const char *mesg1 = "hda: read_intr: status=0x59 { SeekComplete DataRequest Error } { UncorrectableError }, CHS=157/2/9, sector=2826\0"; const char *mesg2 ="end_request: I/O error, dev 03:00, sector 2826\0"; const char *mesg3 = "EXT2-fs: group descriptors corrupted !\0"; openlog("kernel", LOG_CONS, LOG_KERN); syslog(LOG_ERR, mesg1);...

Odd thing: I just installed and tried to run lshw on a Dell R415 running 5.8. It goes through the subsystems it's scanning, hits IDE, and that's it - it just sits there. I've waited minutes. Anyone else seen this? mark

...ears confused (ireason = 0x01). Trying to recover by ending request. Jan 24 05:20:06 weidenwinde kernel: hdg: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request. Jan 24 05:20:06 weidenwinde kernel: hdg: status error: status=0x58 { DriveReady SeekComplete DataRequest } Jan 24 05:20:06 weidenwinde kernel: ide: failed opcode was: unknown Jan 24 05:20:06 weidenwinde kernel: hdg: drive not ready for command Jan 24 05:20:06 weidenwinde kernel: hdg: status timeout: status=0xd0 { Busy } Jan 24 05:20:06 weidenwinde kernel: ide: failed opcode was: unknown Jan 24 05:20:0...

All, Trying to figure out how to deal with, I assume, a dying disk that's unfortunately on / (ext3). Getting errors similar to: Dec 31 20:44:30 mybox kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 31 20:44:30 mybox kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=163423, high=0, low=163423, sector=163360 Dec 31 20:44:30 mybox kernel: end_request: