NASLite Network Attached Storage

I just moved my NL v2.04 02-2007 from an old PC to a new PC and it's frozen up twice today. I can access the machine fine via the keyboard but all network access to the machine is no longer good. I have an intel 10/100 nic in the machine and I've disabled as much as I can in the BIOS. When I'm at the console, how do I get to the syslog to save it? I'd like to find out what is wrong. I'm looking at upgrading to M2 but my wife is hesitant to let me as this NL instance seems flakey at times with going down network wise. Anyone have a thought on what it might be or how to get to the sys logs?

Thanks

Lance

Feb 6 21:24:48 syslog.info syslogd started: BusyBox v1.01 (2007.01.20-18:39+0000)
Feb 6 21:24:48 daemon.info init: ^MStarting pid 2003, console /dev/null: '/sbin/klogd'
Feb 6 21:24:48 user.notice kernel: klogd started: BusyBox v1.01 (2007.01.20-18:39+0000)
Feb 6 21:24:48 user.warn kernel: Linux version 2.4.33.NASLite (root@TZT) (gcc version 3.3.6) #1 Tue Aug 15 01:08:13 UTC 2006
Feb 6 21:24:48 user.info kernel: BIOS-provided physical RAM map:
Feb 6 21:24:48 user.warn kernel: BIOS-e820: 0000000000000000 - 000000000009c000 (usable)
Feb 6 21:24:48 user.warn kernel: BIOS-e820: 000000000009c000 - 00000000000a0000 (reserved)
Feb 6 21:24:48 user.warn kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Feb 6 21:24:48 user.warn kernel: BIOS-e820: 0000000000100000 - 000000001bf00000 (usable)
Feb 6 21:24:48 user.warn kernel: BIOS-e820: 000000001c000000 - 0000000020000000 (reserved)
Feb 6 21:24:48 user.warn kernel: BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
Feb 6 21:24:48 user.warn kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Feb 6 21:24:48 user.notice kernel: 447MB LOWMEM available.
Feb 6 21:24:48 user.warn kernel: On node 0 totalpages: 114432
Feb 6 21:24:48 user.warn kernel: zone(0): 4096 pages.
Feb 6 21:24:48 user.warn kernel: zone(1): 110336 pages.
Feb 6 21:24:48 user.warn kernel: zone(2): 0 pages.
Feb 6 21:24:48 user.err kernel: ACPI: Unable to locate RSDP
Feb 6 21:24:48 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=NASLite.01
Feb 6 21:24:48 user.info kernel: Initializing CPU#0
Feb 6 21:24:48 user.warn kernel: Detected 1808.238 MHz processor.
Feb 6 21:24:48 user.warn kernel: Console: colour VGA+ 80x25
Feb 6 21:24:48 user.warn kernel: Calibrating delay loop. 3604.48 BogoMIPS
Feb 6 21:24:48 user.info kernel: Memory: 447048k/457728k available (2198k kernel code, 10280k reserved, 734k data, 536k init, 0k highmem)
Feb 6 21:24:48 user.info kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Feb 6 21:24:48 user.info kernel: Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Feb 6 21:24:48 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Feb 6 21:24:48 user.info kernel: Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 6 21:24:48 user.warn kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
Feb 6 21:24:48 user.info kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Feb 6 21:24:48 user.info kernel: CPU: L2 Cache: 512K (64 bytes/line)
Feb 6 21:24:48 user.debug kernel: CPU: After generic, caps: 078bfbff e3d3fbff 00000000 00000000
Feb 6 21:24:48 user.debug kernel: CPU: Common caps: 078bfbff e3d3fbff 00000000 00000000
Feb 6 21:24:48 user.warn kernel: CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 02
Feb 6 21:24:48 user.info kernel: Enabling fast FPU save and restore. done.
Feb 6 21:24:48 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
Feb 6 21:24:48 user.info kernel: Checking 'hlt' instruction. OK.
Feb 6 21:24:48 user.info kernel: Checking for popad bug. OK.
Feb 6 21:24:48 user.warn kernel: POSIX conformance testing by UNIFIX
Feb 6 21:24:48 user.info kernel: ACPI: Subsystem revision 20040326
Feb 6 21:24:48 user.info kernel: ACPI: Interpreter disabled.
Feb 6 21:24:48 user.info kernel: PCI: PCI BIOS revision 3.00 entry at 0xfa8d0, last bus=3
Feb 6 21:24:48 user.info kernel: PCI: Using configuration type 1
Feb 6 21:24:48 user.info kernel: PCI: Probing PCI hardware
Feb 6 21:24:48 user.warn kernel: PCI: Probing PCI hardware (bus 00)
Feb 6 21:24:48 user.warn kernel: Transparent bridge - PCI device 10de:026f
Feb 6 21:24:48 user.info kernel: Linux NET4.0 for Linux 2.4
Feb 6 21:24:48 user.info kernel: Based upon Swansea University Computer Society NET3.039
Feb 6 21:24:48 user.warn kernel: Initializing RT netlink socket
Feb 6 21:24:48 user.warn kernel: Starting kswapd
Feb 6 21:24:48 user.info kernel: Journalled Block Device driver loaded
Feb 6 21:24:48 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
Feb 6 21:24:48 user.info kernel: devfs: boot_options: 0x1
Feb 6 21:24:48 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Feb 6 21:24:48 user.warn kernel: pty: 256 Unix98 ptys configured
Feb 6 21:24:48 user.info kernel: Real Time Clock Driver v1.10f
Feb 6 21:24:48 user.info kernel: Floppy drive(s): fd0 is 1.44M
Feb 6 21:24:48 user.info kernel: FDC 0 is a post-1991 82077
Feb 6 21:24:48 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Feb 6 21:24:48 user.info kernel: loop: loaded (max 8 devices)
Feb 6 21:24:48 user.info kernel: Intel(R) PRO/1000 Network Driver - version 5.7.6-k1
Feb 6 21:24:48 user.info kernel: Copyright (c) 1999-2004 Intel Corporation.
Feb 6 21:24:48 user.info kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Feb 6 21:24:48 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
Feb 6 21:24:48 user.warn kernel: FW Version=$Version$
Feb 6 21:24:48 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
Feb 6 21:24:48 user.info kernel: ThunderLAN driver v1.15
Feb 6 21:24:48 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
Feb 6 21:24:48 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
Feb 6 21:24:48 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
Feb 6 21:24:48 user.warn kernel: sk98lin: No adapter found.
Feb 6 21:24:48 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
Feb 6 21:24:48 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
Feb 6 21:24:48 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Feb 6 21:24:48 user.warn kernel: hda: LITE-ON DVDRW LDW-851S, ATAPI CD/DVD-ROM drive
Feb 6 21:24:48 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 6 21:24:48 user.info kernel: SCSI subsystem driver Revision: 1.00
Feb 6 21:24:48 user.info kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
Feb 6 21:24:48 user.info kernel: Detecting Adaptec I2O RAID controllers.
Feb 6 21:24:48 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Aug 15 2006 01:22:52)
Feb 6 21:24:48 user.warn kernel: scsi: Detection failed (no card)
Feb 6 21:24:48 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
Feb 6 21:24:48 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
Feb 6 21:24:48 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
Feb 6 21:24:48 user.warn kernel: 2.00.037.
Feb 6 21:24:48 user.notice kernel: scsi1 : Found a 3ware Storage Controller at 0xbc00, IRQ: 10, P-chip: 1.3
Feb 6 21:24:48 user.info kernel: scsi1 : 3ware Storage Controller
Feb 6 21:24:48 user.warn kernel: Vendor: 3ware Model: Logical Disk 0 Rev: 1.0
Feb 6 21:24:48 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 00
Feb 6 21:24:48 user.debug kernel: libata version 1.20 loaded.
Feb 6 21:24:48 user.debug kernel: PCI(00:0e.0): version 0.8
Feb 6 21:24:48 user.debug kernel: PCI: Setting latency timer of device 00:0e.0 to 64
Feb 6 21:24:48 user.info kernel: ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE000 irq 11
Feb 6 21:24:48 user.info kernel: ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE008 irq 11
Feb 6 21:24:48 user.info kernel: ata1: no device found (phy stat 00000000)
Feb 6 21:24:48 user.info kernel: ata2: no device found (phy stat 00000000)
Feb 6 21:24:48 user.info kernel: scsi2 : sata_nv
Feb 6 21:24:48 user.info kernel: scsi3 : sata_nv
Feb 6 21:24:48 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Feb 6 21:24:48 user.warn kernel: SCSI device sda: 2930313216 512-byte hdwr sectors (1500320 MB)
Feb 6 21:24:48 user.info kernel: Partition check:
Feb 6 21:24:48 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
Feb 6 21:24:48 user.info kernel: raw1394: /dev/raw1394 device initialized
Feb 6 21:24:48 user.info kernel: sbp2: $Rev: 1074 $ Ben Collins
Feb 6 21:24:48 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
Feb 6 21:24:48 user.info kernel: usb.c: registered new driver usbdevfs
Feb 6 21:24:48 user.info kernel: usb.c: registered new driver hub
Feb 6 21:24:48 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
Feb 6 21:24:48 user.debug kernel: PCI: Setting latency timer of device 00:0b.0 to 64
Feb 6 21:24:48 user.info kernel: host/usb-ohci.c: USB OHCI at membase 0xdc825000, IRQ 10
Feb 6 21:24:48 user.info kernel: host/usb-ohci.c: usb-00:0b.0, PCI device 10de:026d
Feb 6 21:24:48 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
Feb 6 21:24:48 user.info kernel: hub.c: USB hub found
Feb 6 21:24:48 user.info kernel: hub.c: 8 ports detected
Feb 6 21:24:48 user.info kernel: Initializing USB Mass Storage driver.
Feb 6 21:24:48 user.info kernel: usb.c: registered new driver usb-storage
Feb 6 21:24:48 user.info kernel: USB Mass Storage support registered.
Feb 6 21:24:48 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Feb 6 21:24:48 user.info kernel: IP Protocols: ICMP, UDP, TCP
Feb 6 21:24:48 user.info kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
Feb 6 21:24:48 user.info kernel: TCP: Hash tables configured (established 32768 bind 65536)
Feb 6 21:24:48 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Feb 6 21:24:48 user.notice kernel: RAMDISK: NASLite file system found at block 0
Feb 6 21:24:48 user.warn kernel: .<6>Freeing initrd memory: 1619k freed
Feb 6 21:24:48 user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
Feb 6 21:24:48 user.warn kernel: VFS: Mounted root (ext2 filesystem).
Feb 6 21:24:48 user.info kernel: Mounted devfs on /dev
Feb 6 21:24:48 user.info kernel: Freeing unused kernel memory: 536k freed
Feb 6 21:24:48 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
Feb 6 21:24:48 user.err kernel: ext3: No journal on filesystem on sd(8,1)

