Create a Custom Capsule (aka Custom Firmware) [with root]

[ilpepe]

For the newer firmwares you'll have to use port 2222. On port 22 FTPS is running.

Works perfectly!

I now have a total noob question. But I need some direction.

I rooted the NAS, and can do my stuff with it.
The thing is that before my ubuntu desktop automatically could mount the NAS, whilst this is nog impossible.
Probably something to do with permissions/file permissions, but I don't know where to start...

Any tips hints in the right direction. Just get me on the track, I'll google around, but right now I'm clueless...

Got it working!
thanks for the script.

I have another question: is NFS possible on the NS2? if yes how?
thanks a lot!

[SilverSkyRat]

OK guys, I finally gave up on trying to make this work on my 2Big Network 2 without error on OS X, so I deleted all my previous posts.

I downloaded Ubuntu 12.04LTS and am running it in a Fusion 6 VM on the Mac.

After making script with sudo, script output:

chris@ubuntu:~/Working$ sudo ./create_capsule.sh
[sudo] password for chris:
-------------------------------------------------
Custom Capsule Creator Script v7
-------------------------------------------------

Analysing your system:
- directory exists ..........no
Do you want to create '/home/chris/Working/lacie' directory? [y/n]: y
OK (done)
- lzma installed ..........yes (/usr/bin/lzma)
- wget installed ..........yes (/usr/bin/wget)
- sha1sum installed ..........yes (/usr/bin/sha1sum)
- tar installed ..........yes (/bin/tar)
- curl installed ..........yes (/usr/bin/curl)
- LaCie hardware: ..........not found
- LaCie firmware version: ..........not found

Choose what to customize:
- Choose LaCie hardware you want to customize:
1. Network Space 2
2. Network Space MAX
3. d2 Network 2
4. 2big Network 2
5. 5big Network 2
Choose one option: 4
- Choose original capsule version to download and customize:
1. Version 1.2.6
2. Version 1.3.3
3. Version 1.3.6
4. Version 2.0.5
5. Version 2.0.6
6. Version 2.1.3
7. Version 2.2.3
8. Version 2.2.7
9. Version 2.2.8
10. Version 2.2.8.3
11. Version 2.2.9.1
12. Version 2.2.9.2
13. Version 2.2.9.3
Choose one option: 13
- Do you want to have root access? [y/n]: y
- Do you want to access TwonkyMedia server web configuration and browse? [y/n]: n
- Do you want to access Transmission Web Interface? [y/n]: n
- Do you want to secure access from a external network? [y/n]: n

Downloading original capsule:
- Downloading 2big Network 2 2.2.9.3 capsule
OK (already downloaded)

Extracting capsule:
- Extracting original (2.2.9.3) capsule ..........OK (done)
- Unpacking original (2.2.9.3) capsule tarball ..........OK (done)
- Unpacking original (2.2.9.3) rootfs tarball (can take up to 5 minutes) ..........OK (done)

Duplicating capsule:
- Duplicating to custom (2.2.9.3.1) capsule folder ..........OK (done)
- Duplicating to custom (2.2.9.3.1) rootfs folder (can take up to 3 minutes) ..........OK (done)

Customizing capsule:
- Enabling root access:
- Enabling sshd in default.runlevel .......... OK (done)
- Downloading custom 'sshd.i'
--2014-03-05 10:30:20-- http://downloads.lacie.nas-central.org/ ... sshd.i.txt
Resolving downloads.lacie.nas-central.org (downloads.lacie.nas-central.org)... 140.211.169.172
Connecting to downloads.lacie.nas-central.org (downloads.lacie.nas-central.org)|140.211.169.172|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2077 (2.0K) [text/plain]
Saving to: `rootfs_2bignetwork2_2.2.9.3.1/etc/initng/sshd.i'

100%[===================================================================================================================================================================>] 2,077 --.-K/s in 0.004s

2014-03-05 10:30:23 (481 KB/s) - `rootfs_2bignetwork2_2.2.9.3.1/etc/initng/sshd.i' saved [2077/2077]

OK (done)

Packing capsule:
- Packing custom (2.2.9.3.1) rootfs tarball (can take up to 30 minutes, depending on compression level) ..........OK (done)
- Changing custom capsule description:
- Original 'rootfs.tar.lzma' sha1sum: 74c58ad79f8572e8837984feeb98525cb480a56c
- New 'rootfs.tar.lzma' sha1sum: ef98f53e0e574c1ca826f084052fe56be339754b
- Replacing sha1sum in 'description.xml'
- Replacing capsule version with new capsule version in 'description.xml' ..........OK (done)
- Adding 2.2.9.3 version to upgradeble versions ..........OK (done)
- Updating 'description.sha1' ..........OK (done)
- Rebuilding capsule file ..........OK (done)

