NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Mon Nov 18, 2019 5:30 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 50 posts ]  Go to page Previous  1, 2, 3, 4  Next
Author Message
PostPosted: Sun Feb 17, 2008 10:08 am 
Offline

Joined: Tue Aug 10, 2004 1:50 pm
Posts: 604
Location: Texas, USA
This BIOS configuration info is out of my notes. Don't remember where it came from but I've used it with measurable success especially when it comes to RAM. I'm not sure if it will make a difference for superboss but it may be worth a try. Use at your own risk ;-)

None of this will make any difference tho if you are sharing IRQs, so that's always first on the list. In my case, I've had RAM do strange things. You'd think that no matter what you do, for a nas RAM is too fast out of the gate to make a difference. Not so. Some boards really crawl with some ram and can be improved using BIOS settings.

Quote:

Memory Tweaks
You can squeeze more performance out of your memory by playing with the settings in the Chipset Features section. The first group of options is concerned with the memory timings, and it's important to get these right as memory throughput is key to the performance of your machine. Setting the timing by SPD is the preferred setting, but you need identical memory sticks in your machine for this to work.

If you have mixed memory, you should use a program such as SiSoft Sandra 2002 to check the capabilities of your memory at set speeds, and set it to 2, 2.5, or 3 (the lower the better). Set the DRAM clock to the required memory speed - again check with SiSoft Sandra for the best setting. Enable Fast R-W Turn Around for better performance, too. Leave the memory hole disabled unless you have ISA cards.

More Memory Tweaks
The CAS Latency Time setting controls the time delay between issuing a command and its being carried out in memory. Usually set to a value of 3, try changing this (and other CAS and RAS settings) to a value of 2 (or 2T).

In the same area you should also find settings related to the MA Wait state as well as RAM access time. Set the Wait State to Fast and the RAM Configuration to the lowest possible access time or highest possible frequency. In each of these cases, what you are attempting to do is overclock RAM so be careful and remember the risks involved.

Processor Tweaks
The most critical CPU settings are related to cache memory. Level 1 cache is built into the CPU, and Level 2 is a separate chip. When the processor is looking for data from memory, these are the first two places it looks. These should always be enabled, or you'll be needlessly sacrificing performance. Some old systems, most notably early Celerons, do not have any Level 2 cache - in this case, ensure that L2 cache is disabled, or the system may freeze on reboot. Disabling the Layer 2 cache ECC check will also improve performance, although you are potentially sacrificing stability, especially if your system is already prone to crashing. One simple CPU setting that usually lives up to its name is Turbo Frequency. Enabling it will often boost your processor speed by up to five per cent on its own.

PCI Settings
These settings, found under Chipset Features, are concerned with how the flow of data is controlled with respect to the PCI bus. You should enable all of the following settings for the best performance: CPU to PCI Write Buffer, PCI Dynamic Bursting, PCI Master 0 WS Write and PCI Master 0 WS Read. If you've got no slow PCI cards in your machine, you should also try enabling PCI #2 Access #1 Retry.

Hard Disk
In general, there isn't a lot you can do within the BIOS to boost your hard drive. There is one tweak for IDE drives, though - enable the IDE HDD Block Mode setting to speed up disk access.


If you are really brave, then tweakbios may be your ticket http://miro.pair.com/tweakbios/

Naslite is a strange animal at times. One thing is for sure tho. It totally kicks butt on tuned hardware.


Top
 Profile  
 
PostPosted: Tue Feb 19, 2008 1:57 pm 
Offline

Joined: Sun Sep 24, 2006 1:32 pm
Posts: 290
Got the new parts today (hurrah!) but as of yet they refuse to even post (nah!) :S I think its due to faulty ram (bye bye Kingston Valueram) and have ordered replacement dimms. What I can say however, is that the Antec Sonata III is quite nice for a NAS box. The drive bays are shifted and all have noise reduction features. The machine has one fan with adjustable speed and the thing is silent! Will post updates when I get some action from this puppy. Carlsberg here I come! :cry:


Top
 Profile  
 