Reset the BIOS for starters.

Turn off power management, APCI.

Disable all devices not needed by NL.

If none of the above work then try flashing the BIOS to the latest version. Trying to eliminate the easy stuff first.

Next, look at the motherboard. I know that you may not want to hear this but there are just some motherboards that refuse to play nice with NASLite. I have had a few that did the same thing. The fix was an Intel motherboard and a Celeron 2.0GHz processor. These can be had for nothing on Ebay now days. Remember that you need a dual quad core 3.3GHz processor to surf the web! Dumb people have these very serviceable boxes sitting around just waiting for you to help them get rid of them and put them to good use! Case in point http://cgi.ebay.com/INTEL-D845WN-MOTHERBOARD-w-P4-1-7GHz-and-512MB_W0QQitemZ360231357737QQcmdZViewItemQQptZMotherboards?hash=item53df764d29 This is the same motherboard I have been using for the past 2 years with no issues at all. $10.00, stupid!

NL M2 is very reliable and stable. Fact is I am still running the Beta of it since the release. I never even upgraded, it's that freaking good. That and I forget to since it just runs and I'm lazy. Honestly, the wife says no to you spending $35.00 for the program! GROW A PAIR!

Mike

LOL @ Grow A Pair...it's not the $35.00 it's the instability of the program. 2.04 is pretty old and this is a newer board so maybe that is the problem but would a MB issue cause only the network to hang? I can access the NL PC via it's own keyboard/monitor, I only lose network connectivity. I'm thinking about pulling the nic and trying the onboard one to see if maybe that works better.

