NASLite Network Attached Storage

I have upgraded from vers1.1 to 1.3 then 1.4 and having had months of trouble free use Last night and today I have started getting some problems. Access to the NAS across my network has slowed down considerably I have some high def movies that suddenly won't play, they just stutter to a halt. I have connected a monitor up to my NASbox for checking any error messages, I have had two incidents of an error saying "waiting for dma" access to anything on the ip address was thrown back as unavailable, it's almost like it's crashed and I have had errors stating "Lockd: unauthenticated request from (c0a80003:998).

I suspect a hardware fault, either the ide on the motherboard or maybe the PSU but it's just coincidental that I have had these problems since the upgrade. the only thing I've done differently is move some very big files, one of my high def movies was 15GB. The transfer speeds whilst copying were quite disapointing, my whole network is gigabit but the transfer speeds were very irregular achieving a max of 56mbps and a minimum of 3mbps, I wondered if this was also ide related, its an old ECS motherboard with an AMD K62 processor on my NAS so I didn't expect the full 1gbps transfer but I thought i'd get more than I am. The hard drive, the ram and the network card are about 6 months old. Any ideas? Or is it time to upgrade the motherboard and processor

Quick, dirty, simple and free soultion before you shell out for any new hardware.... downgrade to the versions that worked and see if the problem goes away, You still wont know which component may be dodgy (if it is hardware) but at least you wont be shelling out for nothing....

I have downgraded to vers 1.3 but still have problem;
Here is sys log anyone notice anything way out? I have to admit I'm struggling with this one

