Not detected

[tijeff9]

Hello,

I have a LaCie CloudBox White. My hard drive stopped working today. When I accessed the FVDW-SL webpage, I encountered errors. So, I decided to reinstall FVDW.

Upon the first opening of the FVDW-SL Console, the U-Boot opening page detected my CloudBox, which had a fixed IP address: 192.168.2.3. The system was installed, and a reboot occurred. Now, I can no longer see the CloudBox on my network. Is there a default IP address, or has it simply become non-functional?

Thank you for your help.

[fvdw]

the ip adress asdigned by uboot is only for installation. When fvdw-sl is running tclooks for a dhcp server to yet an ip. That will/ may be different from the one uboot used.
Use fvdw-sl assistent to find the nas on your lan or look in your router in ip list

[Jocko]

Hi

On a fresh install, NAS gets by default its IP from a DHCP server. So you check if DCHP service is actived on your ISP box

[tijeff9]

I tried as you mentioned with the fvdw assistant no nas found, since I reinstalled fvdw firmware and it did a rebbot I am no longer able to connect to my nas, it could be that it has become defective as a result to install firmware?
Thanks a lot

[fvdw]

if the firmware was installed succesfully your cloudbox is apparently working ok.
How is your Lan setup? Does it have an active dhcp server ?

[tijeff9]

Hello . I have a router whit DHCP the IP adress is on the 192.168.2.xx . I have scan the network whit assistant and check on the router and I don't view the Nas on the network

[fvdw]

what you can do is using fvdw-sl console and load the standalone kernel.
When connected with the telnet client that pops up when the standalone kernel is loaded and started succesfully , give following commands on the command line

Code: Select all

mkdir sda7
mount /dev/sda7 /sda7
cat /sda7/boot.log

If the nas has booted previously ok then the ip it assigned itself is listed on the end of the boot.log.
If the nas did not boot ok then post the ouput of the boot.log file here using copy/paste commands of the telnet client.

[tijeff9]

I tried to do it with the standalone and unfortunately it still doesn't do anything, it remains to wating u-boot and nothing happens. I also noticed that the blue light flashes quickly in front of the box, do you have any other ideas otherwise I think I'll send everything to the trash. thank you

[fvdw]

a blue flashing led means an issue with the harddisk.bI suggest to take out the harddisk and repeat the loading of the standalone kernel. If that works we know that the cloudbox is still ok.
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

[tijeff9]

Hello,

Thank you very much for your response. I tested without the hard drive, and the same thing happens: as soon as I plug in the power, the blue light blinks rapidly.
I then tested the standalone kernel, and it still does the same thing, waiting for U-Boot. I also tested with another non-defective hard drive, and I have the same problem.
Unless someone has another idea, I believe my CloudBox is dead.

Thanks.