search for: ncq

...oting 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 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:0...

...oting 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 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:0...

I''ve been looking into the performance impact of NCQ. Here''s what i found out: http://blogs.sun.com/erickustarz/entry/ncq_performance_analysis Curiously, there''s not too much performance data on NCQ available via a google search ... enjoy, eric

fun example that shows NCQ lowers wait and %w, but doesn''t have much impact on final speed. [scrubbing, devs reordered for clarity] extended device statistics device r/s w/s kr/s kw/s wait actv svc_t %w %b sd2 454.7 0.0 47168.0 0.0 0.0 5.7 12.6 0 74 sd4 44...

I have two identical servers. The only difference is that the first one has Maxtor 250G drives and the second one has Seagate 320G drives. OS: CentOS-4.4 (fully patched) CPU: dual Opteron 280 Memory: 16GB Raid card: 3ware 9550Sx-8LP Raid volume: 4-disk Raid 5 with NCQ and Write Cache enabled On the first server I have decent performance. Nothing spectacular, but good enough. The second one has about 1/3 the write speed. I can't find any difference between the systems. Both of them have the same stripe size, both have ext3 filesystems, both have write ca...

I have two identical servers. The only difference is that the first one has Maxtor 250G drives and the second one has Seagate 320G drives. OS: CentOS-4.4 (fully patched) CPU: dual Opteron 280 Memory: 16GB Raid card: 3ware 9550Sx-8LP Raid volume: 4-disk Raid 5 with NCQ and Write Cache enabled On the first server I have decent performance. Nothing spectacular, but good enough. The second one has about 1/3 the write speed. I can't find any difference between the systems. Both of them have the same stripe size, both have ext3 filesystems, both have write ca...

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

Does CentOS support NCQ on SATA drives? If so is there something I must do to turn this support on? Matt

Does SATA Native Command Queueing and Linux software RAID1 play well together or is it better to turn off NCQ when doing software RAID?

...s when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage 3112 PCI adapter card. Does anyone have any ideas? Regards, Peter

...t is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: drive cache: write back (on a side note, the system has 6 SATA disks, the older ST3120827AS Seagate-disk here exhibits this significantly more often than the others, but they too are affected) From other sources this is reported as a AHCI NCQ bug. My workaround, which was suggested somewhere else, was to disable NCQ; (in rc.local) for D in sd{a,b,c,d,e,f} ; do echo 1 > /sys/block/$a/device/queue_depth done This resolves the above issue, and from several times an hour, I have not experienced it since (~30h). Yours, -S -- Sime...

...15.107086] usb 1-1: new full speed USB device using ohci_hcd and address 2 [ 15.119952] ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 15.151896] ata17.00: ATA-7: HITACHI HDS7250SASUN500G 0648KPU78F, K2AOAJ0A, max UDMA/133 [ 15.151898] ata17.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 15.151905] ata17.00: max_sectors limited to 256 for NCQ [ 15.153868] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 15.153870] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 15.153872] usb usb3: Product: OHCI Host Controller [ 15.1538...

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

...n 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] 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 add...

Is there anyway to enable NCQ on CentOS 4.6? I guess anouther question is on a somewhat high activity mail server with a single SATA2 drive will it do any good? Matt

...in a RAID-5 configuration. All drives are setup for 3.0 GiB SATA link, and the motherboard also supports that. Looking in dmesg when the system comes up, I see that reflected as well: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32) ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3.00: ATA...

On 10.11.2015 20.18, Gordon Messmer wrote: > On 11/10/2015 10:14 AM, Christer Solskogen wrote: >> Queued TRIM seems to be a problem with this kind of drive (with the >> latest firmware), and a "recent" kernel (4.1.x) seems to have this >> fixed this without disabling NCQ completely. Is that patch backported >> to the "mainline" CentOS 6 or CentOS7 kernel? > > Can you provide any references to the specific bug you're referring to? This is the first I found. http://linux.slashdot.org/story/15/07/30/1814200/samsung-finds-fixes-bug-in-linux-t...

First Post! Sorry, I had to get that out of the way to break the ice... I was wondering if it makes sense to zone ZFS pools by disk slice, and if it makes a difference with RAIDZ. As I''m sure we''re all aware, the end of a drive is half as fast as the beginning ([i]where the zoning stipulates that the physical outside is the beginning and going towards the spindle increases hex

Queued TRIM seems to be a problem with this kind of drive (with the latest firmware), and a "recent" kernel (4.1.x) seems to have this fixed this without disabling NCQ completely. Is that patch backported to the "mainline" CentOS 6 or CentOS7 kernel? -- chs

So after troubleshooting this for about a week, I was finally able to create a raid 10 device by installing the system, copying the md modules onto a floppy, and loading the raid10 module during the install. Now the problem is that I can't get it to show up in anaconda. It detects the other arrays (raid0 and raid1) fine, but the raid10 array won't show up. Looking through the logs