Error: "Failed to read file '/tmp/bgstatusfs2WVj' (size=0)."

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Error: "Failed to read file '/tmp/bgstatusfs2WVj' (size=0)."

      Hi,
      I just installed a fresh OMV 3.16.0 and I'm getting the following error in the web interface:

      Source Code: Failed to read file /tmp/bgstatusRTD5Oz (size=0).

      1. Error #0:
      2. exception 'OMV\Exception' with message 'Failed to read file '/tmp/bgstatusRTD5Oz' (size=0).' in /usr/share/php/openmediavault/json/file.inc:198
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/json/file.inc(213): OMV\Json\File->getContents()
      5. #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(334): OMV\Json\File->read()
      6. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(514): OMV\Rpc\ServiceAbstract->updateBgProcStatus('/tmp/bgstatusRT...', 'outputfilename', '/tmp/bgoutputNC...')
      7. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      8. #4 /usr/share/openmediavault/engined/rpc/config.inc(208): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      9. #5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      12. #8 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      13. #9 {main}
      Display All
      It appears most of the time when I try to save and apply my changes but sometimes I'm lucky and the error doesn't show up.
      Logging out/rebooting seems to fix it for "one saving".

      I hope you can help me :)

      Best regards,
      Daniel
    • Oh sorry, I made a careless mistake. When looking up the version number I got into the kernel line.

      OMV version is 3.0.36
      Kernel 3.16.0-4-amd64

      I updated everything from the Update Manager Tab and my new OMV Version is 3.0.52.

      That did not solve my issue. For instance I got the same error for checking for new updates and trying to upload the extras deb to the plugins.
    • It is installed on a SD Card. I made sure to use a new, high quality one with wear leveling. Also it has a capacity of 32 GB so that should be enough space for the wear leveling to get through the installation without destroying the card.
      I've got similar errors when I installed it to a ssd but I didn't keep this installation due to problems with the network.
      So I guess it must be some configuration problem.

      I couldn't find anything interesting in the logs. I looked into syslog, daemon.log and messages.
    • I assumed that there might be some sort of a bug in the code. I was able to get it working again with some changes that I will explain now:

      In the file /usr/share/php/openmediavault/json/file.inc I changed the getContens() method to use php's file_get_contents()

      PHP Source Code: /usr/share/php/openmediavault/json/file.inc

      1. public function getContents() {
      2. // Seek to the beginning of the file.
      3. if (FALSE === rewind($this->fh)) {
      4. throw new \OMV\Exception("Failed to rewind file '%s'.",
      5. $this->filename);
      6. }
      7. // Get the information about the file.
      8. if (FALSE === ($fstats = fstat($this->fh))) {
      9. throw new \OMV\Exception("Failed to get file stats from '%s'.",
      10. $this->filename);
      11. }
      12. // Get the whole file contents.
      13. /*
      14. if (FALSE === ($contents = fread($this->fh, $fstats['size']))) {
      15. throw new \OMV\Exception("Failed to read file '%s' (size=%d).",
      16. $this->filename, $fstats['size']);
      17. }
      18. */
      19. $contents = file_get_contents($this->filename);
      20. if ($this->exists()== False) {
      21. throw new \OMV\Exception("FILE DOESNT EXIST");
      22. }
      23. if ($contents === False) {
      24. throw new \OMV\Exception("Failed to read file with file_get_contents '%s' (size=%d).",
      25. $this->filename, $fstats['size']);
      26. }
      27. return $contents;
      28. }
      Display All

      Then I got an invalid JSON Error in line 217 (original file)

      I checked the returned json string for validity and it was ok.
      Then I went to usr/share/php/openmediavault/functions.inc to check the is_json method and found that the
      regex in line 363 is responsible (but I absolutly don't know why because the regex looks fine to me).
      I commented it out and my is_json method looks like this now:

      Source Code: /usr/share/php/openmediavault/functions.inc

      1. function is_json($var) {
      2. if (!is_string($var))
      3. return FALSE;
      4. if (empty($var))
      5. return FALSE;
      6. // E.g. '1.1.1.1' is identified as JSON by json_decode.
      7. if (!preg_match("/^[\[\{]/", $var))
      8. //return FALSE;
      9. if (is_null(json_decode_safe($var)))
      10. return FALSE;
      11. return (json_last_error() == JSON_ERROR_NONE);
      12. }
      Display All

      Now I don't get any "Failed to read file '/tmp/...'" errors any more and it seems to work great.

      As I'm not very familiar with the project I'm unsure if my changes will break something in another place or what some sideeffects might be.



      Also I found that there is a misleading error message in the read method:

      Source Code: /usr/share/php/openmediavaullt/json/file.json

      1. public function read($decode = TRUE, $assoc = TRUE) {
      2. // Read the whole file contents.
      3. $contents = $this->getContents();
      4. // Validate the JSON data.
      5. if (FALSE === $this->validate($contents)) {
      6. throw new \OMV\Exception("File '%s' contains invalid JSON: %s",
      7. $this->filename, json_last_error_msg());
      8. }
      9. // Decode the content if requested.
      10. if (TRUE === $decode) {
      11. if (NULL === ($contents = json_decode_safe($contents, $assoc))) {
      12. throw new \OMV\Exception(
      13. "Failed to decode content in file '%s': %s",
      14. $this->filename, json_last_error_msg());
      15. }
      16. }
      17. return $contents;
      18. }
      Display All
      In line 7 (source code from this post) json_last_error_msg() is called but as far as I can see if the $contents is empty the validate method will return false before json_decode can be called so json_last_error_msg() will return No Error, which is kind of confusing for the end user.
    • viperman3 wrote:

      Is there a proper fix implimented for this issue?
      Did you install from the ISO? What is the output of:

      ls -al /
      ls -al /tmp/
      omv 4.0.6 arrakis | 64 bit | 4.12 backports kernel | omvextrasorg 4.1.0
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • I installed using iso to bootable usb (used unetbootin-windows-625.exe to create bootable usb)

      output for ls -al /

      Source Code

      1. root@nas:~# ls -al /
      2. total 96
      3. drwxr-xr-x 24 root root 4096 Dec 16 11:51 .
      4. drwxr-xr-x 24 root root 4096 Dec 16 11:51 ..
      5. drwxr-xr-x 2 root root 4096 Dec 16 12:19 bin
      6. drwxr-xr-x 3 root root 4096 Dec 16 12:20 boot
      7. drwxr-xr-x 18 root root 3080 Dec 17 14:17 dev
      8. drwxrwxr-x 99 root root 4096 Dec 17 14:27 etc
      9. drwxr-xr-x 2 root root 4096 Sep 19 12:27 export
      10. drwxr-xr-x 2 root root 4096 Sep 12 00:09 home
      11. lrwxrwxrwx 1 root root 31 Dec 16 11:50 initrd.img -> /boot/initrd.img-3.16.0-4-amd64
      12. drwxr-xr-x 17 root root 4096 Dec 16 11:50 lib
      13. drwxr-xr-x 2 root root 4096 Dec 16 11:50 lib64
      14. drwxr-xr-x 2 root root 4096 Sep 19 13:31 live-build
      15. drwx------ 2 root root 16384 Dec 16 11:50 lost+found
      16. drwxr-xr-x 4 root root 4096 Dec 17 14:15 media
      17. drwxr-xr-x 2 root root 4096 Sep 19 13:25 mnt
      18. drwxr-xr-x 2 root root 4096 Sep 19 13:25 opt
      19. dr-xr-xr-x 137 root root 0 Dec 17 14:16 proc
      20. drwx------ 3 root root 4096 Dec 16 12:23 root
      21. drwxr-xr-x 24 root root 1120 Dec 17 14:50 run
      22. drwxr-xr-x 2 root root 12288 Dec 16 14:17 sbin
      23. drwxr-xr-x 4 root root 4096 Dec 16 11:50 srv
      24. dr-xr-xr-x 13 root root 0 Dec 17 14:17 sys
      25. drwxrwxrwt 8 root root 260 Dec 18 00:17 tmp
      26. drwxr-xr-x 10 root root 4096 Dec 16 11:51 usr
      27. drwxr-xr-x 14 root root 4096 Dec 17 00:47 var
      28. lrwxrwxrwx 1 root root 27 Dec 16 11:51 vmlinuz -> boot/vmlinuz-3.16.0-4-amd64
      29. root@nas:~#
      Display All


      output for ls -al /tmp

      Source Code

      1. root@nas:~# ls -al /tmp
      2. total 16
      3. drwxrwxrwt 8 root root 260 Dec 18 00:17 .
      4. drwxr-xr-x 24 root root 4096 Dec 16 11:51 ..
      5. -rw------- 1 root root 0 Dec 17 14:50 bgoutputCKK7Xa
      6. -rw------- 1 root root 127 Dec 17 14:50 bgstatusRq4OqH
      7. drwxrwxrwt 2 root root 40 Dec 17 14:17 .font-unix
      8. drwxrwxrwt 2 root root 40 Dec 17 14:17 .ICE-unix
      9. -rw------- 1 root root 3123 Dec 17 14:32 logfilehr87DT
      10. -rw------- 1 root root 4076 Dec 17 14:32 logfileVMKadV
      11. -rw------- 1 root root 0 Dec 17 14:32 logfilewEAGtT
      12. drwx------ 3 root root 60 Dec 17 14:17 systemd-private-4baf395493f94eb6b7199d259d40c5d4-systemd-timesyncd.service-lGi3xE
      13. drwxrwxrwt 2 root root 40 Dec 17 14:17 .Test-unix
      14. drwxrwxrwt 2 root root 40 Dec 17 14:17 .X11-unix
      15. drwxrwxrwt 2 root root 40 Dec 17 14:17 .XIM-unix
      Display All
    • output for mount

      Source Code

      1. root@nas:~# mount
      2. sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
      3. proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
      4. udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=493176,mode=755)
      5. devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      6. tmpfs on /run type tmpfs (rw,nosuid,relatime,size=793740k,mode=755)
      7. /dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      8. securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
      9. tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
      10. tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
      11. tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
      12. cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
      13. pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
      14. cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
      15. cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
      16. cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
      17. cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
      18. cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
      19. cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
      20. cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
      21. tmpfs on /etc/machine-id type tmpfs (ro,relatime,size=793740k,mode=755)
      22. systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
      23. mqueue on /dev/mqueue type mqueue (rw,relatime)
      24. hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
      25. debugfs on /sys/kernel/debug type debugfs (rw,relatime)
      26. fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
      27. tmpfs on /tmp type tmpfs (rw,relatime)
      28. /dev/sda1 on /var/folder2ram/var/log type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      29. folder2ram on /var/log type tmpfs (rw,nosuid,nodev,noexec,relatime)
      30. /dev/sda1 on /var/folder2ram/var/tmp type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      31. folder2ram on /var/tmp type tmpfs (rw,nosuid,nodev,noexec,relatime)
      32. /dev/sda1 on /var/folder2ram/var/lib/openmediavault/rrd type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      33. folder2ram on /var/lib/openmediavault/rrd type tmpfs (rw,nosuid,nodev,noexec,relatime)
      34. /dev/sda1 on /var/folder2ram/var/spool type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      35. folder2ram on /var/spool type tmpfs (rw,nosuid,nodev,noexec,relatime)
      36. /dev/sda1 on /var/folder2ram/var/lib/rrdcached type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      37. folder2ram on /var/lib/rrdcached type tmpfs (rw,nosuid,nodev,noexec,relatime)
      38. /dev/sda1 on /var/folder2ram/var/lib/monit type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      39. folder2ram on /var/lib/monit type tmpfs (rw,nosuid,nodev,noexec,relatime)
      40. /dev/sda1 on /var/folder2ram/var/lib/php5 type ext4 (rw,noatime,nodiratime,errors=remount-ro,data=ordered)
      41. folder2ram on /var/lib/php5 type tmpfs (rw,nosuid,nodev,noexec,relatime)
      42. rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
      43. binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
      44. /dev/sdb2 on /media/46F0E499F0E4908B type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
      45. root@nas:~#
      Display All

      output for cat /etc/fstab

      Source Code

      1. root@nas:~# cat /etc/fstab
      2. # /etc/fstab: static file system information.
      3. #
      4. # Use 'blkid' to print the universally unique identifier for a
      5. # device; this may be used with UUID= as a more robust way to name devices
      6. # that works even if disks are added and removed. See fstab(5).
      7. #
      8. # <file system> <mount point> <type> <options> <dump> <pass>
      9. # / was on /dev/sda1 during installation
      10. UUID=56af5c7b-f177-4ddb-bf28-28ef09e0b020 / ext4 noatime,nodiratime,errors=remount-ro 0 1
      11. # swap was on /dev/sda5 during installation
      12. # UUID=c567b26f-60c1-474b-8197-00ab15f6698b none swap sw 0 0
      13. tmpfs /tmp tmpfs defaults 0 0
      14. # >>> [openmediavault]
      15. /dev/disk/by-uuid/46F0E499F0E4908B /media/46F0E499F0E4908B ntfs defaults,nofail 0 2
      16. # <<< [openmediavault]
      17. root@nas:~#
      Display All
    • did you ever resolve this?

      I am having the same problem after an update from stonerburner to erasmus.

      Everytime I try to make some configuration changes or update/install plugins I get "Failed to read file '/tmp/bgstatus80tySW' (size=0)."

      Also transmission seems to be broken, cant do any configuration changes and I cant get it enabled from the GUI because this error pops up all the time:
      "The property 'pexenabled' does not exist in the model 'conf.service.transmissionbt'."

      Also this is "stuck":
      The configuration has been changed. You must apply the changes in order for them to take effect.
      And it wont go away when I click Apply or Revert changes.

      I am totally out of ideas here and I think these are odd errors to have after an update... Any help ?
    • i am also having similar error, with stuck "configuration has been changed" banner. omv-aptclean and removing dirtymodules.json did not help

      Shell-Script

      1. Error #0:
      2. OMV\Exception: Failed to read file '/tmp/bgstatusUxkEja' (size=0). in /usr/share/php/openmediavault/json/file.inc:199
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()
      5. #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(306): OMV\Json\File->read()
      6. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(536): OMV\Rpc\ServiceAbstract->finalizeBgProcStatus('/tmp/bgstatusUx...', '', Object(OMV\Exception))
      7. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      8. #4 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      9. #5 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      12. #8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      13. #9 {main}
      Display All
    • Fresh install of ArmBian -> Update packages -> Install OMV


      Shell-Script

      1. Error
      2. #0: exception 'OMV\Exception' with message 'Failed to read file '/tmp/bgstatuszSeHGM' (size=0).' in /usr/share/php/openmediavault/json/file.inc:199 Stack trace:
      3. #0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()
      4. #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(334): OMV\Json\File->read()
      5. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(525): OMV\Rpc\ServiceAbstract->updateBgProcStatus('/tmp/bgstatuszS...', 'outputfilename', '/tmp/bgoutputxe...')
      6. #3 /usr/share/openmediavault/engined/rpc/apt.inc(222): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #4 [internal function]: OMVRpcServiceApt->update(NULL, Array)
      7. #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) #6 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('update', NULL, Array)
      8. #7 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Apt', 'update', NULL, Array, 1) #8 {main}
      Display All
      Board is an ARM Alwinner A10, installed on a microSD card. Reinstalled several times, this happens all the time. OMV 3.0.89
      Main Server: OMV 3, Cooler Master Elite 120, Asrock E350M1, 8GB DDR3, 64GB SSD for OS, 2x4TB + 2x2TB - Seagate, 1x500GB HGST, 1x500GB WD.
      Additional Server: PCDuino3 Nano, OMV 3, ARM V7 Alwinner A20, 1GB DDR3, 300GB +160 GB old IDE Seagate Drives, running over wifi.
    • i did a fresh reinstall, upgraded to arrakis, installed a bunch of plugins and the Failed to read file '/tmp/bgstatusybb9l8' (size=0). error reappeared.

      the issue started with this plugin installation (pasted only the errored parts):


      Source Code

      1. Setting up nut-client (2.7.4-5) ...
      2. Created symlink /etc/systemd/system/multi-user.target.wants/nut-monitor.service -> /lib/systemd/system/nut-monitor.service.
      3. Job for nut-monitor.service failed because of unavailable resources or another system error.
      4. See "systemctl status nut-monitor.service" and "journalctl -xe" for details.
      5. invoke-rc.d: initscript nut-client, action "start" failed.
      6. * nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
      7. Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)
      8. Active: failed (Result: resources) since Wed 2017-10-11 22:13:30 CEST; 16ms ago
      9. Process: 24571 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)
      10. CPU: 1ms
      11. Oct 11 22:13:30 HP-OMV systemd[1]: Starting Network UPS Tools - power devic…r...
      12. Oct 11 22:13:30 HP-OMV upsmon[24571]: upsmon disabled, please adjust the co…eeds
      13. Oct 11 22:13:30 HP-OMV upsmon[24571]: Then set MODE to a suitable value in …e it
      14. Oct 11 22:13:30 HP-OMV systemd[1]: nut-monitor.service: PID file /var/run/n…tory
      15. Oct 11 22:13:30 HP-OMV systemd[1]: Failed to start Network UPS Tools - powe…ler.
      16. Oct 11 22:13:30 HP-OMV systemd[1]: nut-monitor.service: Unit entered failed…ate.
      17. Oct 11 22:13:30 HP-OMV systemd[1]: nut-monitor.service: Failed with result …es'.
      18. Hint: Some lines were ellipsized, use -l to show in full.
      Display All



      Source Code

      1. Setting up virtualbox (5.1.28-dfsg-1~bpo9+1) ...
      2. vboxweb.service is a disabled or a static unit, not starting it.
      3. Job for virtualbox.service failed because the control process exited with error code.
      4. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
      5. invoke-rc.d: initscript virtualbox, action "restart" failed.
      6. * virtualbox.service - LSB: VirtualBox Linux kernel module
      7. Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
      8. Active: failed (Result: exit-code) since Wed 2017-10-11 22:13:36 CEST; 15ms ago
      9. Docs: man:systemd-sysv-generator(8)
      10. Process: 25184 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)
      11. CPU: 88ms
      Display All


      I suspect it's virtualbox causing the issue in my case, as it was plugin i installed in the previous run as well.
    • molnart wrote:

      I suspect it's virtualbox causing the issue in my case, as it was plugin i installed in the previous run as well.
      in my case it seems to be related to flashmemory plugin which is installed by default on ARM systems afaik.

      This makes OMV unusable at all, I can't save settings, nor install packages via UI
      Main Server: OMV 3, Cooler Master Elite 120, Asrock E350M1, 8GB DDR3, 64GB SSD for OS, 2x4TB + 2x2TB - Seagate, 1x500GB HGST, 1x500GB WD.
      Additional Server: PCDuino3 Nano, OMV 3, ARM V7 Alwinner A20, 1GB DDR3, 300GB +160 GB old IDE Seagate Drives, running over wifi.