Oct 16 13:24:10 MyServer syslog.info syslogd started: BusyBox v1.01 (2005.10.01-00:52+0000)
Oct 16 13:24:10 MyServer daemon.info init: ^MStarting pid 315, console /dev/null: '/sbin/klogd'
Oct 16 13:24:10 MyServer user.notice kernel: klogd started: BusyBox v1.01 (2005.10.01-00:52+0000)
Oct 16 13:24:10 MyServer user.warn kernel: Linux version 2.4.27.NASLite (root@stimpy) (gcc version 3.3.2) #8 Sat Jan 1 11:12:55 MST 2005
Oct 16 13:24:10 MyServer user.info kernel: BIOS-provided physical RAM map:
Oct 16 13:24:10 MyServer user.warn kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
Oct 16 13:24:10 MyServer user.warn kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Oct 16 13:24:10 MyServer user.warn kernel: BIOS-e820: 0000000000100000 - 0000000007bf0000 (usable)
Oct 16 13:24:10 MyServer user.warn kernel: BIOS-e820: 0000000007bf0000 - 0000000007bf3000 (ACPI NVS)
Oct 16 13:24:10 MyServer user.warn kernel: BIOS-e820: 0000000007bf3000 - 0000000007c00000 (ACPI data)
Oct 16 13:24:10 MyServer user.warn kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Oct 16 13:24:10 MyServer user.notice kernel: 123MB LOWMEM available.
Oct 16 13:24:10 MyServer user.warn kernel: On node 0 totalpages: 31728
Oct 16 13:24:10 MyServer user.warn kernel: zone(0): 4096 pages.
Oct 16 13:24:10 MyServer user.warn kernel: zone(1): 27632 pages.
Oct 16 13:24:10 MyServer user.warn kernel: zone(2): 0 pages.
Oct 16 13:24:10 MyServer user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 BOOT_IMAGE=naslite.01
Oct 16 13:24:10 MyServer user.info kernel: Initializing CPU#0
Oct 16 13:24:10 MyServer user.warn kernel: Detected 334.091 MHz processor.
Oct 16 13:24:10 MyServer user.warn kernel: Console: colour VGA+ 80x25
Oct 16 13:24:10 MyServer user.warn kernel: Calibrating delay loop... 666.82 BogoMIPS
Oct 16 13:24:10 MyServer user.info kernel: Memory: 121220k/126912k available (1412k kernel code, 5308k reserved, 372k data, 508k init, 0k highmem)
Oct 16 13:24:10 MyServer user.info kernel: Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Oct 16 13:24:10 MyServer user.info kernel: Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
Oct 16 13:24:10 MyServer user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Oct 16 13:24:10 MyServer user.info kernel: Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Oct 16 13:24:10 MyServer user.warn kernel: Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
Oct 16 13:24:10 MyServer user.info kernel: Enabling new style K6 write allocation for 123 Mb
Oct 16 13:24:10 MyServer user.info kernel: CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
Oct 16 13:24:10 MyServer user.debug kernel: CPU: After generic, caps: 008021bf 808029bf 00000000 00000002
Oct 16 13:24:10 MyServer user.debug kernel: CPU: Common caps: 008021bf 808029bf 00000000 00000002
Oct 16 13:24:10 MyServer user.warn kernel: CPU: AMD-K6(tm) 3D processor stepping 0c
Oct 16 13:24:10 MyServer user.info kernel: Checking 'hlt' instruction... OK.
Oct 16 13:24:10 MyServer user.info kernel: Checking for popad bug... OK.
Oct 16 13:24:10 MyServer user.warn kernel: POSIX conformance testing by UNIFIX
Oct 16 13:24:10 MyServer user.info kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb460, last bus=1
Oct 16 13:24:10 MyServer user.info kernel: PCI: Using configuration type 1
Oct 16 13:24:10 MyServer user.info kernel: PCI: Probing PCI hardware
Oct 16 13:24:10 MyServer user.warn kernel: PCI: Probing PCI hardware (bus 00)
Oct 16 13:24:10 MyServer user.info kernel: PCI: Using IRQ router SIS5595 [1039/0008] at 00:01.0
Oct 16 13:24:10 MyServer user.info kernel: Linux NET4.0 for Linux 2.4
Oct 16 13:24:10 MyServer user.info kernel: Based upon Swansea University Computer Society NET3.039
Oct 16 13:24:10 MyServer user.warn kernel: Initializing RT netlink socket
Oct 16 13:24:10 MyServer user.warn kernel: Starting kswapd
Oct 16 13:24:10 MyServer user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
Oct 16 13:24:10 MyServer user.info kernel: devfs: boot_options: 0x1
Oct 16 13:24:10 MyServer user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Oct 16 13:24:10 MyServer user.warn kernel: pty: 256 Unix98 ptys configured
Oct 16 13:24:10 MyServer user.info kernel: Real Time Clock Driver v1.10f
Oct 16 13:24:10 MyServer user.info kernel: Floppy drive(s): fd0 is 1.44M
Oct 16 13:24:10 MyServer user.info kernel: FDC 0 is a post-1991 82077
Oct 16 13:24:10 MyServer user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Oct 16 13:24:10 MyServer user.info kernel: loop: loaded (max 8 devices)
Oct 16 13:24:10 MyServer user.info kernel: Intel(R) PRO/1000 Network Driver - version 5.2.52-k3
Oct 16 13:24:10 MyServer user.info kernel: Copyright (c) 1999-2004 Intel Corporation.
Oct 16 13:24:10 MyServer 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
Oct 16 13:24:10 MyServer user.warn kernel: FW Version=$Version$
Oct 16 13:24:10 MyServer user.info kernel: pcnet32.c:v1.30c 05.25.2004 tsbogend@alpha.franken.de
Oct 16 13:24:10 MyServer user.info kernel: ThunderLAN driver v1.15
Oct 16 13:24:10 MyServer user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
Oct 16 13:24:10 MyServer user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
Oct 16 13:24:10 MyServer user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
Oct 16 13:24:10 MyServer user.warn kernel: sk98lin: No adapter found.
Oct 16 13:24:10 MyServer user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.25.
Oct 16 13:24:10 MyServer user.info kernel: r8169 Gigabit Ethernet driver 1.2 loaded
Oct 16 13:24:10 MyServer user.info kernel: PCI: Found IRQ 11 for device 00:0a.0
Oct 16 13:24:10 MyServer user.debug kernel: eth0: Identified chip type is 'RTL8169s/8110s'.
Oct 16 13:24:10 MyServer user.info kernel: eth0: RTL8169 at 0xc8800000, 00:0f:b5:47:73:c2, IRQ 11
Oct 16 13:24:10 MyServer user.info kernel: eth0: Auto-negotiation Enabled.
Oct 16 13:24:10 MyServer user.info kernel: eth0: 1000Mbps Full-duplex operation.
Oct 16 13:24:10 MyServer user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
Oct 16 13:24:10 MyServer user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Oct 16 13:24:10 MyServer user.info kernel: SIS5513: IDE controller at PCI slot 00:00.1
Oct 16 13:24:10 MyServer user.info kernel: SIS5513: chipset revision 208
Oct 16 13:24:10 MyServer user.info kernel: SIS5513: not 100% native mode: will probe irqs later
Oct 16 13:24:10 MyServer user.info kernel: SIS5513: SiS530 ATA 66 controller
Oct 16 13:24:10 MyServer user.info kernel: ide0: BM-DMA at 0x4000-0x4007, BIOS settings: hda:pio, hdb:pio
Oct 16 13:24:10 MyServer user.info kernel: ide1: BM-DMA at 0x4008-0x400f, BIOS settings: hdc:pio, hdd:pio
Oct 16 13:24:10 MyServer user.warn kernel: hda: ST3400832A, ATA DISK drive
Oct 16 13:24:10 MyServer user.warn kernel: hdb: LTN403L, ATAPI CD/DVD-ROM drive
Oct 16 13:24:10 MyServer user.warn kernel: blk: queue c03662e0, I/O limit 4095Mb (mask 0xffffffff)
Oct 16 13:24:10 MyServer user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 16 13:24:10 MyServer user.warn kernel: hda: attached ide-disk driver.
Oct 16 13:24:10 MyServer user.warn kernel: hda: host protected area => 1
Oct 16 13:24:10 MyServer user.info kernel: hda: 781422768 sectors (400088 MB) w/8192KiB Cache, CHS=48641/255/63, UDMA(66)
Oct 16 13:24:10 MyServer user.info kernel: Partition check:
Oct 16 13:24:10 MyServer user.info kernel: host0/bus0/target0/lun0: p1
Oct 16 13:24:10 MyServer user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Oct 16 13:24:10 MyServer user.info kernel: IP Protocols: ICMP, UDP, TCP
Oct 16 13:24:10 MyServer user.info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Oct 16 13:24:10 MyServer user.info kernel: TCP: Hash tables configured (established 8192 bind 16384)
Oct 16 13:24:10 MyServer user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Oct 16 13:24:10 MyServer user.notice kernel: RAMDISK: NASLite file system found at block 0
Oct 16 13:24:10 MyServer user.warn kernel: .<6>Freeing initrd memory: 1428k freed
Oct 16 13:24:10 MyServer user.warn kernel: VFS: Mounted root (ext2 filesystem).
Oct 16 13:24:10 MyServer user.info kernel: Mounted devfs on /dev
Oct 16 13:24:10 MyServer user.info kernel: Freeing unused kernel memory: 508k freed
Oct 16 13:25:45 MyServer user.notice kernel: lockd: unauthenticated request from (c0a80003:999)
Oct 16 13:25:45 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 13:25:45 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 13:25:45 MyServer user.err syslog: can't get hostname of 192.168.0.3
Oct 16 13:25:46 MyServer user.notice kernel: lockd: unauthenticated request from (c0a80003:999)
Oct 16 13:25:46 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 13:25:46 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 13:25:46 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1 (/): no export entry
Oct 16 13:25:46 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1 (/): no export entry
Oct 16 13:25:56 MyServer user.err syslog: can't get hostname of 192.168.0.3
Oct 16 13:27:28 MyServer auth.info login[424]: root login on `pts/0'
Oct 16 20:07:05 MyServer user.notice kernel: lockd: unauthenticated request from (c0a80003:939)
Oct 16 20:07:05 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 20:07:05 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 20:07:06 MyServer user.err syslog: can't get hostname of 192.168.0.3
Oct 16 20:07:09 MyServer user.notice kernel: lockd: unauthenticated request from (c0a80003:939)
Oct 16 20:07:09 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 20:07:09 MyServer user.notice syslog: export request from 192.168.0.3
Oct 16 20:07:09 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1/Home Video (/): no export entry
Oct 16 20:07:09 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1 (/): no export entry
Oct 16 20:07:09 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1 (/): no export entry
Oct 16 20:07:10 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1/Home Video (/): no export entry
Oct 16 20:07:10 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1 (/): no export entry
Oct 16 20:07:16 MyServer user.err syslog: can't get hostname of 192.168.0.3
Oct 17 18:53:37 MyServer user.notice kernel: lockd: unauthenticated request from (c0a80003:980)
Oct 17 18:53:37 MyServer user.notice syslog: export request from 192.168.0.3
Oct 17 18:53:37 MyServer user.notice syslog: export request from 192.168.0.3
Oct 17 18:53:39 MyServer user.err syslog: can't get hostname of 192.168.0.3
Oct 17 18:53:42 MyServer user.notice kernel: lockd: unauthenticated request from (c0a80003:980)
Oct 17 18:53:42 MyServer user.notice syslog: export request from 192.168.0.3
Oct 17 18:53:42 MyServer user.notice syslog: export request from 192.168.0.3
Oct 17 18:53:42 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1 (/): no export entry
Oct 17 18:53:42 MyServer user.warn syslog: refused mount request from 192.168.0.3 for /Disk-1 (/): no export entry
Oct 17 18:53:49 MyServer user.err syslog: can't get hostname of 192.168.0.3

Any help again much appreciated, should be able to get my hands on a new motherboard with a celeron 1.4ghz processor in the next couple of weeks but I'd like to get to the bottom of this first assuming it isn't hardware related.

I looked at your log and compare it to mine,

Here is where i think the problem lays.

scroll down on your log the the section below and you will see your problem seesms to start after kernel freeing unused.
on my log its doing something with the network card.

My log
# Oct 16 13:09:39 NAS user.info kernel: Freeing unused kernel memory: 496k freed
# Oct 16 13:09:39 NAS user.info kernel: eth0: Media Link On 100mbps full-duplex
# Oct 17 09:58:27 NAS user.info kernel: eth0: Media Link Off
# Oct 17 09:58:46 NAS user.info kernel: NETDEV WATCHDOG: eth0: transmit timed out
# Oct 17 09:58:46 NAS user.info kernel: eth0: Transmit timeout, status 00000004 00000000
# Oct 17 09:58:47 NAS user.info kernel: eth0: Media Link On 100mbps full-duplex
# Oct 17 18:36:50 NAS auth.info login[11593]: root login on `pts/0'
# Oct 17 18:41:16 NAS auth.info login[12645]: root login on `pts/0'

