NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Thu Mar 28, 2024 8:36 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 16 posts ]  Go to page 1, 2  Next
Author Message
PostPosted: Mon Sep 05, 2005 1:18 am 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
I'm really frustrated!!! I followed Tony's "NASLite+ In a Nutshell" instructions to a tee...

I purchased a NutShell Pro (STB1030N), the reccomented dongle (Iomega Mini USB), and NASLite+ for USB Flash. Next I modified the power cable, removed the CPU fan, added a case fan, and drilled holes in the expansion slot cover plate. Then I fought with a BIOS password (and won). Next I worked through a hardware problem (a bad memory stick).
I formatted my USB drive with the HP utility that Tony recommended. I've got everything installed and try my first boot...

The screen looks different than the documentation... "Launching Services" and "Initializing Network" are both listed as successful and the userid/password admin/nas does not work.

I've checked out the forums and find several users with the same problem but the solution is always with the floppy drive. I dont have a floppy drive!!!

Since I purchased 4 of the NutShell Pro units, I configured a second unit and I get the exact same problem. The problem is not 100% repeatable on ether machine. About 50% of the time the USB drive is not found at all. After reading the forums, I realize that there is a known problem that requires a hard power-off on some machines.

Tony, do you really have a STB1030N running with an Iomega Mini Flash Disk and NASLite+ for USB Flash? If you tell me that I've been BLOCKED_WORD and your documentation is just an elaberate practical joke, I'm gonna be really mad!!!

How should I proceed?

Thanks... Alan


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 8:07 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Quote:
Tony, do you really have a STB1030N running with an Iomega Mini Flash Disk and NASLite+ for USB Flash? If you tell me that I've been BLOCKED_WORD and your documentation is just an elaberate practical joke, I'm gonna be really mad!!!


I most definately do have a Nutshell Pro (STB1030N) running with an Iomega Mini Flash on the back and NASLite+ for USB Flash v1.0. Although I did not have the BIOS problems that you had, the process as outlined in the guide is accurate and the one that I used to complete my project.

That said, it sounds like you are almost there. The first thing I'd try at this point is to boot with the USB Flash removed. That should give you an idea of where the password is coming from. I suspect the USB Flash you are using may be the problem, so here is what I'd do:

1. Boot with the USB Flash removed.
2. Make sure the machine is in "DEFAULTS" mode. If so then the USB Flash was the problem.
3. Make sure you can login using admin/nas (lowercase as always)
4. Now insert the USB Flash in the USB port.
5. Hit "ENTER" on the keyboard to get rid of the USB init messages.
6. Do your configuration as nessessary and save it.
7. Reboot and life should be good once again ;-)

Below is a copy of the my system and sys_log info pages - a proof of a running STB1030N:

----------------------------------------------------------------------------------------------

Operating System

Linux 2.4.27.NASLite #23 Mon Mar 14 15:56:58 MST 2005 i586

Uptime

07:55:01 up 3 min, load average: 0.01, 0.07, 0.03

Processor (CPU)

vendor_id : CyrixInstead
model name : Cyrix MediaGXtm MMXtm Enhanced
cpu MHz : 267.272
cache size : 16 KB
bogomips : 532.48

Memory

total used free shared buffers
Mem: 62368 11240 51128 0 180

Disks

Filesystem Size Used Available Use% Device
System 3.9M 3.4M 528.0k 87% RAM Disk
Storage Area 146.7G 8.0k 146.7G 0% NAS Disk-1

Network Interface

e100: Intel(R) PRO/100 Network Connection
Link encap:Ethernet HWaddr 00:30:00:03:CA:F7
inet addr:192.168.1.254 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:92 (92.0 B) TX bytes:3010 (2.9 KiB)
Interrupt:10 Base address:0xe000 Memory:e3100000-e3100038

----------------------------------------------------------------------------------------------

Server System Log

