similar to: ATA error: hard drive going bad?

On Fri, 2013-09-06 at 16:39 +0200, Alessandro Vesely wrote: Both sets of log contain stuff like: > Sep 6 15:22:53 pcale kernel: [ 126.828195] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x6 frozen > Sep 6 15:22:53 pcale kernel: [ 126.828199] ata4: SError: { 10B8B } > Sep 6 15:22:53 pcale kernel: [ 126.828201] ata4.00: failed command: SMART > Sep 6 15:22:53 pcale

Hi, I''ve got similar problem - after HW failure - two of three disks became unavailable and now I''m unable to btrfsck. Btrfs lays on /dev/sdb1,/dev/sdc1,/dev/sdd1 - sdc+sdd became unavailable Here is kernel log: ============================================ Mar  9 23:56:28 ftp2 kernel: [121492.593338] ata7.00: exception Emask 0x60 SAct 0x1 SErr 0x800 action 0x6 frozen Mar  9

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

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

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

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

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

Hi, I have a SATA PCIe 6Gbps 4 port controller card made by Startech. The kernel (Linux viz1 2.6.32-220.4.1.el6.x86_64) sees it as Marvell Technology Group Ltd. 88SE9123 I use it to provide extra SATA ports to a raid system. The HD's are all "WD2003FYYS" and so run at 3Gbps on the 6Gbps controller. However I am seeing lots of instances of errors like this

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

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

Hallo, "never change a running system" ... For some months I run btrfs unter kernel 3.2.5 and 3.2.9, without problems. Yesterday I compiled kernel 3.3.4, and this morning I started the machine with this kernel. There may be some ugly problems. Copying something into the btrfs "directory" worked well for some files, and then I got error messages (I''ve not

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

On my C5 machine (a Dell XPS420) I have a 500Gb disk on the internal SATA controller. I also have a SiI3132 dual-port multi-device eSATA card. This is connected to an external SATA array of disks. Now occasionally I see something like this in my logs ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x0 ata7.01: irq_stat 0x00060002, device error via D 2H FIS ata7.01: cmd

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

Having some huge issues with Xen on one of my boxes. I''m using the package from Arch Linux repository, though I have tried Vanilla source with identical results. This package works on two of my other computers (all it does patch-wise is change the Xen init.d scripts to Arch Linux compatible ones, and add support for xz-compressed dom0 kernels). My syslinux.cfg menu line is as follows:

On 06/16/15 07:59, Ashish Yadav wrote: > Hi, > > On Tue, Jun 16, 2015 at 2:26 AM, <m.roth at 5-cent.us> wrote: > >> I was rsync'ing data from one system to another, and the recipient >> suddenly started throwing DRDY errors. Now, it's a fairly new WD Red 3TB, >> and I'd think it was just a bad drive... but I'm really confused by this, >>

I was rsync'ing data from one system to another, and the recipient suddenly started throwing DRDY errors. Now, it's a fairly new WD Red 3TB, and I'd think it was just a bad drive... but I'm really confused by this, from the logs: Jun 15 15:34:43 <servername> kernel: ata3: SError: { Dispar } Dispar? And googling, every reference I find to that word always has something else

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