can u post your SMB Server Configuration

Hi edeng,

Thanks for your help yes I'll post the SMB config when I get home tonight.

edeng,

SMB log as requested hope it means something to you 'cause it's over my head

[2005/10/16 13:24:08, 0] smbd/server.c:main(791)
smbd version 2.2.12 started.
Copyright Andrew Tridgell and the Samba Team 1992-2002
[2005/10/16 13:25:47, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 422)
[2005/10/16 13:25:54, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/16 13:26:58, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 423)
[2005/10/16 14:03:02, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/16 14:25:59, 1] smbd/service.c:make_connection(636)
office (192.168.0.7) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 1752)
[2005/10/16 14:26:50, 1] smbd/service.c:close_cnum(677)
office (192.168.0.7) closed connection to service Disk-1
[2005/10/16 20:07:10, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 8893)
[2005/10/16 20:07:12, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/16 20:07:12, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 8894)
[2005/10/16 20:07:23, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/16 20:07:37, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 8895)
[2005/10/16 20:07:37, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 8895)
[2005/10/16 20:07:41, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/16 20:07:41, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/16 21:16:24, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 10370)
[2005/10/16 21:23:33, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 09:12:30, 1] smbd/service.c:make_connection(636)
office (192.168.0.7) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 25386)
[2005/10/17 09:44:53, 1] smbd/service.c:close_cnum(677)
office (192.168.0.7) closed connection to service Disk-1
[2005/10/17 12:49:58, 1] smbd/service.c:make_connection(636)
office (192.168.0.7) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 29902)
[2005/10/17 13:31:11, 1] smbd/service.c:close_cnum(677)
office (192.168.0.7) closed connection to service Disk-1
[2005/10/17 17:47:28, 1] smbd/service.c:make_connection(636)
office (192.168.0.7) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 3738)
[2005/10/17 18:45:47, 1] smbd/service.c:close_cnum(677)
office (192.168.0.7) closed connection to service Disk-1
[2005/10/17 18:46:10, 1] smbd/service.c:make_connection(636)
office (192.168.0.7) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 4999)
[2005/10/17 18:53:42, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 5105)
[2005/10/17 18:53:44, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 18:55:00, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 5106)
[2005/10/17 18:55:11, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 19:03:55, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 5319)
[2005/10/17 19:09:18, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 19:10:34, 1] smbd/service.c:close_cnum(677)
office (192.168.0.7) closed connection to service Disk-1
[2005/10/17 19:34:08, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 5950)
[2005/10/17 19:34:09, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 19:34:10, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 5951)
[2005/10/17 19:34:21, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 19:34:26, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 5952)
[2005/10/17 19:34:33, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 19:34:47, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 5953)
[2005/10/17 19:34:47, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 19:35:03, 1] smbd/service.c:make_connection(636)
xp3000 (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 6059)
[2005/10/17 19:35:03, 1] smbd/service.c:close_cnum(677)
xp3000 (192.168.0.3) closed connection to service Disk-1
[2005/10/17 21:07:18, 1] smbd/service.c:make_connection(636)
office (192.168.0.7) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 7953)
[2005/10/17 21:23:14, 1] smbd/service.c:make_connection(636)
laptop (192.168.0.2) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 8269)
[2005/10/17 21:23:29, 1] smbd/service.c:close_cnum(677)
laptop (192.168.0.2) closed connection to service Disk-1
[2005/10/17 21:23:38, 1] smbd/service.c:make_connection(636)
laptop (192.168.0.2) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 8270)
[2005/10/17 21:48:35, 0] lib/util_sock.c:read_data(436)
read_data: read failure for 4. Error = No route to host
[2005/10/17 21:48:35, 1] smbd/service.c:close_cnum(677)
laptop (192.168.0.2) closed connection to service Disk-1
[2005/10/17 22:14:06, 1] smbd/service.c:close_cnum(677)
office (192.168.0.7) closed connection to service Disk-1
[2005/10/18 16:39:20, 1] smbd/service.c:make_connection(636)
office (192.168.0.3) connect to service Disk-1 as user NAS-User (uid=98, gid=98) (pid 32527)