* Sep 5 07:51:35 NASLite syslog.info syslogd started: BusyBox v1.00-pre10 (2004.06.01-20:52+0000)
* Sep 5 07:51:35 NASLite daemon.info init: Starting pid 258, console /dev/null: '/sbin/klogd'
* Sep 5 07:51:35 NASLite syslog.notice klogd: klogd started: BusyBox v1.00-pre10 (2004.06.01-20:52+0000)
* Sep 5 07:51:35 NASLite user.warn klogd: Linux version 2.4.27.NASLite (root@stimpy) (gcc version 3.3.2) #23 Mon Mar 14 15:56:58 MST 2005
* Sep 5 07:51:35 NASLite user.info klogd: BIOS-provided physical RAM map:
* Sep 5 07:51:35 NASLite user.warn klogd: BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
* Sep 5 07:51:35 NASLite user.warn klogd: BIOS-e801: 0000000000100000 - 0000000004000000 (usable)
* Sep 5 07:51:35 NASLite user.notice klogd: 64MB LOWMEM available.
* Sep 5 07:51:35 NASLite user.warn klogd: On node 0 totalpages: 16384
* Sep 5 07:51:35 NASLite user.warn klogd: zone(0): 4096 pages.
* Sep 5 07:51:35 NASLite user.warn klogd: zone(1): 12288 pages.
* Sep 5 07:51:35 NASLite user.warn klogd: zone(2): 0 pages.
* Sep 5 07:51:35 NASLite user.info klogd: DMI not present.
* Sep 5 07:51:35 NASLite user.warn klogd: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 BOOT_IMAGE=naslite.01
* Sep 5 07:51:35 NASLite user.info klogd: Initializing CPU#0
* Sep 5 07:51:35 NASLite user.info klogd: Working around Cyrix MediaGX virtual DMA bugs.
* Sep 5 07:51:35 NASLite user.warn klogd: Detected 267.272 MHz processor.
* Sep 5 07:51:35 NASLite user.warn klogd: Console: colour VGA+ 80x25
* Sep 5 07:51:35 NASLite user.warn klogd: Calibrating delay loop... 532.48 BogoMIPS
* Sep 5 07:51:35 NASLite user.info klogd: Memory: 60576k/65536k available (1406k kernel code, 4572k reserved, 396k data, 496k init, 0k highmem)
* Sep 5 07:51:35 NASLite user.warn klogd: Checking if this processor honours the WP bit even in supervisor mode... Ok.
* Sep 5 07:51:35 NASLite user.info klogd: Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
* Sep 5 07:51:35 NASLite user.info klogd: Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
* Sep 5 07:51:35 NASLite user.info klogd: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Sep 5 07:51:35 NASLite user.info klogd: Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
* Sep 5 07:51:35 NASLite user.warn klogd: Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
* Sep 5 07:51:35 NASLite user.info klogd: Working around Cyrix MediaGX virtual DMA bugs.
* Sep 5 07:51:35 NASLite user.debug klogd: CPU: After generic, caps: 00808131 00818131 00000000 00000001
* Sep 5 07:51:35 NASLite user.debug klogd: CPU: Common caps: 00808131 00818131 00000000 00000001
* Sep 5 07:51:35 NASLite user.warn klogd: CPU: Cyrix MediaGXtm MMXtm Enhanced stepping 04
* Sep 5 07:51:35 NASLite user.info klogd: Checking 'hlt' instruction... OK.
* Sep 5 07:51:35 NASLite user.info klogd: Checking for popad bug... OK.
* Sep 5 07:51:35 NASLite user.warn klogd: POSIX conformance testing by UNIFIX
* Sep 5 07:51:35 NASLite user.info klogd: PCI: PCI BIOS revision 2.10 entry at 0xfad90, last bus=0
* Sep 5 07:51:35 NASLite user.info klogd: PCI: Using configuration type 1
* Sep 5 07:51:35 NASLite user.info klogd: PCI: Probing PCI hardware
* Sep 5 07:51:35 NASLite user.warn klogd: PCI: Probing PCI hardware (bus 00)
* Sep 5 07:51:35 NASLite user.info klogd: PCI: Using IRQ router NatSemi [1078/0100] at 00:12.0
* Sep 5 07:51:35 NASLite user.info klogd: Linux NET4.0 for Linux 2.4
* Sep 5 07:51:35 NASLite user.info klogd: Based upon Swansea University Computer Society NET3.039
* Sep 5 07:51:35 NASLite user.warn klogd: Initializing RT netlink socket
* Sep 5 07:51:35 NASLite user.warn klogd: Starting kswapd
* Sep 5 07:51:35 NASLite user.info klogd: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Sep 5 07:51:35 NASLite user.info klogd: devfs: boot_options: 0x1
* Sep 5 07:51:35 NASLite user.info klogd: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Sep 5 07:51:35 NASLite user.warn klogd: pty: 256 Unix98 ptys configured
* Sep 5 07:51:35 NASLite user.info klogd: Real Time Clock Driver v1.10f
* Sep 5 07:51:35 NASLite user.warn klogd: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
* Sep 5 07:51:35 NASLite user.info klogd: loop: loaded (max 8 devices)
* Sep 5 07:51:35 NASLite user.info klogd: Intel(R) PRO/1000 Network Driver - version 5.2.52-k3
* Sep 5 07:51:35 NASLite user.info klogd: Copyright (c) 1999-2004 Intel Corporation.
* Sep 5 07:51:35 NASLite user.info klogd: 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
* Sep 5 07:51:35 NASLite user.warn klogd: FW Version=$Version$
* Sep 5 07:51:35 NASLite user.info klogd: pcnet32.c:v1.30c 05.25.2004 tsbogend@alpha.franken.de
* Sep 5 07:51:35 NASLite user.info klogd: ThunderLAN driver v1.15
* Sep 5 07:51:35 NASLite user.info klogd: TLAN: 0 devices installed, PCI: 0 EISA: 0
* Sep 5 07:51:35 NASLite user.info klogd: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Sep 5 07:51:35 NASLite user.info klogd: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Sep 5 07:51:35 NASLite user.notice klogd: Intel(R) PRO/100 Network Driver - version 2.3.43-k1
* Sep 5 07:51:35 NASLite user.notice klogd: Copyright (c) 2004 Intel Corporation
* Sep 5 07:51:35 NASLite user.notice klogd:
* Sep 5 07:51:35 NASLite user.info klogd: PCI: Found IRQ 11 for device 00:0a.0
* Sep 5 07:51:35 NASLite user.info klogd: IRQ routing conflict for 00:0a.0, have irq 10, want irq 11
* Sep 5 07:51:35 NASLite user.debug klogd: e100: selftest OK.
* Sep 5 07:51:35 NASLite user.notice klogd: e100: eth0: Intel(R) PRO/100 Network Connection
* Sep 5 07:51:35 NASLite user.notice klogd:
* Sep 5 07:51:35 NASLite user.warn klogd: sk98lin: No adapter found.
* Sep 5 07:51:35 NASLite user.info klogd: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.25.
* Sep 5 07:51:35 NASLite user.info klogd: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Sep 5 07:51:35 NASLite user.info klogd: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Sep 5 07:51:35 NASLite user.info klogd: CS5530: IDE controller at PCI slot 00:12.2
* Sep 5 07:51:35 NASLite user.info klogd: CS5530: chipset revision 0
* Sep 5 07:51:35 NASLite user.info klogd: CS5530: not 100% native mode: will probe irqs later
* Sep 5 07:51:35 NASLite user.debug klogd: PCI: Setting latency timer of device 00:12.0 to 64
* Sep 5 07:51:35 NASLite user.info klogd: ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
* Sep 5 07:51:35 NASLite user.info klogd: ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
* Sep 5 07:51:35 NASLite user.warn klogd: hda: SAMSUNG SP1604N, ATA DISK drive
* Sep 5 07:51:35 NASLite user.debug klogd: hda: cs5530_set_xfer_mode(PIO 4)
* Sep 5 07:51:35 NASLite user.debug klogd: hda: cs5530_set_xfer_mode(UDMA 2)
* Sep 5 07:51:35 NASLite user.warn klogd: blk: queue c0365d80, I/O limit 4095Mb (mask 0xffffffff)
* Sep 5 07:51:35 NASLite user.warn klogd: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Sep 5 07:51:35 NASLite user.warn klogd: hda: attached ide-disk driver.
* Sep 5 07:51:35 NASLite user.warn klogd: hda: host protected area => 1
* Sep 5 07:51:35 NASLite user.info klogd: hda: 312581808 sectors (160042 MB) w/2048KiB Cache, CHS=19457/255/63, UDMA(33)
* Sep 5 07:51:35 NASLite user.info klogd: Partition check:
* Sep 5 07:51:35 NASLite user.info klogd: /dev/ide/host0/bus0/target0/lun0: p1
* Sep 5 07:51:35 NASLite user.info klogd: SCSI subsystem driver Revision: 1.00
* Sep 5 07:51:35 NASLite user.info klogd: usb.c: registered new driver hub
* Sep 5 07:51:35 NASLite user.info klogd: host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Sep 5 07:51:35 NASLite user.info klogd: PCI: Assigned IRQ 15 for device 00:13.0
* Sep 5 07:51:35 NASLite user.info klogd: host/usb-ohci.c: USB OHCI at membase 0xc4804000, IRQ 15
* Sep 5 07:51:35 NASLite user.info klogd: host/usb-ohci.c: usb-00:13.0, PCI device 0e11:a0f8
* Sep 5 07:51:35 NASLite user.info klogd: usb.c: new USB bus registered, assigned bus number 1
* Sep 5 07:51:35 NASLite user.info klogd: hub.c: USB hub found
* Sep 5 07:51:35 NASLite user.info klogd: hub.c: 2 ports detected
* Sep 5 07:51:35 NASLite user.info klogd: Initializing USB Mass Storage driver...
* Sep 5 07:51:35 NASLite user.info klogd: usb.c: registered new driver usb-storage
* Sep 5 07:51:35 NASLite user.info klogd: USB Mass Storage support registered.
* Sep 5 07:51:35 NASLite user.info klogd: NET4: Linux TCP/IP 1.0 for NET4.0
* Sep 5 07:51:35 NASLite user.info klogd: IP Protocols: ICMP, UDP, TCP
* Sep 5 07:51:35 NASLite user.info klogd: IP: routing cache hash table of 512 buckets, 4Kbytes
* Sep 5 07:51:35 NASLite user.info klogd: TCP: Hash tables configured (established 4096 bind 8192)
* Sep 5 07:51:35 NASLite user.info klogd: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Sep 5 07:51:35 NASLite user.notice klogd: RAMDISK: NASLite file system found at block 0
* Sep 5 07:51:35 NASLite user.warn klogd: ...<6>hub.c: new USB device 00:13.0-1, assigned address 2
* Sep 5 07:51:35 NASLite user.warn klogd: .<6>scsi0 : SCSI emulation for USB Mass Storage devices
* Sep 5 07:51:35 NASLite user.warn klogd: Vendor: LEXAR Model: JUMPDRIVE Rev: 1.02
* Sep 5 07:51:35 NASLite user.warn klogd: Type: Direct-Access ANSI SCSI revision: 02
* Sep 5 07:51:35 NASLite user.warn klogd: .Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
* Sep 5 07:51:35 NASLite user.warn klogd: ...SCSI device sda: 62464 512-byte hdwr sectors (32 MB)
* Sep 5 07:51:35 NASLite user.warn klogd: .sda: Write Protect is off
* Sep 5 07:51:35 NASLite user.info klogd: /dev/scsi/host0/bus0/target0/lun0: p1
* Sep 5 07:51:35 NASLite user.debug klogd: WARNING: USB Mass Storage data integrity not assured
* Sep 5 07:51:35 NASLite user.debug klogd: USB Mass Storage device found at 2
* Sep 5 07:51:35 NASLite user.warn klogd: .<6>Freeing initrd memory: 1295k freed
* Sep 5 07:51:35 NASLite user.warn klogd: VFS: Mounted root (ext2 filesystem).
* Sep 5 07:51:35 NASLite user.info klogd: Mounted devfs on /dev
* Sep 5 07:51:35 NASLite user.info klogd: Freeing unused kernel memory: 496k freed
* Sep 5 07:51:35 NASLite user.err klogd: e100: eth0 NIC Link is Up 100 Mbps Full duplex