If I were to move to M2 is the upgrade jsut a swap out or will I have to move my data off and reformat Raid array?

I would look into the Intel board it's just that the P4's run warm and it gets toasty in my room in the summer time and my old P4 always had issues in here during the warmer months. The athlon runs pretty well in here so I'd like to stick with it. I'll try resetting the bios and stuff and see if that helps at all..

Forgot to add, is there a way to look at the sys log to see if something odd is happening from the terminal itself? Or only through the web, which isn't working when this "breaks"?

I saw this in the logs and wondered if it meant anything:

Feb 6 22:29:33 user.info kernel: Freeing unused kernel memory: 536k freed
Feb 6 22:29:33 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
Feb 6 22:29:33 user.err kernel: ext3: No journal on filesystem on sd(8,1)
-->Feb 6 22:38:19 user.info kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 6 22:38:21 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex

gave a transmit time out and then seemed to "reconnect"

Thanks

Lance

All the issues I had were with Athlon processors and their motherboards.

If you are using a newer motherboard and processor then it is likely that M2 will help you rather than hurt. It is based on a kernel that is modular and supports a much larger array of hardware as well as much more modern hardware.

You will not need to migrate your data off of the array to go to M2, just load the new OS cdrom or USB stick on the box and go.

Keep in mind that you may still need to give up on the Athlon MB and processor for this job though.

