Posts by calexm

    nand-sata-install simply works. It transfers the rootfs (your OS partition) to connected USB/SATA storage and after the following reboot only the bootloader remains on SD card but the whole OS lives on USB/SATA storage. But this doesn't make sense if the storage on a HC1 or HC2 is a HDD and the disk should spin down since with the rootfs on this HDD it will either constantly be woken up or you need to configure the HDD to never spin down.

    Thank you. I'll take a look on this. Also the spin down concept is new for me.. This is my first NAS I build.. But I;m already reading a few things about it.

    Well, that's the real benefit of all these little ARM things. They usually have all the video hardware to do transcoding :)
    Can you please elaborate on how this 'integrates' with OMV now? I would assume you're running Emby not inside a Docker but modified the base system?

    No, I didn't modify the base system. It's OMV as I downloaded it and updated it. The Howto offers a link to download a tar.xz file with the customized ffmpeg .deb's and emby 3.5.3 (also .deb). The user that posted that guide states that this packages will work with an Armbian Stretch distro.


    First, you install the ffmpeg packages. I got dependency errors on this step but I was able to easily fix them with apt-get update --fix-missing.
    Then, you Install emby, set it as usual and select Hardware acceleration: Exynos V4L2.


    Emby works on port 8096 by default, so there wasn't any conflict with OMV Web UI and Emby Web UI at all.

    Thanks for clarifying. Might be worth a quick tutorial with some uploaded screenshots outlining how a cheap HC1 or HC2 can be used for NAS + Emby server with HW accelerated video transcoding.
    It's sad that most OMV users believe transcoding would need a huge Xeon box and 100W wasted for CPU cores being at 100% when a small ARM thingy can do the same at below 10W barely using the CPU cores at all.

    Maybe I could work on that. I could guide on How I did it even I followed TechnoDadLife videos, there were some stuff that I didn't see on those, like that we should connect to the NAS through SSH after install and immediately run omv-firstaid to configure Ethernet interface. Also a couple situations that I had with Sharedfolders permissions.


    I was almost 'breaking my head with the walls' to find a way to access my NAS remotely (I had some trouble with my privative ISP Modem/Router). Now, I'm using my router (GL.iNet GL-AR750S-Ext Gigabit) also as a VPN server. This way I have access to my NAS from my phone (with the FileExplorer app) being in my LAN or using DATA/another wifi. My need started because my wife needed to backup some photos/files from her phone and we just had a regular off-line External HD.

    Just adding: If the disk on the HC1/HC2 should not spin down anyway, it's always an idea to partition the disk for one appropriately sized rootfs partition and another data partition and then use nand-sata-install to move the rootfs to the disk.

    @tkaiser, this is out of my knowledge, do you have topic thread(link) for that? Thanks.

    Well, that's the real benefit of all these little ARM things. They usually have all the video hardware to do transcoding :)
    Can you please elaborate on how this 'integrates' with OMV now? I would assume you're running Emby not inside a Docker but modified the base system?

    No, I didn't modify the base system. It's OMV as I downloaded it and updated it. The Howto offers a link to download a tar.xz file with the customized ffmpeg .deb's and emby 3.5.3 (also .deb). The user that posted that guide states that this packages will work with an Armbian Stretch distro.


    First, you install the ffmpeg packages. I got dependency errors on this step but I was able to easily fix them with apt-get update --fix-missing.
    Then, you Install emby, set it as usual and select Hardware acceleration: Exynos V4L2.


    Emby works on port 8096 by default, so there wasn't any conflict with OMV Web UI and Emby Web UI at all.

    Thanks for clarifying. Might be worth a quick tutorial with some uploaded screenshots outlining how a cheap HC1 or HC2 can be used for NAS + Emby server with HW accelerated video transcoding.
    It's sad that most OMV users believe transcoding would need a huge Xeon box and 100W wasted for CPU cores being at 100% when a small ARM thingy can do the same at below 10W barely using the CPU cores at all.

    Maybe I could work on that. I could guide on How I did it even I followed TechnoDadLife videos, there were some stuff that I didn't see on those, like that we should connect to the NAS through SSH after install and immediately run omv-firstaid to configure Ethernet interface. Also a couple situations that I had with Sharedfolders permissions.


    I was almost 'breaking my head with the walls' to find a way to access my NAS remotely (I had some trouble with my privative ISP Modem/Router). Now, I'm using my router (GL.iNet GL-AR750S-Ext Gigabit) also as a VPN server. This way I have access to my NAS from my phone (with the FileExplorer app) being in my LAN or using DATA/another wifi. My need started because my wife needed to backup some photos/files from her phone and we just had a regular off-line External HD. Besides, now I can move all my backups to my OMV NAS :)

    Well, that's the real benefit of all these little ARM things. They usually have all the video hardware to do transcoding :)
    Can you please elaborate on how this 'integrates' with OMV now? I would assume you're running Emby not inside a Docker but modified the base system?

    No, I didn't modify the base system and it isn't a Docker either. It's OMV as I downloaded it and updated it. The Howto offers a link to download a tar.xz file with the customized ffmpeg .deb's and emby 3.5.3 (also .deb). The user that posted that guide states that this packages will work with an Armbian Stretch distro.


    First, you install the ffmpeg packages. I got dependency errors on this step but I was able to easily fix them with apt-get update --fix-missing.
    Then, you Install emby, set it as usual and select Hardware acceleration: Exynos V4L2.


    Emby works on port 8096 by default, so there wasn't any conflict with OMV Web UI and Emby Web UI at all.

    I mentioned Emby and transcoding before with this in mind: https://forum.armbian.com/topi…u4hc1hc2-armbian-stretch/

    @tkaiser Thank you for this tip. I followed the howto that you posted and works like a charm. I had emby in Docker when I had OMV in a Rpi. I just had it for 2 weeks. I tested playing a movie and the ffmepg was using 90-95% of CPU. Now that I have this other set-up on a Odroid HC2 the CPU is barely used when playing a movie. It's a huge difference.


    If someone else follows the instructions of the link above, do exactly the user says. If you get errors on the install of the *.deb's, run: sudo apt-get update --fix-missing. At some point, you'll have to modify the emby-server config file, make sure you back it up and edit the line suggested. Besides that, it runs smoothly.

    @calexm :You have 1Gbit :) from the manual:
    Ethernet RJ-45 jack
    The standard RJ45 Ethernet port for LAN connection supports 10/100/1000 Mbps speed. The green LED Flashes when there is 100 Mbps connectivity, and the yellow LED Flashes when there is 1000 Mbps connectivity.
    Cheers, T.

    Thanks.


    Yes you are right. After I posted this, I started to do some test. First I used the ethtool command to check the speed of my ethernet port and then Iperf3.


    Also, this time after booting OMV on the HC2 I connected through SSH and ran omv-firstaid to set the ethernet configurations. In my previous install on a Raspb Pi I didnt do this and didn't found the ethernet interface on the Web UI.

    @Adoby I know that you are using HC2 for your setup, so here a question if you can help me with. I just installed OMV 4 on my new HC2. I plugged my CAT6 cable into the device and booted it. I see that the light on the Ethernet port of HC2 is ambar instead of green, that means network is working on 10/100mbits instead of 1000mbits. Is there any set-up that I'm missing?


    The router I'm using is new and 1000 mbits capable and the CAT 6 cable too.


    Thanks.

    Thank you.


    Yes, on my first install on RPi I followed the videos of Technodadlife and everything was working fine. I had OMV + Emby (docker) But it seemed a little slow so that's why I going to move from raspberry to HC2.


    I also want to use a VPN but when I connect my client to this VPN I can't see the OMV server anymore. I'm still trying to figure that out.

    @Adoby do you have emby on you HC2 as a docker? I have OMV on a Raspberry. my OMV has docker and in this docker I have emby. I have read a lot of post about OMV+Rpi and decided to go with HC2. At the moment I'm writing this, I'm starting to set my HC2 with OMV from scratch. I just wanted to know if I should also add emby with docker.


    My plan is using this setup as a backup as well.