system sources, remote and local

Intel NUC
   https://www.intel.com/content/.../mini-pcs.html

   NUC6iSYK
      http://Intel.../documents/boardsandkits/NUC6i5SYB_NUC6i3SYB_TechProdSpec.pdf

Orange Pi
   http://www.orangepi.org/downloadresources/

   Zero
      https://www.armbian.com/orange-pi-zero/

Friendly Arm
    http://wiki.friendlyarm.com/wiki/index.php/Main_Page

   Nano Pi Neo
       http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO
   Nano Pi Neo2
      http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2
   Nano Pi Neo Dock
      http://wiki.friendlyarm.com/wiki/index.php/1-bay_NAS_Dock_v1.2_for_NanoPi_NEO/NEO2
   NanoPC T4
      http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T4 

Solidrun

   Cubox i4pro
      https://www.solid-run.com/downloads/

Raspberry Pi

   Zero
   Zero W
   Raspberrypi 2
   Raspberrypi 3+
      https://www.raspberrypi.org/downloads/raspbian/

Hardkernel
   https://wiki.odroid.com/

   Odroid HC2
      https://wiki.odroid.com/odroid-xu4/os_images/third_party
      https://www.hardkernel.com/main/products/prdt_info.php?g_code=G151505170472 

friendlyarm nanopi t4 with rockchip 3399

Notes about setting up Lubuntu bits on the t4 board

login is pi, default pi

http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T4#Connect_NVME_SSD_High_Speed_Hard_Disk_to_T4

Connect NVME SSD High Speed Hard Disk to T4

Connect a NVME SSD hard disk to NanoPC-T4's M.2 interface, initialize and automatically mount the SSD by running the following commands. Before proceed turn off your T4 and connect an SSD to your T4. Power on your T4 and open a command line utility(go to top left of the GUI and enter System Tools -> LXTerminal) or SSH to your T4.

We suggest you switch to "root" by running the following command:

su -

The password for "root" is "fa".

Detection of SSD

root@FriendlyELEC:~# cat /proc/partitions 
major minor  #blocks  name
   1        0       4096 ram0
 259        0  125034840 nvme0n1

If there is a nvme0n1 device node it means an SSD is recognized by T4.

Partition of SSD

To mount an SSD under Linux we re-partition it as one section by running the following command:

(echo o; echo n; echo p; echo 1; echo ""; echo ""; echo w; echo q) | fdisk /dev/nvme0n1

If you want to re-partition it to multiple sections you can run "fdisk /dev/nvme0n1". For more detail about this command refer to the fdisk's manual.

Format Section to EXT4

After an SSD is successfully partitioned you can check its sections by running "cat /proc/partitions". The image provided treats a PCIe nvme device's sections as an eMMC's sections you will find that an SSD has some small sections.

We can check the "blocks" column and the biggest section is available for users. The /dev/nvme0n1p7 section is used to store data:

root@FriendlyELEC:~# cat /proc/partitions 
major minor  #blocks  name
   1        0       4096 ram0
 259        0  125034840 nvme0n1
 259        1       4096 nvme0n1p1
 259        2       4096 nvme0n1p2
 259        3       4096 nvme0n1p3
 259        4      12288 nvme0n1p4
 259        5      32768 nvme0n1p5
 259        6      32768 nvme0n1p6
 259        7  124932440 nvme0n1p7

The following command formats a section to ext4:

mkfs.ext4 /dev/nvme0n1p7

Auto Mount SSD on System Startup

Before we mount an SSD's section you need to know its Block ID. You can check it by running "blkid":

blkid /dev/nvme0n1p7
/dev/nvme0n1p7: UUID="13fb682e-ef40-4c71-b98b-3d17403e1205" TYPE=“ext4"

Add a "Block ID" to "/etc/fstab" and here is what it looks like

UUID=<Block ID> /media/nvme ext4 defaults 0 0

You need to replace <Block ID> with the UUID obtained by running "blkid". To mount the SSD in our example we made the "/etc/fstab" file as follows:

UUID=13fb682e-ef40-4c71-b98b-3d17403e1205 /media/nvme ext4 defaults 0 0

We want to mount an SSD to "/media/nvme" but this directory doesn't exist. Therefore we create it and change its access right by running the following commands:

mkdir /media/nvme
chmod 777 /media/nvme

Run "mount" to check if the SSD is mounted successfully:

mount /media/nvme

You can reboot your T4 to check if your SSD will be automatically mounted:

poweroff

-30-

Openmediavault notes

Openmediavault is an opensource nas system that supports intel and arm.

Most notes here will be related to the Friendlyarm Nanopi Neo and Nanopi Neo2

First tests with v1.0 media dock had some problems.  The USB port on the dock board worked, but the original attempt to use a Seagate 2tb drive didn't work.

After much help from Friendlyarm and debugging the kernel, it appeared that there was a probably known bug manifested for the drive in this case.  Will be testing later with other drives and also new builds of the kernel as well to see if that problem works out.

Great support from Friendlyarm in working on this.

V1.0 JM20329 SATA -> USB bridge.  The board has a 12V supply which runs both the SATA drive and the NEO or NEO2 board.

Updates for V1.2 to follow.

The Friendlyarm NEO and NEO2 both have debian builds with openmediavault already built.  Most of the instructions for installing the OMV on the Intel or generic build up install can be ignored, because as supplied, the Friendlyarm images have been installed with generic settings, then the SD images saved.

The instructions below have instructions on a "from bare metal" install on Intel and perhaps others, and the info for configuring the Openmediavault post install from the web interface is the reason for including the links or information here.


Links:

Howto forge page on installing scratch openmediavault.

https://www.howtoforge.com/tutorial/install-open-media-vault-nas/

Current OMV version for NEO2 in use:

5/25/2017, link below

http://www.mediafire.com/file/89ugz0iig8jt6lv/nanopi-neo2_debian-nas-jessie_4.11.2_20170525.img.zip