similar to: Major problems with 2.0.7 and SATA drives

One of my CentOS boxes has started giving me errors. The box is CentOS-4.4 (i386) fully updated. It has a pair of SATA drives in a software raid 1 configuration. The errors I see are: ata1: command 0xca timeout, stat 0x50 host_stat 0x24 ata1: status=0x50 { DriveReady SeekComplete } Info fld=0x1e22b8, Current sda: sense key No Sense ata2: command 0xca timeout, stat 0x50

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

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:

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.

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

I wrote a bunch of files to a backup DVD about two months ago and now neither of my drives will read it. I get mount errors from "not a directory" to something like "unrecognized file system type" and so on, usually after a really long wait and a notice about how the drive is write-protected (duh). Here's what happened most recently: # mount /dev/hdc /mnt mount: block

Hi All, I'm currently running an embedded linux system (arm) with a CF card mounted as EXT3. I'll copy some system details below... Anyway, I'm getting some drive errors 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:

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

I have a problem with SATA disk. Once, i start up my system (1 domain0 and 2 domainU on the same machine), it is good. But, where some of them have high traffic and thus require high disk usage i get this error in dom0''s dmesg: ATA: abnormal status 0xD0 on port 0x9F7 ATA: abnormal status 0xD0 on port 0x9F7 ATA: abnormal status 0xD0 on port 0x9F7 ata1: command 0x35 timeout, stat 0xd0

now that i am done ranting. i have a question. I received this error today and i think it was today only so far, but the error is as follows. hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hda: drive_cmd: error=0x04Aborted Command i did some googling and found some stuff...but some said go out and get another drive this one is going to hard drive heaven very soon... and other

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

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

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

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

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

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

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