PostPosted: Tue Mar 04, 2008 7:25 am 
Offline

Joined: Sun Sep 24, 2006 1:32 pm
Posts: 290
Ralph wrote:
The dual processor will be good for the future, once we move to the 2.6 kernel we will support multiple cores/cpus.


Any timeframe when this might happen and what version of the 2.6 kernel is likely to be used? I'm considering replacing my LSI card with a 3Ware 9xxx series but its needs kernel version 2.6.19 for driver support..

As for my new setup, the motherboard has been sent off for RMA :(


Top
 Profile  
 
PostPosted: Thu Mar 06, 2008 4:11 pm 
Offline

Joined: Sun Sep 24, 2006 1:32 pm
Posts: 290
Got the replacement board today.. The NL box is now running on an AMD 64 Athlon X2 4000+ with 2GB RAM, LSI Megaraid 150-4 on the PCI-X slot and the array is a RAID5 consisting of 4x Samsung Spinpoint P120 250GB SATA drives. I just benchmarked it real quick (with diskwriggler) and the numbers were not very exciting. Writes in the 30MB/s range and reads at 40MB/s... I was expecting alot higher numbers given the upgrade of switching to PCI-X etc. Admittedly the reads doubled but seeing the numbers that other members are posting with lower speced setups I consider these numbers to be low still. Am I expecting too much out of this setup or does anyone have any idea what the problem is? Sys log reads:

Quote:
* Mar 6 20:23:16 user.notice kernel: klogd started: BusyBox v1.01 (2007.03.15-22:03+0000)
* Mar 6 20:23:16 user.warn kernel: Linux version 2.4.35.NASLite (root@tzt) (gcc version 3.4.6) #2 Sun Aug 12 09:03:16 EDT 2007
* Mar 6 20:23:16 user.info kernel: BIOS-provided physical RAM map:
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 0000000000000000 - 000000000009ec00 (usable)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 0000000000100000 - 000000007feb0000 (usable)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 000000007feb0000 - 000000007fee3000 (ACPI NVS)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
* Mar 6 20:23:16 user.warn kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
* Mar 6 20:23:16 user.notice kernel: 1150MB HIGHMEM available.
* Mar 6 20:23:16 user.notice kernel: 896MB LOWMEM available.
* Mar 6 20:23:16 user.warn kernel: On node 0 totalpages: 523952
* Mar 6 20:23:16 user.warn kernel: zone(0): 4096 pages.
* Mar 6 20:23:16 user.warn kernel: zone(1): 225280 pages.
* Mar 6 20:23:16 user.warn kernel: zone(2): 294576 pages.
* Mar 6 20:23:16 user.info kernel: ACPI: RSDP (v002 Nvidia ) @ 0x000f7e40
* Mar 6 20:23:16 user.info kernel: ACPI: XSDT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7fee3100
* Mar 6 20:23:16 user.info kernel: ACPI: FADT (v003 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7feecc80
* Mar 6 20:23:16 user.info kernel: ACPI: TCPA (v001 HTC HTCACPI 0x42302e31 AWRD 0x00000000) @ 0x7feece80
* Mar 6 20:23:16 user.info kernel: ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x7feecf00
* Mar 6 20:23:16 user.info kernel: ACPI: HPET (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000098) @ 0x7feed180
* Mar 6 20:23:16 user.info kernel: ACPI: MCFG (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7feed200
* Mar 6 20:23:16 user.info kernel: ACPI: MADT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7feecdc0
* Mar 6 20:23:16 user.info kernel: ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x03000000) @ 0x00000000
* Mar 6 20:23:16 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=naslite.01
* Mar 6 20:23:16 user.info kernel: Initializing CPU#0
* Mar 6 20:23:16 user.warn kernel: Detected 2109.644 MHz processor.
* Mar 6 20:23:16 user.warn kernel: Console: colour VGA+ 80x25
* Mar 6 20:23:16 user.warn kernel: Calibrating delay loop. 4207.41 BogoMIPS
* Mar 6 20:23:16 user.info kernel: Memory: 2065140k/2095808k available (2214k kernel code, 30276k reserved, 642k data, 540k init, 1178304k highmem)
* Mar 6 20:23:16 user.info kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
* Mar 6 20:23:16 user.info kernel: Inode cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Mar 6 20:23:16 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Mar 6 20:23:16 user.info kernel: Buffer cache hash table entries: 131072 (order: 7, 524288 bytes)
* Mar 6 20:23:16 user.warn kernel: Page-cache hash table entries: 524288 (order: 9, 2097152 bytes)
* Mar 6 20:23:16 user.info kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
* Mar 6 20:23:16 user.info kernel: CPU: L2 Cache: 512K (64 bytes/line)
* Mar 6 20:23:16 user.debug kernel: CPU: After generic, caps: 178bfbff ebd3fbff 00000000 00000000
* Mar 6 20:23:16 user.debug kernel: CPU: Common caps: 178bfbff ebd3fbff 00000000 00000000
* Mar 6 20:23:16 user.warn kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping 01
* Mar 6 20:23:16 user.info kernel: Enabling fast FPU save and restore. done.
* Mar 6 20:23:16 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
* Mar 6 20:23:16 user.info kernel: Checking 'hlt' instruction. OK.
* Mar 6 20:23:16 user.warn kernel: ACPI: IRQ9 SCI: Edge set to Level Trigger.
* Mar 6 20:23:16 user.warn kernel: POSIX conformance testing by UNIFIX
* Mar 6 20:23:16 user.warn kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
* Mar 6 20:23:16 user.warn kernel: mtrr: detected mtrr type: Intel
* Mar 6 20:23:16 user.info kernel: ACPI: Subsystem revision 20040326
* Mar 6 20:23:16 user.info kernel: PCI: PCI BIOS revision 3.00 entry at 0xf20f0, last bus=9
* Mar 6 20:23:16 user.info kernel: PCI: Using configuration type 1
* Mar 6 20:23:16 user.info kernel: ACPI: Interpreter enabled
* Mar 6 20:23:16 user.info kernel: ACPI: Using PIC for interrupt routing
* Mar 6 20:23:16 user.info kernel: ACPI: System [ACPI] (supports S0 S1 S3 S4 S5)
* Mar 6 20:23:16 user.info kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
* Mar 6 20:23:16 user.warn kernel: PCI: Probing PCI hardware (bus 00)
* Mar 6 20:23:16 user.warn kernel: Transparent bridge - PCI device 10de:0370
* Mar 6 20:23:16 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
* Mar 6 20:23:16 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 5 7 9 *10 11 14 15)
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK2] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK5] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK6] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK7] (IRQs *5 7 9 10 11 14 15)
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK8] (IRQs 5 7 9 10 *11 14 15)
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LP2P] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LUBA] (IRQs 5 *7 9 10 11 14 15)
* Mar 6 20:23:16 user.warn kernel: abled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LMC1] (IRQs 5 *7 9 10 11 14 15)
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LAZA] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LPMU] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LSMB] (IRQs *5 7 9 10 11 14 15)
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LUB2] (IRQs 5 7 9 10 *11 14 15)
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LIDE] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LSID] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LFID] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LSA2] (IRQs 5 7 9 10 11 14 15) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC5] (IRQs 16) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC6] (IRQs 16) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC7] (IRQs 16) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APC8] (IRQs 16) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [AMC1] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APMU] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [AAZA] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [ASA2] (IRQs 20 21 22 23) *0, disabled.
* Mar 6 20:23:16 user.info kernel: PCI: Probing PCI hardware
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LSMB] enabled at IRQ 5
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LUBA] enabled at IRQ 7
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 11
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LMC1] enabled at IRQ 7
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 10
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK7] enabled at IRQ 5
* Mar 6 20:23:16 user.warn kernel: ACPI: PCI Interrupt Link [LNK8] enabled at IRQ 11
* Mar 6 20:23:16 user.info kernel: PCI: Using ACPI for IRQ routing
* Mar 6 20:23:16 user.info kernel: Linux NET4.0 for Linux 2.4
* Mar 6 20:23:16 user.info kernel: Based upon Swansea University Computer Society NET3.039
* Mar 6 20:23:16 user.warn kernel: Initializing RT netlink socket
* Mar 6 20:23:16 user.warn kernel: Starting kswapd
* Mar 6 20:23:16 user.warn kernel: allocated 32 pages and 32 bhs reserved for the highmem bounces
* Mar 6 20:23:16 user.info kernel: Journalled Block Device driver loaded
* Mar 6 20:23:16 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Mar 6 20:23:16 user.info kernel: devfs: boot_options: 0x1
* Mar 6 20:23:16 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Mar 6 20:23:16 user.info kernel: ACPI: Power Button (FF) [PWRF]
* Mar 6 20:23:16 user.info kernel: ACPI: Fan [FAN] (on)
* Mar 6 20:23:16 user.info kernel: ACPI: Processor [CPU0] (supports C1)
* Mar 6 20:23:16 user.info kernel: ACPI: Processor [CPU1] (supports C1)
* Mar 6 20:23:16 user.info kernel: ACPI: Thermal Zone [THRM] (40 C)
* Mar 6 20:23:16 user.warn kernel: pty: 256 Unix98 ptys configured
* Mar 6 20:23:16 user.info kernel: Real Time Clock Driver v1.10f
* Mar 6 20:23:16 user.info kernel: Floppy drive(s): fd0 is 1.44M
* Mar 6 20:23:16 user.info kernel: FDC 0 is a post-1991 82077
* Mar 6 20:23:16 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
* Mar 6 20:23:16 user.info kernel: loop: loaded (max 8 devices)
* Mar 6 20:23:16 user.info kernel: Intel(R) PRO/1000 Network Driver - version 7.3.20-k4
* Mar 6 20:23:16 user.info kernel: Copyright (c) 1999-2006 Intel Corporation.
* Mar 6 20:23:16 user.info kernel: dgrs: SW=$Id: dgrs.c,v 1.13 2000/06/06 04:07:00 rick Exp $ FW=Build 550 11/16/96 03:45:15
* Mar 6 20:23:16 user.warn kernel: FW Version=$Version$
* Mar 6 20:23:16 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Mar 6 20:23:16 user.info kernel: ThunderLAN driver v1.15
* Mar 6 20:23:16 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
* Mar 6 20:23:16 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Mar 6 20:23:16 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Mar 6 20:23:16 user.warn kernel: sk98lin: No adapter found.
* Mar 6 20:23:16 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Mar 6 20:23:16 user.debug kernel: PCI: Setting latency timer of device 00:11.0 to 64
* Mar 6 20:23:16 user.info kernel: eth0: forcedeth.c: subsystem: 01043:81fb bound to 00:11.0
* Mar 6 20:23:16 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Mar 6 20:23:16 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Mar 6 20:23:16 user.info kernel: NFORCE-MCP55: IDE controller at PCI slot 00:0c.0
* Mar 6 20:23:16 user.info kernel: NFORCE-MCP55: chipset revision 161
* Mar 6 20:23:16 user.info kernel: NFORCE-MCP55: not 100% native mode: will probe irqs later
* Mar 6 20:23:16 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Mar 6 20:23:16 user.info kernel: NFORCE-MCP55: 00:0c.0 (rev a1) UDMA133 controller
* Mar 6 20:23:16 user.info kernel: NFORCE-MCP55: neither IDE port enabled (BIOS)
* Mar 6 20:23:16 user.info kernel: SCSI subsystem driver Revision: 1.00
* Mar 6 20:23:16 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
* Mar 6 20:23:16 user.info kernel: Detecting Adaptec I2O RAID controllers.
* Mar 6 20:23:16 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Aug 12 2007 09:05:44)
* Mar 6 20:23:16 user.warn kernel: scsi: Detection failed (no card)
* Mar 6 20:23:16 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Mar 6 20:23:16 user.notice kernel: megaraid: found 0x1000:0x1960:bus 4:slot 1:func 0
* Mar 6 20:23:16 user.notice kernel: scsi1:Found MegaRAID controller at 0xf8814000, IRQ:11
* Mar 6 20:23:16 user.notice kernel: megaraid: [713S:G121] detected 1 logical drives.
* Mar 6 20:23:16 user.notice kernel: megaraid: supports extended CDBs.
* Mar 6 20:23:16 user.info kernel: megaraid: channel[0] is raid.
* Mar 6 20:23:16 user.info kernel: scsi1 : LSI Logic MegaRAID 713S 254 commands 16 targs 4 chans 7 luns
* Mar 6 20:23:16 user.notice kernel: scsi1: scanning scsi channel 0 for logical drives.
* Mar 6 20:23:16 user.warn kernel: Vendor: MegaRAID Model: LD 0 RAID5 715G Rev: 713S
* Mar 6 20:23:16 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
* Mar 6 20:23:16 user.notice kernel: scsi1: scanning scsi channel 1 for logical drives.
* Mar 6 20:23:16 user.notice kernel: scsi1: scanning scsi channel 2 for logical drives.
* Mar 6 20:23:16 user.notice kernel: scsi1: scanning scsi channel 3 for logical drives.
* Mar 6 20:23:16 user.notice kernel: scsi1: scanning scsi channel 4 [P0] for physical devices.
* Mar 6 20:23:16 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Mar 6 20:23:16 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
* Mar 6 20:23:16 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
* Mar 6 20:23:16 user.warn kernel: 3w-xxxx: No cards found.
* Mar 6 20:23:16 user.debug kernel: libata version 1.20 loaded.
* Mar 6 20:23:16 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
* Mar 6 20:23:16 user.warn kernel: SCSI device sda: 1465159680 512-byte hdwr sectors (750162 MB)
* Mar 6 20:23:16 user.info kernel: Partition check:
* Mar 6 20:23:16 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
* Mar 6 20:23:16 user.info kernel: raw1394: /dev/raw1394 device initialized
* Mar 6 20:23:16 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
* Mar 6 20:23:16 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Mar 6 20:23:16 user.info kernel: usb.c: registered new driver usbdevfs
* Mar 6 20:23:16 user.info kernel: usb.c: registered new driver hub
* Mar 6 20:23:16 user.debug kernel: PCI: Setting latency timer of device 00:0a.1 to 64
* Mar 6 20:23:16 user.info kernel: ehci_hcd 00:0a.1: PCI device 10de:036d
* Mar 6 20:23:16 user.info kernel: ehci_hcd 00:0a.1: irq 11, pci mem f8818000
* Mar 6 20:23:16 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
* Mar 6 20:23:16 user.debug kernel: PCI: cache line size of 64 is not supported by device 00:0a.1
* Mar 6 20:23:16 user.info kernel: ehci_hcd 00:0a.1: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
* Mar 6 20:23:16 user.info kernel: hub.c: USB hub found
* Mar 6 20:23:16 user.info kernel: hub.c: 10 ports detected
* Mar 6 20:23:16 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Mar 6 20:23:16 user.debug kernel: PCI: Setting latency timer of device 00:0a.0 to 64
* Mar 6 20:23:16 user.info kernel: host/usb-ohci.c: USB OHCI at membase 0xf881a000, IRQ 7
* Mar 6 20:23:16 user.info kernel: host/usb-ohci.c: usb-00:0a.0, PCI device 10de:036c
* Mar 6 20:23:16 user.info kernel: usb.c: new USB bus registered, assigned bus number 2
* Mar 6 20:23:16 user.info kernel: hub.c: USB hub found
* Mar 6 20:23:16 user.info kernel: hub.c: 10 ports detected
* Mar 6 20:23:16 user.info kernel: usb.c: registered new driver usbkbd
* Mar 6 20:23:16 user.info kernel: usbkbd.c: :USB HID Boot Protocol keyboard driver
* Mar 6 20:23:16 user.info kernel: Initializing USB Mass Storage driver.
* Mar 6 20:23:16 user.info kernel: usb.c: registered new driver usb-storage
* Mar 6 20:23:16 user.info kernel: USB Mass Storage support registered.
* Mar 6 20:23:16 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
* Mar 6 20:23:16 user.info kernel: IP Protocols: ICMP, UDP, TCP
* Mar 6 20:23:16 user.info kernel: IP: routing cache hash table of 16384 buckets, 128Kbytes
* Mar 6 20:23:16 user.info kernel: TCP: Hash tables configured (established 262144 bind 65536)
* Mar 6 20:23:16 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Mar 6 20:23:16 user.notice kernel: RAMDISK: NASLite file system found at block 0
* Mar 6 20:23:16 user.warn kernel: <6>hub.c: new USB device 00:0a.1-2, assigned address 2
* Mar 6 20:23:16 user.warn kernel: .<6>scsi2 : SCSI emulation for USB Mass Storage devices
* Mar 6 20:23:16 user.warn kernel: . Vendor: Generic Model: USB Flash Drive Rev: 1.00
* Mar 6 20:23:16 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
* Mar 6 20:23:16 user.warn kernel: Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
* Mar 6 20:23:16 user.warn kernel: -byte hdwr sectors (268 MB)
* Mar 6 20:23:16 user.warn kernel: .sdb: Write Protect is off
* Mar 6 20:23:16 user.info kernel: /dev/scsi/host2/bus0/target0/lun0: unknown partition table
* Mar 6 20:23:16 user.debug kernel: WARNING: USB Mass Storage data integrity not assured
* Mar 6 20:23:16 user.debug kernel: USB Mass Storage device found at 2
* Mar 6 20:23:16 user.warn kernel: <6>Freeing initrd memory: 1962k freed
* Mar 6 20:23:16 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
* Mar 6 20:23:16 user.warn kernel: VFS: Mounted root (ext2 filesystem).
* Mar 6 20:23:16 user.info kernel: Mounted devfs on /dev
* Mar 6 20:23:16 user.info kernel: Freeing unused kernel memory: 540k freed
* Mar 6 20:23:16 user.info kernel: kjournald starting. Commit interval 5 seconds
* Mar 6 20:23:16 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
* Mar 6 20:23:16 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.


