omv on rpi:



Since we're running an Armbian userland we can make also use of some Armbian
functionality. Since I have a few wireless IoT sensors here (OPi Zero and
NanoPi Air) I wanted to setup an own 'IoT Wi-Fi' truly separated from my normal
Wi-Fi.

One single step needed on a RPi 3: 'sudo armbian-config' --> Hotspot --> NAT
(you could also choose 'Bridge' instead but I wanted NAT by intention)

Everything else happens in the background (installing and setting up dnsmasq
and routing/filtering) and afterwards there's a new wireless network called
'ARMBIAN' with default passphrase '12345678' on channel 5 available (you need
to change this immediately in /etc/hostapd.conf of course).

[IMG:http://kaiser-edv.de/tmp/NumpU6/RPi_Plus_Wi-Fi.jpg] On my RPi 2 I tested
the same with two dual-band/dual-antenna Wi-Fi sticks. The cheap one based on
Ralink RT5572 worked out of the box (driver and firmware included), the more
expensive one featuring RTL8812AU (802.11ac) needed an out of tree driver I
chose to install via DKMS:

    apt install raspberrypi-kernel-headers
    follow every step here: https://forum.armbian.com/index.php?/topic/3949-odroid-xu4-wifi-usb-dongle-realtek-rtl8812au/&do=findComment&comment=29521
    reboot

Please note that for powerful wireless dongles you need a stable 5V/2A power
source that does not suffer from voltage drops and on a RPi 2 you have to define 
'max_usb_current=1' in /boot/config.txt to allow 1200mA available at the
USB ports and not just the default 600mA (all USB ports share this limit!)
----------------------

The RPi image will install three packages from archive.raspberrypi.org/debian/ on first boot: 
raspberrypi-bootloader, libraspberrypi-bin and raspberrypi-kernel. 
This is a lot of stress for the SD card and might take some time so there's some patience 
needed until the RPi reboots and can be used afterwards. 
If users try this with really crappy, broken or counterfeit SD cards most probably OMV
won't start after the reboot since filesystem is already corrupted. 
This will save these users a lot of time they would otherwise waste with installing OMV 
again and again. Just to keep in mind for support questions: 
if it doesn't work at all then most probably it's the SD card that needs to be replaced (some recommendations).
forum.armbian.com/index.php?/t…findComment&comment=2952://forum.armbian.com/index.php?/topic/954-sd-card-performance/
---------------------
Quoting the readme.txt on Sourceforge download page: 'A third partition for
data use will be automatically resized on first boot but you have to format it
manually with the fs of your choice!' and quoting first post above:

    The image resizes the rootfs automagically to ~3.7GB on first boot and
creates a 3rd partition using the remaining space of the SD card you need to
initialize manually if you want to use it for OMV shares ('mkfs.ext4|mkfs.btrfs
/dev/mmcblk0p3')

So yes, it requires manual interaction and a decision: not using remaining
space is a valid option since it increases longevity of your SD card. A lot of
users fear SD cards wearing out too fast and this is one of the strategies to
fight this.

Since we're talking about running this image now with at least kernel 4.9 using
btrfs (with transparent file compression) is possible so I thought it would be
a better idea to encourage users to think what to do with the 3rd partition.
Eg. mounting it as /var/log with btrfs and compress-force=zlib logfiles 40GB in
size will fit easily on a 4 GB partition.
-----------------------------------------


installing display:

git clone https://github.com/goodtft/LCD-show.git
chmod _R 755 LCD-show
cd LCD-show
eg: sudo ./LCD35-show 

disable LCD:
if you need to switch back to the traditional HDMI display
sudo ./LCD-hdmi