The P4 in that auction doesn't run hot, it's to damn slow to run hot! But it's more than fast enough to serve in a NAS function under M@.

Mike

Well I went ahead and purchased the M2 and got it up and running via the CDROM-Floppy (I tried the install to the USB and it installed but wouldn't boot even though USB was selected as a boot device) but it's up and running as of now. I'll have to see for how long however. The other version wouldn't even transfer a GB of data before shutting down network connectivity.

I'm going to try running the two movies now and see if it stays up and running.

Thanks for the help/info

Edit: Well that didn't help matters at all either. I booted up with 1.61 of M2 and at about 459MB of data being transferred it crapped out again. I guess it could be the Intel Nic that is doing this and I may switch over to the onboard nic and see if that fixes anything but I Thought the intel nics were supposed to be of superior quality from what I read here. It's just very frustrating going from AMD to AMD and it crashing out like this. I'll update this if changing out the nic helps.

Edit 2: Well it must have been something to do with the NIC (Intel Pro/1000 GT) or it's PCI slot as I went to the onboard lan and NL has been running for 2 hours and for 4 movies and transfered over 1.5GB of data when before it wouldnt' run much past 40 minutes and < 1 GB of data before crapping out. So I may try and put the nic back in and switch PCI slots with the 7506-8 Raid card and see if maybe that helps matters as I would like to get this thing to GB capable since I'm planning to upgrade my switches soon.

Lance

Lance:
In your first post you said In your second post (post#3) the SYSLOG says In your third=last post (#5) you said The second quote above seems to indicate a GigaBit card, but running at reduced speed (or worse). It could be the card, the PCI slot or cabling or non-Giga devices/cabling.

certainly change the pci slot - if its before the raid card try it after it or vica versa - thats cured more problems than enough for me

also if you have the nic in a pci slot have you turned off the on board nic - it does not always seem to matter - but it does no harm to

if you cannot turn the onboard nic off and want to use the one in the pci slot have you checked the setting within NAslite for more than one nic - it should be set to last

Georg, yeah I see the typo now, I meant to type 10/100/1000 card in my first post. It is running at 100Mbs though as I haven't upgraded my switches. The cable works fine with my onboard card. Would it make a difference using it with onboard vs the PCI NIC? The card (from what I read can do all speeds so I figured I was ok to run it at 100Mbs, is that not the case? I haven't had time to shut the machine down and move it to another slot (There are only 2 pci slots on the board and one has the Raid card and the other the nic so I'll have to swap them during a down time to test).

So far the machine has been up all day since my last edit without an issue. Perhaps I'll hold out the card until I try to move to a Gigabit switch. I had originally bought the card when I was having problems transferring multiple GB of data and I get getting a Path Too Deep error when doing so but couldn't get the card working with NL 2.04 in my last box so with the new box I figured I would try it out since I was starting with a new box.

Lance

Tony,

Thanks for the tips, I will definitely try it in another slot when I can take it down for a while. I did turn off the onboard nic while I was using the separate nic along with everything else in the bios that I knew to turn off. I just kept getting some wierd timeout and it would recover sometimes and not others. But once it went offline via the network you can't get the status anymore (which i think is not a good limitation on the product, one of the few) so I couldnt' see exactly what happened when it went offline.

Lance

You are having an IRQ conflict likely from the sound of things. Moving the NIC and RAID card will not fix this is my guess.

You can try turning off PNP OS in the BIOS and see if that helps.

Again, you may still consider the path I mentioned earlier, buying the same board I have and using that. I am not having any issues with it and it's fast with just a JBOD setup right now. For $10.00 it's hard to go wrong.

Mike

Yeah the $25 ($10 + $15 shipping) for the other board is ok but I'll need to find another video card to go in it as I have to have video so I can stand at the machine if something happens to go wrong and stuff and I would rather get this guy working. I'll try and find the option to turn off the PNP OS in the BIOS as well when I put the card back in. I was hoping something in the logs would show a conflict to let you know there is a problem rather than randomly failing. But at least it's fine now with the onboard nic just I wanna move to gigabit soon and I'll need to put a card back in or at that time move to another board.

Edit: I rebooted really quick to mess with the BIOS and saw a "Resources Controlled By" field in the Plug and Play area that was set to Auto which according to Phoenix Bios docs says that if set to Auto the BIOS sets up the IRQ's I tried switching that to manual and made sure the Parallel and serial ports were off. Hopefully that will make a difference.

Mike, I also forgot to ask what do you think about it loading up for 1000 Mbs even though I'm only doing 100Mbs? do you think that might have been a problem?


Lance

OK,

If video is a must then here is a board, this is the exact one I have. http://cgi.ebay.com/One-or-Lot-Intel-D845EBG2-MotherBoard-socket-478-2G-CPU_W0QQitemZ190361693803QQcmdZViewItemQQptZLH_DefaultDomain_0?hash=item2c5270ee6b This has the video on board.

As far as the NIC, it makes no difference to NL if the NIC has to drop back to 100Mb/sec. Performance will not be impacted unless you have an IRQ conflict.

Mike

Well it looks like I might have gotten the IRQ conflict solved. I turned off everything again including the PNP stuff and swapped the cards (I agree this might have been needless but it fits better this way) and I was able to copy a 5.5GB file and the server has been up serving movies for 1:15 which is longer than it had before when it was crashing. I'll continue testing but so far so good.

Lance

Just wanted to say thanks again..Machine has been up and running for 19 hours now and seems to be stable.

Lance