NASLite Network Attached Storage

Today I was transferring files from one older NAS to my (NASLIte-M2) NAS Server : I was working from one of my Vista clients and after 15 - 20 minutes I had < Connection Lost > message regarding NASLite Server and a RED cross on both NASLIte mapped disks .
So I tried to communicate with NASLIte via a Telnet session but nothing to do --> host not found (or something similar).
I had to reboot my NASLite Server to have mapped disks working again but after some minutes again ... Connection Lost and so on.
What could be the reason of this failure ??
Is there any session log anywhere to let me (us) understand what happened ??

Michele.

problem is Vista i think - again - i thing its been covered on here before - have a search it might bring something up

I have not experienced the Vista issues but once or twice. They fixed them selves with a reboot of Vista.

On the other hand I have had the same thing happen, regardless of the client OS, and it turned out to be the server hardware I was using. What is the hardware of the new server?

Mike

I don't think it's a Vista problem too, because I used the same clients with my previous NASLite-M2 (mini)Server and I had ZERO problems : I think that this NASLite-M2 config seems to crash.
I think that could really be an hardware problem in this new Server, but probably if there was a kind of LOG somewhere maybe I could "localize" the problem : is it there one ??
The hardware is an ASUS Socket 939 nVidia based M/B (A8Nxx), an Athlon 64 3500+ CPU, 1 GB Ram (PC-3200 DDR1), a PCI Express Realtek based Gigabit NIC (brand new), a Flash (boot) IDE Disk (the same I used in the previous config) and two WD Caviar 1 TB SATA2 HDDs.
I may try to change memory modules, but I have no other CPU or M/B to test ... is there any LOG somewhere ??

Michele.

There is the boot log, again just go to the web page of the server and look at the tabs. There you will find it.

I will be honest, I have not had luck with most of the Athlon based motherboards I have tried NL with. I did have great luck with an old AMD K6/2 300 that was rock solid but that was an Intel chipset. My Opteron server is fast a stable as well but that is a true server from Sun Micro systems and is based on server chipsets. Server hardware tends to focus much more on stability and compatibility over cutting edge performance and support for the latest greatest hardware.

Really good basic server machines that are cheap on Ebay are by Rackables. Also Sun x86 based machines work great as well and can be had for reasonable prices on Ebay.

Mike

I definitively changed my NAS Hardware (M/B & CPU) trying to give a solution to my problems : now there is an Asus LGA775 Intel based Motherboard and cheap Celeron 430 CPU ... obviously Boot Flash and SATA HDDs remained the same ones.
Everything seems to work well now but I took a look at NASLite Log and I found some Warnings :

# May 28 18:45:41 [4] Driver 'sd' needs updating - please use bus_type methods
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] Write Protect is off
# May 28 18:45:41 [1] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
# May 28 18:45:41 [2] sda:
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] Write Protect is off
# May 28 18:45:41 [1] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
# May 28 18:45:41 [4] sda1
# May 28 18:45:41 [2] sdb:
# May 28 18:45:41 [3] sd 0:0:0:0: [sda] Attached SCSI disk
# May 28 18:45:41 [4] sdb1
# May 28 18:45:41 [3] sd 0:0:1:0: [sdb] Attached SCSI disk
# May 28 18:46:06 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:06 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:06 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:06 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:06 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:06 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:06 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:06 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:06 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:07 [2] ATL1E 0000:01:00.0: ATL1E: eth0 NIC Link is Up<1000 Mbps Full Duplex>
# May 28 18:46:18 [5] hda: task_pio_intr: status=0x51 { DriveReady SeekComplete Error }
# May 28 18:46:18 [5] hda: task_pio_intr: error=0x04 { DriveStatusError }
# May 28 18:46:18 [5] hda: possibly failed opcode: 0xa1
# May 28 18:46:22 [2] kjournald starting. Commit interval 5 seconds
# May 28 18:46:22 [2] EXT3 FS on sda1, internal journal
# May 28 18:46:22 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 28 18:46:24 [2] kjournald starting. Commit interval 5 seconds
# May 28 18:46:24 [2] EXT3 FS on sdb1, internal journal
# May 28 18:46:24 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 28 18:46:47 [2] Adding 1048568k swap on /export/Disk-1/_NL_SWAP/VRAM. Priority:-1 extents:266 across:1068316k

Can anyone or can you explain me those messages ??

Michele.