similar to: Kernel drive_cmd error messages

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

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.

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.

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,

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:

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)

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

> <sebastian.vuorinen@helsinki.fi> wrote: > > On Wed, 2005-04-20 at 18:34 -0700, Steve Nospam > > wrote: > > > I have to admit,I'm ignorant. I'm seeing a > > problem > > > reported in syslog (2.6.11.7 kernel debian > dist.) > > The > > > problem reported is: > > > Apr 20 20:19:53 sandbox kernel: hda: drive_cmd: >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''m using xen to run real linux system. I''ve configured partition for my system. When I''m installing Debian Etch everything is fine but when I''m starting installed system I get a hang. My xen disk conf is: disk = [ ''phy:/dev/root/node1,ioemu:hda,w'' ] device_model =

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

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

Hello, Straight from the floor of Astricon 2004, I am happy to release my updated Asterisk 1.0 RPMS for RedHat 7.3 and RedHat 9.0 platform. Current Release --------------- asterisk-1.0-0 libpri-1.0-0 zaptel-1.0-0 kernel-module-zaptel-1.0-0 RedHat 7.3 ---------- ftp://ftp.nacs.net/asterisk/rh73/RPMS/ ftp://ftp.nacs.net/asterisk/rh73/SRPMS/ RedHat 9.0 ----------

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

Hello all, It's my birthday today, so as my present I would like everyone possible to download and test my updated set of RPMS for Asterisk 0.7.1. By popular request, I installed and built a set of RPMS for RedHat 9.0, and in the process fixed a bunch of issues from the initial build. I have also updated and will be maintaining a page on the Asterisk Wiki located at:

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

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

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