plugout.net

Hello there,

I replaced the 2TB Seagate HDD in my Cloudbox with a 4TB Hitachi. Obviously, I now need to reinstall fvdwsl firmware. Since it seems easier to do so under Windows, I configured a Windows XP machine in VirtualBox with a "bridge" connection to the router and allowed primiscuous mode to all. The virtual machine has a 192.168.1.9 local IP address.

The LaCie Cloudbox had been assigned a 192.168.1.10 local IP through static DHCP in the router.

I then started the fvdw console, and replaced the 192.168.1.252 with 192.168.1.10 IP address, and followed the instructions to select the Kirkwood UIMAGE. However, a moment after the Telnet window appears, I get a "Time out" message.

What am I doing incorrectly?

You need to attach the cloudbox directly to your PC/Mac via LAN!
Important: when first using the program in windows and you have a firewall running you must grant access to several programs like tftp nc and clunc-open. Windows will ask for this permission. If you don't grant access the console cannot work.

This is contradictory: do I need to attach the NAS and computer directly, or do I need to connect them both to the LAN?

Windows didn't ask me to grant access to any program, though I don't recall turning on the firewall.

Wouldn't there be an easier restore method without using Windows?

I meant LAN as LAN cable, without a router.
Unfortunately you cannot clone your old HDD as you need a new partition table for drives over 3TB.

Did you make sure you followed the instructions correctly? Are you sure you selected the correct image?

Maybe @fvdw can help? :)

Hello there,

I replaced the 2TB Seagate HDD in my Cloudbox with a 4TB Hitachi. Obviously, I now need to reinstall fvdwsl firmware. Since it seems easier to do so under Windows, I configured a Windows XP machine in VirtualBox with a "bridge" connection to the router and allowed primiscuous mode to all. The virtual machine has a 192.168.1.9 local IP address.

The LaCie Cloudbox had been assigned a 192.168.1.10 local IP through static DHCP in the router.

I then started the fvdw console, and replaced the 192.168.1.252 with 192.168.1.10 IP address, and followed the instructions to select the Kirkwood UIMAGE. However, a moment after the Telnet window appears, I get a "Time out" message.

What am I doing incorrectly?

The static ip is assigned to a mac address, u-boot uses most of the time another mac address then the firmware. remove the static ip address in your router and leave the default settings as they are in the fvdw-sl console.

next in the u-boot command window that you get in the fvdw-sl console when choosing load standalone kernel or writing firmware) you have the message waiting for u-boot, in this command window did you see it change after you started your cloudbox that u-boot was interrupted and that the standalone kernel was uploaded and started succesfully ? If that upload fails then there is no standalone kernel uploaded and not started so telnet cannot connect.

This virtual box stuff might not work it need dedicated access to your network interface. if you have more then one network interface on your pc for instance wireless and wired, disable them all except one ->the wired one

I did as Benaslan said, connecting the NAS to the LAN port of the Mac. The Win XP virtual machine has 169.254.60.47 as an IP, and the fvdw console assumed 169.254.60.252 for the NAS.

At first trying to upload, it detected the U-boot correctly, but Telnet window still times out. Am I missing a step here¿

detecting u-boot is one but you must see as I described that the standalone kernel is really uploaded and started. In the u-boot command command window it will show the upload and with many xxxxxxxx and then message on loading and starting of the kernel.
Did you see that ?

I selected the "install fvdw firmware" option from the fvdw-console. The last windows I see are those:


Then



Then the "auto1" window disappears, Telnet window appears, but always give a "timed out" message.

The upoading of the kernel fails. Can only be if the tftp server cannot communicatie with the ethernet port or a firewall is blocking the traffic. Furthermore you selected the wrong kernel you must select the standalone kernel. However as long as the tftp server cannot send the files selecting the correct file wil not help you. You need to find out why tftpd server cannot send or receive files

I suggest you set the IP Adress of your VM to something more accurate like
192.168.1.101
Gateway to 192.168.1.1
Subnet 255.255.255.0
DNS 192.168.1.1

So the NAS hopefully adopts to the 192.168.1.xxx range