Problem with OMV on Odroid XU4

    • OMV 3.x

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

    • Problem with OMV on Odroid XU4

      Hello all!

      I'm having an odd problem with running OMV and NFS on an odroid XU4 system. First of all some details about OMV on the odroid device:

      Hostname = odroidxu4
      version = 3.0.92
      kernel = 4.9.61-odroidxu4

      The odroid is using an external hard drive connected to the usb port of that device although it has its own power supply.


      The system I'm connecting to OMV is just a normal x86 box running debian 9 via ethernet. I also get the same error on a different debian box running the next version of debian (buster).


      The problem is that whenever I try to mount the device after power on via NFS I get the following error:

      Source Code

      1. mount.nfs: requested NFS version or transport protocol is not supported

      I can get it to work if I disable, save then re-enable and save NFS and reboot OMV. But does anyone know why I'd get that error each time at all?

      OMV seems to have installed OK on the odroid system; I can log into OMV's web browser interface ok, I can SSH in with no problems, it sees the ethernet and USB 3 hard drive with no problems.

      The USB hard drive I'm using with the odroid device and OMV is an external hard drive made by a company called orico. It's a two-bay device (I Just have one of the bays filled with a SATA 2TB hard drive). OMV lists this device as " 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp." - after poking around online this is apparently a JMS567 chipset based system.

      BTW OMV is not running from the USB device, it is running from a microsd card installed in the odroid XU4.

      thanks

      ljones

      The post was edited 3 times, last by ljones ().

    • Still not got anywhere so far. A little more info though;

      (From a debian box connected to OMV)

      Source Code

      1. $ mount -t nfs -v -o noatime 192.168.1.1:/test /tmp/0
      2. [code]
      3. mount.nfs: timeout set for Tue Feb 6 18:28:24 2018
      4. mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.1,clientaddr=192.168.1.9'
      5. mount.nfs: mount(2): Connection refused
      6. mount.nfs: trying text-based options 'addr=192.168.1.1'
      7. mount.nfs: prog 100003, trying vers=3, prot=6
      8. mount.nfs: portmap query retrying: RPC: Program not registered
      9. mount.nfs: prog 100003, trying vers=3, prot=17
      10. mount.nfs: portmap query failed: RPC: Program not registered
      11. mount.nfs: requested NFS version or transport protocol is not supported
      12. root@debian:/home/aaaaa#
      13. root@debian:/home/aaaaa# mount -t nfs -v 192.168.1.1:/test /tmp/0mount.nfs: timeout set for Tue Feb 6 18:28:51 2018
      14. mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.1,clientaddr=192.168.1.9'
      15. mount.nfs: mount(2): Connection refused
      16. mount.nfs: trying text-based options 'addr=192.168.1.1'
      17. mount.nfs: prog 100003, trying vers=3, prot=6
      18. mount.nfs: portmap query retrying: RPC: Program not registered
      19. mount.nfs: prog 100003, trying vers=3, prot=17
      20. mount.nfs: portmap query failed: RPC: Program not registered
      21. mount.nfs: requested NFS version or transport protocol is not supported
      Display All

      Source Code

      1. $ service nfs status
      2. Unit nfs.service could not be found.

      Source Code

      1. showmount -e 192.168.1.1
      2. clnt_create: RPC: Program not registered

      Source Code

      1. $ service nfs-kernel-server status
      2. nfs-server.service - NFS server and services
      3. Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor p
      4. Active: active (exited) since Tue 2018-02-06 18:23:35 GMT; 46s ago
      5. Process: 584 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, statu
      6. Process: 582 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUC
      7. Main PID: 584 (code=exited, status=0/SUCCESS)
      8. Tasks: 0 (limit: 4915)
      9. CGroup: /system.slice/nfs-server.service


      Weird. Why would 'service nfs status' fail like that when service nfs-kernel-server works? Or is this still an OMV problem?

      ljones
    • Was not sure what to try but in the end I tried doing (on the debian box, not the OMV):

      Source Code

      1. $ apt-get remove nfs-kernel-server

      From memory, nfs-common is (presumably) still installed. Weirdly this seems to be working so far and I'm not getting mounting errors any more. Weird because before in the past this seemed to be needed to installed.

      Update
      Unfortunatly it dosen't seem to have worked. Worked a couple of times now I'm back to the same problem again :(

      ljones

      The post was edited 2 times, last by ljones ().

    • Now starting to look at OMV;

      Source Code

      1. root@odroidxu4:~# systemctl status nfs-common -l
      2. ● nfs-common.service - LSB: NFS support files common to client and server
      3. Loaded: loaded (/etc/init.d/nfs-common)
      4. Active: active (exited) since Fri 2018-02-09 17:14:26 GMT; 49min ago
      5. Feb 09 17:14:26 odroidxu4 nfs-common[333]: Starting NFS common utilities: statd
      6. Feb 09 17:14:26 odroidxu4 nfs-common[333]: Not starting: portmapper is not running ... (warning).
      7. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

      Source Code

      1. root@odroidxu4:~# systemctl status nfs-kernel-server -l
      2. ● nfs-kernel-server.service - LSB: Kernel NFS server support
      3. Loaded: loaded (/etc/init.d/nfs-kernel-server)
      4. Active: active (exited) since Fri 2018-02-09 17:14:35 GMT; 45min ago
      5. Feb 09 17:14:35 odroidxu4 nfs-kernel-server[1295]: Exporting directories for NFS kernel daemon...exportfs: No host name given with /export/test (fsid=1,rw,no_subtree_check,insecure), suggest *(fsid=1,rw,no_subtree_check,insecure) to avoid warning
      6. Feb 09 17:14:35 odroidxu4 nfs-kernel-server[1295]: exportfs: No host name given with /export (ro,fsid=0,root_squash,no_subtree_check,hide), suggest *(ro,fsid=0,root_squash,no_subtree_check,hide) to avoid warning
      7. Feb 09 17:14:35 odroidxu4 nfs-kernel-server[1295]: .
      8. Feb 09 17:14:35 odroidxu4 nfs-kernel-server[1295]: Starting NFS kernel daemon: nfsd
      9. Feb 09 17:14:35 odroidxu4 nfs-kernel-server[1295]: Not starting: portmapper is not running ... (warning).
      10. Feb 09 17:14:35 odroidxu4 systemd[1]: Started LSB: Kernel NFS server support.
      Display All

      What does "active (exited)" mean? Does that mean it was running and it has stopped or ? And should portmapper be running (if it isn't maybe it crashed?). Not sure.

      ljones
    • Ok, I gave this a try, but it didn't work -- after trying I could not mount NFS at all (the debian box would just hang). So I've tried to reverse it by doing:

      Source Code

      1. update-rc.d rpcbind disable

      So far I've not had the NFS problem I had above (in the sense I haven't had to disable/enable NFS and restart OMV). But I'm keeping an eye on it as I don't think it is solved!

      ljones