NASLite Network Attached Storage

I decided to upgrade from NASLite+, and I've been forced to go back to it.

First I had trouble finding a PC that would configure the keys, as my Athlon 64 systems wouldn't do it. Eventually I managed that, on a P4.

Now I have programmed keys which boot! But you can't use them because although it says it's saved, and the USB key flashes to say it was accessed, when you reboot you go straight back to the default admin blank system.
I've tried three different keys on three different systems, with exactly the same result. Any thoughts? (and no, they aren't write protected...)

Hm,

That's strange since saving the configuration is done by the same code that reads it. Are you sure that you are looking at the defaults after configuration?

Yes I do. Because none of the information is saved and the sytem comes back without the services running.

Based on another thread I'm going to try some more keys...

I have exactly the same problem with a Sony USB device.

What I don't understand is how the device gets written to succesfully initially and then fails to accept the configuration settings

Keith

picknmix / keith

This is strange. I can't duplicate it on any of my hardware. Are your USB flash disks configured as superfloppy or a partition?

Mine's set to superfloppy

I've now tried two different USB keys - Verbatim and Sony, plus I've tried with three different types of CF card through a USB adapter - Kingston, SanDisk and Lexar.

Other than the SanDisk, which wouldn't work at all, all the other devices would accept being programmed by the CD, would then boot OK but fail to accept any changes to the configuration.

I'm using a Shuttle FN41 motherboard - using method 1 (superfloppy)
Method 2 won't work at all.

I think I'm about to give up on this until it's fixed.

Keith

I'm having what seems to be a similar problem. I have no trouble creating a USB drive as either a super floppy or bootable partition on three different FLASH devices; 128 meg Lexar jumpdrive, 64 meg "EL Cheepo", 32 Sandisk CF card through a Sandisk reader. I can not get either of the three to boot my Compaq Ipaq desktop but I can get the CF card to boot an ARCOM SBC-GX1 motherboard that has a bootable CF slot but it will not save the configuration. The GX1 has USB ports and writes the config to the USB flash but will not read it. I know it would be better if had a generic motherboard that would bot from USB but......Thanks

I am also having problems with setting up Naslite for USB. I programmed the first USB stick ( a dell 128Mb) and am using a Dell optiplex machine. This one accepted the boot program but hung halfway through. I then used a Sony 128Mb stick and this booted and let me into the default configuration screen but didn't save any information. Everytime i switch on i go straight into the default configuration and all previous changes have been forgotten. HELP. i am desperate to get past this stage so i can actually make use of the program.

Well,

It's definitely apparent that this is not an isolated issue, so I'll be working on resolving that next. I still can't replicate the problem on any of the machines here so the next step i think will be to collect some data from your machines - if that would be acceptable

I'll be preparing a small floppy-based utility that you can download and make a floppy to boot on the troubled systems. The utility will get some info about the hardware. You can then email me the results so I can take a look at what we are up against.

Hopefully, the issue will become obvious shortly.

BTW, do the MBs you are trying to use support SATA?

No - the one I'm working with doesn't.

I've made a temporary fix for my MB by moving the files from the CD version of NASLite+ to a Key and using that instead of the CD drive. I can at least get two drives in my case now.

Looking forward to the fix though - let us know when the floppy version is ready and I'll E-Mail the info you need

Keith

Hello everyone,

In order to allow us to take a look at your Computer/USB Flash combinations that fail, we’ve created a small bootable floppy disk utility that should collect some hardware data for us to examine. The Hardware Info Utility is available for download at the following link:

http://www.serverelements.com/utility/NASLite-Hardware-Utility.exe

To use it, observe the following steps:

1 - Make a bootable 1.44M floppy disk by executing NASLite-Hardware-Utility.exe in Windows.

2 - Use the newly created bootable floppy disk to boot the problem hardware with the USB Flash in place. Essentially configure as if you’ll be using the NASLite+ for USB Flash utility CD or booting from the USB Flash, but instead boot the floppy disk.

3 - Email me the HARDWARE.DAT file that is created on the floppy disk. The floppy is FAT, so you’ll be able to read it in Windows.

Repeat steps 2 and 3 for as many PC/USB Flash combinations as you can, emailing us each of the HARDWARE.DAT files in between.

That will allow for close examination of how the kernel renders the different hardware variations in the devfs tree. After a number of samples, the shortcoming should become obvious.

Thanks in advance for your support.

maybe a stupid question? are you using the USB stick always in the same USB port....if not, i know you have this problem.
Wolfgang

Hi Tony.

I have the same issue (USB Key is created ok, system loads, but config is not saved).

Where do we send that hardware.dat file to?

Well,

We've spent a fair amount of time on this, but have been unable to replicate the problem. Also, examining the hardware info files that have been submitted suggests that the hardware is in fact available and rendered in the necessary context. So the question remains;

Why is the configuration saved yet not restored on reboot?

The only answer that we can come up with is the USB hardware initialization timing. NASLite+ for USB Flash assumes the USB drive is available at the time it fetches the configuration. If it isn't then the default mode is initiated.

The reason for the problem is most likely slow to initialize USB hardware.

So, a revision to the OS will have to be issued. We need some beta-testers to verify the fix in the next few days.

Please private-message me if you are willing...