OMV6 Unable to remote mount Zyxel NAS

ramack · 25. Oktober 2022

Hi,

Relatively new OMV6 install (cloned from a HDD to SDD). I'm trying to remote mount a Zyxel NAS326 in OMV6, but have having errors when applying the change. I've tried several iterations that have succeeded for others, but not working for me. (Options/ver 3 to 2, rebooting, refreshing etc). Could this possibly be a result of cloning my original install from a HDD to a SSD and the UUID is wrong?

After applying changing I get a big red box pop-up, only including the false ID.

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color remotemount 2>&1' with exit code '1': debian:

ID: restart_N326_remotemount
    Function: cmd.run
        Name: systemctl restart 'srv-dce5f521\x2de7e1\x2d4663\x2d9e1d\x2db228d4b24858.mount'
      Result: False
     Comment: Command "systemctl restart 'srv-dce5f521\x2de7e1\x2d4663\x2d9e1d\x2db228d4b24858.mount'" run
     Started: 17:36:03.275958
    Duration: 22.988 ms
     Changes:
              ----------
              pid:
                  43412
              retcode:
                  1
              stderr:
                  Job failed. See "journalctl -xe" for details.
              stdout:

Alles anzeigen

Output of journalctl -xe

Code

sudo journalctl -xe
[sudo] password for Rich: 
Oct 24 17:36:32 openmediavault kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/0003:03F0:604A.0065/input/input112
Oct 24 17:36:32 openmediavault kernel: hid-generic 0003:03F0:604A.0065: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:00:1d.0-2/inpu>
Oct 24 17:36:33 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:33 openmediavault omv-engined[43745]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:39 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:39 openmediavault omv-engined[43752]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:45 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:45 openmediavault omv-engined[43759]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:50 openmediavault autoshutdown[609]: root: INFO: 'main(): ------------------------------------------------------'
Oct 24 17:36:50 openmediavault autoshutdown[609]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Oct 24 17:36:51 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp0s25'
Oct 24 17:36:51 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:51 openmediavault omv-engined[43821]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:56 openmediavault sudo[31360]: pam_unix(sudo:session): session closed for user root
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.3 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.5 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.7 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.8 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.10 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.20 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.22 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.24 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.39 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.47 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.48 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.54 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.70 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.72 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.73 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.74 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): 192.168.1.202 is active'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown'
Oct 24 17:36:56 openmediavault autoshutdown[609]: root: INFO: 'main(): Active check failed, 1 cycles until shutdown ...'
Oct 24 17:36:57 openmediavault autoshutdown[609]: root: INFO: 'main(): Sleep for 20s'
Oct 24 17:36:58 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:36:58 openmediavault omv-engined[43935]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:37:04 openmediavault php[42924]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:37:04 openmediavault omv-engined[43943]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.
Oct 24 17:37:06 openmediavault sudo[43942]:     Rich : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Oct 24 17:37:06 openmediavault sudo[43942]: pam_unix(sudo:session): session opened for user root(uid=0) by Rich(uid=1002)

Alles anzeigen

Code

sudo blkid
/dev/sdb1: UUID="b19d92a6-e2e0-4b5f-8a73-772915a100a1" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b2aff62a-cf62-4adc-946c-bfbdec0a3361"
/dev/sda1: UUID="071ed228-4729-40a6-9843-5dd0249af839" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d6df43fd-01"

Any ideas? Thanks.

Krisbee · 25. Oktober 2022

ramack Did you check/tick the "fstab" option when you created the remote mount? It looks like it's optional in the plugin UI but I don't think it is . I don't know why you are seeing those time zone errors.

If there's any doubt your OMV6 can see your zyxel shares, you can always check that at the OMV CLI with a showmount command and or test whether it mounts at the CLI. I assumed you've picked NFS at the mount type for your remote mount - picking SMB/CIFS when you intend to use rsync can give serious perms headaches.

Once the remount is correctly mount it should show up under your filesystems.

ramack · 25. Oktober 2022

Zitat von Krisbee

Did you check/tick the "fstab" option when you created the remote mount? It looks like it's optional in the plugin UI but I don't think it is . I don't know why you are seeing those time zone errors.

Yes, I checked the box with similar/same results.

No, I was using smb/cifs. NFS makes sense now that you point it out. But would that affect mounting?

Krisbee · 25. Oktober 2022

ramack Keep fstab selected and use NFS for this job. Don't select NFSv4 unless you are sure the zyxel NAS supports it. Whether you should be using rsize/wsize options is debatable. Once mounted you can then create a task with a rysnc command with the options you need. E,g, : syncing remote mount directory path to local absolute shared folder path.

As always taking care with permissions and sync to a test folder on OMV first. This just mimics the command you would executed at the CLI.

ramack · 26. Oktober 2022

Still getting errors. I'm thinking a fresh install might help, maybe just to eliminate any clone info that might be causing problems. Should I consider OMV5 instead of OMV6? The hardware isn't "new" but it's definitely not old. Lenovo mini form factor, Intel 3GHz. 4G RAM.

ryecoaaron · 26. Oktober 2022

Zitat von ramack

Should I consider OMV5 instead of OMV6?

Definitely not. OMV 5 is EOL. OMV 6 doesn't have anymore hardware requirements than OMV 5 either.

Krisbee · 27. Oktober 2022

ramack What are the errors? Please be more specific. You know how to mount a nfs share at the OMV6 CLI to test if OMV6 can see your zyxel shares? Check what zyxel NFS shares are visible to OMV6 at the CLI with:

Code

showmount -e <ip of zyxel>

mount with:

Code

mount -vvv -t nfs  <ip of zyxel>:/<sharename>  /mnt

umount /mnt

The inclusion of the -vvv option will show the NFS version of export from the zyxel NAS..

If it mounts a the CLi you can check perms on zyxel. Assuming of course the zyxel has stored the data on a linux compat file system and not ntfs. Let's get the basics right and then set this up via OMv6 webui.

OMV6 Unable to remote mount Zyxel NAS

ramack 25. Oktober 2022

Jetzt mitmachen!

Ähnliche Themen

Unable to see plugins in OMV 6 Web UI. after migrating