---------------------------------------------

New capsule built: '/home/chris/Working/lacie/2bignetwork2_2.2.9.3.1.capsule'
After upgrading you can:
- use SSH/SFTP with root privileges with your Lacie NAS with login 'root' (login: root | password: [same as admin password] | Port: 2222)

chris@ubuntu:~/Working$

Did factory reset (to 1.2.5), factory updates using LNA to 2.2.8 then 2.2.9.3. Using “Share/Update” folder to upgrade to 2.2.9.3.1, this is the info from unicorn_core.log:

Mar 5 10:51:07 NetRAID [INFO update.check_for_capsule@70] capsule found: /media/internal_1/shares/1/Update/2bignetwork2_2.2.9.3.1.capsule
Mar 5 10:51:07 NetRAID [DEBUG capsule.extract@254] extract files from /media/internal_1/shares/1/Update/2bignetwork2_2.2.9.3.1.capsule
Mar 5 10:51:17 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/description.xml
Mar 5 10:51:17 NetRAID [DEBUG capsule.parse@186] parse XML
Mar 5 10:51:18 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/repository/bootfs.tar.lzma
Mar 5 10:51:18 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/uImage
Mar 5 10:51:18 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/exec/pre_exec/checkLogSize.sh
Mar 5 10:51:18 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/exec/pre_exec/updateBootfsLib.sh
Mar 5 10:51:18 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/exec/post_exec/cleanupLegacyFiles.sh
Mar 5 10:51:18 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/repository/uImage
Mar 5 10:51:19 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/exec/pre_exec/removeOldFiles.sh
Mar 5 10:51:19 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/repository/rootfs.tar.lzma
Mar 5 10:51:25 NetRAID [DEBUG capsule.check@170] original hash = ef98f53e0e574c1ca826f084052fe56be339754b
Mar 5 10:51:25 NetRAID [DEBUG capsule.check@171] computed hash = e262e5ed227a8569d188c8609754626c552ce0cc
Mar 5 10:51:25 NetRAID [ERROR update.decapsule@101] an error occured when decapsuling
Mar 5 10:51:25 NetRAID Traceback (most recent call last):
Mar 5 10:51:25 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/update.py", line 97, in decapsule
Mar 5 10:51:25 NetRAID capsule.extract()
Mar 5 10:51:25 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 261, in extract
Mar 5 10:51:25 NetRAID self.__check_files()
Mar 5 10:51:25 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 332, in __check_files
Mar 5 10:51:25 NetRAID CapsuleFile(os.path.join(self.directory, filename)).check(hash_val)
Mar 5 10:51:25 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 172, in check
Mar 5 10:51:25 NetRAID raise CapsuleHashException('file %s has a bad hash' % self.filename)
Mar 5 10:51:25 NetRAID CapsuleHashException: file /capsule/repository/rootfs.tar.lzma has a bad hash
Mar 5 10:51:25 NetRAID [DEBUG module.stop_modules@397] Stopping unicorn.jobs

Using LNA to upgrade: No detection in log of update capsule, no update performed, it said "could not update" (obviously)

Factory reset to 1.2.5, factory update using LNA to 1.3.7, using “Share/Update” folder to upgrade to 2.2.9.3.1, output from unicorn.log (no unicorn_core.log on 1.3.7):