thanks again for your help

edeng

So how stupid am I

here is the SMB server config you asked for not the SMB log as previously posted sorry it's been a long day

[global]
netbios name = MyServer
workgroup = MSHome
server string = NASLite (IP: 192.168.0.6)
security = share
client codepage = 850
interfaces = eth0
name resolve order = bcast host
max open files = 1014
socket options = TCP_NODELAY
map archive = yes
map system = yes
map hidden = yes
nt acl support = yes
local master = no
max log size = 10

[Disk-1]
path = /export/Disk-1
comment = NAS Disk-1 ( Read / Write )
invalid users = root admin
guest account = NAS-User
read only = no
writeable = yes
public = yes

[Disks]
path = /export
comment = NAS Disks ( Read Only )
guest account = NAS-User
read only = yes
writeable = no
public = yes

[Info]
comment = NAS Information ( Read Only )
path = /export/Info
guest account = NAS-User
read only = yes
writeable = no


Thanks again

Wilbur

Hi wilbur,

All of your settings appear to be normal. I would not change the board quire yet since I don’t think it’s the problem. On initial boot, NASLite initiates a SMART self test for all mountable drives. That test lasts for a bit of time. On your 400G drive it may take 1 hour or so after initial boot. During that self test, the drive performance can be erratic. Different drives behave differently, but generally performance will be lower during the self-test.