As a reference this guy is getting 200+MB/s reads on his software based RAID5 with 4 similiar drives.. ? Perhaps I'm comparing pears with apples here?


Top
 Profile  
 
PostPosted: Thu Mar 06, 2008 7:26 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1681
Location: Up State NY in the USA!!!!
Keep in mind that the numbers are on the local machine. If you look at those I am getting on my Vista box with software RAID they are fairly consistent with his.

You may just be running into issues with drivers being poorly written and regardless of the hardware it will not perform better than it is now.

Mike


Top
 Profile  
 
PostPosted: Fri Mar 07, 2008 1:48 am 
Offline

Joined: Sun Sep 24, 2006 1:32 pm
Posts: 290
Well it's not likely to be a driver issue as Ralph used the very same drivers for his card when doing the Passmark benchmarks found here:
viewtopic.php?f=8&t=1224&start=0&st=0&sk=t&sd=a&hilit=numbers

If anyone with a raid 5 consisting of 4 drives could post some diskwriggler numbers I'd appreciate it a lot!


Top
 Profile  
 
PostPosted: Fri Mar 07, 2008 4:47 am 
Offline

Joined: Fri Jan 12, 2007 4:27 am
Posts: 577
Location: Scotland
I did - in the "strange behaviour" thread in the CDD forum.... ;)


