Reinstalling firmware, timing out?

[Cubytus]

Is the standalone kernel the one named UIMAGE ? Is it the option "Install fvdw firmware"?

What should I pay attention to with the TFTP server? Win XP didn't ask me for any specific firewall permission. I did as Benaslan wrote, manually assigning an IP to the virtual network adapter, but still nothing works from Telnet.

Finally, wouldn't there be an easier way to do this whole reinstallation in Linux, or just disconnect the hard drive and install an .img on it, just like the Raspberry Pi?

[fvdw]

Yes this can be done, but most people don't have a linux px or are not familuar with using linux and dont feel comfortable to remove harddisk and connecting them to a pc. Thats why we made fvdwsl console. No linux required, no disk to be removed. Yes the apple user have a disadvantage as the console runs under windows. There was a guide how to prepare a harddisk using linux. But I have no intention to write it again. I can sent you an old guide if you want.

[Cubytus]

If you can find this old guide, then I would be happy to test if it still works. No firewall, antivirus or manual network setting to worry about :)

But still, I would like to understand how I could make the Windows console work as you describe. Any idea?

Edit: here are the steps performed. The firewall has been disabled.

q1.png

q2.png

q3.png

q5.png

q6.png

Still timeout in Telnet

[cloudbox2]

Hi All,

I am in exactly the same position. I've followed all steps on this thread (excluding fixing the NAS IP address) and getting the "telenet timed out" message.

I've been using the 'Standalone kernet, load and start' from the FDVW-SL console and loading the Kirkwood UIMAGE.

One point to note - might make a difference?! I have the lacie whitebox that doesnt have a on off flip switch. It has a push button on/off which you need to keep 30secs pressed to turn off the unit, so I just unplug the power when I'm supposed to power off the unit, and re-connect when I'm asked to turn on the lacie.

Any advise would be really great.

Thanks in advance.

[fvdw]

@cubytus
:disapprove
You are using the wrong kernel (I have already mentioned this before) you must use the kirkwood standalone kernel in the tftp/ subfolder and NOT the kirwood kernel in tftp/firmware/kirkwood subfolder.
You can not miss it it contains the word standalone in the name

@cloudbox2
Which kernel did you select?

[cloudbox2]

Thanks for your reply.

I selected: UIMAGE-3142-KIRKWOOD-150-standalone from the tftp folder.

Still timing out... :s

Could this be an IP issue or because I'm switching on/off the cloudbox via the power socket?

[fvdw]

No that will not be the reason.
Common causes are:
Using a wireles connection between pc and lan, (use a wired connection),
Firewall issues(disable fire wall)
More then 1 network interface in your pc. (Disable all except one)

[cloudbox2]

Using a wireles connection between pc and lan, (use a wired connection), - I've connected the nas directly to the laptop via a ethernet cable
Firewall issues(disable fire wall) - all disabled
More then 1 network interface in your pc. (Disable all except one) - only using windows 10

"Houston, we have a problem!"

(Sorry for hijacking this thread - I hope others will also benefit from this though)

[Cubytus]

I selected the one as fvdw said, and of course, completely disabled the firewall for the interface.

q0.png

What is the difference between /tftp and /tftp/firmware folders? Is one for the source code, another for binaries?

It was long to complete, but eventually succeeded. The guide was not too clear the firmware would be directly in tftp folder. I did it all from a virtual Windows XP machine, and didn't use my Win 7 hardware computer as I still consider one shouldn't have to have a real, hardware computer running Windows to reinstall a Linux-based system.

I tried it with Mini Windows XP from Hiren's Boot CD, but it's apparently too slow to do anything useful.

The guide could be improved with what Benaslan said, i.e. to manually set an IP address to the Ethernet card and completely disable the firewall and antivirus, instead of trying to navigate permission dialogs that don't appear, etc.

@fvdw, what is the "old" guide explaining how to image the hard drive? I think that, even if it implies removing the hard drive, the success rate must be higher.

Is the fvdw-console supposed to send the right file at the right time, and coordinate Telnet, U-boot console and the tftp server? How is the U-Boot console made available on the LAN port? I naively thought one had to have access to the serial port for it…

[fvdw]

The files in the firmware subfolder are used by the firmware installer program which can be started using the install firmware action and reading the instructions. I think it is obvious when te console ask to select a standalone kernel that shoud you should select a standalone kernel, read more carefully the dialog windows that pops up.

There is no need to set the ip address manual, both ways, using the defaults or setting it as you like will work if your setup is correct.

Why we develop the console ? This is because most users don't have experience or knowledge to use linux or don't even have an usb->sata interface and don't feel comfortable to take out the harddisk and give all kind of linux commands. Also most users have a windows pc, then it is not so likely to use linux. Of course persons with linux machines might prefer manual install. Maybe one day we will make a fvdw-sl console for linux users. But as the number of potential user will be low it is not high on the priority list. Believe me using the manual setup via linux and taking out the disk is far more complicated and troublesome for most users. And then there are the MAC users. Agree for those the console is not ideal. But I don't have MAC it is difficult to develop a similar tool for it for me, sorry

About how u-boot is made available via lan port is by design of uboot. Uboot has a netconsole mode that can be activated instead of using the serial interface. When booting uboot on lacie devices checks for a signal on the lan if it should change to netconsole. That is what the fvdw-sl console does, sending this signal an forcing uboot to netconsole mode and the start a program to talk to uboot etc etc