LaCie Cloudbox Inoperable

[Tayzer]

Hi all. So, I've been browsing through the forums here for a few weeks now working on a Lacie Cloudbox, and unfortunately I havent found anything that compares to the issue I am faced with. I'm a freelance IT and electronics tech, so defenitely not a newbie when it comes to hacking and cracking to get the job done. Fingers crossed I havent blown the box all together lol.

So, heres what I got. Have a Lacie cloubox, white casing, 2TB hdd. About 3 years old, still had the ORIGINAL firmware on it. The HDD suffered an "Ooops" moment at the hands of a friend, so I was in the process of fixing the partition table and saving data. Thus when I came across this lovely place, in efforts to update, like seriously, the outdated crappy seagate stuff. Now, the partition table is fixed right and proper on the HDD. My problem lies with the box controller.

With HDD in and ethernet cable plugged in, I apply the power cord, and the ethernet port lights up green, then switches over to the orange activity, which does flash with network activity. And that, is quite literally, all the thing does. The HDD does not spin up, there is no new device on the network, the red and blue status leds dont even whisper, nada. And, just to be thorough, I have used now 5 USB-Serial adapters on the serial/jtag port on-board, and there is nothing. Zip, zilch, nada.

Leading up to this was a firmware update from the software download here. I have the possibility that the download glitched and was partially corrupted, or, and quite possibly more likely, there was a 'slight issue' as the firmware was loaded onto the box, and the complete firmware image was not written over, resulting in a very, very hard brick.

The firmware upload was via serial and tftp. Up until the box had accepted, unpacked, and started installing the firmware image, it was all fine and dandy. Box went down for reboot........... Aaaaaaaaand never came back up :thinking I let the box sit on and connected to ethernet for literally 48 hours, and nothing. Now, me being me, and loving to tinker and learn new fun stuff, and the box being 3 years old and out of warranty, Im looking at this thing, and theres gotta be something, something, hidden out there in the cracks of cyberspace that can kick it back to life.

I have the J2/JTAG/Serial port, and Arduinos, and Arduinos setup as JTAG programmers, and USB-serial adapters, and soldering iron, and will and determination, and laptop(albeit slightly pissed off laptop for all the software ive been burning through, whoops). Really hoping there might be something I've missed in my searches, or a slight tiny tidbit someone might have tucked away lol, cause i've gone from :thinking to :fists to :hairpull one thing I havent tried yet, is there is another connector port, next to the status led connector, labeled J3, but no info on that as of yet, no multimeter to probe it out at the moment.

So, uhrm, yea lol. Thanks in advance for any help or advice anyone might have :lol:

[fvdw]

Hi there, quite a story. I overlooked this post sorry for late response.

Is the problem still existing?
If so load the standalone kernel using the fvdw-sl console. Read the intructions in the fvdw-sl console how to do that. But I think you are familiar with as you mention you have installed our firmware with it, or not?
After the standalone kernel has loaded onnect with the telnet client that will popup on your windows pc and give commands:

Code: Select all

fdisk -l

Code: Select all

gdisk -l /dev/sda

Code: Select all

dmesg

And post output here