----------------------------------------------------------------------------------------------

I hope that helps Alan...


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 11:21 am 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
Tony, I've tried your instructions on two 1030Ns machines using two different Iomega Mini USB Flash Disks (both are brand new, I opened the plastic package myself). Both of the flash disks have been formatted with the HP tool that you recommended in one of the forum posts.

When I boot the systems (without the flash disk installed) the system comes up in "DEFAULTS" mode - Yea!!!. After logging in and inserting the flash drive I get several lines of text indicating that the flash drive is correctly identified, is working properly, and is not write protected.

usb.c: new USB device 00:13.0-1, assigned address 2
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: I0MEGA Model: UMni64MB*IOM2C4 Rev:
Type: Direct Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi1, chanel 0, id 0, lun 0
SCSI device sdb: 126976 512-byte hdwr sectors (65 MB)
sdb: Write Protect is off
/dev/scsi/host1/bus0/target0/lun0: p1


I change my configuration then select option 9 to save the configuration. The light on the end of the flash drive comes on (and stays on for approx 40 seconds) then it goes off, a message flashes on the screen (too fast for me to read - something like could not change address 09) and I get the terse error message "Could not save configuration. The USB Flash drive is not available."


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 11:34 am 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
Tony, I have several USB flash drives so I decided to try the others. Your instructions worked fine with a SanDisk Cruzer Mini (128MB). The configuration is saved properly. Unfortionately the device sticks out 2.5".

