Install firmware on new harddrive

[thekman31]

Hi,

I know this question has been asked before but there was no detailed resolution.

My Lacie CloudBox drive has failed, so I bought a new drive to replace it.

When installing the firmware downloaded from this site, do I have to install through the network or can I plug the drive directly into a PC and install?

I have tried using the network option, but I get a timeout error when trying to get a telnet session.

Could anyone help?

[Auroro]

Hi, thekman31.

It sounds as if you trying it to install it from Windows.

I installed the firmware mostly manually from a Linux box, without removing the drive from the NAS, and with clunc and the bash installation script. I don't do Windows, but would suggest the following:

The Windows software should just work without needing to telnet into the NAS.

Read the directions carefully three or four times.

Make sure that the NAS is connected to the router that is the gateway for the computer and gives out IP Nos.

Telnet to the IP No. leased to the NAS, either log into the router and find it or, I believe, "arp -a" works on Windows and should tell you what it is. Otherwise, try to telnet to 192.168.[0 or 1].252.

Could a firewall be blocking the telnet port (23).

If all of that fails and you have access to a Linux box: either (a) install the firmware with clunc and the bash installation script or (b) install the drive on the Linux box and install the firmware manually (there are instructions for the same on the Forum).

Good luck.

[thekman31]

Hi Auroro,

Thanks for replying.

I've tried numerous ways to get something to happen but still no luck.

Here's what I've done so far, perhaps you can tell me if I'm missing something.

1. Set my router to give Nas an IP of 192.168.1.252 (this is binded by MAC address)
2. Powered off NAS. New hard drive is installed, with no partitions on it (perhaps I need to partition it first)
3. Started FVDW-SL console
4. Selected Action->Standalone kernel load and start
5. Selected yes for is your device a lacie NAS.
6. Selected UIMAGE-395-NWSP2CL-179-standalone and clicked OK (have tried others too)
7. U-boot console window then appears. I then plug in NAS.
8. After a few seconds, the u-boot window disappears, and console says waiting for telnet client to start
9. Telnet client then starts, but times out after 10 secs.

After that, nothing happens.

Hope you can help me.

[fvdw]

you do not need to assign an ip to the nas.
When the u-boot window is there and you start the nas does it show that it loads the kernel

you should see something like this

Code: Select all

Filename 'UIMAGE-395-NWSP2CL-179-standalone'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################
done


and then

Code: Select all

## Booting image at 00800000 ...
   Image Name:   Linux-3.9.5
   Created:     xxxxx
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    xxxxxxxxxxxx
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...


sometimes the telnet client gives up to fast. Then just use the connect button in the telnet client to try again.

Ps your router must use ip number in range of 192.168.0.xxx or 192.168.1.xxx
If your router uses the first one then use 192.168.0.252 to approach the nas with the telnet client if it is the second use 192.168.1.252
Do not use a wireless connection between windows pc en LAN

[thekman31]

The uboot window has never shown the output that you stated.

When I start the NAS after the uboot console windows displays, it disappears almost instantly afterwards.

No loading is happening.

I should mention I am running this under Windows with firewall and antivirus both disabled.

How could I try the same process using linux?

[fvdw]

no the process should work very well under windows. It seems to me that the tftp server can not be contacted. Did the tftp server start when you before the u-boot window appeared ? ((a window should have pop up with title tftp server)
If it did then for whatever reason your lan is blocking access to the tftp server. If the tftp server didn't start automatic you could start it manually in th fvdw-sl console before choosing load standalone kernel.

If the standalone kernel doesn't seems to run we can try to run it form u-boot terminal console and enable netconsole output to see if we get info were there kernel loading fails fails

To do this switch off your ws, then fire up the fvdw-sl console, start the the tftp server and then choose the action u-boot console
A command window will pop up mentioning that it is waiting for u-boot
Now start the cloudbox
The u-boot console should intrupt boot and ask you to click on it., now you get a Marvell>> prompt in the u-boot console window.
Now we are talking to u-boot running on the cloudbox.
Set boot parameters by entering after this prompt these commands
(do not replace ip addr and serverip and so on by actual ip's, type the command exactly as given)

Code: Select all

Marvell>> setenv ipaddr ${ipaddr}; setenv serverip ${serverip}
Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7

(you can paste it in the window, right click on title bar of the window and choose edit)

Then upload the kernel

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-395-NWSP2CL-179-standalone

this will give output that it uploads the kernel and mention when it is done

next boot the kernel

Code: Select all

Marvell>> bootm

and see what happens.
Also look in the tftp window what happens there

[thekman31]

Success!

Ubuntu was my friend in the end. Installed with no issues at all.

For anyone looking for the same thing using Ubuntu, here's what I did:

I had a brand new drive, exactly the same model and size as the failed Lacie Drive. It was uninitialized with no partitions.

1. Download clunc: ftp://lacie-nas.org/tools/clunc-1.1.tar.gz
2. Download tftpd-hpa (I followed instructions from here: http://www.cyberciti.biz/faq/install-configure-tftp-server-ubuntu-debian-howto/
3. Make sure that tftpd-hpa 's folder location is the tftp folder of the fvdw-sl-console.rar file downloaded from this page: http://plugout.net/viewtopic.php?f=7&t=1271.
4. Untar, make and run with ./clunc -i ip_address_of_nas (can be anything that is not used by another device. I used 192.168.0.252)
5. Power on NAS, after a few seconds clunc will display a Marvell>> prompt.
6. At the prompt type the following: setenv ipaddr ip_address_of_nas; setenv serverip your_computer_ip; tftpboot 0x800000 name_of_image_file (in my case it was, UIMAGE-395-NWSP2CL-179-standalone)
7. If the tftpd-hpa is running correctly, you should see Loading: ########## and then the Marvell>> prompt. If tftpd-hpa is not working, the output will display Loading: T T T.
8. Next type: setenv bootargs ip=dhcp console=ttyS0,115200 netconsole=6666@ip_address_of_nas/,6666@your_computer_ip/
9. The console will echo the command you typed and then take you back to the Marvell>> prompt.
10. Next type: bootm 0x800000
11. The nas should then boot the image and load the kernel. In the output that follows, look for the line netconsole=6666@dhcp_assigned_ip_of_nas/. This is the address to telnet into. The Marvell>> prompt will not display again.
12. Open up another terminal and you should now be able to telnet in to the nas using the dhcp address.

From this point, follow the steps from step 6 onwards from the install_fvdw_sl_firmware_hlp.htm. This file is included in the fvdw-sl-console.rar file in help directory.

Hope this helps someone and thanks to all for your help as well.