plugout.net

hi, currently i'm trying to install fdvw on a lacie cloudbox 2tb....

as the instructions says wait for u boot, then telnet... that is where i get stuck, it times out ....

is there any solution to how to install it manually ?? i try to reconnect but still times out ...

edit: wrong file... fixed it

kicsrules wrote:hi, currently i'm trying to install fdvw on a lacie cloudbox 2tb....

as the instructions says wait for u boot, then telnet... that is where i get stuck, it times out ....

is there any solution to how to install it manually ?? i try to reconnect but still times out ...

edit: wrong file... fixed it

Hello,
I'm discovering this forum and try to follow instructions since my LaCie Cloudbox hard drive had suddenly stopped to work (dead).
I bought a new hard drive and try to setup from scratch.
I'm ending with the same time out at telnet step. The uboot is working. NAS is taking an ip adress (192.168.1.252) but can't be ping or telnet
how did you fix your issue ?
I used kirkwood img UIMAGE-3142-NWSP2CL-14
is that correct ?
Thanks
uby

Ok, sorry, wrong file...
Now I understand.

;) Yes you must select the kirkwood standalone kernel, it has a name including the the word "standalone"

I'm having the same issue with the telnet timing out. The window opens and then nothing - no log on prompt and then the time out error window opens. After it times out, I can log-on manually so a connection can be established and it stays established (I am on a wired connection). I'm using a cloudbox with a freshly formatted 3tb disk. Any suggestions?

So you can log on manually with telnet ?

If so you can proceed with the commands to install firmware or other action you want to do.

If the telnet client times out, but after a while you can log on manually it means that the kernel loading takes more the normal. Most of the time this is caused by an issue with the harddisk. During kernel loading the disk is probed by the kernel. If the disk respond slow or not, a repeats the probing several times. After several attemps it gives up. A normal good disk should respond fast. A slow response can have several causes

fvdw wrote:So you can log on manually with telnet ?

If so you can proceed with the commands to install firmware or other action you want to do.

If the telnet client times out, but after a while you can log on manually it means that the kernel loading takes more the normal. Most of the time this is caused by an issue with the harddisk. During kernel loading the disk is probed by the kernel. If the disk respond slow or not, a repeats the probing several times. After several attemps it gives up. A normal good disk should respond fast. A slow response can have several causes

Where can I find the commands to install the firmware?

Gilbert115 wrote:The firmware is cloudbox fvdw-sl 16.1 which I believe is the latest. That was a fresh install and no patches have been applied.

So if you have this version you should not need to install again the firmware! except if you have made some bad changes on the firmware partition

When I first set up I was able to get the full suite of information. Now all I get is a blank box with the Current System Status hanging on 'execution command, please wait'.

What you may do if you can load the upgrade menu is to upgrade the firmware by using the same image version (viewtopic.php?f=7&t=2313) which will give you a clean firmware partition.

i was flashing the wrong file, good thing it didn't flash ....

Jocko wrote:

Gilbert115 wrote:The firmware is cloudbox fvdw-sl 16.1 which I believe is the latest. That was a fresh install and no patches have been applied.

So if you have this version you should not need to install again the firmware! except if you have made some bad changes on the firmware partition

When I first set up I was able to get the full suite of information. Now all I get is a blank box with the Current System Status hanging on 'execution command, please wait'.

What you may do if you can load the upgrade menu is to upgrade the firmware by using the same image version (viewtopic.php?f=7&t=2313) which will give you a clean firmware partition.

I ended up resolving the problem with a new HD - it looks like the one I was trying to use is bad.

Thanks for the help!