Trying to install on a new Cloudbox

[Cubytus]

Hi there,

I'm trying to install the firmware on a CloudBox running stock firmware.

So after starting the console, I correct the NAS IP to 192.168.1.102, the IP it receives from the router, then select my computer's IP, then use the "Install firmware" command and select the UIMAGE for the Kirkwood.

Then console just sits there and doesn't catch the boot, Kernel is never loaded, only LaCie's own firmware boots.

The fvdwsl console itself isn't responding anymore.

That is, on a Windows 11 computer.

I also tried leaving the NAS IP at the default .252 address, then .251, to no avail

[Jocko]

Hi Cubytus,

I am not at home for 10 days. So I can not help you much. But this is wrong :

So after starting the console, I correct the NAS IP to 192.168.1.102, the IP it receives from the router, then select my computer's IP

With fvdw-sl console, NAS gets a temporary IP address (eg. 192.168.1.252) not linked with former used. You should not change this setting

[Cubytus]

Thanks Jocko, I also tried this, but still didn't work. NAS connected to the LAN.

[Cubytus]

Any clue about what's going on? :thinking

[Jocko]

Hi Cubytus,

I am sorry but I forgot to answer you after going back...

Before investigating more, did you check these points listed in this topic :
viewtopic.php?f=7&t=2645

Please to note about "- more than one ethernet adapter in your PC " without that you can never get a telnet access. So all network interface must be disabled on your laptop except the one used by the wire connection

[Cubytus]

I did as the other page said: disabling all interfaces except the Ethernet one.

I installed patch02 by first creating fvdw share, then enabling Samba 4.x, then letting it reboot. This is actually mandatory for Windows 11 compatibility.

Now I have 2 more fvdw-powered Cloudboxes :woohoo

Even as the install process is pretty fast once everything is set up properly, there are still grey areas that won't make sense to a non-techie:

1. I think https://plugout.net/viewtopic.php?f=7&t=2645 should be updated: even virtual wired adapters or VPN virtual adapters must be disabled because they will interfere with the console.
2. In the instructions, make it clear that .252 must not be already in use and that it's hard-coded in UBoot (I assume)
3. No matter the setting, blue LED doesn't power on.
4. Also make it clear that Cloudbox original firmware can't be backed up. It is written, but not emphasized enough.
5. In the GUI, make it clear that add-ons can't be installed or SMB 4.x be enabled without first giving forum credentials in the right tab (and being a registered donor):
6. Non-techies never refer to their devices by the architecture name, so you could emphasize the commercial name while keeping the CPU name/architecture between parenthesis.
7. This part of the instructions: "you will see the interrupt in the u-boot window". It's technically true, but it's a pop-under. The user may only see a black command window appearing below the already existing windows and won't know what it is unless they click on it.
8. Provide an easy way to upload a patch from the computer. Currently, one has to create the fvdw share, a new user, then return to LAN browsing, upload the patch, then switch again to the web GUI to select patch and give commands.
9. Reboot after adding shares or users. At first they often don't appear right away, and a reboot solves that.
10. Automatically create shares when an add-on or server creates it. It doesn't make much sense to know that tr-downloads is automatically created on install but somehow doesn't appear in the list.
11. I may insist, but given how easy the Cloudbox is to open, a directly-flashable .img could also work. The advantage is not having to deal with all Windows-related quirks, and not needing Windows in the first place.