Posts by ekent

    Apologies if this is a stupid question. Will these steps work with a Helios4?
    The reason I ask is because the initial steps I followed on their forum was to install Armbian Stretch (Debian 9) and then install OMV4 afterwards using armbian-config.
    Looking forward to using OMV5! Thanks :)

    Hey @Adoby, thanks for the effort you went to with your response! There's an enormous amount of information there and must have taken a while to put together.

    I feel as though I have the information now to make an informed decision. I might start with rsnapshot as a base and then as my knowledge - and confidence - increases. I might switch to using your scripts :)

    Thank you for your detailed response.

    I have a Helios4 that at this stage am planning to start off with 2 separate drives. One for shared data and the other for snapshot backups.
    I was planning on using rsnapshot to achieve this, but I'm intrigued by the method that you've developed @Adoby.

    I understand that both use rsync behind the scenes and you have mentioned that you like your process as it's more 'external' and you run it via a cron.
    What are the differences and/or benefits between using rsnapshot and your method?
    Thanks :)

    KISS: use ext4 and rsnapshot

    Thanks! I am also a fan of this approach. You can implement the most complicated and data protective approach, but if you don't understand how to implement it correctly or how it really works, then it's a ticking time bomb in my mind.

    I have considered going the btrfs with btrbk route, but something has been holding me back.... Maybe it's just that to really justify using that filesystem I need to have a better understanding of the filesystem and how to make full use of it's positive features and avoid it's negatives.

    I presume that none of your advice would change with the impending OMV5 release (which i'm planning on waiting for before setting up my NAS ;) ).

    In any case you should have some kind of off-site backup like cloud or external drive you store in a different place.
    Also check the user guide which is linked in my signature.

    Thank you! I will definitely check out the user guide. Downloading as I type.

    tkaiser will not anwer, most likely. I would say, yes, stay with ext4.

    Thanks @macom I don't think that I want to setup a raid type scenario with snapraid like what Sinobi is describing above. But I suppose the question should be asked, should I be doing that? What would you recommend for creating incremental backups with ext4? Something like Snapshot? Or would it be better to go down the path of Snapraid?

    Thanks for taking the time to respond, I'm just trying to ensure that I get the best possible setup that I can and make sure that I still understand how it works and how to implement it correctly and be able to maintain it :)

    I have just received a Helios4 (3rd batch) and am making the final decision for filesystem for my drives. I was leaning towards btrfs and btrbk for backups, but what you have described above is a little over my head. If that is the case would you recommend sticking to something like ext4 and rsnapshot?

    Thanks :)

    @tkaiser thank you so much for your detailed responses! It's really appreciated and there is a lot of information there that will take me some time to sift through and understand and I can only imagine how much time it spent putting it together.

    @ekent I've also thought about buying 1 or 2 helios4. If you also live in germany and intereseted in helios4, we may order together to save shipping costs.

    @sirleon I'd be more than happy to do a combined order with you (and thank you for the offer). Unfortunately I live in Australia ;) so I feel it wouldn't work.

    If you love your data then care about data integrity. That means

    Use a checksummed filesystem if possible

    Use ECC RAM if possible

    I'm at the point where I can't decide whether to get:

    • 2 or 3 HC2s (and have backups physically separated from productive data). Positive = easy to multiply
    • Spend a little more and get a RockPro64 with NAS case (have backups connected to the same SBC and therefore in the same physical location) (but this has downside of limiting to 2 hard drives) or I get another one down the track....
    • Or to spend a little more again and get a Helios4 (campaign ending in about 3 weeks) (and have backups connected to the same SBC and thus in the same physical location).

    I'm planning on using a checksummed filesystem (btrfs). As far as I can tell, Helios4 is the only SBC in this thread that has ECC Ram. Is the Helios4 worth the extra cost for a home NAS? I do care about my data, as does everyone I think ;) .

    In the long run, I think I'll be able to live with the extra cost (though it might be painful in the short term).

    Hi all,

    After going through the thread Which energy efficient ARM platform to choose? I was really taken by the Helios4, but thought that it was out of my price range. As a result I then was considering the Odroid-HC2 and was very impressed by that machine, but realised that in order to get what I wanted I'd need to get 2-3 of them. Once I realised that, that brought me back to the Helios4. I think that I'm going to get one, and am seriously excited by the prospect (as it offers the opportunity to combine ECC Ram and a checksummed filesystem) and it's performance.

    Just wanted to ask a couple of questions though before I commit to it (sorry very nervous Non-pro, first time home NAS setup user):

    • The Helios4 has a dual core ARM Cortex A9 CPU and the Odroid-HC2 has an Octa Core CPU featuring a Samsung Exynos5422 Cortex-A15 2Ghz and Cortex-A7. Now I know that it's not as simple as saying one is dual core and one is octa core. But just wondering if someone could outline what the difference is between these two CPU configurations? As to me it "sounds" as though the CPU in the Odroid-HC2 is more powerful...
    • @tkaiser in this thread Which energy efficient ARM platform to choose?, you counseled that SBCs are not really appropriate for RAID as RAID requires absolutely reliable hardware. I suppose that this is still the case with the Helios4? With the Helios4, I'd be keen to utilise it's capability of 4 HDDs down the track and have 1-2 for backing up the other 2 Productive disks. Considering this, would the appropriate method to perform backups be btrbk (for btrfs) or rsnapshot (for ext4)?

    Thanks :)

    ing different protocols for the same shares is a recipe for disaster (unfortunately OMV allows this)

    I thought that might be the case.

    I would use SMB for data shares (even if this has downsides with Mac and Linux clients) and in case you want to use OMV as a TimeMachine backup appliance use a single different share with AFP for this.

    Thanks @tkaiser, I appreciate the advice. I think I will want to use OMV as a TImeMachine backup, so I'll configure a single different share for that :) .

    I am about to buy an Odroid-HC2 and plan to setup OMV on that for general backing up, and storing and sharing of media files (music and videos) over my local network.

    At the moment the following OSs exist in my house

    • Windows 10 (PC)
    • Apple (Macbook Pro OSX 10.11)
    • Linux (Kodi Media Centre)

    As I understand it, each have their preferred File Share protocols. So which should I use when setting up OMV? Configuring all of them and using SMB for Windows, AFP for Mac and NFS for Linux seems inefficient to me and there's high chance of overlap and confusion (on my part).

    Are there any suggestions for how to approach this?
    Thanks :)

    Manual backup doesn't work in my experience (you always have good reasons to skip backing up prior to a data loss). We're using checksummed filesystems everywhere since data integrity is important and as such btrfs together with btrbk does the job on ARM SBCs and with large x86 installations ZFS combined with znapzend is used (or proprietary solutions like Open-e/Jovian). The differentiation between btrfs on ARM and ZFS on x86 is due to kernel support here and there.

    But if you're not a 'storage pro' and really familiar with those contemporary filesystems using the older established variants like XFS or ext4 might be a better idea (then combined with traditional approaches like rsnapshot which integrates nicely with OMV).

    Again, thank you.
    Yeah, I'm not a storage pro and not familiar with btrfs and ZFS. Seeing as I haven't even ordered the SBC or hdd for my new setup, I've got time to research and investigate btrfs. If I'm struggling to wrap my head around getting it setup, then I can fall back to ext4 (what I'm using now) and use rsnapshot which I can see is available as a plugin in OMV.

    Thanks a heap for the information in your post. That's quite the setup you've got there. And you clearly are a fan and believer in the HC2!

    Then buy yourself two HC2, or three or even four HC2. Or go towards a normal pc / x86 server .... And if you really like the idea with ARM as a server then Gigabyte has a cool R281-T91

    I think I will go back to the HC2 option. I was really taken with it initially so didn't need to try too hard to convince myself. BTW that Gigabyte R281-T91 is off the chain!! Super cool, but slightly more than what I need I feel ;) .

    I hadn't realised this or really thought about. But it makes a lot of sense, especially with my experience with SBCs up to this point. I guess that's why i'm posting and asking questions here. So thanks for taking the time to respond.

    Having backups separated physically from your productive data is interesting and again something I really wasn't considering. Having said that, I like the idea! When you say that you have your backups physically separated from your productive data, how are you handling your backups? Is that an automatic process? Or are you doing it manually from your productive data?

    I mentioned the SATA HAT with an if clause: 'If I would want to add up to 4 disks to an SBC' (but I really don't want to add a bunch of disks to an SBC, at least not with all disks active at the same time)

    Also you should keep in mind that this SATA HAT is brand new and currently not tested by any of us here ( ryecoaaron ordered a kit but I would believe this will take some time). I would better wait for people sharing their experiences.

    Thank you for clarifying your points there. I think I took what you said out of context.

    I'm currently using a Raspberry Pi 2B with a 2TB HDD. It's terrible!

    After reading through this thread I thought that I'd settled on getting an Odroid-HC2, but now I'm thinking I'd like the ability to have 2 or more 3.5" drives (probably up to 4) connected, possibly even in a RAID1 configuration. I'd like to be able to do general backing up of files and also stream music and movies etc to a media centre.

    If I would want to add up to 4 disks to an SBC I would clearly go the SATA route (taking an old PC enclosure and then implanting a NanoPi M4 with its SATA HAT inside the enclosure and feed the whole setup with an external 12V brick or do something similar with an EspressoBin)

    This suggestion really grabbed my interest and seems pretty doable from my perspective as I'm pretty sure I've got an old enclosure hanging around somewhere. Do you think it would be the best setup for what I'm looking for? Sorry for being a bit of a newb, but what exactly do you mean when you say

    feed the whole setup with an external 12V brick

    Does that mean that the whole setup SBC and drives would be powered by the one power supply? If so, what would that power supply look like?
    Thanks :)

    Upon further investigation, I have found that the Odroid-HC2 is available in Australia for a reasonable price. I have 2 Raspberry Pi 2Bs and am looking at replacing both of them.

    • The first one is running OSMC (Kodi) as a media centre accessing
    • The second is running OMV serving as a NAS for general backup and as a media storage for one running the media centre

    I am now thinking that I'll replace 1) with the rock64 and will replace 2) with the Odroid-HC2


    I have been using a Raspberry Pi 2B with OMV for the last few months and have been extremely frustrated with the performance. After doing some investigating here, and looking at prices and what was available to get shipped reasonably to Australia, I decided to get a 4GB rock64 which I'm excitedly waiting for. However, I feel that I should have read this thread before making my purchase as I purchased a 16GB eMMCwith it.

    Have I wasted my money? Will it be OK for me to use this eMMC with my rock64? Or should I just accept that it is a sunk cost and get an A1 or A2 performance class SD?