I thought I would be smart and copy the config file from the SanDisk to the I0MEGA. When I attach the SanDisk to a Win XP machine it says the flash drive is empty. Now I'm confused again... Are you saving the configuration to the file system or are you doing low-level IO to the flash drive.

Any idea how I can use the small I0MEGA drives?

BTW, I havent formatted a drive yet, but the functionality of NASLite is exactly what I was looking for -- simple and efficient. I've tried both the web and telnet interfaces.

Thanks... Alan


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 1:26 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Hi Alan,

Looking at this:
Quote:
usb.c: new USB device 00:13.0-1, assigned address 2
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: I0MEGA Model: UMni64MB*IOM2C4 Rev:
Type: Direct Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi1, chanel 0, id 0, lun 0
SCSI device sdb: 126976 512-byte hdwr sectors (65 MB)
sdb: Write Protect is off
/dev/scsi/host1/bus0/target0/lun0: p1

There is a SCSI device already enumerated when you insert the Iomega, so that is a problem. At this point, if another usb drive is working, there is no apparent reason for the Iomega drive not to work. The above indicates that there already is an sda device present and therefore the Iomega gets rendered as sdb. That is a problem since the only SCSI device identified by the NASLite kernel should be the configuration flash drive and that should be sda.

I'll repeat the process in my original post from a powered down state. Make sure you keep an eye on the USB initialization message. If the USB device gets rendered as anything other than disk sda, configuration will fail. Again, the only reason it may render as sdb is that an sda is already present. In theory that is not possible unless you are plugging different usb drives in and out. That will cause each to be assigned a consecutive device, so do it only once with only one usb drive.

