search for: noncq

...e workloads. However, the latest C7 server I built, ran into problems with them on on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error write fpdma queued". Googling on it threw up old suggestions to limit SATA link speed to 1.5Gbps using libata.force boot options and/or noncq. Lowering the link speed helped to reduce the frequency of the errors (from not getting a smartctl output to getting a complete listing within 2 tries). Tried two Reds produced in Jan 2016, two HGST, two SSDs on the same combination of cable/bay/SATA port as well as different combos. SSD maxed out...

...a Marvell controller in AHCI and one BTRFS formatted hard drive. We isolated the problem by relocating the disk to an Intel contoller (SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11) had a lot of problems and I managed to overcome them by passing libata.force=noncq for a couple of weeks, until it failed generally). Now that the disk is on the intel contoller it works fine and data is intact, but whenever I do mount or unmount I see: Aug 10 18:34:47 MyServerHere kernel: btrfs: bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 166, gen 0 The problem is "...

...r, the latest C7 server I built, ran into problems with them on > on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error > write fpdma queued". Googling on it threw up old suggestions to limit > SATA link speed to 1.5Gbps using libata.force boot options and/or > noncq. Lowering the link speed helped to reduce the frequency of the > errors (from not getting a smartctl output to getting a complete > listing within 2 tries). > I discovered, amidst great initial pain, that most, if not all, of the problems I had with SATA disks were caused by SATA cables...

...r, the latest C7 server I built, ran into problems with them on > on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error > write fpdma queued". Googling on it threw up old suggestions to limit > SATA link speed to 1.5Gbps using libata.force boot options and/or > noncq. Lowering the link speed helped to reduce the frequency of the > errors (from not getting a smartctl output to getting a complete > listing within 2 tries). any chance your SATA cables aren't up to SATA3 (6gbps) performance levels ? the C236 chipset is the server version of the Z170, la...

...r, the latest C7 server I built, ran into problems with them on > on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error > write fpdma queued". Googling on it threw up old suggestions to limit > SATA link speed to 1.5Gbps using libata.force boot options and/or > noncq. Lowering the link speed helped to reduce the frequency of the > errors (from not getting a smartctl output to getting a complete > listing within 2 tries). <snip> Sorry, we don't seem to have any Supermicros with that m/b, but with the ones we have (all X9* m/bs), as well as our ma...

....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: Advanced Micro Devices [AMD] RS780 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx) 00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI br...