General NAS-Central Forums

Welcome to the NAS community
It is currently Thu Jun 29, 2017 3:46 am

All times are UTC




Post new topic Reply to topic  [ 75 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next
Author Message
PostPosted: Thu Nov 27, 2014 9:26 pm 
Offline

Joined: Wed Jun 18, 2014 9:38 pm
Posts: 35
einne wrote:
I am extremely thankful for such fast answer. Can u please let me know also if you were able to wake the device up.


To be honnest I'm not using wol since I buy ARM devices to get up 24/7 with low power consumption... I've not look into wol support on the device tree and MV ebu Linux support.


Top
 Profile  
 
PostPosted: Thu Dec 25, 2014 2:41 pm 
Offline

Joined: Thu Dec 25, 2014 2:31 pm
Posts: 1
Hello
Have you tried to onboard any volume encryption?

Best regards
TK


Top
 Profile  
 
PostPosted: Thu Dec 25, 2014 10:43 pm 
Offline

Joined: Wed Jun 18, 2014 9:38 pm
Posts: 35
tako wrote:
Hello
Have you tried to onboard any volume encryption?

Best regards
TK

Well you can but performance will be very poor... Since cesa security engine is not supported ... Even if you manage to have the current linux cesa driver configured it does not support DMA which mean no real gain vs software encryption...
Last time I tried dmcrypt on a loop file I got 12mB/s ... If you're looking high speed aes encryption you better look at sheep diy nas using AMD a5-5000 or c2550 Intel which both include aes-ni instruction and get >200mB/s encryption...


Top
 Profile  
 
PostPosted: Sun Mar 01, 2015 6:37 pm 
Offline

Joined: Sat Feb 28, 2015 9:30 pm
Posts: 2
Thanks for all the work you've put in and thanks for documenting it!

I got here by Googling for: gzip Salted iomega
Why did I google this? Because I have a firmware updte for the Iomega Home Media Network Hard Disk - Cloud Edition and I wanted to look at it. It is hmnhd-3.2.10.30101.tgz but it isn't a gzip(tar(stuff)). It starts with the string "Salted", unlike normal gzips.

You didn't actually find an answer to your casual query along the same lines but you did update the kernel on an IX4. Great work!

How applicable would that work be to the HMNHDCE? Or to the IX2 (I have two)?


Top
 Profile  
 
PostPosted: Mon Mar 02, 2015 3:34 pm 
Offline

Joined: Wed Jun 18, 2014 9:38 pm
Posts: 35
Hello, thanks for your post,

Concerning the salted iomega package I've never look into decrypting it, since iomega/lenovo deliver some GPL sources...

For your question about how the work presented here could be replicable on your 2 devices:
- HMNHDCE could very well be covered by armarchlinux already : http://archlinuxarm.org/platforms/armv6 ... 3oxnas-eol since they share the same embedded chip is almost 90% of an embedded device those day :). If not then it should be very close and looking at archlinux build scripts which are very easy to read you could build a kernel for this device.
- for your ix2, I think there are plenty of people already doing this : http://archlinuxarm.org/forum/viewtopic.php?f=53&t=8277

Therefore I think you could find a of easy way to turbo charge you devices with funky little Linux stuff without much effort as the one presented here to get IX4 supported by mainline device tree linux :).

Benoit


Top
 Profile  
 
PostPosted: Sun Jul 17, 2016 9:58 am 
Offline

Joined: Fri Jul 15, 2016 10:51 am
Posts: 11
If you what to decrypt the salted/encrypted gzip, this should be a good hint:

Upgrade the NAS, and run the command "ps -ef" to see what is going on:

Code:
root@ixd-300d:/# ps -ef
<<<cut>>>
sh -c openssl enc -d -aes-128-cbc -in "/mnt/system/upload/upload.5syE9E" -k "EMCNTGSOHO" | tar -C "/mnt/system/upgrade/tmp/" -xzmf - apps


"EMCNTGSOHO" is the key for 4.1.210.33855. Maybe it is always this.


Top
 Profile  
 
PostPosted: Sun Jul 17, 2016 10:55 am 
Offline

Joined: Wed Jun 18, 2014 9:38 pm
Posts: 35
Nice hints thanks for contribution!


Top
 Profile  
 
PostPosted: Sun Jul 17, 2016 7:28 pm 
Offline

Joined: Fri Jul 15, 2016 10:51 am
Posts: 11
Hi benoitm974.

I have just bought a new ix4-300d, which I hope can replace my current home server.
For that project it needs to have support for LXC and overlayfs.

I think it is best to first build a rootfs, and try to use it with the stock kernel. Then I can try to build a kernel later.

So my question is: How do I build a multistrap armhf debain. The internet seems to be full of old guides.