Embedding often seems simple, but there are many reasons that may hinder your success. One thing that is extremely important is knowing that the hardware you are using is healthy and in good working order. If that is not the case, then troubleshooting becomes a nightmare as you can see.

The config is low level, so looking for a file will turn out nothing.

Give it another try from a powered down state...


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 9:21 pm 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
Tony, in the example that I previously listed, the reference to sdb was my mistake. As you suggested, I had removed dongle 1 and inserted dongle 2. When I follow your instructions after a reboot, the reference is correctly sta. Sorry for my confusion.

I am still unable to get the I0MEGA flash drives to work. When attempting to save the connection I receive the following:

SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000
I/O error: dev 08:00, sector 8202
1+0 records in
1+0 records out
sda: Unit Not Ready, error = 0x70000
sda : READ CAPACITY failed.
sda : status = 0, message = 00, host = 7, driver = 00


The same machine works just fine with a formatted SanDisk Cruser Mini.

On another note...
I realized that you published v1.1 of NasLite+ for USB Flash Drive a couple of days ago. Thinking that the new version might solve my problem, I downloaded and installed it. When I try to boot the machine (without a hard drive or dongle installed) it gets to a point where is is processing "Media" and just generates periods for a couple of hours (probably longer but I let it run for 2 hours 2 times before rebooting the machine) without booting. Is v1.1 working? When I installed it I just copied the contents of the DATA directory ocer the top of the existing files on the DOC. I'll try again - formatting, running syslinux, and copying the files from the DATA directory.