Top
 Profile  
 
PostPosted: Fri Mar 07, 2008 5:01 am 
Offline

Joined: Sun Sep 24, 2006 1:32 pm
Posts: 290
Hehe yeah I did see this although its hard to compare your himalayan values dipping from 0.4MB/s and reaching up to 65MB/s! :)


Top
 Profile  
 
PostPosted: Sun Mar 09, 2008 4:08 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
I'm running a RAID 5 setup with 5 HDD's, and i'm too embarrassed to post my results. I'm also using an LSI card. I think it's probably my network not up to scratch. I'll be replacing my 8 port 100 meg switch with a Netgear 24 port Gigabit switch (a bit over the top i know, but it was cheap) and renewing a lot of the cabling, so i'll see if it improves.
That said i've never had any problem playing video over the network, so it probably won't make much difference until i start playing HD material.


Top
 Profile  
 
PostPosted: Mon Mar 10, 2008 12:36 am 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1681
Location: Up State NY in the USA!!!!
Save your money on the cables, if the runs are short CAT5 will be more than fine. On the longer runs CAT5e is recommended, say 5 meters and up. CAT6 will not really get you anything but a thinner wallet. All the cables do need to be 4 pair though.

Mike


Top
 Profile  
 
PostPosted: Mon Mar 10, 2008 8:24 am 
Offline

