Lacie Cloudbox 3TB not accessible

[JimmyJackson]

Dear all,

Great site and project with lots of info about problems with lacie NAS systems. Seems that I am not the only one having issues with my cloudbox. However, after trying out several things, I am a little desperate. Connected my quickly blue LED-blinking lacie cloudbox 3TB via LAN cable to the router. Same for my computer. When I start the standalone console in fvdw-sl console 6 everthything works fine. Since I am not able to turn of the cloudbox by pushing the on/oiff button anymore (blue light is blinking quickly before disconnecting and after reconnecting), I have to plug the cable in when u-load starts. After that some files are loaded and Linux-3.14.2 is booted resulting in several OKs. The kernel is started and the telnet windows pops on after a while. Then telnet times out and I cannot connect manually (there is no button under connect).

I have read several posts on this site where a telnet timeout is because the firewall is interfering, or WIFI is used. I can exclude both, since I turned off the firewall and everything is connected via cable (even deactivated my wireless network adapter on my computer to be sure the connection is via cable).

Could somebody help me please :please I really do not want to loose the files on the cloudbox and I dont know what I am doing wrong to proceed to the next steps :dontknow

It's very, very frustrating.

Thank you very much for your help!!!

[fvdw]

Which action did you choose in the fvdw-sl console and which kernel did you select to upload?

[JimmyJackson]

Thanks for your quick reply, fvdw. I chose the standalone kernel, load and start and the UIMAGE-3142-KIRKWOOD-150-standalone.

[fvdw]

Thats the correct kernel :thumbup

I don't understand this part of your explanation

Since I am not able to turn of the cloudbox by pushing the on/oiff button anymore (blue light is blinking quickly before disconnecting and after reconnecting), I have to plug the cable in when u-load starts. After that some files are loaded and Linux-3.14.2 is booted resulting in several OKs...

What should do is switch off your cloudbox. By unplugging the power cable. Connect the LAN cable to the cloudbox (if not already connected). Start the fvdw-sl console and choose action liad standalone kernel and select the standalone kernel. After the command window that will pop up shows waiting for u-boot. Connect the power cable of your cloudbox. The command window should detect it and interrupt boot and uploads the kernel visible in the command window with several lines of xxxxxxx, do you get that? And than a message booting and starting the kernel indeed followed with ok's.
After this the telnet client will popup and tries to connect after 15 sec. Sometimes it fails and times out if there is a problem with the harddisk. You could try to manually connect after it times out using the connect button in the telnet command window and providing the ip of your cloudbox (it is specified in the fvdw-sl console window).
If that doesn't work either you could try the procedure with the disk taken out to see if the disk is causing the problem. The standalone kernel can run without a disk in the box

[JimmyJackson]

I followed your alternative procedure without the harddrive and... telnet connects. I can type in the username (login) and password. Then it waits for a command. Now I am terrified that my harddrive is broken. However, it doesn't make any weird sounds when spinning up. Any suggestions where I can go from here?
Thank you very much! :hail At least now there is some progress.

P.S.: I wasn't able to follow your other alternative, i.e. trying to connect manually in the telnet window. Maybe I am blind but I can't find a way/option to enter the NAS IP and connect in any of the dropdown menues at the top of the telnet window.

[JimmyJackson]

Maybe some background info concerning my cloudbox issue is necessary/helpful: A week ago the connection to the cloudbox became unstable (original and most probably the latest firmware). Sometmes it connected, sometimes not. At that point I was able to shut down the NAS with the power button. After some time, I wasn't able to connect to the cloudbox at all. Then I tried to reset the NAS to factory settings and things got worse. The blue LED was blinking quickly and the cloudbox did not responded to the power button anymore. Lacie support was not helpful at all. They just told me that the clodbox OS is possibly currupted and that I have to look for an "expensive professional data recovery", where success is also not guaranteed. That is exactly what you expect from a large company selling "easy-to-use" NAS systems :dry

Luckily, after some internet searching, I found your site and since then, I tried really hard to get things working, or at least try to find out what's wrong. Thanks to your help, things become a little clearer now. However, I really fear that I will loose my data, since I do not have another backup :sob

[fvdw]

We will do our best to try to recover it. It is not easy on a cloudbox is using raid setup making getting access to the data more complicated and it has no usb port so copying the data must be done via LAN interface. First thing to do is finding out whats wrong with this disk. For that we need to get telnet running with the disk in the box. The reason why it times out might be slow response from the disk delaying completing boot. For that we can use the manually connection method of the telnet client.(I will post a scrrenshot later were the button can be found in the telnet client but it is pretty easy ;)
It can also be a power supply issue, if the power supply is not giving enough power for starting with disk the boot may fail. But you told that your the disk spinning up (is it only spinning up once?)
Instead of using the load and start standalone kernel you could use the action uboot console of the fvdw-sl console. That will open a command window letting you talk to uboot. There we can also do some test to see if the disk is accesible. In the uboot command window you will get prompt like this: marvell>>
After tha prompt enter this command

Code: Select all

ide reset

It should report that it found a disk with partition table.
If you get that enter

Code: Select all

ide part

To see is it list the partitions. If it does there is hope. If not...

[JimmyJackson]

Followed your option with u-boot console.

The command: ide reset brings up:
ide reset

Reset IDE:
Marvel Serial ATA Adapter

Marvel Serial ATA Adapter
Integrated Sata device found

After that I directly typed in "ide part" (no "Marvell>>) and the answer was:
Error - Failed initializing(SRST) drive on channel 0
Failed initializing storage device connected to SATA channel 0
PCIe SATA:ffffffff

Then after "Marvel>>" I typed in "ide part" again and this shows up:
ide part

no IDE devices available
Marvel>>

That no good news, is it? Did I do anything wrong?

You mentioned:

It can also be a power supply issue, if the power supply is not giving enough power for starting with disk the boot may fail. But you told that your the disk spinning up (is it only spinning up once?)

How can I find out, if the disc is running? It does't sound like it's reading/writing...

[JimmyJackson]

You mentioned the lacking USB connection. I have a HDD docking station. Would that be of any help?

[fvdw]

This might be bad news but it explains why telnet times out.
As apparently the disk fails to come online or after long time.
Please repeat in uboot window the ide reset command and wait until the marvell prompt comes back. That will give us an idea how long it will take before booting of the standalone kernel will be delayed.
The fact that ide part gives no info is also not good