Not detected

[fvdw]

how did you exactly load the standalone kernel?
I assume you also used it to install the firmware using the fvdw-sl console. If I understood you correctly that worked, or not ? After that the standalone kernel doesn't load anymore?
I have difficulties to believe that your cloudbox is dead.

I hope you yave installed the firmware and that you did not flashed uboot?

[tijeff9]

During the first boot, when I realized my hard drive was broken, I tried accessing the FVDW page at the address 192.168.2.3, which has worked for years on my network, but I was getting errors at the top of the page. I thought it was probably related to the hard drive failure and that it also affected the software, so I installed a new hard drive and installed the FVDW-L firmware. The U-Boot was detected, and an installation was done. The NAS then shut down for a reboot, but afterward, I no longer had access to my NAS, and I couldn't find it on the network. I tried what you suggested, but it doesn't seem to work either, with or without the hard drive in my NAS. I am sending you a screenshot of the options I tried. Thanks again.

[fvdw]

did you follow these instructions?
cloudbox switched off but connected to the lan
on your pc only one wired network interface active and connected to the lan, disable any wireless card or second wired interface if you have it

start fvdw-sl console on your pc
load standalone kernel
when uboot window mentions waiting for uboot then power on the cloudbox

Furthermore do not change ip of nas or pc in the main window of the fvdw-sl console. Leave them on the defaults set by the console

[tijeff9]

I removed all my network cards and retested again leaving everything at default as you told me I managed to connect but I have timout errors like in the images I send you

[fvdw]

ok so the cloudbox is working. The transfer of the kernel timeouts, the reason must be that your firewall is blocking outbound traffic for the tftp32 server running on your PC. Temporarily disable it or grant the program access through the firewall

[Cubytus]

(…)
Sometimes a not starting harddisk is caused by a faulty power supply. You could check your harddisk by connecting it to another device or if you have another disk to put that in the cloudbox.
It is peculiar that you were able to install the firmware, that makes a faulty harddisk less likely

Yes and no. I had two distinct but similar issues.
On a heavily worn laptop, when really warm, it would indeed run properly. But I could never get it to install a new OS when starting from cold. I didn't have time to trace it, but suspected the SATA connector was faulty.

In a hard drive enclosure I'm still using for backups, I have to repeatedly turn it off and on for the disk to start spinning. Once it's warm enough and I don't turn it off, then no problem accessing it. A few years ago I replaced the capacitors in the PSU (it was from the 2010s era), I guess I'll have to do it again.

And my first computer, from 2005 onwards, started displaying had the same problem after 8 years. I would have to repeatedly press the power button, switching loads one after the other, to finally get it to turn on. Most of the time I didn't turn it off, so was unaware of the issue.

Given how old the LaCie Cloudbox is, I wouldn't be surprised if the original PSU couldn't give the required startup current.

For my part, I don't have the issue since I started to use a custom-made 12V power rail with a Li-Ion battery in-between to act as a DC UPS.