[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Sever load , calculating



Is the blue 40-pin IDC connector of the 80 pin IDE cable at the controller end (motherboard IDE?) and not at the drive end? The reason for this is the blue IDC connector ties the ground plane together.  Is the cable <= 18"? Are both drive on the same controller interface? e.g.: Primary IDE... To get maximum throughput out of two separate drives, I would place each on a controller as the master, then if I had to have a CD drive, I would add it to the Primary IDE as a slave. If you think you might be swapping drive around from time to time, you may want to go the CS (cable select) route, but you must make sure how the cable connects to the mainboard and then to the drives for proper operation. See these links: http://www.unixwiz.net/techtips/ide-cable-select.html

http://www.allpinouts.org/index.php/Ultra_ATA_66/100_IDE

http://www.pcguide.com/ref/hdd/if/ide/confCable80-c.html

http://www.mikeshardware.com/howtos/howto_connect_ide_hd.html


On Sat, 2010-09-11 at 08:45 -0500, Barry Cisna wrote:
Hello All,

Some findings after doing an hdparm -t -T on this servers HD's.

1. On both of the HD's *cached reads* they are doing a respectable
870mb/sec

2. On both Hd's the *buffered reads* they doing a sucky 250kb/sec !!!

This is with no one accessing  the server too.
Anyone have any ideas as to why the buffered reads are so pathetic?
These are a pair of new a couple months ago WDC drives. I used an 80
conductor IDE cable. Is it possible not having hyper-threading enabled
in the system bios(I think) that this is tanking the buffered reads?

dmegs shows drives are doing UDMA 133mhz.
CPU hyper-threading disabled,,,:(.
hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: 0xb0
hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: 0xb0
hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: 0xb0
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }

,,* many lines of the above failed opcode hda* 
hdb drive shows none of these errors..?

Looks like something is haywire with hda drive to me,or is it simply never 'catching up' 
from disk writing?
I have noticed when in the server room the HD light on this server is in fact running 
like mad,but not all the time.

I have not gotten any complaints (yet) of slowness in regards to file
access but I cant imagine it can be anywhere close to what it should be
with these readings.
Bottom line I am kinda stuck as of now as this is what I set up.
Sorry for long post again.

Take Care,
BC




_______________________________________________
K12OSN mailing list
K12OSN redhat com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]