Mar 5 01:47:24 LaCie-2big [INFO update.scan@79] capsule found: /media/internal_1/shares/1/Update/2bignetwork2_2.2.9.3.1.capsule
Mar 5 01:47:24 LaCie-2big [DEBUG capsule.extract@262] extract files from /media/internal_1/shares/1/Update/2bignetwork2_2.2.9.3.1.capsule
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/description.xml
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.parse@194] parse XML
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/repository/bootfs.tar.lzma
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/uImage
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/exec/pre_exec/checkLogSize.sh
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/exec/pre_exec/updateBootfsLib.sh
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/exec/post_exec/cleanupLegacyFiles.sh
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/repository/uImage
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/exec/pre_exec/removeOldFiles.sh
Mar 5 01:47:46 LaCie-2big [DEBUG capsule.check@170] check SHA-1 hash of /capsule/repository/rootfs.tar.lzma
Mar 5 01:47:56 LaCie-2big [DEBUG capsule.check@178] original hash = ef98f53e0e574c1ca826f084052fe56be339754b
Mar 5 01:47:56 LaCie-2big [DEBUG capsule.check@179] computed hash = e262e5ed227a8569d188c8609754626c552ce0cc
Mar 5 01:47:57 LaCie-2big [ERROR update.decapsule@91] an error occured when decapsuling
Mar 5 01:47:57 LaCie-2big Traceback (most recent call last):
Mar 5 01:47:57 LaCie-2big File "/usr/lib/python2.6/site-packages/unicorn/system/update.py", line 87, in decapsule
Mar 5 01:47:57 LaCie-2big capsule.extract()
Mar 5 01:47:57 LaCie-2big File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 268, in extract
Mar 5 01:47:57 LaCie-2big self.__check_files ()
Mar 5 01:47:57 LaCie-2big File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 332, in __check_files
Mar 5 01:47:57 LaCie-2big CapsuleFile (os.path.join (self.directory, filename)).check (hash)
Mar 5 01:47:57 LaCie-2big File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 180, in check
Mar 5 01:47:57 LaCie-2big raise CapsuleHashException ('file %s has a bad hash' % self.filename)
Mar 5 01:47:57 LaCie-2big CapsuleHashException: file /capsule/repository/rootfs.tar.lzma has a bad hash

In both cases the same hash issue occurs; I was thinking it may be a difference in tar, lama or sha1sum from 2.2.8 to 1.3.7 but this proves not.

So, are the tar, lzma or sha1sum not right on Ubuntu 12.04LTS? How can I get the right ones if the OS doesn't have the right ones? Please help!

P.S. I know I said earlier that I did get root access, but I have 2 x 2Big Netowrk 2's and this is the result on both so I have no idea how I got root before really.

[SilverSkyRat]

P.P.S. I know the script was only tested for FW up to 2.2.8, but I need 2.2.9.3 to resolve a Time Machine issue for Mac.

[SilverSkyRat]