Joined: Sun Sep 24, 2006 1:32 pm
Posts: 290
willsy wrote:
I'm running a RAID 5 setup with 5 HDD's, and i'm too embarrassed to post my results. I'm also using an LSI card. I think it's probably my network not up to scratch. I'll be replacing my 8 port 100 meg switch with a Netgear 24 port Gigabit switch (a bit over the top i know, but it was cheap) and renewing a lot of the cabling, so i'll see if it improves.
That said i've never had any problem playing video over the network, so it probably won't make much difference until i start playing HD material.


Please post full system specs and numbers, I'll gladly do what I can to help you improve your speed.


Top
 Profile  
 
PostPosted: Mon Mar 10, 2008 4:07 pm 
Offline

Joined: Mon Apr 17, 2006 12:55 pm
Posts: 143
Location: Newcastle
Cheers superboss.

First i'll try running Diskwriggler from my son's computer (when i can get him off it) just in case it was my computer causing the problem.


Top
 Profile  
 
PostPosted: Mon Mar 10, 2008 9:56 pm 
Offline

Joined: Wed Sep 06, 2006 8:54 am
Posts: 28
OK, I had to play along since I spent a few days getting my RAID working worth a plunk.

2.06 HDD on Compact Flash
MSI 915 based board, 2x512MB DDR2
i686 Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel 2702.712 5387.05 256 KB (Presc-hott obviously)
PCI Trident Video
Intel SRCS16 in a 32bit slot with battery- so WriteBack ON
onboard Broadcom DBM5751 PCI-Express Gb LAN Controller
5x 500MB Samsung HD501LJ in RAID5 no spare

