similar to: hda dma seek errors

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 running RH 7.3 with kernel 2.4.18-27.7.x. Recently I have added a new 60GB Quantum IDE hard drive to the server. I have set it up as a MASTER on a separate IDE channel. Two partitions on the /dev/hdc are /dev/hdc1, /dev/hdc2 - both using ext3. For more detailed HDD parameters, this is 'hdparm -i /dev/hdc': ----------------- /dev/hdc: Model=IC35L060AVV207-0, FwRev=V22OA66A,

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)

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

I finally fixed my drive error 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

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

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

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

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,

Hello everyone, I''m hoping to find an answer to my problem here. Currently I''m installing xen 2.0.7 on 30 dual opteron machines with 4GB memory. The machines have Tyan K8SR as motherboard with Silicon Image 3114 chip sata controler and 2 x 300 GB Western Digital SATA drives. Each xen server has 5 domUs, where some of them have high traffic and thus require high disk usage.

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

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

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,

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

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

Hi I realise this isn't strictly ext3 related, but I'm trying to find the meanings to some error messages that have started appearing in /var/log/messages on a RH73 system after a recent kernel upgrade (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:

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