Since with HD content your transfer requirements are higher than previously, you are now experiencing the lag.

I am not fully sure that’s the problem, but it’s worth a look. Check the Info page for the drive to verify the self-test has completed before you try to stream HD content again.

Another thing to take a look at is the network block in the System Info page. There look for packet errors. Those can also affect performance.

Anyway, hope the above makes sense.

Thanks Tony,
I'll check it out, there was a lot of rebooting and swapping version cd's and config floppies so after a day or so it may have settled down. If not I'll be back on to see if there's anything else

Tony,
I am copying a non HD movie across onto the NASbox and am getting a lot of "too much work at intrupt".

Would this have anything to do with my slow access, at the moment my network speed is only running at 1.5mb/sec even though it's a full Gigabit network.

Any ideas?

Hi wilbur,

I would definately use v1.4 since you have enough RAM (128 is i'm not mistaken). Also, since you are running Gbit, I'd take a serious look at networking. Looking at the logs above, you seem to be having network issues. Start by looking for errors by examining the network section of the System Info page. Do that after you've been copying files for a while. Check the cable carefully. Cheap 100T cables are often not suitable for Gbit, especially on longer runs 50ft+.

Another thing i notised is that your machine is still trying to connect through NFS, but you have the wrong path set in windows. It's not /Disk-1 but /export/Disk-1, etc.

Anyway, I'd say that there is misconficuration or bad net somewhere. At 300MHz+, your PC should keep up with HD transfers without a problem.

Hope that helps.

Tony,
Thanks for advice, I did a number of checks over the weekend put NASlite+ ver 1.4 back in left it to run the SMART check and disconnected the NFS mapped drive so hopefully the NFS issue will be sorted, using a little utility called "Netmeter" I checked my connection speeds, whilst transfering to the NASbox from my HTPC, I get a very eratic transfer rate rising to a maximum of 50mbps dropping down to a minimum of 100kbps then rising again then falling, the graph looks like a heart beat monitor . I then transferred the same data (some MP3's) across the network to my backup disk which happens to be an external HDD attached via USB2.0 to my office PC, the transfer rates here were much better a maximum of 105mbps and a minimum of about 70mbps this graph was a much more solid block and the transfer was 3 times quicker than the NASbox transfer. So first thing I'll do tonight is make up a new CAT6 cable to connect to the NASbox and see if that solves the problem, I have CAT6 to the outlet port on the wall but the patch lead is an old CAT5e cable so maybe that will help. The fact that my transfers to and from other pc's around the network are so good convinces me the cabling to the other machines is up to scratch so I'll post later or tomorrrow the outcome of the new cable. And although my current motherboard and processor are up to the job I will upgrade to a 1.4ghz celeron pc, it's a machine at my works office and I am upgrading some of the office PC's so this one will be going spare

Wilbur, I see what your saying, i downloaded Netmeter and ran a test, when i copy 1Gb to the Nas i get the heart beat like you was saying, high peaks then massive drops thoughout the whole transfer, but if i copy the data back to my windows pc is near enough a solid block,

edeng,

Ok so that would point to it not being our cabling, I can't imagine even in the land of sod we both have dodgy cabling to the NASbox but good everywhere else
So could it be down to the IDE transfer rates? What are you using as your pc for NASlite? Mine is an old system, as previously posted I will be upgrading soon and I know my future motherboard supports Ultra DMA 100 so maybe this will help.
What are your thoughts Tony? Could there be something else causing the stuttering effect of network transfers? I know that transferring huge high def video files was not what NASlite was designed to do initially but it would be great if we can work out where the bottle neck is and find a solution, hopefully it won't be to difficult for you to resolve
I'll send you a picture of each of the netmeter screens so you can see what edeng and I mean.
If there's anything else I can send you in the way of logs etc Tony please let me know.
Your help as always much appreciated