OMV 3 for ODROID-XU4/HC1/HC2/MC1
All these Exynos 5422 based ODROID devices share one single OMV 3 image: OMV_3_0_92_Odroidxu4_4.9.61.img.xz
It's based on OMV 3.0.88, kernel 4.9 LTS and an Armbian/Jessie userland (everything updated from official repos so you get all latest fixes automagically). The rootfs is a btrfs with active transparent filesystem compression combined with zram instead of swap. In case your installation media is 16 GB or more in size a 3rd partition gets automatically created on first boot you have to put a filesystem on manually to make use of it (eg. use it as an OMV share for small amounts of data that always have to be accessible to allow connected HDDs entering sleep/standby mode)
Important to know:
- If you want to use this image on XU3/XU4 together with an old(er) Hardkernel eMMC module unfortunatly you need an SD card (of any size) as first step. This is due to Hardkernel's eMMC modules sold prior to Oct 2017 still hosting an outdated u-boot version in the hidden eMMC boot partitions that are not accessible when you burn the image on your PC/Mac. So simply burn the OMV image to an SD card with Etcher, attach eMMC and SD card to your XU3/XU4, adjust the boot switch to 'SD card' and boot the board. Once it rebooted automatically after few minutes log in through Web UI, change passwords and activate 'permit root login' on the SSH service section. Then login as root via SSH, call 'nand-sata-install' and choose 'Boot from eMMC - system on eMMC'. When finished 'nand-sata-install' will poweroff the board. Remove SD card now, adjust the boot switch and let the board boot from eMMC from then on. Of course it's also possible to transfer the installation to permanently attached USB/SATA storage using the same method (but then the SD card has to remain attached since the bootloader can only be loaded from either SD card or eMMC on these boards)
- When you choose an external USB3 disk enclosure try to get one that contains an 'USB Attached SCSI (UAS)' capable USB-to-SATA bridge. Chips known to work are for example ASMedia ASM1153 and JMicron JMS578, JMS567 or JMS561. Please be aware that some HDD brands use these bridge chips combined with branded/broken firmwares (eg. many external Seagate disk enclosures). In such cases it might be possible that you have to 'blacklist UAS' (visit ODROID forum and search there for these words). This OMV image tries to do this automatically so in case you run into troubles please connect your disk enclosure and reboot at least 2 times, then check again.
- When you run into any storage hassles with ODROID-XU3/XU4/MC1 please always keep in mind that cable/contact problems and underpowering are the most common reasons for this. Always check this first and also check the links from my signature. Why aren't HC1 and HC2 listed? Since those are designed to prevent both powering and cable/contact hassles
The post was edited 2 times, last by tkaiser ().