NASLite Network Attached Storage

I filled up my one hard drive on my NASLite-2 CDD.

I had another hard drive. A SATA one. I hooked it up to a USB to SATA and pluged it in. Telnet to it and formated it. Took about a half hour to format it. Then rebooted but it did not mount it. I telnet again and I think I set it to RW and then rebooted this time it seen it.

Then I started to copy some things off of Disk-0 to the new Disk-1 but it will come back with:

"Cannot copy file: The request could not be performed because of an I/O device error."

I rebooted and then it did not mount it. I guess something is wrong with the hard drive. I don't know I rebooted it 3 times it never seen the hard drive again.

I gave up and put it on my Windows XP. A USB hard drive. I did Management and picked fast format. Then copyed the data over form \\naslite-2\Disk-0 to E:\ that worked.

I don't know what was wrong.

O yes. I it was beeping 3 times about every 5 minutes. So I telnet to it and changed it form 95% to 99% It was 96% full. I saved the config and even after reboots it was still doing the 3 beeps. Till I copyed some files off it to the same USB drive only on my windows XP from naslite-2.

The problem is most likely the USB cable. Poor contact at USB and FireWire connections make such storage a poor choice.

Maybe the USB. But I never pluged any thing in the USB and the one on my XP Is the front USB. It has USB things plugged in and out of it all the time. I just copied a lot from NasLite-2 to the same USB hard drive on my Windows XP.

Moved about 33 GB off the NasLite in about 45 minutes over the Ethernet Should be a Gigabyte Ethernet all the way.

Is there a way a error log would say what went wrong on NasLite?

NASLite-2 has nice stats, so looking at those may help.

The only problems that I have ever had are, #1 IDE misconfig's, #2 master/slave misconfig or #3 loose cables.

Never anything else and I have been running my boxes forever.

I'll get just a bit technical here. The USB plug you use alot should have clean connections that are relitivly clear of oxidation. This is due to the fact that you are sweeping the contact points every time you plug in. There are very few really well made connectors on the low end and the plating is less than crap on on most.

I would also lean towards there being a poorly implemented SATA to USB chipset. MS just may have a work built into their driver to contend with this.

I personaly wouldn't mess with USB hard drives for any sort of data storage, to slow and it is another layer or three of hardwarre that can go wrrong.

Mike