search for: drdy

...5.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 0x409 (media error) <F> ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: exception Emask 0x0 SAct 0x3 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 0x409 (media er...

...5.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 0x409 (media error) <F> ata5.00: status: { DRDY ERR } ata5.00: error: { UNC } ata5.00: exception Emask 0x0 SAct 0x3 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 0x409 (media er...

...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> [ 542.255831] ata1.00: status: { DRDY ERR } [ 542.255837] ata1.00: error: { UNC } [ 542.264434] ata1.00: configured for UDMA/133 [ 542.264505] ata1: EH complete [ 545.075811] ata1.00: exception Emask 0x0 SAct 0xd7c6ff SErr 0x0 action 0x0 [ 545.075820] ata1.00: irq_stat 0x40000008 [ 545.075829] ata1.00: failed command: READ FPDMA...

...SErr 0x0 action 0x0 > [ 26.778690] ata2.00: failed command: READ DMA > [ 26.779131] ata2.00: cmd c8/00:e8:92:ad:00/00:00:00:00:00/e0 tag 0 dma 118784 in > [ 26.779131] res 50/00:00:0a:80:03/00:00:00:00:00/a0 Emask 0x40 (internal error) > [ 26.780691] ata2.00: status: { DRDY } > [ 26.781603] ata2.00: configured for MWDMA2 > [ 26.782034] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s > [ 26.782958] sd 1:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] > [ 26.783646] sd 1:0:0:0: [sda] tag#0 Add. Sense...

...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] res 40/00:18:d3:82:85/00:00:1f:00:00/40 Emask 0x4 (timeout) [ 9.115560] ata9.00: status: { DRDY } [ 9.115562] ata9.00: failed command: READ FPDMA QUEUED I''ve searched and found some bugs referencing this type of problem and followed some suggestions: I added libata.force=noncq to the kernel boot line but it did not help. My hardware is like this: # lspci 00:00.0 Host bridge: A...

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

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, >> from the logs: >> Jun 15 15:34:43 <servername> kernel: ata3: SError: { Dispar } >> >> Dispar? And googling, every reference I fi...

...x0 [44106.091470] ata4.01: BMDMA stat 0x64 [44106.091478] ata4.01: failed command: READ DMA EXT [44106.091492] ata4.01: cmd 25/00:08:a0:ca:72/00:00:4f:00:00/f0 tag 0 dma 4096 in [44106.091495] res 51/40:00:a3:ca:72/40:00:4f:00:00/f0 Emask 0x9 (media error) [44106.091503] ata4.01: status: { DRDY ERR } [44106.091508] ata4.01: error: { UNC } [44106.120384] ata4.00: configured for UDMA/133 [44106.128349] ata4.01: configured for UDMA/133 [44106.128374] ata4: EH complete [44109.364633] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [44109.364642] ata4.01: BMDMA stat 0x64 [44109.36465...

...01:12:29 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:12:29 g2 kernel: ata9.00: cmd 25/00:00:00:fe:d5/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:12:29 g2 kernel: res 51/40:00:19:ff:d5/40:00:04:00:00/00 Emask 0x9 (media error) Jan 6 01:12:29 g2 kernel: ata9.00: status: { DRDY ERR } Jan 6 01:12:29 g2 kernel: ata9.00: error: { UNC } Jan 6 01:12:29 g2 kernel: ata9.00: configured for UDMA/33 Jan 6 01:12:29 g2 kernel: ata9.01: configured for UDMA/33 Jan 6 01:12:29 g2 kernel: ata9: EH complete Jan 6 01:12:33 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 actio...

...tion Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 35.735437] ata1.00: failed command: READ DMA [ 35.745912] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in [ 35.745913] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 35.777373] ata1.00: status: { DRDY } [ 35.785709] ata1: soft resetting link [ 35.946815] ata1.00: configured for MWDMA2 [ 35.955695] ata1.00: device reported invalid CHS sector 0 [ 35.967512] ata1: EH complete [ 66.784177] ata1: lost interrupt (Status 0x50) [ 66.788709] ata1.00: limiting speed to MWDMA1:PIO2 [ 66.79339...

...;> 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, from the logs: >>>> Jun 15 15:34:43 <servername> kernel: ata3: SError: { Dispar } >>>> >>>> Di...

...0: BMDMA stat 0x24 [ 129.241643] ata6.00: failed command: READ DMA EXT [ 129.241649] ata6.00: cmd 25/00:08:5f:dc:2f/00:00:70:00:00/e0 tag 0 dma 4096 in [ 129.241651] res 51/40:00:61:dc:2f/40:00:70:00:00/e0 Emask 0x9 (media error) [ 129.241654] ata6.00: status: { DRDY ERR } [ 129.241656] ata6.00: error: { UNC } [ 129.256243] ata6.00: configured for UDMA/133 [ 129.256261] ata6: EH complete [ 131.640911] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 131.640915] ata6.00: BMDMA stat 0x24 [ 131.640918] ata6.00: failed comma...

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 Controller [AHCI mode] vendor: ATI Technologies Inc <snip> width: 32 bits...

...: ata1.00: irq_stat 0x40000001 Oct 5 08:34:47 server1 kernel: ata1.00: cmd 60/f8:00:b9:1e:71/00:00:14:00:00/40 tag 0 ncq 126976 in Oct 5 08:34:47 server1 kernel: res 41/40:00:40:1f:71/a0:00:14:00:00/00 Emask 0x409 (media error) <F> Oct 5 08:34:47 server1 kernel: ata1.00: status: { DRDY ERR } Oct 5 08:34:47 server1 kernel: ata1.00: error: { UNC } Oct 5 08:34:47 server1 kernel: ata1.00: cmd 60/08:08:b1:1f:71/00:00:14:00:00/40 tag 1 ncq 4096 in Oct 5 08:34:47 server1 kernel: res 41/04:f8:40:1f:71/00:00:14:00:00/00 Emask 0x1 (device error) Oct 5 08:34:47 server1 kernel:...

...erface fatal error Jun 22 03:13:23 viz1 kernel: ata13: SError: { Handshk } Jun 22 03:13:23 viz1 kernel: ata13.00: failed command: WRITE FPDMA QUEUED Jun 22 03:13:23 viz1 kernel: ata13.00: cmd 61/e8:10:98:05:1b/01:00:66:00:00/40 tag 2 ncq 249856 out Jun 22 03:13:23 viz1 kernel: ata13.00: status: { DRDY } Jun 22 03:13:23 viz1 kernel: ata13: hard resetting link Jun 22 03:13:24 viz1 kernel: ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 330) Jun 22 03:13:24 viz1 kernel: ata13.00: configured for UDMA/133 Jun 22 03:13:24 viz1 kernel: ata13: EH complete --------------------------------------- Ve...

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: SError: { Dispar } > > Dispar? And googling, every reference I find to that word alwa...

...015 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 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 } >>> >>&...

...SMART > Sep 6 15:22:53 pcale kernel: [ 126.828205] ata4.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0 > Sep 6 15:22:53 pcale kernel: [ 126.828206] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Sep 6 15:22:53 pcale kernel: [ 126.828207] ata4.00: status: { DRDY } > Sep 6 15:22:53 pcale kernel: [ 126.828211] ata4: hard resetting link > Sep 6 15:22:54 pcale kernel: [ 127.320197] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > Sep 6 15:22:54 pcale kernel: [ 127.321358] ata4.00: configured for UDMA/133 > Sep 6 15:22:54 pcale kernel...

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 entry just in case: menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-am...

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