search for: drdi

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

I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of my Ubuntu machines without success. It keeps giving errors like this: [ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10 frozen [ 9.115550] ata9.00: failed command: READ FPDMA QUEUED [ 9.115556] ata9.00: cmd 60/04:00: d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in [ 9.115557]

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

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

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

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

Valeri Galtsev wrote: > > On Tue, June 16, 2015 7:11 am, mark wrote: >> 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,

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

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

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, 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, 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, > from the logs: > Jun 15 15:34:43 <servername> kernel: ata3:

On Tue, June 16, 2015 7:11 am, mark wrote: > 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

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Either Xen, or the Dom0 kernel (I guess you know better) spits out error messages about ata4 containing "status: { DRDY ERR }" (similar error can be found googling DRDY ERR). I'm not putting the whole error message here because I couldn't copy-paste the message at the booting stage. I'm adding the autoconfigured menu

On Fri 06/Sep/2013 10:12:29 +0200 Ian Campbell wrote: > On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: >> >> I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then >> crashes when used=2837436K free=4127432K. > > On a modern dom0 kernel you need to specify the maximum memory as well, > i.e. dom0_mem=8192M,max:8192M