OMV container did not work on Proxmox!

dopamine

Member
Apr 16, 2019
4
1
8
43
OMV container could not start on Proxmox!

I just installed a omv container on PVE, But there were several problems.
Here were PVE infomation:
Code:
root@pve:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-50
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-25
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-19
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
And OMV:
Code:
root@omv:~# uname -a
Linux omv 4.15.18-12-pve #1 SMP PVE 4.15.18-35 (Wed, 13 Mar 2019 08:24:42 +0100) x86_64 GNU/Linux
root@omv:~# dpkg -l | grep openmediavault
ii  openmediavault                  4.1.22-1                          all          openmediavault - The open network attached storage solution
ii  openmediavault-keyring          1.0                               all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-omvextrasorg     4.1.15                            all          OMV-Extras.org Package Repositories for OpenMediaVault
1. Installation problems
Code:
root@omv:~# omv-initsystem
run-parts: /usr/share/openmediavault/mkconf/sysctl.d/nonrot exited with return code 1
run-parts: /usr/share/openmediavault/initsystem/90sysctl exited with return code 1
So, I did:
Code:
root@omv:~# chmod -x /usr/share/openmediavault/mkconf/sysctl.d/nonrot
root@omv:~# omv-initsystem
Every thing seemed OK.

2. Problem on disk passthrough to LXC:
Here was my disks:
Code:
root@pve:~#  ls -la /dev/sd*
brw-rw---- 1 root disk 8,  0 Apr 16 06:36 /dev/sda
brw-rw---- 1 root disk 8,  1 Apr 16 06:36 /dev/sda1
brw-rw---- 1 root disk 8,  2 Apr 16 06:36 /dev/sda2
brw-rw---- 1 root disk 8,  3 Apr 16 06:36 /dev/sda3
brw-rw---- 1 root disk 8, 16 Apr 16 19:18 /dev/sdb
brw-rw---- 1 root disk 8, 17 Apr 16 19:20 /dev/sdb1
brw-rw---- 1 root disk 8, 18 Apr 16 19:18 /dev/sdb2
brw-rw---- 1 root disk 8, 21 Apr 16 23:02 /dev/sdb5
brw-rw---- 1 root disk 8, 32 Apr 16 06:37 /dev/sdc
brw-rw---- 1 root disk 8, 48 Apr 16 06:37 /dev/sdd
And my lxc's configuration:
Code:
root@pve:~# cat /etc/pve/lxc/201.conf
arch: amd64
cores: 1
hostname: omv
memory: 2048
net0: name=eth0,bridge=vmbr0,hwaddr=92:84:87:4C:B9:86,ip=dhcp,ip6=dhcp,type=veth
ostype: debian
rootfs: local-lvm:vm-201-disk-0,size=8G
swap: 2048
unprivileged: 1
##
lxc.apparmor.profile: unconfined
lxc.mount.auto: cgroup:rw
lxc.mount.auto: proc:rw
lxc.mount.auto: sys:rw
##
##
lxc.cgroup.devices.allow = b 8:16 rwm
lxc.cgroup.devices.allow = b 8:17 rwm
#lxc.cgroup.devices.allow = b 8:18 rwm
lxc.cgroup.devices.allow = b 8:21 rwm
lxc.autodev: 1
lxc.hook.autodev:/var/lib/lxc/201/mount-hook.sh
##
##
##lxc.apparmor.profile = lxc-container-default-with-mounting
##
##
##lxc.mount.entry: /mnt/sdb5 mnt/2C7E72EB7E72ACE8 none bind,create=dir,optional 0 0
lxc.mount.entry: /mnt/sdb1 mnt/sdb1 none bind,create=dir,iocharset=utf8,optional 0 0
lxc.mount.entry: /mnt/sdb5 mnt/sdb5 none bind,create=dir,iocharset=cp936,optional 0 0
##
And hook script:
Code:
root@pve:~# cat /var/lib/lxc/201/mount-hook.sh
#!/bin/sh
mknod -m 777 ${LXC_ROOTFS_MOUNT}/dev/sdb b 8 16
mknod -m 777 ${LXC_ROOTFS_MOUNT}/dev/sdb1 b 8 17
#mknod -m 777 ${LXC_ROOTFS_MOUNT}/dev/sdb2 b 8 18
mknod -m 777 ${LXC_ROOTFS_MOUNT}/dev/sdb5 b 8 21
#mknod -m 777 /dev/sdb b 8 16
#mknod -m 777 /dev/sdb1 b 8 17
#mknod -m 777 /dev/sdb2 b 8 18
#mknod -m 777 /dev/sdb5 b 8 21
I stated the lxc:
Code:
root@pve:~# lxc-start -n 201 -F --logfile 201.log
....
lxc-start: 201: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
root@pve:~# cat 201.log
lxc-start 201 20190415135407.798 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 1
lxc-start 201 20190415135407.798 ERROR    conf - conf.c:lxc_setup:3650 - Failed to run autodev hooks
lxc-start 201 20190415135407.798 ERROR    start - start.c:do_start:1279 - Failed to setup container "201"
lxc-start 201 20190415135407.799 ERROR    sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 5)
lxc-start 201 20190415135407.799 ERROR    start - start.c:__lxc_start:1989 - Failed to spawn container "201"
lxc-start 201 20190415135408.747 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 201 20190415135408.747 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start 201 20190417104056.521 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 1
lxc-start 201 20190417104056.522 ERROR    conf - conf.c:lxc_setup:3650 - Failed to run autodev hooks
lxc-start 201 20190417104056.522 ERROR    start - start.c:do_start:1279 - Failed to setup container "201"
lxc-start 201 20190417104056.522 ERROR    sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 5)
lxc-start 201 20190417104056.522 ERROR    start - start.c:__lxc_start:1989 - Failed to spawn container "201"
lxc-start 201 20190417104057.474 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 201 20190417104057.474 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start 201 20190417104403.134 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 1
lxc-start 201 20190417104403.134 ERROR    conf - conf.c:lxc_setup:3650 - Failed to run autodev hooks
lxc-start 201 20190417104403.134 ERROR    start - start.c:do_start:1279 - Failed to setup container "201"
lxc-start 201 20190417104403.134 ERROR    sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 5)
lxc-start 201 20190417104403.134 ERROR    start - start.c:__lxc_start:1989 - Failed to spawn container "201"
lxc-start 201 20190417104404.102 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 201 20190417104404.102 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start 201 20190417105701.208 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 1
lxc-start 201 20190417105701.208 ERROR    start - start.c:lxc_fini:1035 - Failed to run lxc.hook.post-stop for container "201"
lxc-start 201 20190417105711.970 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 1
lxc-start 201 20190417105711.970 ERROR    conf - conf.c:lxc_setup:3650 - Failed to run autodev hooks
lxc-start 201 20190417105711.970 ERROR    start - start.c:do_start:1279 - Failed to setup container "201"
lxc-start 201 20190417105711.970 ERROR    sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 5)
lxc-start 201 20190417105711.970 ERROR    start - start.c:__lxc_start:1989 - Failed to spawn container "201"
lxc-start 201 20190417105712.922 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 201 20190417105712.922 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start 201 20190417120631.259 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 1
lxc-start 201 20190417120631.259 ERROR    conf - conf.c:lxc_setup:3650 - Failed to run autodev hooks
lxc-start 201 20190417120631.259 ERROR    start - start.c:do_start:1279 - Failed to setup container "201"
lxc-start 201 20190417120631.259 ERROR    sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 5)
lxc-start 201 20190417120631.259 ERROR    start - start.c:__lxc_start:1989 - Failed to spawn container "201"
lxc-start 201 20190417120632.210 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 201 20190417120632.210 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options
I could not boot the lxc.