Ok, gave perms 777 to the working folder (recursive) and changed compression level in the script to 6 (which is the default level on this lzma (xz). I now have a bad hash on an earlier file (from the unicorn_core.log):

Mar 5 16:01:07 NetRAID [INFO update.check_for_capsule@70] capsule found: /media/internal_1/shares/1/Update/2bignetwork2_2.2.9.3.1.capsule
Mar 5 16:01:07 NetRAID [DEBUG capsule.extract@254] extract files from /media/internal_1/shares/1/Update/2bignetwork2_2.2.9.3.1.capsule
Mar 5 16:01:15 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/description.xml
Mar 5 16:01:15 NetRAID [DEBUG capsule.parse@186] parse XML
Mar 5 16:01:15 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/repository/bootfs.tar.lzma
Mar 5 16:01:15 NetRAID [DEBUG capsule.check@161] check SHA-1 hash of /capsule/uImage
Mar 5 16:01:16 NetRAID [DEBUG capsule.check@170] original hash = c923cfedbfae2ed99e16d224e04a5f6748962b9d
Mar 5 16:01:16 NetRAID [DEBUG capsule.check@171] computed hash = 87374d5f01b9b4db6b0bd7b55f444355b11d55bf
Mar 5 16:01:16 NetRAID [ERROR update.decapsule@101] an error occured when decapsuling
Mar 5 16:01:16 NetRAID Traceback (most recent call last):
Mar 5 16:01:16 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/update.py", line 97, in decapsule
Mar 5 16:01:16 NetRAID capsule.extract()
Mar 5 16:01:16 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 261, in extract
Mar 5 16:01:16 NetRAID self.__check_files()
Mar 5 16:01:16 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 332, in __check_files
Mar 5 16:01:16 NetRAID CapsuleFile(os.path.join(self.directory, filename)).check(hash_val)
Mar 5 16:01:16 NetRAID File "/usr/lib/python2.6/site-packages/unicorn/system/capsule.py", line 172, in check
Mar 5 16:01:16 NetRAID raise CapsuleHashException('file %s has a bad hash' % self.filename)
Mar 5 16:01:16 NetRAID CapsuleHashException: file /capsule/uImage has a bad hash
Mar 5 16:01:16 NetRAID [DEBUG module.stop_modules@397] Stopping unicorn.jobs

So maybe it is the lzma compression level? I'll try level 1 next.

[SilverSkyRat]

Woohoo!! I'm a happy chappy

Changing lzma compression level to 1 in the script did the trick.
- Clean, fresh unicorn_core.log
- From initng.log:

Mar 5 16:31:42 NetRAID InitNG: Service sshd is up.

Version shows as 2.2.9.3, but I don't mind hehehe, i'll make sure the other unit is happy too... it is

A big thanks for the script and the functionality!

[orwell84]

Hi there!
First and foremost, thanks for all your effort.

I have a Lacie 5 BIG Network 2 with firmware 2.2.9.3
I would like to load a custom capsule.

Despite that I read that version 2.2.9.3 would be not compatible with in 5 BIG Network 2, I tried to, but predictably I could not achieve the update, Ive managed to create a custom capsule with my Mythbuntu HTPC (Ive created a custom capsule with a 2.2.9.3 base).

I cannot load it, neither with LNA nor manual (forced), well, it was expected however.

I tried to downgrade to 2.2.2.3 first with forced mode, then with a recovery mode and it seemed to get it, but firmware version 2.2.9.3 is active...

Is there any chance to downgrade to an older version and then create a capsule with a 2.2.2.3.1 version and apply it?

EDIT: [ Sorry, Ive noticed that this is a 2BIG forum, but I thought I arrived here from a 5BIG forum..]

[Mijzelf]

Is there any chance to downgrade to an older version

A factory reset should bring your box back to the original version. Which version that is depends on the age of your box.

EDIT: [ Sorry, Ive noticed that this is a 2BIG forum, but I thought I arrived here from a 5BIG forum..]

There is only one big thread about the Custom Capsule, which happens to be in the 2Big2 subforum.

[orwell84]

Is there any chance to downgrade to an older version

A factory reset should bring your box back to the original version. Which version that is depends on the age of your box.

Good point, thanks.
Although last time I reset to factory defaults, my Lacie didn´t start up... and I have to make a recovery, I think I will try again.

EDIT: [ Sorry, Ive noticed that this is a 2BIG forum, but I thought I arrived here from a 5BIG forum..]

There is only one big thread about the Custom Capsule, which happens to be in the 2Big2 subforum.

Ok, thanks again.

[orwell84]

Finally I got it.

I reset to factory defaults, but again my Lacie didn´t start. Then a recovery procedure with 2.2.3 is achieved.
Trying to update with a custom capsule 2.2.3.1 with standard procedure, fail.
Update with custom capsule mode forced, seems to be ok, however systems shows only 2.2.3

Managed to get ssh root access and trasmission and townky web access...

Two restarts needed to get same password as admin´s for root in ssh.

The capsule was made with no issue with a Mythbuntu (Ubuntu with 2.6.32-55-generic), so:

Ubuntu | 2.2.3 (dont know) | 2.2.3.1| yes

I have no data in it, so, if you need some other test, I will be very proud of helping here....

[msmet]

Works like a charm... after a few tries

Created the capsule for 2.2.8.5 on MintLinux
Did a factory reset to 1.2.9
Reboot with new capsule in /MyShare/Update
Got upgraded (including reboot)
Another reboot was required to get actually root access with admin password
Disabled automatic firmware updates

ssh, scm, twonky, etc... all working

MintLinux (VM) | 1.2.9 | 2.2.8.5.1 | Yes (msmet)

Thanks a zillion @ Myzelf and andreus!! Great work guys!

[blsfsg]

Well done!

Works perfect for 5big2 and v2.2.10.1 on an already rooted 5big2.
Thank you very much!

[musafirrlail]

Thanks for this script Andreus. It's amazing.

Custom capsule built on Lubuntu 12.04 for Lacie D2 Network 2| Original firmware version 2.2.8 (not rooted) | Custom firmware version 2.2.8.1 (rooted) | Got root access? Yes

Thanks again for your work.

Is there a way to update transmission because there's no magnet link in it and upload seems not working

If I can know howto you do that, Because I Have also D2N2 and wanna try follow from begin

[Eyeball]

Thnx again! Script still working. Updated 2.2.12.2 via Lacie Dashboard. Then "unlocked" features with this script (don't know why I did not update and root using the script in first place). Anyhow working great!

Xubuntu 15.4 | Network Space 2 | 2.2.12.2 | 2.2.12.1 (rooted) | Yes (by Eyeball)

[topoldo]

Tnx! Script still working great!!! I created my custom script and I updated my NS2 which I recovered from brick using the other thread concerning the installation of the Lacie firmware in a new/bricked HD.

Linux Mint 18 (xfce version, 32bit, virtual on VMWare Player in Windows) | Network Space 2 | 2.2.10.1 | 2.2.10.2.1 (rooted) | Yes (by topoldo)

Please note that in my hands I also tried to update to versions 2.2.12.1 and 2.2.12.2 but I was unsuccessfull from rooting point of you while Twonky & Transmission were ok.
So I downgraded to version 2.2.10.1
Cheers,
Topoldo