I'm keeping the faith that we'll get this thing working.

Thanks... Alan


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 9:44 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
There is something wrong with the Iomega flash drives since it clearly fails to initialize properly. The one I used behaves normally and in the same way as the Lexars i usually use.

Anyway, v1.1 is a bit different so the troubleshooting approach will have to be different also. 1.1 will not initialize unless it finds the configuration media. That's why you see the dots adding up each second.

What I'd do is install NASlite on the Iomega drive via the CD-ROM on another machine. That will insure that the configuration is null and no funny stuff is left on the USB drive itself. Then, I'll insert it into the 1030N USB port prior to powerup. Once everything is in place and v1.1 is in the DOC, I'll boot and hope to enter DEFAULTS mode as expected. At that time, login, configure save and reboot. Hopefully, all should be good.

When placing NASLite on the Iomega, I'd use Option 2 and configure it as an HD partition.

Your persistance with this project is admirable and I hope that the final result is as good as you expect. Such projects can often be very frustrating. You had the unfortunate case to receive a goofy BIOS, have a case of bad RAM and now a fussy Flash drive. I would say that this is not common, but I've had days or should I say weeks just like this. The good thing is that at the end things tend to work out. You are close, the only thing left is to trim the prong on the back ;-)

Let me know how the next attempt goes...


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 9:47 pm 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
Tony, did you ever want to take a BIG hammer and smash a computer into 1 million pieces? I'm there!!!

I'm crazy (I keep doing the same thing expecting different results). Now I'm getting different results...

After a power-down reboot using a formatted flash drive, I'm sometimes able to get a "Configuration saved." message followed by the following lines (8 times)

hub.c: Cannot enable port 1 of hub 1, disabling port.
hub c: Maybe the USB cable is bad?


Of course, I'm not using a cable.

