NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Sat Apr 27, 2024 6:47 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 15 posts ] 
Author Message
 Post subject: bad performance
PostPosted: Mon Oct 12, 2009 7:25 pm 
Offline

Joined: Mon Oct 12, 2009 7:17 pm
Posts: 42
Location: Munich, Germany
Hi,
today I did the upgrade from naslite SMB to naslite-M2.
I hoped to get an improved read/write performance by this, but unfortunately there is no big difference. The transfer rate for read and write is around 400kB/s. Before it was ~350.
The server is a Piii 800MHz with 640MB RAM, 4x IDE HDD, sizes between 20GB and 320GB. I use the first HDD as boot device. With naslite SMB it was a floppy.
I already searched the forum and correspondingly tried to switch the PCI slots for the NIC (3C905B-TX) and to disable everything in the BIOS which is not needed. Nothing really helped. I cannot tell exactly the root cause for the observed improvement from 350 to 400. Has it been the SMB-to-M2-upgrade or any of the other changes/settings described above...? I don't know. Anyway, it's not that much. I would appreciate a factor of 10 or so :D
So, 400kB/s is ~3.2Mb/s (correct?!) which is far below the theoretical 100Mb/s of my network.
I have only CAT5E and CAT6 cables, the switch is a 3COM 16x 10/100. 4 computers attached to the switch.
I copied several big files between my different computers in order to check the performance. Roughly estimated the transfer speed between any of my other computers is around a factor of 10 higher than to and from the naslite-M2.
Is there anything like a "performance improvement manual" ?
Any additional tip would be helpful.
Thanks a lot in advance

Additional information:
while copying files naslite-M2 concurrently gives the following error message:
# Oct 13 01:14:04 [4] hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
# Oct 13 01:14:04 [4] hdc: drive_cmd: error=0x04 { DriveStatusError }
so far several hundred times I guess


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Mon Oct 12, 2009 8:40 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
I have had a number of machines that no mater what I tried I could not get them to run in a satisfactory fashion and had to abandon the MB. You fail to mention the maker of the MB. Also, have you looked to see if the NIC in the NL server is running full duplex? Have you tried just a NAS to client connection via a cable? Most modern NICs are MDI/MDIX and don't require a cross over cable to give this a try, it eliminates all the variables between. Make sure the cable is greater than 1 Meter, preferably 2 and is tested good.

Try this and post back.

Mike


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Mon Oct 12, 2009 9:45 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:01 pm
Posts: 801
Location: ServerElements
Post your syslog, probably a IRQ conflict. And possibly a bad drive.


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Tue Oct 13, 2009 3:16 am 
Offline

Joined: Mon Oct 12, 2009 7:17 pm
Posts: 42
Location: Munich, Germany
Hi folks,

thanks for the quick reply. I'll try to do everything you suggested and will come back to you this evening.

