similar to: Quantum IDE HDD DMA issue.

Hi, Sorry if this is an old and fixed issue but I can't really seem to find a definitive explanation/fix to this in the mail lists. Ever since I upgraded to FC2 my server randomly decides that it can no longer access the disk and "aborts" the ext3 journal leaving it read-only as expected. I've seen the same errors on other mail list, explained away as disk or disk cable

Hello all. I'm using RedHat 7.2 now and haven't have any problems until today. I can still boot into the system at this time, but cannot load X at all. I'm getting the following error message when I try to run fsck. /contains a file system with errors, check forced. Pass 1: Checking inodes, blocks and sizes Error reading block 1277964 (Attempt to read block from filesystem resulted

Hi All, I m a novice developer of Linux applications. Recently I faced a file system corruption. (I guess) I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions. One fine day, it just started sending kernel messages on the serial console. The message was like this. EXT3-fs error (device ide0(3,2)):

I had a busy mailserver fail on me the other day. Below is what was printed in dmesg. We first suspected a hardware failure (raid controller or something else), so we moved the drives to another (identical hardware) machine and ran fsck. Fsck complained ("short read while reading inode") and asked if I wanted to ignore and rewrite (which I did). After booting up again, the problem came

Hi, I get the below from dmesg. The server seems to run fine, but 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

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

Hi, I run hundreds of Redhat 8.0 boxes and Fedora Core 1 boxes, both Operation systems boxes give me some trouble reporting disk errors like the following (collected from /var/log/messages of each linux boxes by my 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

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

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 },

Hi, I'm having some 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

I've got an approximately 100GB ext3 FS which we recently sized down from 300GB using e2fsadm (with the disc offline obviously). I noticed the following in dmesg the other day: EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14827639 EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc: bad inode number: 14041793 EXT3-fs error (device lvm(58,8)): ext3_get_inode_loc:

Hi, yesterday my linux machine gave me some smartd errors so i checked the disk in another machine and it had defective sectors, I installed a new hard disk on the original machine. Today this is being reported in 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

Help! I am running FC1, with a maxtor 160GB HD installed. Drive is only about a month old. I had just finished moving data from an older HD that was making some funny sounds and throwing some random errors. All was well. Last night we lost power for several hours and 1 machine's UPS/shutdown system didn't power down the workstation. The other 7 in our office did fine. The power

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,

I was creating some directories (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

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:

Hi upon booting this morning (Redhat 8.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

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

Hi, with being exposed to more and more failed hard disks reports, I've accumulated several questions of the logged messages in /var/log/messages file: like how to identifying 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

Hello I seem to be getting some messages via email and in var/log/messages as well, i think its a hard drive gone bad but was wondering if anyone has seen something similar to this or would have some ideas if its fixable or not, here are the messages This email was generated by the smartd daemon running on: host name: localhost.localdomain DNS domain: localdomain NIS domain: (none)