3. Another problem
I comentted all the command on /var/lib/lxc/201/mount-hook.sh, I could boot the lxc with some errors:
Code:
root@pve:~# lxc-start -n 201 -F --logfile 201.2.log
systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK                                                                              +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +EL                                                                             FUTILS +KMOD +IDN)
Detected virtualization lxc.
Detected architecture x86-64.
Welcome to Debian GNU/Linux 9 (stretch)!
Set hostname to <omv>.
Failed to read AF_UNIX datagram queue length, ignoring: No such file or director                                                                             y
Failed to install release agent, ignoring: No such file or directory
...
[UNSUPP] Starting of Arbitrary Executable Fi…tem Automount Point not supported.
...
systemd-journald-audit.socket: Failed to listen on sockets: Operation not permit                                                                             ted
[FAILED] Failed to listen on Journal Audit Socket.
See 'systemctl status systemd-journald-audit.socket' for details.
systemd-journald-audit.socket: Unit entered failed state.
system.slice: Failed to reset devices.list: Operation not permitted
system.slice: Failed to set invocation ID on control group /system.slice, ignori                                                                             ng: Operation not permitted
[  OK  ] Created slice System Slice.
systemd-remount-fs.service: Failed to reset devices.list: Operation not permitte                                                                             d
systemd-remount-fs.service: Failed to set invocation ID on control group /system                                                                             .slice/systemd-remount-fs.service, ignoring: Operation not permitted
         Starting Remount Root and Kernel File Systems...
