Hi guys,
after the upgrade i have some problems:
No filesystems are visible in the gui - disk listing is ok and all services seems to run well. First i also had no plugin listing but i could fix it with some hints of this forum 
Side notice: after trying to list filesystems the system slows down until it is unuseable and needs a reset.
Also a giant count of omv-engined are started - it feels to much but i could be wrong ...
Any ideas ?
PS: smart info is available in the logs
And how do you expect help if you don't even say how many disks you have?
Or what hardware for that matter.
If you only have the OS disk, then this is normal because OMV6 won't show it unless you install the sharerootfs plugin.
there are 6 disks including system drive - 2 raid volumes and the others standalone so enough to show something
How many filesystems do you expect to see? How many filesystems have you mounted via the OMV UI?
Can you please execute and post the output of the following command?
# omv-rpc -u admin 'FileSystemMgmt' 'getList' '{"start":0,"limit":-1}' | jqIf you enable the browser dev tools via F12, are there any error messages shown in the 'Console' tab when you visit the file system page?
And maybe also the output of cat /etc/fstab
If the FS was previously done outside of OMV, it won't show on the GUI on omv6.
Can you please execute and post the output of the following command?
Code# omv-rpc -u admin 'FileSystemMgmt' 'getList' '{"start":0,"limit":-1}' | jq
If you enable the browser dev tools via F12, are there any error messages shown in the 'Console' tab when you visit the file system page?
No output on shell - needs to be canceled after a while like a hanging process 
Output in browser looks good excluding some design drops ...
And maybe also the output of cat /etc/fstab
If the FS was previously done outside of OMV, it won't show on the GUI on omv6.
FS was created on older omv version which was migrated to v6:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=9408c02c-cb33-44ce-aeb8-8aaf5ba8af2b / ext4 errors=remount-ro 0 1
UUID=66964ab2-96c7-4b30-bbd9-697758084573 swap swap defaults 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
tmpfs /tmp tmpfs defaults 0 0
# >>> [openmediavault]
/dev/disk/by-id/md-name-CENTRALNAS:RAID1 /srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/6335188a-59e4-439b-a6fb-8ba0573d4b0d /srv/dev-disk-by-uuid-6335188a-59e4-439b-a6fb-8ba0573d4b0d ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/e37e08df-04eb-402b-a8ff-6015956b49a3 /srv/dev-disk-by-uuid-e37e08df-04eb-402b-a8ff-6015956b49a3 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/Daten /export/Daten none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/Backup /export/Backup none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/Downloads /export/Downloads none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/Webspace /export/Webspace none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/TFTPBoot /export/TFTPBoot none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/Deployment /export/Deployment none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/ISO /export/ISO none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/FTP /export/FTP none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/KODISources /export/KODISources none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/Builds/ /export/Builds none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/RWShare/ /export/RWShare none bind,nofail 0 0
/srv/dev-disk-by-id-md-name-CENTRALNAS-RAID1/LatestDownload/ /export/LatestDownload none bind,nofail 0 0
/RootFS-Storage/ /export/RootFS-Storage none bind,nofail 0 0
/srv/dev-disk-by-uuid-6335188a-59e4-439b-a6fb-8ba0573d4b0d/Multimedia/ /export/Multimedia none bind,nofail 0 0
/srv/dev-disk-by-uuid-6335188a-59e4-439b-a6fb-8ba0573d4b0d/Fun/ /export/Fun none bind,nofail 0 0
# <<< [openmediavault]
No output on shell - needs to be canceled after a while like a hanging process
Can you retry with sudo omv-rpc -u admin 'FileSystemMgmt' 'getList' '{"start":0,"limit":-1}' | jq
otherwise it can not connect to the daemon and times out.
Can you retry with sudo omv-rpc -u admin 'FileSystemMgmt' 'getList' '{"start":0,"limit":-1}' | jq
otherwise it can not connect to the daemon and times out.
i tried both and i agree it seems it is a connection problem
sudo makes the difference:
If it does not work with sudo check the status of the omv-engind: systemctl status openmediavault-engined.service
Running this as prdinary user has this problem:
getcwd("/home/pi", 4096) = 9
newfstatat(AT_FDCWD, "/home/pi/./openmediavault/baseexception.inc", 0x7fd50b1f18, AT_SYMLINK_NOFOLLOW) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/php/openmediavault/baseexception.inc", {st_mode=S_IFREG|0644, st_size=1557, ...}, AT_SYMLINK_NOFOLLOW) = 0
openat(AT_FDCWD, "/usr/share/php/openmediavault/baseexception.inc", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=1557, ...}) = 0
read(4, "<?php\n/**\n * This file is part o"..., 1557) = 1557
close(4) = 0
close(3) = 0
write(2, "{\"response\":null,\"error\":{\"code\""..., 351{"response":null,"error":{"code":0,"message":"Failed to connect to socket: Permission denied","trace":"OMV\\Rpc\\Exception: Failed to connect to socket: Permission denied in \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc:141\nStack trace:\n#0 \/usr\/sbin\/omv-rpc(107): OMV\\Rpc\\Rpc::call('FileSystemMgmt', 'getList', Array, Array, 2)\n#1 {main}"}}root should be allowed to acces the socket.
Alles anzeigensudo makes the difference:
If it does not work with sudo check the status of the omv-engind: systemctl status openmediavault-engined.service
Running this as prdinary user has this problem:
PHPgetcwd("/home/pi", 4096) = 9 newfstatat(AT_FDCWD, "/home/pi/./openmediavault/baseexception.inc", 0x7fd50b1f18, AT_SYMLINK_NOFOLLOW) = -1 ENOENT (No such file or directory) newfstatat(AT_FDCWD, "/usr/share/php/openmediavault/baseexception.inc", {st_mode=S_IFREG|0644, st_size=1557, ...}, AT_SYMLINK_NOFOLLOW) = 0 openat(AT_FDCWD, "/usr/share/php/openmediavault/baseexception.inc", O_RDONLY) = 4 fstat(4, {st_mode=S_IFREG|0644, st_size=1557, ...}) = 0 read(4, "<?php\n/**\n * This file is part o"..., 1557) = 1557 close(4) = 0 close(3) = 0 write(2, "{\"response\":null,\"error\":{\"code\""..., 351{"response":null,"error":{"code":0,"message":"Failed to connect to socket: Permission denied","trace":"OMV\\Rpc\\Exception: Failed to connect to socket: Permission denied in \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc:141\nStack trace:\n#0 \/usr\/sbin\/omv-rpc(107): OMV\\Rpc\\Rpc::call('FileSystemMgmt', 'getList', Array, Array, 2)\n#1 {main}"}}root should be allowed to acces the socket.
Service is up and running and reacts to other requests but on the end there is a hint - broken pipe ...
Mai 12 16:31:34 CENTRALNAS omv-engined[18339]:
Mai 12 16:32:44 CENTRALNAS omv-engined[19125]: Failed to write to socket: Broken pipe
Mai 12 16:32:44 CENTRALNAS omv-engined[19125]:
Mai 12 16:33:54 CENTRALNAS omv-engined[20025]: Failed to write to socket: Broken pipe
Mai 12 16:33:54 CENTRALNAS omv-engined[20025]:
Mai 12 16:39:55 CENTRALNAS systemd[1]: openmediavault-engined.service: Supervising process 17924 which is not our child. We'll most likely not notice when it exits.
Mai 12 16:39:56 CENTRALNAS systemd[1]: openmediavault-engined.service: Supervising process 17924 which is not our child. We'll most likely not notice when it exits.
Mai 12 16:39:58 CENTRALNAS systemd[1]: openmediavault-engined.service: Supervising process 17924 which is not our child. We'll most likely not notice when it exits.
Mai 12 16:39:58 CENTRALNAS systemd[1]: openmediavault-engined.service: Supervising process 17924 which is not our child. We'll most likely not notice when it exits.
Mai 12 16:40:36 CENTRALNAS systemd[1]: openmediavault-engined.service: Supervising process 17924 which is not our child. We'll most likely not notice when it exits.
stop openmediavault-engind sudo systemctl stop openmediavault-engined
start the engind in debug mode in forground sudo omv-engind -df
tell us what you see
same here....
aufter upgrade to v6 my file system tab is showing nothing.
also my plugin tag is emty.
i always got error
"500 - Internal Server Error
Invalid RPC response. Please check the syslog for more information.a few seconds ago
additional my plugins are all missing.
i had a lot of different settings in combination with my second synology NAS.
I think it would be better to do a fresh install of omv 6.
is there a way to do so with the gui or via command line?
i dont want to take the nas and plug an monitor...
thank u in advanced.
Kind regards...
Check the syslog as the message tells you. After that one can advice.
stop openmediavault-engind sudo systemctl stop openmediavault-engined
start the engind in debug mode in forground sudo omv-engind -df
tell us what you see
omv-engined[67157]:
omv-engined[67462]: Child process forked (pid=67462)
omv-engined[67462]:
omv-engined[67463]: Child process forked (pid=67463)
omv-engined[67463]:
omv-engined[67464]: Child process forked (pid=67464)
omv-engined[67464]:
omv-engined[67462]: Executing RPC (service=FileSystemMgmt, method=getListBg, params={"start":0,"limit":25,"sortdir":"asc","sortfield":"canonicaldevicefile"}, context={"username":"admin","role":1}) ...
omv-engined[67462]:
omv-engined[67463]: Executing RPC (service=System, method=getInformation, params=null, context={"username":"admin","role":1}) ...
omv-engined[67463]:
omv-engined[67462]: RPC response (service=FileSystemMgmt, method=getListBg): {"response":"\/tmp\/bgstatus14JT2m","error":null}
omv-engined[67462]:
omv-engined[67464]: Executing RPC (service=FileSystemMgmt, method=getListBg, params={"start":0,"limit":25,"sortdir":"asc","sortfield":"canonicaldevicefile"}, context={"username":"admin","role":1}) ...
omv-engined[67464]:
omv-engined[67464]: RPC response (service=FileSystemMgmt, method=getListBg): {"response":"\/tmp\/bgstatusALeEQv","error":null}
omv-engined[67464]:
omv-engined[67491]: Child process forked (pid=67491)
omv-engined[67491]:
omv-engined[67491]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatus14JT2m","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[67491]:
omv-engined[67463]: RPC response (service=System, method=getInformation): {"response":{"ts":1652452790,"time":"Fr 13 Mai 2022 16:39:50 CEST","hostname":"CENTRALNAS.HEIMNETZ","version":"6.0.27-1 (Shaitan)","cpuModelName":"AMD FX-8800P Radeon R7, 12 Compute Cores 4C+8G","cpuUsage":88.02992518703242,"memTotal":"8236032000","memFree":"554881024","memUsed":"7472238592","memAvailable":"0","memUtilization":"1.00000","kernel":"Linux 5.16.0-0.bpo.4-amd64","uptime":18272.92,"loadAverage":{"1min":6.15,"5min":2.85,"15min":1.52},"configDirty":false,"rebootRequired":false,"pkgUpdatesAvailable":false},"error":null}
omv-engined[67463]:
omv-engined[67496]: Child process forked (pid=67496)
omv-engined[67496]:
omv-engined[67496]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatusALeEQv","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[67496]:
omv-engined[67491]: RPC response (service=Exec, method=getOutput): {"response":{"filename":"\/tmp\/bgstatus14JT2m","pos":0,"output":"","pendingOutput":false,"running":true},"error":null}
omv-engined[67491]:
omv-engined[67496]: RPC response (service=Exec, method=getOutput): {"response":{"filename":"\/tmp\/bgstatusALeEQv","pos":0,"output":"","pendingOutput":false,"running":true},"error":null}
omv-engined[67496]:
omv-engined[67521]: Child process forked (pid=67521)
omv-engined[67521]:
omv-engined[67521]: Executing RPC (service=FileSystemMgmt, method=getListBg, params={"start":0,"limit":25,"sortdir":"asc","sortfield":"canonicaldevicefile"}, context={"username":"admin","role":1}) ...
omv-engined[67521]:
omv-engined[67521]: RPC response (service=FileSystemMgmt, method=getListBg): {"response":"\/tmp\/bgstatuslBrQgO","error":null}
omv-engined[67521]:
omv-engined[67558]: Child process forked (pid=67558)
omv-engined[67558]:
omv-engined[67593]: Child process forked (pid=67593)
omv-engined[67593]:
omv-engined[67593]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatusALeEQv","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[67593]:
omv-engined[67593]: RPC response (service=Exec, method=getOutput): {"response":{"filename":"\/tmp\/bgstatusALeEQv","pos":0,"output":"","pendingOutput":false,"running":true},"error":null}
omv-engined[67593]:
omv-engined[67558]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatus14JT2m","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[67558]:
omv-engined[67558]: RPC response (service=Exec, method=getOutput): {"response":{"filename":"\/tmp\/bgstatus14JT2m","pos":0,"output":"","pendingOutput":false,"running":true},"error":null}
omv-engined[67558]:
omv-engined[67608]: Child process forked (pid=67608)
omv-engined[67608]:
omv-engined[67623]: Child process forked (pid=67623)
omv-engined[67623]:
omv-engined[67608]: Executing RPC (service=System, method=getInformation, params=null, context={"username":"admin","role":1}) ...
omv-engined[67608]:
omv-engined[67623]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatuslBrQgO","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[67623]:
omv-engined[67623]: RPC response (service=Exec, method=getOutput): {"response":{"filename":"\/tmp\/bgstatuslBrQgO","pos":0,"output":"","pendingOutput":false,"running":true},"error":null}
omv-engined[67623]:
Do you get any errors like before?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!