The two lines at the bottom in my last mail are from the syslog. As mentioned, I get the identical message a lot of times. It seems that NL brings up this message for every packet which is copied to that disk.
I also tried to transfer the files via ftp (Filezilla on XP) but not any difference.
And another information: naslite SMB was running before on a different machine (Pii 350MHZ). The performance was the same there. So I did not get any improvement so far neither by changing the MB nor by upgrading to NL-M2... :(

So, I'll do my very best to follow your advice :)

Ok, the rest of the log I will post tonight. Additionaly, I'll also remove one of the disks because it is an even older one than the others and I just connected it in order to get the data to a new disk. And I'll try to directly connect another PC.

Thx


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Tue Oct 13, 2009 12:34 pm 
Offline

Joined: Mon Oct 12, 2009 7:17 pm
Posts: 42
Location: Munich, Germany
Now, here is more info:

    1. I was able to solve a IRQ conflict between the AGP adapter and the NIC. Both was set to 11, now the AGP is set to disabled, at least at boot. I don't know how it is handled now because the AGPcard is the only graphic adapter in my system and I definitively still see something on the screen... :?
    Anyway, there was no effect to the performance.

    2. I tried to directly connect the NL-M2 (3C905B-TX) to my Thinkpad T41 with a normal patch cable (CAT5E). It did not work. I did not get any connection. Seems that I need twisted pair for such a test or what do think?

    4. I switched on the journaling for all 4 disks


Finally, here is the syslog. There is an error message regarding "serialize io". What does it mean?

* Oct 13 18:29:30 [3] klogd started: BusyBox v1.01 (2008.07.26-02:54+0000)
* Oct 13 18:29:30 [4] Linux version 2.4.37.NASLite (root@tzt) (gcc version 3.4.6) #2 Mon Jan 12 23:05:48 EST 2009
* Oct 13 18:29:30 [2] BIOS-provided physical RAM map:
* Oct 13 18:29:30 [4] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
* Oct 13 18:29:30 [4] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* Oct 13 18:29:30 [4] BIOS-e820: 0000000000100000 - 0000000027ff0000 (usable)
* Oct 13 18:29:30 [4] BIOS-e820: 0000000027ff0000 - 0000000027ff3000 (ACPI NVS)
* Oct 13 18:29:30 [4] BIOS-e820: 0000000027ff3000 - 0000000028000000 (ACPI data)
* Oct 13 18:29:30 [4] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
* Oct 13 18:29:30 [3] 0MB HIGHMEM available.
* Oct 13 18:29:30 [3] 639MB LOWMEM available.
* Oct 13 18:29:30 [4] On node 0 totalpages: 163824
* Oct 13 18:29:30 [4] zone(0): 4096 pages.
* Oct 13 18:29:30 [4] zone(1): 159728 pages.
* Oct 13 18:29:30 [4] zone(2): 0 pages.
* Oct 13 18:29:30 [3] ACPI disabled because your bios is from 1999 and too old
* Oct 13 18:29:30 [3] You can enable it with acpi=force
* Oct 13 18:29:30 [4] Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
* Oct 13 18:29:30 [4] No local APIC present or hardware disabled
* Oct 13 18:29:30 [2] Initializing CPU#0
* Oct 13 18:29:30 [4] Detected 799.708 MHz processor.
* Oct 13 18:29:30 [4] Console: colour VGA+ 80x25
* Oct 13 18:29:30 [4] Calibrating delay loop. 1595.80 BogoMIPS
* Oct 13 18:29:30 [2] Memory: 639212k/655296k available (2326k kernel code, 15700k reserved, 684k data, 560k init, 0k highmem)
* Oct 13 18:29:30 [2] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Oct 13 18:29:30 [2] Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
* Oct 13 18:29:30 [2] Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Oct 13 18:29:30 [2] Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
* Oct 13 18:29:30 [4] Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
* Oct 13 18:29:30 [2] CPU: L1 I cache: 16K, L1 D cache: 16K
* Oct 13 18:29:30 [2] CPU: L2 cache: 256K
* Oct 13 18:29:30 [3] CPU serial number disabled.
* Oct 13 18:29:30 [2] Intel machine check architecture supported.
* Oct 13 18:29:30 [2] Intel machine check reporting enabled on CPU#0.
* Oct 13 18:29:30 [1] CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
* Oct 13 18:29:30 [1] CPU: Common caps: 0383f9ff 00000000 00000000 00000000
* Oct 13 18:29:30 [4] CPU: Intel Pentium III (Coppermine) stepping 03
* Oct 13 18:29:30 [2] Enabling fast FPU save and restore. done.
* Oct 13 18:29:30 [2] Enabling unmasked SIMD FPU exception support. done.
* Oct 13 18:29:30 [2] Checking 'hlt' instruction. OK.
* Oct 13 18:29:30 [4] POSIX conformance testing by UNIFIX
* Oct 13 18:29:30 [4] mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
* Oct 13 18:29:30 [4] mtrr: detected mtrr type: Intel
* Oct 13 18:29:30 [2] ACPI: Subsystem revision 20040326
* Oct 13 18:29:30 [2] ACPI: Interpreter disabled.
* Oct 13 18:29:30 [2] PCI: PCI BIOS revision 2.10 entry at 0xfb0e0, last bus=1
* Oct 13 18:29:30 [2] PCI: Using configuration type 1
* Oct 13 18:29:30 [2] PCI: Probing PCI hardware
* Oct 13 18:29:30 [4] PCI: Probing PCI hardware (bus 00)
* Oct 13 18:29:30 [2] PCI: Via IRQ fixup
* Oct 13 18:29:30 [2] PCI: Using IRQ router VIA [1106/0596] at 00:07.0
* Oct 13 18:29:30 [2] Activating ISA DMA hang workarounds.
* Oct 13 18:29:30 [2] Linux NET4.0 for Linux 2.4
* Oct 13 18:29:30 [2] Based upon Swansea University Computer Society NET3.039
* Oct 13 18:29:30 [4] Initializing RT netlink socket
* Oct 13 18:29:30 [4] Starting kswapd
* Oct 13 18:29:30 [2] Journalled Block Device driver loaded
* Oct 13 18:29:30 [2] devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Oct 13 18:29:30 [2] devfs: boot_options: 0x1
* Oct 13 18:29:30 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Oct 13 18:29:30 [4] pty: 256 Unix98 ptys configured
* Oct 13 18:29:30 [2] Real Time Clock Driver v1.10f
* Oct 13 18:29:30 [2] Floppy drive(s): fd0 is 1.44M
* Oct 13 18:29:30 [4] floppy0: no floppy controllers found
* Oct 13 18:29:30 [4] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
* Oct 13 18:29:30 [2] loop: loaded (max 8 devices)
* Oct 13 18:29:30 [2] Intel(R) PRO/1000 Network Driver - version 7.3.20-k4
* Oct 13 18:29:30 [2] Copyright (c) 1999-2006 Intel Corporation.
* Oct 13 18:29:30 [2] 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
* Oct 13 18:29:30 [4] FW Version=$Version$
* Oct 13 18:29:30 [2] PCI: Found IRQ 11 for device 00:0e.0
* Oct 13 18:29:30 [4] 3c59x: Donald Becker and others. http://www.scyld.com/network/vortex.html
* Oct 13 18:29:30 [2] 00:0e.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xe800. Vers LK1.1.18
* Oct 13 18:29:30 [2] pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Oct 13 18:29:30 [2] ThunderLAN driver v1.15
* Oct 13 18:29:30 [2] TLAN: 0 devices installed, PCI: 0 EISA: 0
* Oct 13 18:29:30 [2] dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Oct 13 18:29:30 [2] ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Oct 13 18:29:30 [4] sk98lin: No adapter found.
* Oct 13 18:29:30 [2] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Oct 13 18:29:30 [2] Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Oct 13 18:29:30 [2] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Oct 13 18:29:30 [2] VP_IDE: IDE controller at PCI slot 00:07.1
* Oct 13 18:29:30 [2] VP_IDE: chipset revision 16
* Oct 13 18:29:30 [2] VP_IDE: not 100% native mode: will probe irqs later
* Oct 13 18:29:30 [2] ng 33MHz system bus speed for PIO modes; override with idebus=xx
* Oct 13 18:29:30 [2] VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
* Oct 13 18:29:30 [2] ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
* Oct 13 18:29:30 [2] ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
* Oct 13 18:29:30 [4] hda: WDC WD205AA-00BAA0, ATA DISK drive
* Oct 13 18:29:30 [4] hdb: WDC WD3200AAJB-00J3A0, ATA DISK drive
* Oct 13 18:29:30 [4] hdc: IBM-DTLA-307030, ATA DISK drive
* Oct 13 18:29:30 [4] hdd: SAMSUNG SP2514N, ATA DISK drive
* Oct 13 18:29:30 [4] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Oct 13 18:29:30 [4] ide1 at 0x170-0x177,0x376 on irq 15
* Oct 13 18:29:30 [4] hda: attached ide-disk driver.
* Oct 13 18:29:30 [4] hda: host protected area => 1
* Oct 13 18:29:30 [2] hda: 40079088 sectors (20520 MB) w/2048KiB Cache, CHS=2494/255/63, UDMA(66)
* Oct 13 18:29:30 [4] hdb: attached ide-disk driver.
* Oct 13 18:29:30 [4] hdb: host protected area => 1
* Oct 13 18:29:30 [2] hdb: 625142448 sectors (320073 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(66)
* Oct 13 18:29:30 [4] hdc: attached ide-disk driver.
* Oct 13 18:29:30 [4] hdc: host protected area => 1
* Oct 13 18:29:30 [2] hdc: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(66)
* Oct 13 18:29:30 [4] hdd: attached ide-disk driver.
* Oct 13 18:29:30 [4] hdd: host protected area => 1
* Oct 13 18:29:30 [2] hdd: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(66)
* Oct 13 18:29:30 [2] Partition check:
* Oct 13 18:29:30 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Oct 13 18:29:30 [2] /dev/ide/host0/bus0/target1/lun0: p1
* Oct 13 18:29:30 [2] /dev/ide/host0/bus1/target0/lun0:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [2] hdd: DMA disabled
* Oct 13 18:29:30 [4] ide1: reset: success
* Oct 13 18:29:30 [4] p1
* Oct 13 18:29:30 [2] /dev/ide/host0/bus1/target1/lun0: p1
* Oct 13 18:29:30 [2] SCSI subsystem driver Revision: 1.00
* Oct 13 18:29:30 [2] Loading Adaptec I2O RAID: Version 2.4 Build 5
* Oct 13 18:29:30 [2] Detecting Adaptec I2O RAID controllers.
* Oct 13 18:29:30 [2] Red Hat/Adaptec aacraid driver (1.1-3 Jan 12 2009 23:06:00)
* Oct 13 18:29:30 [4] scsi: Detection failed (no card)
* Oct 13 18:29:30 [3] megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Oct 13 18:29:30 [4] GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Oct 13 18:29:30 [4] GDT-HA: Found 0 PCI Storage RAID Controllers
* Oct 13 18:29:30 [2] scsi1 : SCSI host adapter emulation for IDE ATAPI devices
* Oct 13 18:29:30 [4] 3ware Storage Controller device driver for Linux v1.02.00.037.
* Oct 13 18:29:30 [4] 3w-xxxx: No cards found.
* Oct 13 18:29:30 [1] libata version 1.20 loaded.
* Oct 13 18:29:30 [2] raw1394: /dev/raw1394 device initialized
* Oct 13 18:29:30 [2] sbp2: $Rev: 1074 $ Ben Collins
* Oct 13 18:29:30 [5] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Oct 13 18:29:30 [2] usb.c: registered new driver usbdevfs
* Oct 13 18:29:30 [2] usb.c: registered new driver hub
* Oct 13 18:29:30 [2] host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Oct 13 18:29:30 [2] host/uhci.c: USB UHCI at I/O 0xe400, IRQ 10
* Oct 13 18:29:30 [2] usb.c: new USB bus registered, assigned bus number 1
* Oct 13 18:29:30 [2] hub.c: USB hub found
* Oct 13 18:29:30 [2] hub.c: 2 ports detected
* Oct 13 18:29:30 [2] usb.c: registered new driver usbkbd
* Oct 13 18:29:30 [2] usbkbd.c: :USB HID Boot Protocol keyboard driver
* Oct 13 18:29:30 [2] Initializing USB Mass Storage driver.
* Oct 13 18:29:30 [2] usb.c: registered new driver usb-storage
* Oct 13 18:29:30 [2] USB Mass Storage support registered.
* Oct 13 18:29:30 [2] NET4: Linux TCP/IP 1.0 for NET4.0
* Oct 13 18:29:30 [2] IP Protocols: ICMP, UDP, TCP
* Oct 13 18:29:30 [2] IP: routing cache hash table of 8192 buckets, 64Kbytes
* Oct 13 18:29:30 [2] TCP: Hash tables configured (established 262144 bind 65536)
* Oct 13 18:29:30 [2] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Oct 13 18:29:30 [3] RAMDISK: NASLite file system found at block 0
* Oct 13 18:29:30 [4] <6>Freeing initrd memory: 4137k freed
* Oct 13 18:29:30 [4] EXT2-fs warning: checktime reached, running e2fsck is recommended
* Oct 13 18:29:30 [4] VFS: Mounted root (ext2 filesystem).
* Oct 13 18:29:30 [2] Mounted devfs on /dev
* Oct 13 18:29:30 [2] Freeing unused kernel memory: 560k freed
* Oct 13 18:29:30 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] ide1: reset: success
* Oct 13 18:29:30 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 18:29:30 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
* Oct 13 18:29:30 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 13 18:29:30 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 18:29:30 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,65), internal journal
* Oct 13 18:29:30 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 13 18:29:30 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 18:29:30 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
* Oct 13 18:29:30 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 13 18:29:30 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 18:29:30 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,65), internal journal
* Oct 13 18:29:30 [2] EXT3-fs: mounted filesystem with ordered data mode.


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Tue Oct 13, 2009 2:29 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
You need to check jumpers and cables. My bet is your master/slave jumpers are wrong or you are using the wrong cables if you have the jumpers set to CS.

Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 18:29:30 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 18:29:30 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Tue Oct 13, 2009 3:01 pm 
Offline

