similar to: SATA NCQ and Linux Software RAID

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 440.7 0.0 45825.9 0.0 0.0 5.5 12.4 0 78 sd6 445.7 0.0

All, I have a problem with a new Seagate hard disk. The problem occurs 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

I have had great luck with nvidia fakeraid on RAID1, but I see there are preferences for software raid. I have very little hands on with full Linux software RAID and that was about 14 years ago. I am trying to determine which to use on a rebuild in a "standard" CentOS/Xen enviroment. It seems to me that while FakeRaid is/can be completely taken care of in dom0 dmraid whereas with

> My ThinkStation runs CentOS 7 which I installed on a BIOS RAID 0 setup > with two identical 256 Gb SSDs after removing Windows. It runs fine but I > just discovered in gparted something that does not seem right: > > - Launching gparted it complains "invalid argument during seek for red on > /dev/md126" and when I click on Ignore I get another error "The backup

Once upon a time, Simon Matter <simon.matter at invoca.ch> said: > I'm a bit confused what you have here. Did you mix pseudo hardware RAID > (BIOS RAID 0) with software RAID here? Because /dev/md126 clearly is part > of a software RAID. IIRC the old dmraid support for motherboard RAID has been phased out, but mdraid has grown support for Intel (and maybe some other?) common

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

Hi people, I am building a cheap remote rsync backup server using a software raid 5 array of 4 500GB disks. What I have available on the market is: 1. HITACHI GST Deskstar T7K500 500GB 7200rpm 16MB cache Serial ATA II-300 2. SEAGATE Barracuda 7200.10 with NCQ 500GB 7200rpm 16MB cache Serial ATA II-300 3. Western Digital 500GB SATAII RAID EDITION Caviar SE16 7200rpm 8.9ms 16MB cache I am

I'm just setting up a SuperMicro system which has twin SATA disks on an Intel IHC7 RAID-capable controller. The system came with Fedora 5 pre-installed, which I will be removing and replacing with CentOS 4.5. But before doing so, I've been having a look at how the original vendor configured it. When I've built systems previously, I've disabled any RAID controller and used kernel

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 sectors: LBA48

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'm sure this eventually will be resolved with a BIOS or kernel update, but in case someone experiences this on this or a similar motherboard, I thought I'd post a problem-and-workaround report. Platform CentOS5, x86_64 kernel-2.6.18-53.1.21.el5 Motherboard Asus M3a78-EMH HDMI SATA-controller configured as AHCI Experienced symptom; Periodic, ~20s lockups/freezes, several a

Hi, Just to bring one more Debian concern to the Syslinux table: the default metadata format in upstream mdadm changed to 1.2, which means MD superblocks at the beginning of the partition, after a 4 KB hole. Is our favorite bootloader prepared to handle such situations? -- Thanks, Feri.

I have noticed that when I do software raid installed (RAID1) that I reboot and one of the first things it says is md1 is not in sync doing background reconstruction... md0 is my /root partition md1 is my /home partition why would md1 not be in sync after an install. Jerry

P? Thu, 3 Oct 2019 07:38:05 -0500 Valeri Galtsev <galtsev at kicp.uchicago.edu> skrev: > > On Oct 3, 2019, at 6:24 AM, G?nther J. Niederwimmer > > <gjn at gjn.priv.at> wrote: > > > > > > 07:00.0 Serial Attached SCSI controller [0107]: Intel Corporation > > C602 chipset 4-Port SATA Storage Control Unit [8086:1d6b] (rev 06)? > > > > what

Hi A server has FakeRAID installed, I want to remove it to make it mdadm driven .... If I delete the FakeRAID including - disabling it in the BIOS - removing the dmraid driver from initrd - deleting all meta data from partitions - deleting all dmraid packages is the data still available on the drives, i.e. the partitions, filesystem and files are still ok? I know that FakeRAID controller

My ThinkStation runs CentOS 7 which I installed on a BIOS RAID 0 setup with two identical 256 Gb SSDs after removing Windows. It runs fine but I just discovered in gparted something that does not seem right: - Launching gparted it complains "invalid argument during seek for red on /dev/md126" and when I click on Ignore I get another error "The backup GPT table is corrupt, but the

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

On my machine I have SATA0: HD SATA1: HD these two drives are set as RAID1 SATA2: HD extra SATA3: DVD SATA4: external USB disk Snip from dmesg shows the ATAPI device being detected. ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xe400 irq 10 ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xe408 irq 10 ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATAPI: PIONEER BD-ROM