Lacie network assistant cannot find drive

If you do anything wrong, it can break your device. You should only proceed when you understand what you are doing. Luckily you donвЂ™t have to, at least not when your device is running firmware 1.1.8, as I found out thanks to a post from user вЂhardel09вЂІ (read here).

However I didnвЂ™t want to physically open the device and void the warrant. I decided I didnвЂ™t want to submit the device for RMA again and wanted to get root access to the device and repair it (read: make it more stable) myself. I expect this might be caused by the autoscan feature that indexes the media on the device, or maybe the device just doesnвЂ™t have enough memory to cope with the continuous transfer of big files. The system log showed a kernel that was randomly killing processes. Therefore I sent the device for RMA to LacieвЂ™s service desk where it was repaired.ДЄt least I thought it was, because after copying those large files again, the device broke again, but this time I was luckily still able to reboot and keep the device up a little while before it required a new reboot.

This broke my device in such a way that it would become unusable (no admin panel, though still pingable). My problem with the NAS is that the kernel running on the device starts killing processes when I copy very large (2 GB+) files to the NAS via file -and print-sharing (using the samba server). The NAS has an ARM926EJ-S processor, a 1TB hard disk, 16MB of memory, an USB port and no fan (which makes it pretty quiet). Very handy, if it works as you expect it to. This device, also called Network Attached Storage (NAS), enables you to hook it onto your (local) network and access files via file -and print sharing, ftp and other protocols.

Lacie network assistant cannot find drive