Joined: Mon Oct 12, 2009 7:17 pm
Posts: 42
Location: Munich, Germany
Tony wrote:
You need to check jumpers and cables. My bet is your master/slave jumpers are wrong or you are using the wrong cables if you have the jumpers set to CS.



I'm pretty sure that the HDD-jumpers are set correctly.
But I'll double-check, thanks for the hint.
Just a dumb question: Master has to be at the end of the cable, slave in the middle, correct (plus the jumpers of course)?

What is the consequence for such an old Piii system when I still use the old 40pin cables?

Any comment to the "serialize io" message?

What do you expect if I buy me an Intel Pro/1000 GT instead of the old 3C905B-TX?

Thx

edit: I made a small change for the ide1-master: before it was set to Master_with_force_slave_present. Now I set it just to Master.
Here is the result:


* Oct 13 21:04:58 [3] klogd started: BusyBox v1.01 (2008.07.26-02:54+0000)
* Oct 13 21:04:58 [4] Linux version 2.4.37.NASLite (root@tzt) (gcc version 3.4.6) #2 Mon Jan 12 23:05:48 EST 2009
* Oct 13 21:04:58 [2] BIOS-provided physical RAM map:
* Oct 13 21:04:58 [4] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
* Oct 13 21:04:58 [4] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* Oct 13 21:04:58 [4] BIOS-e820: 0000000000100000 - 0000000027ff0000 (usable)
* Oct 13 21:04:58 [4] BIOS-e820: 0000000027ff0000 - 0000000027ff3000 (ACPI NVS)
* Oct 13 21:04:58 [4] BIOS-e820: 0000000027ff3000 - 0000000028000000 (ACPI data)
* Oct 13 21:04:58 [4] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
* Oct 13 21:04:58 [3] 0MB HIGHMEM available.
* Oct 13 21:04:58 [3] 639MB LOWMEM available.
* Oct 13 21:04:58 [4] On node 0 totalpages: 163824
* Oct 13 21:04:58 [4] zone(0): 4096 pages.
* Oct 13 21:04:58 [4] zone(1): 159728 pages.
* Oct 13 21:04:58 [4] zone(2): 0 pages.
* Oct 13 21:04:58 [3] ACPI disabled because your bios is from 1999 and too old
* Oct 13 21:04:58 [3] You can enable it with acpi=force
* Oct 13 21:04:58 [4] Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
* Oct 13 21:04:58 [4] No local APIC present or hardware disabled
* Oct 13 21:04:58 [2] Initializing CPU#0
* Oct 13 21:04:58 [4] Detected 799.711 MHz processor.
* Oct 13 21:04:58 [4] Console: colour VGA+ 80x25
* Oct 13 21:04:58 [4] Calibrating delay loop. 1595.80 BogoMIPS
* Oct 13 21:04:58 [2] Memory: 639212k/655296k available (2326k kernel code, 15700k reserved, 684k data, 560k init, 0k highmem)
* Oct 13 21:04:58 [2] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Oct 13 21:04:58 [2] Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
* Oct 13 21:04:58 [2] Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Oct 13 21:04:58 [2] Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
* Oct 13 21:04:58 [4] Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
* Oct 13 21:04:58 [2] CPU: L1 I cache: 16K, L1 D cache: 16K
* Oct 13 21:04:58 [2] CPU: L2 cache: 256K
* Oct 13 21:04:58 [3] CPU serial number disabled.
* Oct 13 21:04:58 [2] Intel machine check architecture supported.
* Oct 13 21:04:58 [2] Intel machine check reporting enabled on CPU#0.
* Oct 13 21:04:58 [1] CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
* Oct 13 21:04:58 [1] CPU: Common caps: 0383f9ff 00000000 00000000 00000000
* Oct 13 21:04:58 [4] CPU: Intel Pentium III (Coppermine) stepping 03
* Oct 13 21:04:58 [2] Enabling fast FPU save and restore. done.
* Oct 13 21:04:58 [2] Enabling unmasked SIMD FPU exception support. done.
* Oct 13 21:04:58 [2] Checking 'hlt' instruction. OK.
* Oct 13 21:04:58 [4] POSIX conformance testing by UNIFIX
* Oct 13 21:04:58 [4] mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
* Oct 13 21:04:58 [4] mtrr: detected mtrr type: Intel
* Oct 13 21:04:58 [2] ACPI: Subsystem revision 20040326
* Oct 13 21:04:58 [2] ACPI: Interpreter disabled.
* Oct 13 21:04:58 [2] PCI: PCI BIOS revision 2.10 entry at 0xfb0e0, last bus=1
* Oct 13 21:04:58 [2] PCI: Using configuration type 1
* Oct 13 21:04:58 [2] PCI: Probing PCI hardware
* Oct 13 21:04:58 [4] PCI: Probing PCI hardware (bus 00)
* Oct 13 21:04:58 [2] PCI: Via IRQ fixup
* Oct 13 21:04:58 [2] PCI: Using IRQ router VIA [1106/0596] at 00:07.0
* Oct 13 21:04:58 [2] Activating ISA DMA hang workarounds.
* Oct 13 21:04:58 [2] Linux NET4.0 for Linux 2.4
* Oct 13 21:04:58 [2] Based upon Swansea University Computer Society NET3.039
* Oct 13 21:04:58 [4] Initializing RT netlink socket
* Oct 13 21:04:58 [4] Starting kswapd
* Oct 13 21:04:58 [2] Journalled Block Device driver loaded
* Oct 13 21:04:58 [2] devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Oct 13 21:04:58 [2] devfs: boot_options: 0x1
* Oct 13 21:04:58 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Oct 13 21:04:58 [4] pty: 256 Unix98 ptys configured
* Oct 13 21:04:58 [2] Real Time Clock Driver v1.10f
* Oct 13 21:04:58 [2] Floppy drive(s): fd0 is 1.44M<4>keyboard: Timeout - AT keyboard not present?(ed)
* Oct 13 21:04:58 [4] keyboard: Timeout - AT keyboard not present?(f4)
* Oct 13 21:04:58 [4]
* Oct 13 21:04:58 [4] floppy0: no floppy controllers found
* Oct 13 21:04:58 [4] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
* Oct 13 21:04:58 [2] loop: loaded (max 8 devices)
* Oct 13 21:04:58 [2] Intel(R) PRO/1000 Network Driver - version 7.3.20-k4
* Oct 13 21:04:58 [2] Copyright (c) 1999-2006 Intel Corporation.
* Oct 13 21:04:58 [2] 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
* Oct 13 21:04:58 [4] FW Version=$Version$
* Oct 13 21:04:58 [2] PCI: Found IRQ 11 for device 00:0e.0
* Oct 13 21:04:58 [4] 3c59x: Donald Becker and others. http://www.scyld.com/network/vortex.html
* Oct 13 21:04:58 [2] 00:0e.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xe800. Vers LK1.1.18
* Oct 13 21:04:58 [2] pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Oct 13 21:04:58 [2] ThunderLAN driver v1.15
* Oct 13 21:04:58 [2] TLAN: 0 devices installed, PCI: 0 EISA: 0
* Oct 13 21:04:58 [2] dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Oct 13 21:04:58 [2] ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Oct 13 21:04:58 [4] sk98lin: No adapter found.
* Oct 13 21:04:58 [2] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Oct 13 21:04:58 [2] Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Oct 13 21:04:58 [2] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Oct 13 21:04:58 [2] 0:07.1
* Oct 13 21:04:58 [2] VP_IDE: chipset revision 16
* Oct 13 21:04:58 [2] VP_IDE: not 100% native mode: will probe irqs later
* Oct 13 21:04:58 [2] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Oct 13 21:04:58 [2] VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
* Oct 13 21:04:58 [2] ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
* Oct 13 21:04:58 [2] ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
* Oct 13 21:04:58 [4] hda: WDC WD205AA-00BAA0, ATA DISK drive
* Oct 13 21:04:58 [4] hdb: WDC WD3200AAJB-00J3A0, ATA DISK drive
* Oct 13 21:04:58 [4] hdc: IBM-DTLA-307030, ATA DISK drive
* Oct 13 21:04:58 [4] hdd: SAMSUNG SP2514N, ATA DISK drive
* Oct 13 21:04:58 [4] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Oct 13 21:04:58 [4] ide1 at 0x170-0x177,0x376 on irq 15
* Oct 13 21:04:58 [4] hda: attached ide-disk driver.
* Oct 13 21:04:58 [4] hda: host protected area => 1
* Oct 13 21:04:58 [2] hda: 40079088 sectors (20520 MB) w/2048KiB Cache, CHS=2494/255/63, UDMA(66)
* Oct 13 21:04:58 [4] hdb: attached ide-disk driver.
* Oct 13 21:04:58 [4] hdb: host protected area => 1
* Oct 13 21:04:58 [2] hdb: 625142448 sectors (320073 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(66)
* Oct 13 21:04:58 [4] hdc: attached ide-disk driver.
* Oct 13 21:04:58 [4] hdc: host protected area => 1
* Oct 13 21:04:58 [2] hdc: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(66)
* Oct 13 21:04:58 [4] hdd: attached ide-disk driver.
* Oct 13 21:04:58 [4] hdd: host protected area => 1
* Oct 13 21:04:58 [2] hdd: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(66)
* Oct 13 21:04:58 [2] Partition check:
* Oct 13 21:04:58 [2] /dev/ide/host0/bus0/target0/lun0: p1 p2
* Oct 13 21:04:58 [2] /dev/ide/host0/bus0/target1/lun0: p1
* Oct 13 21:04:58 [2] /dev/ide/host0/bus1/target0/lun0:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [2] hdd: DMA disabled
* Oct 13 21:04:58 [4] ide1: reset: success
* Oct 13 21:04:58 [4] p1
* Oct 13 21:04:58 [2] /dev/ide/host0/bus1/target1/lun0: p1
* Oct 13 21:04:58 [2] SCSI subsystem driver Revision: 1.00
* Oct 13 21:04:58 [2] Loading Adaptec I2O RAID: Version 2.4 Build 5
* Oct 13 21:04:58 [2] Detecting Adaptec I2O RAID controllers.
* Oct 13 21:04:58 [2] Red Hat/Adaptec aacraid driver (1.1-3 Jan 12 2009 23:06:00)
* Oct 13 21:04:58 [4] scsi: Detection failed (no card)
* Oct 13 21:04:58 [3] megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Oct 13 21:04:58 [4] GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Oct 13 21:04:58 [4] GDT-HA: Found 0 PCI Storage RAID Controllers
* Oct 13 21:04:58 [2] scsi1 : SCSI host adapter emulation for IDE ATAPI devices
* Oct 13 21:04:58 [4] 3ware Storage Controller device driver for Linux v1.02.00.037.
* Oct 13 21:04:58 [4] 3w-xxxx: No cards found.
* Oct 13 21:04:58 [1] libata version 1.20 loaded.
* Oct 13 21:04:58 [2] raw1394: /dev/raw1394 device initialized
* Oct 13 21:04:58 [2] sbp2: $Rev: 1074 $ Ben Collins
* Oct 13 21:04:58 [5] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Oct 13 21:04:58 [2] usb.c: registered new driver usbdevfs
* Oct 13 21:04:58 [2] usb.c: registered new driver hub
* Oct 13 21:04:58 [2] host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Oct 13 21:04:58 [2] host/uhci.c: USB UHCI at I/O 0xe400, IRQ 10
* Oct 13 21:04:58 [2] usb.c: new USB bus registered, assigned bus number 1
* Oct 13 21:04:58 [2] hub.c: USB hub found
* Oct 13 21:04:58 [2] hub.c: 2 ports detected
* Oct 13 21:04:58 [2] usb.c: registered new driver usbkbd
* Oct 13 21:04:58 [2] usbkbd.c: :USB HID Boot Protocol keyboard driver
* Oct 13 21:04:58 [2] Initializing USB Mass Storage driver.
* Oct 13 21:04:58 [2] usb.c: registered new driver usb-storage
* Oct 13 21:04:58 [2] USB Mass Storage support registered.
* Oct 13 21:04:58 [2] NET4: Linux TCP/IP 1.0 for NET4.0
* Oct 13 21:04:58 [2] IP Protocols: ICMP, UDP, TCP
* Oct 13 21:04:58 [2] IP: routing cache hash table of 8192 buckets, 64Kbytes
* Oct 13 21:04:58 [2] TCP: Hash tables configured (established 262144 bind 65536)
* Oct 13 21:04:58 [2] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Oct 13 21:04:58 [3] RAMDISK: NASLite file system found at block 0
* Oct 13 21:04:58 [4] [truncated] .<6>Freeing init
* Oct 13 21:04:58 [4] EXT2-fs warning: checktime reached, running e2fsck is recommended
* Oct 13 21:04:58 [4] VFS: Mounted root (ext2 filesystem).
* Oct 13 21:04:58 [2] Mounted devfs on /dev
* Oct 13 21:04:58 [2] Freeing unused kernel memory: 560k freed
* Oct 13 21:04:58 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] ide1: reset: success
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [2] hdb: DMA disabled
* Oct 13 21:04:58 [4] ide0: reset: success
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
* Oct 13 21:04:58 [4] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
* Oct 13 21:04:58 [4] ide0: reset: success
* Oct 13 21:04:58 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 21:04:58 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
* Oct 13 21:04:58 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 13 21:04:58 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 21:04:58 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,65), internal journal
* Oct 13 21:04:58 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 13 21:04:58 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 21:04:58 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
* Oct 13 21:04:58 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 13 21:04:58 [2] kjournald starting. Commit interval 5 seconds
* Oct 13 21:04:58 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,65), internal journal
* Oct 13 21:04:58 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 13 21:04:58 [2] Adding Swap: 1048568k swap-space (priority -1)


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Wed Oct 14, 2009 11:18 am 
Offline