If I do EXACTLY the same thing again - power off reboot, with formatted dongle (I've tried 2 dongles) I may get the error listed in the previous post, or I may get the error listed in this post. Either way, I cant get these I0MEGA dongles to work.

Now where did I put that BIG hammer?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 9:55 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Alan,

Is the strange behavior only with the Iomega or does it behave poorly with the with your SanDisk also?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 9:59 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Also, what is the version of your BIOS? I'm using 2A434H09. You can see it on the top line when you enter the BIOS settings...


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 10:19 pm 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
Both of my IOMEGA flash drives are having a problem but the SanDisk 128MB has not yet had a problem. I have a SanDisk 256 that I'm going to test with too. I'm thinking that the problem is the I0MEGA drives. The nice thing about the I0MEGA drives is that they are not only small, they are cheap.

I verified that my BIOS version is the same as yours (2A434H09).


Top
 Profile  
 
 Post subject:
PostPosted: Mon Sep 05, 2005 11:31 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Well Alan,

The only conclusion I can derive is that there is someting substandard about the Iomega disks you have. There is no reason for a flash device to act out unless there is something weird about it. The only flash drive that I've had problems with is a flash/mp3 player combo that has an identity crisis on boot, but other than that all of the flash disks i've used are consistant.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Sep 06, 2005 9:42 pm 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
Tony, it looks like we got it...

After getting around the BIOS password, identifying that I had a bad memory stick, and replacing the faulty I0MEGA USB flash drives all works well (with v1.0 that is).

I picked up a couple of FMI (generic stuff sold at CompUSA) 128MB USB flash drives that were on sale at CompUSA for only $9/each. They are about 1/3 larger than the tiny I0MEGA but much smaller than the SanDisk that I was testing with.

Now I've got all the confidence in the world that v1.1 will be a slam dunk :-) I'll let you now how I make out with that. Seriously, thanks so much for all of your assistance!!!

Thanks again... Alan


Top
 Profile  
 
 Post subject:
PostPosted: Tue Sep 06, 2005 10:22 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Good to hear that Alan. For a moment there I thought you'd give up and walk away from the challenge ;-)

One thing I can add to the instructions in the guide is that there is no speaker in the Nutshell. However, there are speaker headers on the board, so one can easily be added. Also, even with the fan, I think that drive cooling is barely adequate. At 40-45 degrees C, it's borderline for my taste. The problem however is esthetics, so if you don't care about pretty looks, make some more holes for increased airflow.

Other than that, it's a nice package.

The only improvement would be the addition of a second drive, but that will be considerably more difficult than the first one. With the heat-generating power supply on the opposite end, the only place to put it would be next to the first one. Not an easy task.

Anyway, let me know how v1.1 does for you. I expect that everything should fall right in place.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Sep 07, 2005 12:07 am 
Offline

Joined: Sat Aug 20, 2005 3:13 pm
Posts: 20
Tony, v1.1 went on very smoothly. The only hiccup was when I tried to use the "virgin" USB flash drive. The system went into the mode where it wouldnt recognise the admin/nas account.

I booted the v1.1 image in a CD and used mode 2 to copy the system and config files to the flash drive and all was well.

I like your idea about adding a speaker. I'm going to do that for sure.

RE: adding a 2nd drive, I dont think it would be too tough, if you notice there are two threaded screw holes at the front of the unit. If the slot assembly is removed at the back, I think some cheap strapping from Home Depot could be bent and drilled in such a way that it is suspended over the motherboard from the front to the back of the machine. The two drives would lay on top of it. Since the drives have screw holes on the bottom, they could be screwed to the straps. Hey it might work!!!

The two things that I would be afraid of would be the temp and power consumption. I'm clueless about the power supply. do you think it would support 2 drives?

Is there aLinux package available (that you could add to a future version of NASLite) that could report the system/motherboard temp from the system tab?

I over-drilled every other hole on the top of the case so that it looks nice but gets better air flow. I took a Black sharpie and ran it along the inside of the holes so the shiney silver metal doesnt look so bad.

My Linux skills are weak... If I added a 2nd drive (a 2nd 300GB) can I use both drives as one large 600GB drive without mirroring? I think that is called JBOD (or something like that)???

Goodnight... Alan


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 8 guests


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

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