search for: dma_intr

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=...

...it does worry me. What should I do? Other than take a backup.. :-) hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy } ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11242764, high=0, low=11242764, sector=11242760 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11242760 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda:...

...er what I do (Y or N) the results are the same. The problem will not go away. Does anyone have any ideas as to a fix, or to what the problem is? When I do a fsck and it marks the fs as clean I reboot and login the system. But I still cannot load xwindows. below is some output from dmesg: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=81423, sector=81360 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=10223775, sector=10223712 end_request: I/O error, dev 03:...

i too am an idiot.. and request help here's the sccop i originally formatted the drive with 3 partitions and installed rh8 /boot / swap everything worked. my plan was to have this drive only be a data drive so i inatlled rh8 on another drive and mounted this one on /share so /share looked like /share /bin /sbin /mp3 /usr /etc /dev and so on so i deleted all the

...own script). And a "badblocks" command on some of the related hard drive reports that failed sectors found, while others reports no, false-positive. Any one can give me suggestions or hints? Thanks a lot. ...... Host: arc242 arc242: Apr 29 13:51:32 arc242 kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc242: Apr 29 13:51:32 arc242 kernel: hdb: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=38613129, sector=38613064 arc242: Apr 29 13:51:36 arc242 kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } arc242: Apr 29 1...

...Filesystem still has errors ********** /dev/hdc1: 939701/36634624 files (0.3% non-contiguous), 8812231/73242335 blocks [root at server /]# ================================================= Errors in messages: ================================================= Jul 20 04:09:13 server kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jul 20 04:09:13 server kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=526647391, high=31, low=6553695, sector=526647391 Jul 20 04:09:13 server kernel: end_request: I/O error, dev hdc, sector 526647391 Jul 20 04:09:13 server kerne...

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 &...

...me serious problems diagnosing a hardware issue in my linux system. The following error occurs intermittently. I have replaced hard drives and it is still occurring. I'm trying to determine if it's a device conflict, a problem with the motherboard or something else. Can anyone help? hda: dma_intr: status=0x51 {DriveReady SeekComplete Error} hda: dma_intr: 0x40 {Uncorrectable Error}, LBA sect = 32405, sector=32328 end_request: I/O error, dev 03:01 (hda) sector 32405 (this repeats for a whole lot of sectors...) The above error terminates with invalidate: busy buffer Then a kernel pani...

Hello LINUX GURUS, I am fairly new to LINUX OS, so pardon my ignorance about LINUX OS. I have installed LINUX 7.2 on IBM netfinity 4000R server. OS works fine for few days and start giving me this error message all of a sudden: "kernel: hda: dma_intr: status=0x51 { Driveready SeekComplete Error }" "kernel: hda: dma_intr: status=0x40 { UncorrectableError }, LBAsect=4944861, sector=4736016" "kernel: end_request: I/O error. dev 03:02 (hda), sector 4736016" SYSTEM details: Red hat 7.2(2.4.7-10) BIOS DATE: 5/17/00 Drive: /d...

Hi, I have an ext3 file system question for a while: How to obtain failed file (inode) from LBA section reported by Linux kernel? The following lines are a simple example: ... FCbox1: Nov 1 04:08:59 FCbox1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } FCbox1: Nov 1 04:08:59 FCbox1 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=165843413, high=9, low=14848469, sector=129761360 ... I'd like to know the tools|commands(&subcommands) used to do the translation below, any help...

...localhost.localdomain DNS domain: localdomain NIS domain: (none) The following warning/error was logged by the smartd 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...

...able to recover with tomsrt, e2fsck etc. Sometimes it took a little while, but I can't even get started on this one. I have been looking at lde but don't think I know enough of what I'm doing to make that work. During the booting of the machine it throws the following errors: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=90895772, high=5, low=7009692, sector=0 end_request: I/O error, dev 03:03 (hda), sector 0 ... repeats 10 time kjournald starting. Commit interval 5 seconds I have commented the particular par...

...tories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts give the following error: #mkdir: cannot create directory `xxxxx': Input/output error The contents of /var/log/messages shows this: Aug 5 10:48:57 inet05 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Aug 5 10:48:57 inet05 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=43072608, sector=43072608 Aug 5 10:48:57 inet05 kernel: ide: failed opcode was: unknown Aug 5 10:48:57 inet05 kernel: end_request: I/O error, dev hda, sector...

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: I/O error, dev 03:41 (hdb), sector 163360 When I rebooted, the system threw me...

...0), i received this error 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

Would the following be symptoms of hardware problems or just a corrupt fs? Will fsck tonight when a new power supply is going into the machine. Kernel: 2.4.17 Drive: Maxtor D740X-6L 80GB connected via HPT366 Feb 25 21:26:33 viper kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 25 21:26:33 viper kernel: hde: dma_intr: error=0x40 { UncorrectableError }, LBAsect=96469063, sector=96469000 Feb 25 21:26:33 viper kernel: end_request: I/O error, dev 21:01 (hde), sector 96469000 Feb 25 21:26:33 viper kernel: EXT3-fs error (dev...

...logwatch. I have a Maxtor (200gig) as hda, a cdrom as hdc and another hard disk that is used for storage as hdd. All plain IDE (not sata) --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present end_request: I/O error, dev hda, sector...: 216 Time(s) hda: dma_intr: error=0x40 { Uncorrect...: 216 Time(s) hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }...: 216 Time(s) -- Comments? ------------------------------------------------------------ Erick Perez ------------------------------------------------------------

I can not start my laptop anymore, due to what looks like a physical HD failure. During boot I get: hda: dma_intr: error=0x40 { Uncorrectable Error }, LBAsect=260112, sector 51144 and then JBD: Failed to read block at offset 5864 JBD: recovery failed EXT3-fs: error loading journal then the laptop is frozen. While I understand this drive will need a prompt replacement, I am trying to recover at least the d...

...the IDE channel on the 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. -...

...g failed disks(partitions), where is the exact failed sector(s) on the hard disk, and why badblocks reports OK to the reported disk failure. Let me explained the above with the following several example. scenario #1, a PATA hard disk failed.. Host: host1 ..... Jun 21 16:55:09 host1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jun 21 16:55:09 host1 kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=234304234, high=13, low=16200426, sector=196487120 Jun 21 16:55:09 host1 kernel: end_request: I/O error, dev 03:0b (hda), sector 196487120 ..... The case #1, show...