Joined: Mon Sep 11, 2006 10:38 am
Posts: 231
Location: Belleville MI
I don't know but I have a Gigibit card in mine and it's super fast. Saving files to it and getting files from it. So I guess it's just the NIC card being 10/100 not a 10/100/1000. You would have to have it on both ends, a Gigibit networks card with a Gigibit switch. They don't cost a lot now. 2 Gigibit cars about $25 I guess and a 8 port gigabit switch can get for about $40.

Look for the D-Link DGS-2208 I just looked on Google and found it here. for a good price.

I posted in here a good Intel gigibit card with a link to a place that has it for like $10. That one works very good with NASlite. [url=http://www.tekby.com/product_info.php?products_id=831708
]Here is the link I posted.[/url] They have it for a good price and that's were I got my gigibit card that works very good with NASlite.

-Raymond Day


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Wed Oct 14, 2009 12:05 pm 
Offline

Joined: Mon Oct 12, 2009 7:17 pm
Posts: 42
Location: Munich, Germany
Update:

I removed the old HDDs. Now I have just 2 instead 4... however... just 50GB less...

Therefore I had to reinstall the CDROM again and configure NL to save on FDD.

Now I have:
IDE0 Master: disk-0
IDE0 Slave: CDROM
IDE1 Master: disk-1

