search for: drivestatuserror

...t this error in dom0''s dmesg: TA: abnormal status 0xD0 on port 0xD080EC87 ATA: abnormal status 0xD0 on port 0xD080EC87 ATA: abnormal status 0xD0 on port 0xD080EC87 ata1: command 0x35 timeout, stat 0x51 host_stat 0x61 ata1: status=0x51 { DriveReady SeekComplete Error } ata1: error=0x04 { DriveStatusError } SCSI error : <0 0 0 0> return code = 0x8000002 sda: Current: sense key=0xb ASC=0x0 ASCQ=0x0 end_request: I/O error, dev sda, sector 449410141 also in dom0''s /var/log/messages, I have this: Sep 19 00:15:59 x8 kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Sep 19 00:...

...r message Nov 17 02:55:07 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_find_entry: bad entry in directory #1111941: inode out of bounds - offset=36, inode=537868397, rec_len=12, name_len=4 I've also had these messages too Nov 3 20:25:42 jaguar kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 3 20:34:07 jaguar kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } I'm just guessing, but i presume it's a sign of a bad hard drive? Thanks, Matt

I am getting occasional seek error on my boot drive. The messages are as follows: pshda: dma_intr: status = 0x51 { Drive ReadySeekComplete Error } hda: dma_intr: error= 0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown Everything seems to be working fine but these errors do have me concerned. The last time they occurred I was created a fairly large cpio backup file in the '/tmp' directory. The drive has been checked via fsck, and any errors found were reported...

...martd daemon: Device: /dev/hda, 993 Currently unreadable (pending) sectors For details see host's SYSLOG (default: /var/log/messages). Nov 23 18:20:22 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 23 18:20:22 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 23 18:20:22 localhost kernel: ide: failed opcode was: unknown Nov 23 18:20:22 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 23 18:20:22 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 23 18:20:22 localhost kernel: ide: fa...

...de (from 2.4.18-19.7 to 2.4.18-27.7). The kernel itself hasn't been modified, and is the stock RH release. The error messages in question are: Mar 19 23:21:26 spike kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } Mar 19 23:21:26 spike kernel: hda: drive_cmd: error=0x04 { DriveStatusError } I've tried finding a suitable resource on the web detailing what the messages mean, can anyone provide a link to a useful resource? Thanks in advance, Matt

...motherboard. After botting the machine up everything works fine again: the /hdc1 and /hdc2 partitions were cleaned and are accessible. However the I still notice the following errors in the /var/log/messages (occasionaly): ----------------- Oct 26 12:19:38 lynx kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 26 12:19:38 lynx kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } ----------------- I am trying to determine where the problem is: - connection cable, - motherboard IDE port, - hard drive, - ext3 filesystem in kernel 2.4.18-27.7.x. - sth else. I'd appreciate...

...and I'm wondering if they're due to bad/old drivers, something with EXT3 and CF latency, or something else entirely. These are the errors: hda: write_intr error1: nr_sectors=1, stat=0x51 hda: write_intr: status=0x51 { DriveReady SeekComplete Error } hda: write_intr: error=0x04 { DriveStatusError } end_request: I/O error, dev 03:01 (hda), sector 528431 Let me know if you have any idea what I could do to fix these issues. Ideally it wouldn't involve a recompile of the kernel! Thanks in advance... Some system/configuration info: kernel 2.4.9-ac10 PCMCIA CS 3.1...

..., port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 and virtual mashines kernel reports: hda: set_multmode: status=0x41 { DriveReady Error } hda: set_multmode: error=0x04 { DriveStatusError } ide: failed opcode was: 0xef hda: cache flushes supported hda: hda1 hda2 and here is hang. - -- Pozdrawiam Dariusz Malec http://www.kos.wsiz.rzeszow.pl http://www.kos.wsiz.rzeszow.pl/~dmalec GG:1720216 JID:dmalec@jabber.kos.wsiz.rzeszow.pl "Podwładny powinien przed obliczem przełożonego m...

My Centos 5.2 box shuts itself down during a long tar -x. There is plenty of disk available. This is new; it worked in the past. Any suggestions? Thanks, Mike.

I''ve been following unstable day to day with mercurial but I''m still having a 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

Can anyone point me in the right direction for correcting errors on an HD when using LVM? I've tried e2fsck and indicates bad block. I've tried with -b 8193, 16384, and 32768 and no good. I've found some info about reiserfsck on google, but this utility doesn't seem to be included in Centos4.3. I did find it on my old FC1 box. I am thinking now I really should have went with

...ast Ethernet driver 0.9.27 >hda: max request size: 512KiB >hda: 6144000 sectors (3145 MB) w/256KiB Cache, CHS=6095/255/63, (U)DMA >hda: lost interrupt >hda: lost interrupt >hda: lost interrupt >hda: set_multmode: status=0x41 { DriveReady Error } >hda: set_multmode: error=0x04 { DriveStatusError} >ide: failed opceode was: 0xef >hda: lost interrupt >hda: lost interrupt >hda: cache flushes supported > hda:<4>hda: dma_timer_expiry: dma status == 0x24 >hda: DMA interript recovery >hda: lost interrupt > hda1 hda2 hda3 >Done. >Begin: Mounting root file system....

...problem. This has been going on quite a while. I've posted before with no success on getting this fixed. I was getting these errors. Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } And now for the amazing smartctl -a command. The output actually had a link that advised and directed me to a link to upgrade my firmware, which looks to have fixed it. Simply amazing. smartctl -a /dev/hda: smartctl version 5.33 [i686-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen...

Hi there, I''m using the Suse Enterprise 10 RC2 along with Xen 3.0.2 on X86-64 and I''m experiencing a problem with the network. I boot into the Xen kernel and everything works just fine. I can browse the net etc. However after a while the network stops responding completely. I am not sure what causes this to happen or what triggers it. After a few hours, the network just stops

Hi, Updated to current bk today, and my machine stopped booting ... I''ve tracked it down to the apic changes from end of last week. cset 1.1307 boots fine, 1.1308 doesn''t. Diff of the boot messages is below. Full logs are also attached. Gerd --- log-1.1307 2005-04-21 14:40:57.372885027 +0200 +++ log-1.1308 2005-04-21 14:38:52.236553392 +0200 @@ -7,7 +7,7 @@