old Dlink DGS1024 4port Gigabit rackable brown box switch, cat5 or cat5e short runs

client: vostro200 VistaBasic Core2 E6550 (2.33Ghz) 2GBRAM , added a PCIe Broadcom NetXtreme (don't know the chip)

C:\Users\rm\Desktop\diskWriggler-1.0.1.win32>diskwriggler -NTSC -C -t -n 1000 -o \\airbox\disk-1

File Type : All frames in one container file (699,840,000 bytes).

Writing 1000 x 699840 byte frames into file \\airbox\disk-1/framestream.dat
696 frames in 5.01 secs ==> 139.06 FPS (92.81 MB/s)
304 frames in 2.26 secs ==> 134.33 FPS (89.66 MB/s)
Write Summary : 1000.00 frames in 7.27 secs
: 134.33(min) 137.57(avg) 139.06(max) FPS
: 89.66(min) 91.82(avg) 92.81(max) MB/s

Reading 1000 x 699840 byte frames from file \\airbox\disk-1/framestream.dat
571 frames in 5.00 secs ==> 114.18 FPS (76.20 MB/s)
429 frames in 3.76 secs ==> 114.22 FPS (76.23 MB/s)

Read Summary : 1000.00 frames in 8.76 secs
: 114.18(min) 114.17(avg) 114.22(max) FPS
: 76.20(min) 76.20(avg) 76.23(max) MB/s


C:\Users\rm\Desktop\diskWriggler-1.0.1.win32>diskwriggler -NTSC -C -t -n 2000 -o \\airbox\disk-1

File Type : All frames in one container file (1,399,680,000 bytes).

Writing 2000 x 699840 byte frames into file \\airbox\disk-1/framestream.dat
727 frames in 5.00 secs ==> 145.37 FPS (97.02 MB/s)
544 frames in 5.02 secs ==> 108.41 FPS (72.35 MB/s)
244 frames in 5.00 secs ==> 48.77 FPS (32.55 MB/s)
337 frames in 5.00 secs ==> 67.36 FPS (44.96 MB/s)
148 frames in 2.23 secs ==> 66.25 FPS (44.22 MB/s)

Write Summary : 2000.00 frames in 22.26 secs
: 48.77(min) 89.83(avg) 145.37(max) FPS
: 32.55(min) 59.96(avg) 97.02(max) MB/s

Reading 2000 x 699840 byte frames from file \\airbox\disk-1/framestream.dat
7 frames in 5.17 secs ==> 1.35 FPS (0.90 MB/s)
90 frames in 5.02 secs ==> 17.94 FPS (11.98 MB/s)
153 frames in 5.02 secs ==> 30.48 FPS (20.34 MB/s)
179 frames in 5.02 secs ==> 35.64 FPS (23.79 MB/s)
176 frames in 5.02 secs ==> 35.05 FPS (23.39 MB/s)
170 frames in 5.32 secs ==> 31.98 FPS (21.35 MB/s)
84 frames in 5.03 secs ==> 16.71 FPS (11.15 MB/s)
149 frames in 5.01 secs ==> 29.73 FPS (19.85 MB/s)
175 frames in 5.01 secs ==> 34.94 FPS (23.32 MB/s)
169 frames in 5.04 secs ==> 33.52 FPS (22.37 MB/s)
179 frames in 5.04 secs ==> 35.54 FPS (23.72 MB/s)
176 frames in 5.00 secs ==> 35.17 FPS (23.47 MB/s)
178 frames in 5.04 secs ==> 35.29 FPS (23.55 MB/s)
115 frames in 3.22 secs ==> 35.69 FPS (23.82 MB/s)

Read Summary : 2000.00 frames in 68.98 secs
: 1.35(min) 28.99(avg) 35.69(max) FPS
: 0.90(min) 19.35(avg) 23.82(max) MB/s


So obviously a flawed test.
NASlite RAM caching works! ... so the test _has_ to write past the RAM. Then it's read immediately back while the write is finishing.... well, the end result is still about there. I get around 25MBps reading typically. Strange, since it writes quite well.
FYI, with the SATA adaptecs, megaraids, and the SRCS16 (megaraid 1.6) you'll get 8MBps writing without the battery and disk caching off. 16MBps with disk caching on, and then finally good writing with the battery and writeback ON. There needs to be a hack for enabling writeback without the battery. Um, haven't they heard of UPS's ??

Guys, no more talk of obsessing over processors, I was happily running this RAID on a P3 800 setup with the SAME speeds!


Top
 Profile  
 
PostPosted: Tue Mar 11, 2008 1:07 am 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1681
Location: Up State NY in the USA!!!!
avldwx wrote:
.....Guys, no more talk of obsessing over processors, I was happily running this RAID on a P3 800 setup with the SAME speeds!


I have said that may times but they still think that a faster processor will mean faster transfers. NAS takes VERY LITTLE in the way of processor horse power. A PIII 400 with 512MB of RAM will be more than enough for a gigabit card. I simply have given all of my older boards to others so they can make NAS boxes and so use a P4 I have laying around. Don't get all tied up with the fastest processors, spend it on the HDD and a good RAID controller.

Mike


Top
 Profile  
 
PostPosted: Wed Mar 12, 2008 10:26 am 
Offline

Joined: Sun Sep 24, 2006 1:32 pm
Posts: 290
Since I've replaced pretty much everything in my box besides the drives and the raid card I guess its time to replace the raid card as well :S The "cached" numbers posted by avldwx makes me wanna cry when I look at the numbers I'm getting :cry:

How would I go about benchmarking the same setup using Ubuntu? I know how to get it installed on an USB key but not sure how to deal with the data on my drives?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 50 posts ]  Go to page Previous  1, 2, 3, 4  Next

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group