I also renewed the jumper-settings and exchanged the old 40pin cable for new 40pin cables.

As an effect of all of this, I do not get a DMA-error anymore.
Unfortunately, the transfer speed is still the same: just below 400kB/s = 3.2Mbit/s
As my network should be capable of 100Mbit/s I don't know where the remaining 96.8 are :evil: :?



* Oct 14 15:35:15 [3] klogd started: BusyBox v1.01 (2008.07.26-02:54+0000)
* Oct 14 15:35:15 [4] Linux version 2.4.37.NASLite (root@tzt) (gcc version 3.4.6) #2 Mon Jan 12 23:05:48 EST 2009
* Oct 14 15:35:15 [2] BIOS-provided physical RAM map:
* Oct 14 15:35:15 [4] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
* Oct 14 15:35:15 [4] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
* Oct 14 15:35:15 [4] BIOS-e820: 0000000000100000 - 0000000027ff0000 (usable)
* Oct 14 15:35:15 [4] BIOS-e820: 0000000027ff0000 - 0000000027ff3000 (ACPI NVS)
* Oct 14 15:35:15 [4] BIOS-e820: 0000000027ff3000 - 0000000028000000 (ACPI data)
* Oct 14 15:35:15 [4] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
* Oct 14 15:35:15 [3] 0MB HIGHMEM available.
* Oct 14 15:35:15 [3] 639MB LOWMEM available.
* Oct 14 15:35:15 [4] On node 0 totalpages: 163824
* Oct 14 15:35:15 [4] zone(0): 4096 pages.
* Oct 14 15:35:15 [4] zone(1): 159728 pages.
* Oct 14 15:35:15 [4] zone(2): 0 pages.
* Oct 14 15:35:15 [3] ACPI disabled because your bios is from 1999 and too old
* Oct 14 15:35:15 [3] You can enable it with acpi=force
* Oct 14 15:35:15 [4] Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
* Oct 14 15:35:15 [4] No local APIC present or hardware disabled
* Oct 14 15:35:15 [2] Initializing CPU#0
* Oct 14 15:35:15 [4] Detected 799.703 MHz processor.
* Oct 14 15:35:15 [4] Console: colour VGA+ 80x25
* Oct 14 15:35:15 [4] Calibrating delay loop. 1595.80 BogoMIPS
* Oct 14 15:35:15 [2] Memory: 639212k/655296k available (2326k kernel code, 15700k reserved, 684k data, 560k init, 0k highmem)
* Oct 14 15:35:15 [2] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Oct 14 15:35:15 [2] Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
* Oct 14 15:35:15 [2] Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Oct 14 15:35:15 [2] Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
* Oct 14 15:35:15 [4] Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
* Oct 14 15:35:15 [2] CPU: L1 I cache: 16K, L1 D cache: 16K
* Oct 14 15:35:15 [2] CPU: L2 cache: 256K
* Oct 14 15:35:15 [3] CPU serial number disabled.
* Oct 14 15:35:15 [2] Intel machine check architecture supported.
* Oct 14 15:35:15 [2] Intel machine check reporting enabled on CPU#0.
* Oct 14 15:35:15 [1] CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
* Oct 14 15:35:15 [1] CPU: Common caps: 0383f9ff 00000000 00000000 00000000
* Oct 14 15:35:15 [4] CPU: Intel Pentium III (Coppermine) stepping 03
* Oct 14 15:35:15 [2] Enabling fast FPU save and restore. done.
* Oct 14 15:35:15 [2] Enabling unmasked SIMD FPU exception support. done.
* Oct 14 15:35:15 [2] Checking 'hlt' instruction. OK.
* Oct 14 15:35:15 [4] POSIX conformance testing by UNIFIX
* Oct 14 15:35:15 [4] mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
* Oct 14 15:35:15 [4] mtrr: detected mtrr type: Intel
* Oct 14 15:35:15 [2] ACPI: Subsystem revision 20040326
* Oct 14 15:35:15 [2] ACPI: Interpreter disabled.
* Oct 14 15:35:15 [2] PCI: PCI BIOS revision 2.10 entry at 0xfb0e0, last bus=1
* Oct 14 15:35:15 [2] PCI: Using configuration type 1
* Oct 14 15:35:15 [2] PCI: Probing PCI hardware
* Oct 14 15:35:15 [4] PCI: Probing PCI hardware (bus 00)
* Oct 14 15:35:15 [2] PCI: Via IRQ fixup
* Oct 14 15:35:15 [2] PCI: Using IRQ router VIA [1106/0596] at 00:07.0
* Oct 14 15:35:15 [2] Activating ISA DMA hang workarounds.
* Oct 14 15:35:15 [2] Linux NET4.0 for Linux 2.4
* Oct 14 15:35:15 [2] Based upon Swansea University Computer Society NET3.039
* Oct 14 15:35:15 [4] Initializing RT netlink socket
* Oct 14 15:35:15 [4] Starting kswapd
* Oct 14 15:35:15 [2] Journalled Block Device driver loaded
* Oct 14 15:35:15 [2] devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Oct 14 15:35:15 [2] devfs: boot_options: 0x1
* Oct 14 15:35:15 [2] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Oct 14 15:35:15 [4] pty: 256 Unix98 ptys configured
* Oct 14 15:35:15 [2] Real Time Clock Driver v1.10f
* Oct 14 15:35:15 [2] Floppy drive(s): fd0 is 1.44M
* Oct 14 15:35:15 [2] FDC 0 is a post-1991 82077
* Oct 14 15:35:15 [4] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
* Oct 14 15:35:15 [2] loop: loaded (max 8 devices)
* Oct 14 15:35:15 [2] Intel(R) PRO/1000 Network Driver - version 7.3.20-k4
* Oct 14 15:35:15 [2] Copyright (c) 1999-2006 Intel Corporation.
* Oct 14 15:35:15 [2] 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
* Oct 14 15:35:15 [4] FW Version=$Version$
* Oct 14 15:35:15 [2] PCI: Found IRQ 11 for device 00:10.0
* Oct 14 15:35:15 [4] 3c59x: Donald Becker and others. http://www.scyld.com/network/vortex.html
* Oct 14 15:35:15 [2] 00:10.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xe800. Vers LK1.1.18
* Oct 14 15:35:15 [2] pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Oct 14 15:35:15 [2] ThunderLAN driver v1.15
* Oct 14 15:35:15 [2] TLAN: 0 devices installed, PCI: 0 EISA: 0
* Oct 14 15:35:15 [2] dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Oct 14 15:35:15 [2] ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Oct 14 15:35:15 [4] sk98lin: No adapter found.
* Oct 14 15:35:15 [2] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Oct 14 15:35:15 [2] Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Oct 14 15:35:15 [2] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Oct 14 15:35:15 [2] VP_IDE: IDE controller at PCI slot 00:07.1
* Oct 14 15:35:15 [2] VP_IDE: chipset revision 16
* Oct 14 15:35:15 [2] VP_IDE: not 100% native mode: will probe irqs later
* Oct 14 15:35:15 [2] ystem bus speed for PIO modes; override with idebus=xx
* Oct 14 15:35:15 [2] VP_IDE: VIA vt82c596b (rev 23) IDE UDMA66 controller on pci00:07.1
* Oct 14 15:35:15 [2] ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
* Oct 14 15:35:15 [2] ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
* Oct 14 15:35:15 [4] hda: WDC WD3200AAJB-00J3A0, ATA DISK drive
* Oct 14 15:35:15 [4] hdb: CD-ROM 48X/AKU, ATAPI CD/DVD-ROM drive
* Oct 14 15:35:15 [4] hdc: SAMSUNG SP2514N, ATA DISK drive
* Oct 14 15:35:15 [4] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Oct 14 15:35:15 [4] ide1 at 0x170-0x177,0x376 on irq 15
* Oct 14 15:35:15 [4] hda: attached ide-disk driver.
* Oct 14 15:35:15 [4] hda: host protected area => 1
* Oct 14 15:35:15 [2] hda: 625142448 sectors (320073 MB) w/8192KiB Cache, CHS=38913/255/63, UDMA(33)
* Oct 14 15:35:15 [4] hdc: attached ide-disk driver.
* Oct 14 15:35:15 [4] hdc: host protected area => 1
* Oct 14 15:35:15 [2] hdc: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(33)
* Oct 14 15:35:15 [4] hdb: attached ide-cdrom driver.
* Oct 14 15:35:15 [2] hdb: ATAPI 48X CD-ROM drive, 128kB Cache
* Oct 14 15:35:15 [2] Uniform CD-ROM driver Revision: 3.12
* Oct 14 15:35:15 [2] Partition check:
* Oct 14 15:35:15 [2] /dev/ide/host0/bus0/target0/lun0: p1
* Oct 14 15:35:15 [2] /dev/ide/host0/bus1/target0/lun0: p1
* Oct 14 15:35:15 [2] SCSI subsystem driver Revision: 1.00
* Oct 14 15:35:15 [2] Loading Adaptec I2O RAID: Version 2.4 Build 5
* Oct 14 15:35:15 [2] Detecting Adaptec I2O RAID controllers.
* Oct 14 15:35:15 [2] Red Hat/Adaptec aacraid driver (1.1-3 Jan 12 2009 23:06:00)
* Oct 14 15:35:15 [4] scsi: Detection failed (no card)
* Oct 14 15:35:15 [3] megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Oct 14 15:35:15 [4] GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Oct 14 15:35:15 [4] GDT-HA: Found 0 PCI Storage RAID Controllers
* Oct 14 15:35:15 [2] scsi1 : SCSI host adapter emulation for IDE ATAPI devices
* Oct 14 15:35:15 [4] 3ware Storage Controller device driver for Linux v1.02.00.037.
* Oct 14 15:35:15 [4] 3w-xxxx: No cards found.
* Oct 14 15:35:15 [1] libata version 1.20 loaded.
* Oct 14 15:35:15 [2] raw1394: /dev/raw1394 device initialized
* Oct 14 15:35:15 [2] sbp2: $Rev: 1074 $ Ben Collins
* Oct 14 15:35:15 [5] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Oct 14 15:35:15 [2] usb.c: registered new driver usbdevfs
* Oct 14 15:35:15 [2] usb.c: registered new driver hub
* Oct 14 15:35:15 [2] host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Oct 14 15:35:15 [2] host/uhci.c: USB UHCI at I/O 0xe400, IRQ 10
* Oct 14 15:35:15 [2] usb.c: new USB bus registered, assigned bus number 1
* Oct 14 15:35:15 [2] hub.c: USB hub found
* Oct 14 15:35:15 [2] hub.c: 2 ports detected
* Oct 14 15:35:15 [2] usb.c: registered new driver usbkbd
* Oct 14 15:35:15 [2] usbkbd.c: :USB HID Boot Protocol keyboard driver
* Oct 14 15:35:15 [2] Initializing USB Mass Storage driver.
* Oct 14 15:35:15 [2] usb.c: registered new driver usb-storage
* Oct 14 15:35:15 [2] USB Mass Storage support registered.
* Oct 14 15:35:15 [2] NET4: Linux TCP/IP 1.0 for NET4.0
* Oct 14 15:35:15 [2] IP Protocols: ICMP, UDP, TCP
* Oct 14 15:35:15 [2] IP: routing cache hash table of 8192 buckets, 64Kbytes
* Oct 14 15:35:15 [2] TCP: Hash tables configured (established 262144 bind 65536)
* Oct 14 15:35:15 [2] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Oct 14 15:35:15 [3] RAMDISK: NASLite file system found at block 0
* Oct 14 15:35:15 [4] .<6>Freeing initrd memory: 4137k freed
* Oct 14 15:35:15 [4] EXT2-fs warning: checktime reached, running e2fsck is recommended
* Oct 14 15:35:15 [4] VFS: Mounted root (ext2 filesystem).
* Oct 14 15:35:15 [2] Mounted devfs on /dev
* Oct 14 15:35:15 [2] Freeing unused kernel memory: 560k freed
* Oct 14 15:35:15 [2] kjournald starting. Commit interval 5 seconds
* Oct 14 15:35:15 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
* Oct 14 15:35:15 [2] EXT3-fs: mounted filesystem with ordered data mode.
* Oct 14 15:35:15 [2] kjournald starting. Commit interval 5 seconds
* Oct 14 15:35:15 [2] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
* Oct 14 15:35:15 [2] EXT3-fs: mounted filesystem with ordered data mode.


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Wed Oct 14, 2009 11:03 pm 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
Try a new 80-conductor cable (it's still 40 pins) ... might solve Master/Slave conflicts (if there are any).


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Thu Oct 15, 2009 2:35 am 
Offline

Joined: Mon Oct 12, 2009 7:17 pm
Posts: 42
Location: Munich, Germany
georg wrote:
Try a new 80-conductor cable (it's still 40 pins) ... might solve Master/Slave conflicts (if there are any).


How would I then have to set the jumpers? Is cable select (CS) required with those cables? And would I have to set the jumpers still regarding master/slave?


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Thu Oct 15, 2009 11:36 am 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
No ... cable-select is not required, but it normally works. Then again I have had some manufacturer's HDDs which don't like the CS setting (edit: especially when mixed with a different mfg's drive). There are other ways of doing it, but the most conservative way is to always put the Master at the End of the cable, set it's jumper to Master (sometimes described as "Master with Slave Present", depending on the mfg of the drive), and put the slave in the "middle" with the appropriate Slave jumper for it.


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Fri Oct 16, 2009 6:13 am 
Offline

Joined: Mon Oct 12, 2009 7:17 pm
Posts: 42
Location: Munich, Germany
:D :D :D :D :D :D :D :D :D :D
After my Piii died I switched back to my old Pii 350.
Initially I was really :evil: seeing that the transfer speed was down from 400kB (Piii) to 250kB/s (Pii).
As the system did not give me any hint regarding IRQs I just gave it a try and switched the NIC to another PCI port. And suddently: huuuuuurray ..... ~4.5MB/s .... nearly a factor of 20 faster. Thanks a lot for your tipps.
Now, I am:
:D :D :D :D :D :D :D :D :D :D

Next question: what is the bottle neck now?
Can the system itself do more than this?
I see you folks reporting transfer rates of ~12MB/s in a 100Mbit/s Network environment. Is it realistic to get that with my system? If not, what would be the minimum configuration to get there?


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Fri Oct 16, 2009 11:36 am 
Offline

Joined: Sat Nov 19, 2005 6:39 pm
Posts: 633
Location: California
9 MB/s is more realistic. The fact that you are getting only half on an old mobo may be related to the HDDs being in PIO mode (not DMA). I am not sure if the DMA mode is supported on so old a board. There are HDD test diagnostic disk you could download from web to find out the transfer speed and/or mode used for the HDDs.


Top
 Profile  
 
 Post subject: Re: bad performance
PostPosted: Fri Oct 16, 2009 2:15 pm 
Offline

Joined: Sun Apr 02, 2006 9:05 pm
Posts: 1688
Location: Up State NY in the USA!!!!
The first machine I had NASLite loaded on was a P200MMX with a 3C905TX card and 128MB of EDO memory. I used a pair of drives, 40GB and 60GB on their own channels and had routine transfers of around 9MB/sec.

I for the life of me can not see any reason why you would get only 4MB/second with the setup you have. I would default all the settings in the BIOS and make sure that all the memory is in good order.

Mike


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 15 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 139 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:  
Powered by phpBB® Forum Software © phpBB Group