Errors when updating system and mounting a drive in OMV5 with Nanopi M4 (Rock 3399) ARM

    Hello to all!


    I’m installing OMV5 for the first time, and for me it was not an easy task.


    I have a SBC Nanopi M4

    I originally set Armbian_20.02.7_Nanopim4_buster_legacy_4.4.213_desktop

    (Linux 4.4.213-rk3399)

    and further on through armbian-config


    Firstly, the problems started after the automatic installation of OMV5 - the wifi module fell off and there was no network on the board - the problem was solved by reinstalling the network manager.


    Further, in the OMV system itself, I could not update the components - it produced a bunch of errors.

    These errors appear when the wifi module is working and the presence of an Internet connection

    2020-03-31 20.13.57 192.168.1.138 e94e2040a3ca.png

    2020-03-31 20.14.14 192.168.1.138 0dad14c9bf99.png



    After which I tried to install the disks. As a test, I managed to connect and mount 1 flash drive to 8GB, but there were problems with the second 128GB drive and it does not want to be mounted in any way!


    2020-03-31 20.48.04 192.168.1.138 ead70b893b85.png


    I tried to restart the system and reinstall Armbian - but I get the same errors again ((


    what could it be? Help me please!


    I tried to install only the server, but then I have problems connecting the wifi network and bluetooth

    also tried current and legacy versions


    More or less stable, only this version works for me (Armbian_20.02.7_Nanopim4_buster_legacy_4.4.213_desktop)


    When installing, I followed just this instruction


    I will try again install buster server...if no more idea....

    Thanx for answer

    Quote from Baklab

    I have problems connecting the wifi network and bluetooth

    You will need to plug it in until you can setup wifi from the OMV web interface (although I would never use wifi).

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    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!

    and I get the same error when mounting a disk (

    moreover, this time more than one flash drive is not mounted ((

    not 8 GB not 128 GB

    8 GB flash drive mounted ... but at 128gb it produces the same error.


    Armbian_20.02.7_Nanopim4_buster_current_5.4.28


    2020-03-31 23.12.07 192.168.1.136 703c211900cd.png


    Quote from Baklab

    but i have no wifi in web interface( (

    When I click Add Wifi in the interfaces tab on my NanoPiM4 running OMV 5.x, I see the "wlan0" device. Not sure why you don't.


    Quote from Baklab

    but at 128gb it produces the same error

    What filesystem?


    Quote from Baklab

    I tried another 512GB flash drive - it was mounted on a surprise (although it was in exfat), but when creating a shared directory I got the following error

    Don't use exfat. Use a native Linux filesystem.

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    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!

    Quote from ryecoaaron

    When I click Add Wifi in the interfaces tab on my NanoPiM4 running OMV 5.x, I see the "wlan0" device. Not sure why you don't.

    I don’t know, when installing a buster server current my board does not see the Wi-Fi device.


    ifconfig shows only ethernet and loop:

    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.1.136 netmask 255.255.255.0 broadcast 192.168.1.255

    ether 32:95:6f:18:4c:71 txqueuelen 1000 (Ethernet)

    RX packets 11625 bytes 4088028 (3.8 MiB)

    RX errors 0 dropped 0 overruns 0 frame 0

    TX packets 6464 bytes 3566996 (3.4 MiB)

    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    device interrupt 27


    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

    inet 127.0.0.1 netmask 255.0.0.0

    inet6 ::1 prefixlen 128 scopeid 0x10<host>

    loop txqueuelen 1000 (Local Loopback)

    RX packets 1442 bytes 650309 (635.0 KiB)

    RX errors 0 dropped 0 overruns 0 frame 0

    TX packets 1442 bytes 650309 (635.0 KiB)

    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    Installing a network manager does not help (


    maybe I need to install some drivers manually?


    Quote from ryecoaaron

    What filesystem?

    ext4 - therefore I am surprised. At the same time, I tried to format it several times through OMV5. Formatting completed successfully, but mounting failed



    Quote from ryecoaaron

    Don't use exfat. Use a native Linux filesystem.

    I understand, but I did it for an experiment

    Quote from Baklab

    I don’t know, when installing a buster server current my board does not see the Wi-Fi device.

    Is this a v2 board? I am also using the 4.4 kernel on my v1 board. Maybe there is an issue with the 5.4 kernel. I never use wireless so not much experience there.


    Quote from Baklab

    Installing a network manager does not help (

    And it never will. networkmanager doesn't create devices. It just configures them just like OMV (which uses sytemd-networkd). networkmanger will just cause problems with OMV.

    Quote from Baklab

    I understand, but I did it for an experiment

    OMV doesn't support exfat. That is why I told you not to use it.

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    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!

    Quote from ryecoaaron

    Is this a v2 board? I am also using the 4.4 kernel on my v1 board. Maybe there is an issue with the 5.4 kernel. I never use wireless so not much experience there.

    this is v1

    i try to install 4.4



    Quote from ryecoaaron

    OMV doesn't support exfat. That is why I told you not to use it.

    but its work! my card 512 gb (exfat) work well

    and 128 gb in ext4 - dont work and not mounted


    other errors have not yet noticed

    Quote from Baklab

    but its work! my card 512 gb (exfat) work well

    and 128 gb in ext4 - dont work and not mounted

    I guess Volker did add support for exfat. Didn't remember that. Still wouldn't use it. I don't know why your ext4 filesystem is having problems. I've never had this problem before but I would guess the drive needs to be wiped better.

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    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!

    Quote from Baklab

    I tried to format it in OMV - it did not help

    I will try to format it manually, and not through the web interface

    Not format. Wipe. Go to the Physical Disks tab and wipe it.

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    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!

    Quote from ryecoaaron

    Not format. Wipe. Go to the Physical Disks tab and wipe it.

    yes, i maen it. i wipe it, format (create file system) - not resolved



    i install kernel 4.4 - wifi work...BUT!


    again I get an error! how so ???


    When I try to mount any disk, I now get the following error ...


    2020-04-01 21.52.56 192.168.1.136 c2ff5fc60e75.png


    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working if not isinstance(exes, collections.Iterable): /usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function) nanopim4: ---------- ID: create_filesystem_mountpoint_110da769-901d-4e0d-b38b-0abd88f7c8c2 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_110da769-901d-4e0d-b38b-0abd88f7c8c2 for file /etc/fstab was charged by text Started: 21:52:26.337983 Duration: 1.697 ms Changes: ---------- ID: mount_filesystem_mountpoint_110da769-901d-4e0d-b38b-0abd88f7c8c2 Function: mount.mounted Name: /srv/dev-disk-by-label-Untitled Result: False Comment: mount: /srv/dev-disk-by-label-Untitled: unknown filesystem type 'exfat'. Started: 21:52:26.357959 Duration: 1075.033 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: Changes were made Started: 21:52:27.434826 Duration: 11.381 ms Changes: ---------- diff: --- +++ @@ -1,2 +1,5 @@ UUID=3795425a-ea8c-4a26-8861-09da07c2eddc / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 +# >>> [openmediavault] +/dev/disk/by-label/Untitled /srv/dev-disk-by-label-Untitled exfat defaults,nofail 0 2 +# <<< [openmediavault] Summary for nanopim4 ------------ Succeeded: 2 (changed=1) Failed: 1 ------------ Total states run: 3 Total run time: 1.088 s

    I really do not understand what is happening, again an error occurred while mounting the disk. this time I mount a 500 GB flash drive that I just wiped and formatted in OMV


    what am I doing wrong?!

    Why are so many errors streaming on different firmware?

    i reale not understand((

    please help



    2020-04-02 00.54.12 192.168.1.136 4f09794e87b7.png



    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working if not isinstance(exes, collections.Iterable): /usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function) nanopim4: ---------- ID: create_filesystem_mountpoint_ba28a0c5-832a-44a1-a484-bdbcb2c6a0ae Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_ba28a0c5-832a-44a1-a484-bdbcb2c6a0ae for file /etc/fstab was charged by text Started: 00:53:16.153587 Duration: 2.426 ms Changes: ---------- ID: mount_filesystem_mountpoint_ba28a0c5-832a-44a1-a484-bdbcb2c6a0ae Function: mount.mounted Name: /srv/dev-disk-by-id-usb-Kingston_DT_Mini_10_0018F30BC0EFF9B0717F93BB-0-0-part1 Result: True Comment: Target was already mounted Started: 00:53:16.159856 Duration: 504.746 ms Changes: ---------- umount: Forced remount because options (acl) changed ---------- ID: create_filesystem_mountpoint_49549be7-a530-4cb5-a0b7-1de5de727a36 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_49549be7-a530-4cb5-a0b7-1de5de727a36 for file /etc/fstab was charged by text Started: 00:53:16.665151 Duration: 2.593 ms Changes: ---------- ID: mount_filesystem_mountpoint_49549be7-a530-4cb5-a0b7-1de5de727a36 Function: mount.mounted Name: /srv/dev-disk-by-label-500 Result: False Comment: mount: /srv/dev-disk-by-label-500: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. Started: 00:53:16.668153 Duration: 149.105 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: Changes were made Started: 00:53:16.820019 Duration: 54.539 ms Changes: ---------- diff: --- +++ @@ -2,5 +2,5 @@ tmpfs /tmp tmpfs defaults,nosuid 0 0 # >>> [openmediavault] /dev/disk/by-id/usb-Kingston_DT_Mini_10_0018F30BC0EFF9B0717F93BB-0:0-part1 /srv/dev-disk-by-id-usb-Kingston_DT_Mini_10_0018F30BC0EFF9B0717F93BB-0-0-part1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 -/dev/disk/by-id/usb-Mass_Storage_Device_121220160204-0:0-part1 /srv/dev-disk-by-id-usb-Mass_Storage_Device_121220160204-0-0-part1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 +/dev/disk/by-label/500 /srv/dev-disk-by-label-500 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 # <<< [openmediavault] Summary for nanopim4 ------------ Succeeded: 4 (changed=2) Failed: 1 ------------ Total states run: 5 Total run time: 713.409 ms        



    Quote from Baklab

    and yet there is another mistake! (

    when trying to enable extars repo

    This is not a mistake or bug. It is a warning that resources on your relatively slow system are being heavily used (slow sd card I'm guessing) and it lost communication with browser for a brief moment.


    Quote from Baklab

    wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.


    Quote from Baklab

    what am I doing wrong?!

    Why are so many errors streaming on different firmware?

    i reale not understand((

    please help

    I don't know what you are doing. it doesn't like the disk. Maybe there is something wrong with it? I don't have any of these problems on my nanopim4 and I have one ssd and one hard drive connected to it.

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    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!

Participate now!

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

Register Yourself Login