NWSP2 Disk died- starting over with new one

[mdi]

I was able to try another PC with Windows 11. I disabled the WIFI, but on this machine the result is that the u-Boot immediately recognize the connection even if the NAS is not started, so it doesn't connect either.
I don't know why it feels there is a connection but it happens in 1-2 seconds since the u_boot connection is started from the Console.

[fvdw]

Then some other device on your lan is responding to the broadcast of the fvdw-sl console causing uboot window to continue. You will need to disconnect that device.

[mdi]

I just have a couple of RPi computers in the network, they don't use u-Boot. All the rest is disconnected, including tablets (they are turned off completely).
I don't think phones uses u-Boot?...
Any chance I can see the MAC address of the responding device, from the console? Or with a windows command?

Anyway if there is a way with a direct Linux image I can use, that would solve the issue, I think.

[mdi]

Ok, managed to connect!!!

I will try installing the firmware with the console. The culprit was a wifi RGB bulb I have in a lamp.

[mdi]

I was able to install the firmware and also ensured i have the updated uBoot installed too. I'm now restoring the data. Thanks!

[fvdw]

:thumbup :applause ... nice, good to hear that you finally succeeded.

[mdi]

I tried to upgrade to version 18.2, but I receive an error 200 to retrieve the updated firmware.
My user account was set correctly in the SETUP menu (the final status message confirmed it was able to connect with my credentials).
See attached image.

Code: Select all

=> Firmware upgrade step 1 started:
Search firmware version information for nwsp2 ...
The latest version available from http://plugout.net is: fvdw-sl 18.2

Check free space on system partition ... OK
Failed to connect to [http://plugout.net]
Error 200


It seems this got fixed, after applying the patch for version 18.1. Not really evident after reinstalling. (post: viewtopic.php?f=15&t=3532).