similar to: Disk errors on CentOS 5 - libata bug?

I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware. Could someone please tell me what these error are and if there is some known way to prevent them? My configuration: - 2 Hitachi SATA 120 GB Harddisks - Intel P4 3GHz - Tyan Tomcat i875p motherboard - 1 GB ECC RAM - 2

Hello, I was testing Fedora 16 (rc2) Xen host, with included Xen 4.1.1 rpms and Linux 3.1.0 dom0 kernel. Fedora 16 PV domUs seem to work nicely. I noticed a problem with Fedora 16 Xen HVM guests though. The F16 guest kernel (Linux 3.1.0) fails with the qemu-dm emulated DVD-ROM drive.. Full HVM guest kernel dmesg attached to this email. See the end of this email for Xen cfgfile for the

Hello, A message was already posted here regarding this issue- I experience the same problem with 6 machines, all with Hitachi harddrive, VIA Motherboard which uses the sata_via driver: Once every few days each machine freezes or just stops reading from the HD and throws i/o error messages as pasted below. Note that the first "ata exception Emask" errors apear right after booting,

On 14.05.20 08:44, teawater wrote: > Hi David, > > I got a kernel warning with v2 and v3. Hi Hui, thanks for playing with the latest versions. Surprisingly, I can reproduce even by hotplugging a DIMM instead as well - that's good, so it's not related to virtio-mem, lol. Seems to be some QEMU setup issue with older machine types. Can you switch to a newer qemu machine version,

Hi, I have some errors in dmesg: [ 542.255788] ata1.00: exception Emask 0x0 SAct 0xffffff SErr 0x0 action 0x0 [ 542.255797] ata1.00: irq_stat 0x40000008 [ 542.255805] ata1.00: failed command: READ FPDMA QUEUED [ 542.255821] ata1.00: cmd 60/00:00:1a:b7:7a/04:00:1d:00:00/40 tag 0 ncq 524288 in [ 542.255824] res 41/40:00:a0:b7:7a/00:00:1d:00:00/40 Emask 0x409 (media error) <F> [

I''ve been trying to install OpenSUSE 10.3 as an HVM guest without much success. I''ve been using the mini network installation image `openSUSE-10.3-GM-i386-mini.iso''. First I had to binary-edit the iso to turn off gfxboot, which breaks with current xen-unstable. (In theory you can turn off gfxboot by holding down shift but it is almost impossible to get the timing

Got a bunch of servers from Penguin. Supermicro m/b's H8QG6. We put a 3tb drive in for additional workspace for the users, and some of them won't read, others will go for weeks, then spit out DRDY errors. lshw shows the controller as an ATI SB7x0/SB8x0/SB9x0 SATA. I did notice that it shows *-storage description: SATA controller product: SB7x0/SB8x0/SB9x0 SATA

I've been having an extremely hard time using the on board SATA controller on my nvidia based board. I have two 160gig Maxtor SATA drives attached to the on board controller, setup as software raid0. The problem is the array is extremely unreliable, where I'm getting constant I/O errors like: sd 0:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hi All, I am fairly certain that this disk is failing in my server, and I am replacing it straight away anyway. However, I'd appreciate the views of the list just to be sure as I value your opinion(s). I got these errors, once only so far, in /var/log/messages. This disk has / on it. Oct 5 08:34:47 server1 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Oct 5 08:34:47

Hi All, I know Centos 5 is almost EOL and all this is old but.... I'm helping a colleague who has moved a Centos 5 install on an IDE disk to system with a Foxconn M'board. His idea is to use the SATA interface that's on the Foxconn. The thing boots OK and then gets into a loop trying to start the interfaces to the SATA disks. Oceans of stuff like this in /var/log/messages Aug 7

Hello, We have recently purchased two Supermicro servers, AS-1021M-T2RB (http://www.supermicro.com/Aplus/system/1U/1021/AS-1021M-T2RV.cfm), and have built them both with CentOS 5 operating system. They are identical, apart from the manufacturer of the disk drives. Kernel is: Linux version 2.6.18-8.1.6.el5 (mockbuild at builder6.centos.org) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

For some time I have been seeing disk errors in the syslog every seven days. Until today it always happens Sunday morning at 8:13 AM, plus or minus a minute or two. Yesterday it happened at 1:13 AM. Here are the pertinent log entries for the latest occurrence: Jan 6 01:12:29 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:12:29 g2 kernel: ata9.00: BMDMA stat

Hello, every few hours I get the following message in /var/log/message: Jul 5 20:23:28 hXXX kernel: Machine check events logged Jul 5 20:53:28 hXXX kernel: Machine check events logged Jul 5 22:13:28 hXXX kernel: Machine check events logged Jul 5 23:53:28 hXXX kernel: Machine check events logged Jul 5 23:58:27 hXXX kernel: Machine check events logged Jul 6 01:38:27 hXXX kernel: Machine

http://bugs.freedesktop.org/show_bug.cgi?id=25453 Summary: nouveau + multiple xorg servers + suspend2ram trashes root partition Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: high Component: Driver/nouveau

Hi All, Newbie here! I was wondering if anyone has succeeded in getting NCQ enabled with the ServerWorks chipset in the 2.6.18 kernel. I am running a Dell 1435/CentOS 5.0-x86_64 with dual 250GB Western Digital NCQ supported drives, when I load up the OS I get these messages: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488281250 sectors: LBA48

Observed on Linux 3.2.9 after the controller/disk flaked in-out. (The world still needs a SCSI error decoding tool to tell normal people what cmd and res are about.) [ 157.732885] device label srv devid 4 transid 11292 /dev/sdf [ 157.733201] btrfs: disk space caching is enabled [ 172.936515] device label srv devid 4 transid 11292 /dev/sdf [44106.091461] ata4.01: exception Emask 0x0 SAct 0x0

Hi, One of my disks, partitioned into a single btrfs partition, is showing media errors. The problem is that these errors lead to kernel panic from btrfs - that make the filesystem unusable until reboot - and therefore it is very hard for me to do a full backup of the data prior to changing the disk. My current kernel is 3.2.0-8-generic from Ubuntu/precise (based on linux 3.2-final) but I