Lacie update capsule or GPL code? Usefull?

[archpennetje]

Hey everyone, i'm working on installing the fvdw-sl-installer on my new harddisk in the Lacie CLoudbox 3tb, now it will be a 2tb. However it is installing now at the moment. I was wondering if i could use the original Lacie "capsule" for installing the original firmware? Or can't i do a thing with it?
On the Lacie site there is also the GPL code?

I tried ubuntu but the tools from this forum worked for me in windows. For now at least.

Have anyone of you got a "how to about installing the original lacie cloudbox with fvdw-sl-installer?"

[archpennetje]

I just finished the installation, the blue led isn't blinking anymore so thats a :thumbup however i cant start the web interface? Does anybody know which firmware update i can download or what to do now?

I tried pinging the ip adres and that works again also.

[fvdw]

It will not work with the fvdw-sl installer as lacie uses on the cloudbox a very different partition table. However the standalone kernel present in the console could be used to install lacie firmware when we would write a lacie-installer script. To make that work we would need some partition images, these can probably be extracted from the capsules if those contain a full firmware upgrade. A disk copy of another lacie cloudbox might fail as disk uid will be different due to fact that lacie is using raid setup on this box. :disapprove useless on a single disk device.

[fvdw]

I just finished the installation, the blue led isn't blinking anymore so thats a :thumbup however i cant start the web interface? Does anybody know which firmware update i can download or what to do now?

I tried pinging the ip adres and that works again also.

Did you reboot the cloudbox?

[archpennetje]

Yes rebooted it twice now

[fvdw]

How did you discover the ip it uses? Did you use the fvdw-sl assistant?

The ip will be assigned by the dhcp server in your network, most of the time a router

If it has an ip the webinterface should work. If it doesn't try to connect to the nas via the ssh server using a ssh client like putty.

[archpennetje]

I have the cloudbox connected directly to my laptop.
And by using ipconfig, and ping to the ip adres that is showed by ipconfig of my ethernet connection i could ping the nas.

I'll try to connect the nas via my router this afternoon, maybe thats the problem otherwise ill have a look to the other option you posted.

[archpennetje]

super, for me the following worked.
I pinged the nas via a direct connection to my laptop.
However, when i connected it on my router and searched for the new ip adres on my router i got the login screen of the nas.
So up for the next steps!

[archpennetje]

I'm a little bit further with the new firmware.
However it is quite different from the lacie firmware it offers a lot of functionality.

I can't get the public folder visible in Windows Explorer..... don't know why yet.

I'll try it for some time,
But i'm thinking of formatting the drive and putting it in my synology..... the Lacie Cloudbox firmware was nice for using with the torrent files and ease of use with an ipad etc.
On this forum i did see that there was someone that did managed to reinstall the official firmware of lacie? It would be nice to just try to do it, and if it doesnt work this custom firmware is a good alternative.

[Jocko]

Hi archpennetje,

I can't get the public folder visible in Windows Explorer..... don't know why yet.

Maybe you do not yet set the workgroup (lan setup menu).
To be see in windows explorer, your laptop and the nas must use the same workgroup.