systemd-modules-load.service: Failed to reset devices.list: Operation not permit                                                                             ted
systemd-modules-load.service: Failed to set invocation ID on control group /syst                                                                             em.slice/systemd-modules-load.service, ignoring: Operation not permitted
         Starting Load Kernel Modules...
proc-fs-nfsd.mount: Failed to reset devices.list: Operation not permitted
proc-fs-nfsd.mount: Failed to set invocation ID on control group /system.slice/p                                                                             roc-fs-nfsd.mount, ignoring: Operation not permitted
         Mounting NFSD configuration filesystem...
keyboard-setup.service: Failed to reset devices.list: Operation not permitted
keyboard-setup.service: Failed to set invocation ID on control group /system.sli                                                                             ce/keyboard-setup.service, ignoring: Operation not permitted
         Starting Set the console keyboard layout...
system-getty.slice: Failed to reset devices.list: Operation not permitted
system-getty.slice: Failed to set invocation ID on control group /system.slice/s                                                                             ystem-getty.slice, ignoring: Operation not permitted
[  OK  ] Created slice system-getty.slice.
sys-kernel-debug.mount: Failed to reset devices.list: Operation not permitted
sys-kernel-debug.mount: Failed to set invocation ID on control group /system.sli                                                                             ce/sys-kernel-debug.mount, ignoring: Operation not permitted
         Mounting Debug File System...
lvm2-monitor.service: Failed to reset devices.list: Operation not permitted
lvm2-monitor.service: Failed to set invocation ID on control group /system.slice                                                                             /lvm2-monitor.service, ignoring: Operation not permitted
         Starting Monitoring of LVM2 mirrors…ng dmeventd or progress polling...
dev-mqueue.mount: Failed to reset devices.list: Operation not permitted
dev-mqueue.mount: Failed to set invocation ID on control group /system.slice/dev                                                                             -mqueue.mount, ignoring: Operation not permitted
         Mounting POSIX Message Queue File System...
system-container\x2dgetty.slice: Failed to reset devices.list: Operation not per                                                                             mitted
system-container\x2dgetty.slice: Failed to set invocation ID on control group /s                                                                             ystem.slice/system-container\x2dgetty.slice, ignoring: Operation not permitted
[  OK  ] Created slice system-container\x2dgetty.slice.
resolvconf.service: Failed to reset devices.list: Operation not permitted
resolvconf.service: Failed to set invocation ID on control group /system.slice/r                                                                             esolvconf.service, ignoring: Operation not permitted
         Starting Nameserver information manager...
run-rpc_pipefs.mount: Failed to reset devices.list: Operation not permitted
run-rpc_pipefs.mount: Failed to set invocation ID on control group /system.slice                                                                             /run-rpc_pipefs.mount, ignoring: Operation not permitted
         Mounting RPC Pipe File System...
systemd-tmpfiles-setup-dev.service: Failed to reset devices.list: Operation not                                                                              permitted
systemd-tmpfiles-setup-dev.service: Failed to set invocation ID on control group                                                                              /system.slice/systemd-tmpfiles-setup-dev.service, ignoring: Operation not permi                                                                             tted
         Starting Create Static Device Nodes in /dev...
