Raspberry pi 4 announced, better than 3?

  • Could you guide us on how to install It in rpi4? Im newbie

    Please remember you are using a beta version of OMV where most of the omv-extras are not ready on a brand new board...

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Please remember you are using a beta version of OMV where most of the omv-extras are not ready on a brand new board...

    No worry. I dont use any extra atm in my RPI 3. No teamviewer, docker, transmission, or extra.
    Im only using Samba to copy and read files from a 24/7 Rpi3 Nas


    I was waiting for a Rpi4 with Gigabit ethernet and usb 3.0 to upgrade my read/write speeds from 20 mb/sec to at least, 100 mb/sec :)


    I want to know how to install OMV 5 in RPI 4 , The only version I see in the website is for amd64....... so, I need a guide. XD


    Thanks a lot Ryecoaaron :)

  • I want to know how to install OMV 5 in RPI 4 , The only version I see in the website is for amd64....... so, I need a guide. XD

    Just guessing since I don't have one.


    Install the raspbian for RPi4.
    Follow guide - https://forum.openmediavault.o…OMV5-on-Debian-10-Buster/

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • For those that have ordered the RPi4 already, what are you planning on doing with them e.g. are you going to be adding multiple hard drives?


    I am extremely tempted to get one (just because they are cool) but cannot quite see what there main advantages are, when it comes to NAS use.

  • For those that have ordered the RPi4 already, what are you planning on doing with them e.g. are you going to be adding multiple hard drives?


    I am extremely tempted to get one (just because they are cool) but cannot quite see what there main advantages are, when it comes to NAS use.

    I only need one drive so..... Enough for file server NAS for home (Movies, Music, etc).


    For Backup , I think you can use multiple powered hard-drive attached to each usb of RPI4, or using a powered Usb3.0 hub......


    Meanwhile, Let OMV-team enough time for release omv 5.0 :)

  • That is my slight issue - I also have a single hard drive for my home server.


    I am currently using an Odroid HC2, which has the advantage of a neat little case and a single power supply.


    When you add up all the cost of everything, I am not sure the Pi route is going to be the cheaper option either.

  • Next try to fight silent bit rot. A btrfs raid1 made out of two USB3 attached SSDs:


    I hope that with release of OMV5 the mount options are adjusted to noatime,nodiratime instead of relatime.


    Bildschirmfoto 2019-06-26 um 20.45.37.png


    Debug output: http://ix.io/1MRH


    Please be aware that you can run into ugly underpowering issues that look like 'UAS driver' issues or 'btrfs is not ready yet' BS: https://www.cnx-software.com/2…ni-review/#comment-564128


    Underpowering might be related to exceeding the current limitations on the RPi 4 USB ports (close to 1.2A max for all 4 USB ports combined) or it's the usual undervoltage sh*t show we know from almost all (5V powered) SBC already. For anyone thinking about the RPi 4 don't forget to buy their own USB-C PSU!

  • OMV5 installation routine the armbian-config way has some bugs that need to be fixed

    My fixes are online now.


    To get a BETA OMV5 install on the RPi 4 all I did now was:


    • Grab Raspbian Buster Lite and burned it with balenaEtcher
    • Created an empty file called ssh on the boot partition of the SD card
    • Inserted SD card and booted the RPi 4
    • after one minute ssh pi@raspberry.local from my laptop (default password is 'raspberry')
    • sudo -s
    • echo "deb [arch=arm64] http://apt.armbian.com $(lsb_release -cs) main" > /etc/apt/sources.list.d/armbian.list
    • apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 9F0E78D5
    • apt update
    • apt install armbian-config
    • armbian-config (Software --> Softy --> Install OMV)
    • apt upgrade
    • reboot

    Et voilà:
    Bildschirmfoto 2019-06-27 um 09.59.12.png


    If you access the OMV UI the first time do the following things first:

    • In 'General settings' change the admin password
    • In 'Access Rights Management' under 'Users' change the password of the default pi user and add the ssh group (this will allow to remotely administrate OMV through SSH and to use this account for authentication. Windows users look here)
    • optionally create new user accounts and optionally assign these to the groups ssh and sudo in case those users should also administrate the system remotely
    • optionally change the hostname to something like rpi4. This allows you to access all OMV services via this name (no need to remember boring IP addresses). Otherwise the OMV install will be available as http://raspberrypi or http://raspberrypi.local
    • If you change the hostname you need to define the eth0 interface in Network --> Interfaces (set it to DHCP unless you really really know what you're doing. To get a static IP address for whatever reasons assign a static DHCP lease at your router)
  • A btrfs raid1 made out of two USB3 attached SSDs

    Continuing with this btrfs raid1 connected to the two USB3 ports of the RPi 4. This test is about reliability and testing for correct write barrier semantics.


    As almost everybody in the storage world knows btrfs with recent kernels is rock solid wrt power losses or crashes since it's designed for this (CoW -- copy on write). But this only works if the whole data path to the drives in question implements write barriers correctly. So let's test this on RPi 4 since here the XHCI controller is entirely new and the USB implementation of all the older RPi variants is known to be quirky.


    I used the btrfs raid1 to ensure maximum drive activity when testing with iozone -e -I -a -s 1000M -r 1024k -i 0 -i 1 -i 2 (I tested also with other record sizes down to 1K to maximize stress on the storage). Then while the write test is running I simply unplugged the power cable to simulate a power loss.


    This has been repeated 10 times, always checking dmesg output for traces of problems followed by a btrfs scrub:


    No problems whatsoever and as such a confirmation that the USB3 controller on the RPi 4 does not suck unlike the implementation on the older RPi.


    Unfortunately still some retired forum members spend a lot of their spare time on spreading BS and FUD in this forum as well as polluting related Github issues. While it's perfectly understandable that users lack knowledge and testing methodology the inability to grasp even basics and actively refusing to learn sucks and results in sabotaging the work done here. I'm sick of this and won't continue until this problem is resolved.

  • My fixes are online now.
    To get a BETA OMV5 install on the RPi 4 all I did now was:


    • Grab Raspbian Buster Lite and burned it with balenaEtcher
    • Created an empty file called ssh on the boot partition of the SD card
    • Inserted SD card and booted the RPi 4
    • after one minute ssh pi@raspberry.local from my laptop (default password is 'raspberry')
    • sudo -s
    • echo "deb [arch=arm64] http://apt.armbian.com $(lsb_release -cs) main" > /etc/apt/sources.list.d/armbian.list
    • apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 9F0E78D5
    • apt update
    • apt install armbian-config
    • armbian-config (Software --> Softy --> Install OMV)
    • apt upgrade
    • reboot

    Et voilà:
    Bildschirmfoto 2019-06-27 um 09.59.12.png


    If you access the OMV UI the first time do the following things first:

    • In 'General settings' change the admin password
    • In 'Access Rights Management' under 'Users' change the password of the default pi user and add the ssh group (this will allow to remotely administrate OMV through SSH and to use this account for authentication. Windows users look here)
    • optionally create new user accounts and optionally assign these to the groups ssh and sudo in case those users should also administrate the system remotely
    • optionally change the hostname to something like rpi4. This allows you to access all OMV services via this name (no need to remember boring IP addresses). Otherwise the OMV install will be available as http://raspberrypi or http://raspberrypi.local
    • If you change the hostname you need to define the eth0 interface in Network --> Interfaces (set it to DHCP unless you really really know what you're doing. To get a static IP address for whatever reasons assign a static DHCP lease at your router)

    Help :(

  • Help

    You're typing stuff in a Terminal (and missed the leading / in front of /etc/apt/sources.list.d/armbian.list). This is not going to work. Better use SSH as hinted to above. Just use your normal computer and do ssh pi@raspberry.local to connect to the RPi (works on every OS except older Windows versions than Win10, there you need Putty or something like that, in Win10 you need to open cmd.exe).


    With SSH you can use copy&paste then...


    If you didn't created the empty file called ssh on the boot partition you need to follow these procedures: https://www.raspberrypi.org/documentation/remote-access/ssh/

  • Here is a nice synopsis of the RPI4.


    The Raspberry Pi 4's Most Interesting Quirks


    Mainly:
    1) It runs even hotter
    2) It uses more power
    3) You can't play 4k video on it.
    4) The processor is much faster
    5) Ethernet is finally fast
    6) It has USB 3


    See the article for fancy graphs.

  • You can't play 4k video on it.

    I guess Tom's hardware didn't read the tech specs correctly. It only supports 1080p with H264 (which they were testing with). It supports 4k with H265.



    Quote

    H.265 (4kp60 decode), H264 (1080p60 decode, 1080p30 encode)

    omv 5.5.12 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • You're typing stuff in a Terminal (and missed the leading / in front of /etc/apt/sources.list.d/armbian.list). This is not going to work. Better use SSH as hinted to above. Just use your normal computer and do ssh pi@raspberry.local to connect to the RPi (works on every OS except older Windows versions than Win10, there you need Putty or something like that, in Win10 you need to open cmd.exe).
    With SSH you can use copy&paste then...


    If you didn't created the empty file called ssh on the boot partition you need to follow these procedures: https://www.raspberrypi.org/documentation/remote-access/ssh/

    Tank you problem fixing , Omv 5 work but harddisk sharing does not work properly :D


    I'll try re-installation later

  • Tank you problem fixing , Omv 5 work but harddisk sharing does not work properly :D
    I'll try re-installation later


    I've re-installed it now and the harddisk works fine :D Maximum speed data transfer


    missing List


    Root password :D
    mini Dlna plugin
    transmission plugin
    ---------------------------------------------------------
    @Edit: system crashed after rebooting ;(
    ---------------------------------------------------------
    @Edit2 : Reinstall with (Raspbian Buster with desktop) Not lite version


    Works greate,
    no system crash at this time,

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!