PS: I have also been trying to boot a this custom linux. But with no success.


Top
 Profile  
 
PostPosted: Sun Jul 17, 2016 10:41 pm 
Offline

Joined: Wed Jun 18, 2014 9:38 pm
Posts: 35
I suppose the stock kernel won't support the LXC, and you'll probably be in a better shape with a custom kernel.

Isn't 512Mb limiting for LXC container ?

For debian arm you can now do bootstrap with multi-arch arch support from debian. (ex: https://blog.night-shade.org.uk/2013/12 ... hf-rootfs/ )

Benoit


Top
 Profile  
 
PostPosted: Mon Jul 18, 2016 3:30 pm 
Offline

Joined: Fri Jul 15, 2016 10:51 am
Posts: 11
benoitm974 wrote:
Isn't 512Mb limiting for LXC container ?


I would definitely prefer to have had more RAM. But that would have costed 284€ for 2 GB instead of 93€.

I run 10 containers which all uses the same binaries because I use overlayfs. That saves a lot of RAM.

My current setup uses 832 MB of RAM. I think it should be possible to swap some out, and maybe I can free up some by stopping unnecessary processes. The weird this is that htop says that I only use 337MB of RAM.

I will have a look at the link you send now.


Top
 Profile  
 
PostPosted: Mon Jul 18, 2016 6:43 pm 
Offline

Joined: Fri Jul 15, 2016 10:51 am
Posts: 11
I build a Debian Jessie rootfs.

I booted the 3.0.29 kernel. Because it outputs to the serial port. Unlike the 3.2 kernel, which displays nothing.

This is the last output I got on the console:
Code:
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): recovery complete
EXT3-fs (sda2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 8:2.
Freeing init memory: 216K


I connected both ethernet ports, they have light, but none of them outputs anything.

I will try and make a Wheezy rootfs now.


Top
 Profile  
 
PostPosted: Mon Jul 18, 2016 9:00 pm 
Offline

Joined: Fri Jul 15, 2016 10:51 am
Posts: 11
The Wheezy rootfs worked with stock 3.0.29 kernel, other kernels net tested yet.

I tried to replce root=/dev/sda2 with root=UUID=4d742d5f-f7f8-4226-a3ae-a9f3def945e2. But the kernel cannot read UUIDs for some reason:

Code:
VFS: Cannot open root device "UUID=4d742d5f-f7f8-4226-a3ae-a9f3def945e2" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00             896 mtdblock0  (driver?)
1f01             128 mtdblock1  (driver?)
1f02             128 mtdblock2  (driver?)
1f03            4096 mtdblock3  (driver?)
1f04            4096 mtdblock4  (driver?)
1f05         1034240 mtdblock5  (driver?)
1f06         1048576 mtdblock6  (driver?)
0800          997376 sda  driver: sd
  0801          102400 sda1 00000000-0000-0000-0000-000000000sda1
  0802          893952 sda2 00000000-0000-0000-0000-000000000sda2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
CPU0: stopping


I will test the 3.2 stock kernel.


Top
 Profile  
 
PostPosted: Mon Jul 18, 2016 9:11 pm 
Offline

Joined: Fri Jul 15, 2016 10:51 am
Posts: 11
The stock kernel 3.2.40 worked. But without console (there is no /dev/ttyS0). Had to ssh to it. The root=UUID did not work.


Last edited by bekobuprot on Mon Jul 18, 2016 9:46 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Mon Jul 18, 2016 9:17 pm 
Offline

Joined: Wed Jun 18, 2014 9:38 pm
Posts: 35
When you say stock you mean le over stock or debian arm stock? For serial it should just be about kernel boot parameters from uboot. Uuid support is also dependend on uboot version. Or boot a ramdisk with modules to support serial and uuid


Top
 Profile  
 
PostPosted: Mon Jul 18, 2016 10:36 pm 
Offline

Joined: Fri Jul 15, 2016 10:51 am
Posts: 11
benoitm974 wrote:
When you say stock you mean le over stock or debian arm stock?

I mean the kernels you can get from Lenovo for the system.

benoitm974 wrote:
For serial it should just be about kernel boot parameters from uboot. Uuid support is also dependend on uboot version.

It seems /dev/ttyS0 is missing from the system. But it is there if you boot the same kernel with the system from Lenovo.

benoitm974 wrote:
Uuid support is also dependend on uboot version. Or boot a ramdisk with modules to support serial and uuid

If I load initrd too. The system just boots from nand. Ignoring values set in bootargs.

I think it is time to compile a kernel. But I have no idea how I "simply git the current 3.17 git and compil your dts !" :-). I will look into that tomorrow.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 75 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group