user.slice: Failed to reset devices.list: Operation not permitted
user.slice: Failed to set invocation ID on control group /user.slice, ignoring:                                                                              Operation not permitted
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Listening on Journal Socket (/dev/log).
systemd-journald.service: Failed to reset devices.list: Operation not permitted
systemd-journald.service: Failed to set invocation ID on control group /system.s                                                                             lice/systemd-journald.service, ignoring: Operation not permitted
         Starting Journal Service...
[  OK  ] Reached target Swap.
dev-tty.mount: Failed to reset devices.list: Operation not permitted
proc-loadavg.mount: Failed to reset devices.list: Operation not permitted
proc-stat.mount: Failed to reset devices.list: Operation not permitted
dev-null.mount: Failed to reset devices.list: Operation not permitted
dev-zero.mount: Failed to reset devices.list: Operation not permitted
dev-random.mount: Failed to reset devices.list: Operation not permitted
proc-cpuinfo.mount: Failed to reset devices.list: Operation not permitted
sys-fs-fuse-connections.mount: Failed to reset devices.list: Operation not permi                                                                             tted
mnt-sdb5.mount: Failed to reset devices.list: Operation not permitted
-.mount: Failed to reset devices.list: Operation not permitted
dev-tty1.mount: Failed to reset devices.list: Operation not permitted
dev-tty2.mount: Failed to reset devices.list: Operation not permitted
proc-uptime.mount: Failed to reset devices.list: Operation not permitted
proc-diskstats.mount: Failed to reset devices.list: Operation not permitted
dev-full.mount: Failed to reset devices.list: Operation not permitted
proc-meminfo.mount: Failed to reset devices.list: Operation not permitted
proc-swaps.mount: Failed to reset devices.list: Operation not permitted
mnt-sdb1.mount: Failed to reset devices.list: Operation not permitted
dev-urandom.mount: Failed to reset devices.list: Operation not permitted
dev-ptmx.mount: Failed to reset devices.list: Operation not permitted
init.scope: Failed to reset devices.list: Operation not permitted
[  OK  ] Started Remount Root and Kernel File Systems.
quota.service: Failed to reset devices.list: Operation not permitted
quota.service: Failed to set invocation ID on control group /system.slice/quota.                                                                             service, ignoring: Operation not permitted
         Starting Initial Check File System Quotas...
systemd-udev-trigger.service: Failed to reset devices.list: Operation not permit                                                                             ted
systemd-udev-trigger.service: Failed to set invocation ID on control group /syst                                                                             em.slice/systemd-udev-trigger.service, ignoring: Operation not permitted
         Starting udev Coldplug all Devices...
systemd-remount-fs.service: Failed to reset devices.list: Operation not permitte                                                                             d
systemd-remount-fs.service: Failed to set invocation ID on control group /system                                                                             .slice/systemd-remount-fs.service, ignoring: Operation not permitted
[  OK  ] Mounted POSIX Message Queue File System.
sys-kernel-debug.mount: Mount process exited, code=exited status=32
[FAILED] Failed to mount Debug File System.
See 'systemctl status sys-kernel-debug.mount' for details.
sys-kernel-debug.mount: Unit entered failed state.
proc-fs-nfsd.mount: Mount process exited, code=exited status=32
[FAILED] Failed to mount NFSD configuration filesystem.
See 'systemctl status proc-fs-nfsd.mount' for details.
[DEPEND] Dependency failed for NFS server and services.
[DEPEND] Dependency failed for NFSv4 ID-name mapping service.
nfs-idmapd.service: Job nfs-idmapd.service/start failed with result 'dependency'                                                                             .
[DEPEND] Dependency failed for NFS Mount Daemon.
nfs-mountd.service: Job nfs-mountd.service/start failed with result 'dependency'                                                                             .
nfs-server.service: Job nfs-server.service/start failed with result 'dependency'                                                                             .
proc-fs-nfsd.mount: Unit entered failed state.
run-rpc_pipefs.mount: Mount process exited, code=exited status=32
[FAILED] Failed to mount RPC Pipe File System.
See 'systemctl status run-rpc_pipefs.mount' for details.
[DEPEND] Dependency failed for pNFS block layout mapping daemon.
nfs-blkmap.service: Job nfs-blkmap.service/start failed with result 'dependency'                                                                             .
[DEPEND] Dependency failed for RPC security service for NFS client and server.
rpc-gssd.service: Job rpc-gssd.service/start failed with result 'dependency'.
[DEPEND] Dependency failed for RPC security service for NFS server.
rpc-svcgssd.service: Job rpc-svcgssd.service/start failed with result 'dependenc                                                                             y'.
run-rpc_pipefs.mount: Unit entered failed state.
[  OK  ] Reached target NFS client services.
lvm2-lvmetad.service: Failed to reset devices.list: Operation not permitted
lvm2-lvmetad.service: Failed to set invocation ID on control group /system.slice                                                                             /lvm2-lvmetad.service, ignoring: Operation not permitted
...
[FAILED] Failed to mount Configuration File System.
See 'systemctl status sys-kernel-config.mount' for details.
...
[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
...
[FAILED] Failed to start Beep after system start.
See 'systemctl status openmediavault-beep-up.service' for details.
[FAILED] Failed to start watchdog daemon.
See 'systemctl status watchdog.service' for details.
         Starting watchdog keepalive daemon...
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
[FAILED] Failed to start watchdog keepalive daemon.
See 'systemctl status wd_keepalive.service' for details.
...
omv login:
After login to omv, I got the following message:
'
* sys-kernel-config.mount - Configuration File System
   Loaded: loaded (/lib/systemd/system/sys-kernel-config.mount; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-04-17 14:51:20 UTC; 11min ago
    Where: /sys/kernel/config
     What: configfs
...
  Process: 60 ExecMount=/bin/mount configfs /sys/kernel/config -t configfs (code=exited, status=32)
Apr 17 14:51:20 omv systemd[1]: sys-kernel-config.mount: Failed to reset devices.list: Operation not permitted
Apr 17 14:51:20 omv systemd[1]: sys-kernel-config.mount: Failed to set invocation ID on control group /system.slice/sys-kernel-config.mount, ignoring: Operat
Apr 17 14:51:20 omv systemd[1]: Mounting Configuration File System...
Apr 17 14:51:20 omv systemd[1]: sys-kernel-config.mount: Mount process exited, code=exited status=32
Apr 17 14:51:20 omv systemd[1]: Failed to mount Configuration File System.
Apr 17 14:51:20 omv systemd[1]: sys-kernel-config.mount: Unit entered failed state.
Disk on pve mounted, but could not be wrote:
Code:
root@omv:~# ls /mnt/sdb1
lost+found
root@omv:~# cd /mnt/sdb1
root@omv:/mnt/sdb1# touch file_on_omv
touch: cannot touch 'file_on_omv': Permission denied
I entered the web-ui. After clicking the Storage->File Systems, lots of errors:
Code:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; blkid -o full 2>&1' with exit code '2':
Here were the details:
Code:
Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; blkid -o full 2>&1' with exit code '2':  in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/backend/manager.inc(211): OMV\System\Process->execute(Array)
#1 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(803): OMV\System\Filesystem\Backend\Manager->enumerate()
#2 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(69): OMV\System\Filesystem\Filesystem::getFilesystems()
#3 [internal function]: OMVRpcServiceFileSystemMgmt->enumerateFilesystems(NULL, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#5 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(320): OMV\Rpc\ServiceAbstract->callMethod('enumerateFilesy...', NULL, Array)
#6 [internal function]: OMVRpcServiceFileSystemMgmt->getList(Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusfN...', '/tmp/bgoutputZA...')
#10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#11 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(470): OMV\Rpc\ServiceAbstract->callMethodBg('getList', Array, Array)
#12 [internal function]: OMVRpcServiceFileSystemMgmt->getListBg(Array, Array)
#13 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#14 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getListBg', Array, Array)
#15 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'getListBg', Array, Array, 1)

Could any one help?
Thanks!
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!