2018-01-17 18:46 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001685openmediavaultBugpublic2017-03-20 08:15
ReporterDavid B 
Assigned Tovotdev 
StatusclosedResolutionno change required 
PlatformOpenMediaVaultOS3.0.64OS VersionErasmus
Product Version 
Target VersionFixed in Version 
Summary0001685: "File Systems" and "S.M.A.R.T." tabs not Working
DescriptionAs of OMV 3.0.64, the "File Systems" and "S.M.A.R.T." tabs are not working.

Whenever I try to visit the "File Systems" tab, I get an error message after about a minute stating that a communication error occurred. For whatever reason, this also results in my Samba server not working, but it is possible that other things are not working as well. Interestingly, the OMV "Dashboard" tab lists CPU usage at a full 100%. The only way to get everything working again is to crash the server and start it again, as it seems that attempting a traditional reboot fails.

Something similar happens with the "S.M.A.R.T" tab. Whenever I try to load a list of the disks, I get a communication error after several minutes. I do not experience issues with Samba whenever I try this, but once again, CPU usage spikes to a contstant 100%, and the only way to stop it is to crash the server and start again because, as was the case with the "File Systems" tab, the server hangs on traditional reboot and never comes back up.
Steps To ReproduceRecreating the bug is very simple: visit the tab and let the communication error appear.
Additional InformationMy OMV server runs on a Lenovo Q190 small form-factor PC. The drive that I share is a USB3 external HDD that is connected to the PC via one of the two available USB3 ports.
TagsNo tags attached.
Product build
Attached Files




votdev (administrator)

I am not able to reproduce this issue on my test machines. Please try to find out what is going wrong on your system. At first please check the /var/log/syslog and /var/log/nginx/openmediavault-webgui_error.log.
Second please stop the OMV engined and restart it in debug mode:

$ monit stop omv-engined
$ omv-engined -d -f

Then visit the SMART and file system tabs. If there happens an error you should see it in the CLI output.


David B (reporter)

I am not getting any error messages when running in debug mode, nor do I have any errors in either of the logs that indicate what is going on here. I wonder if perhaps a fresh OMV installation would resolve the problem.


David B (reporter)

A fresh OMV installation seems to have resolved the issue. It seems that while the issue may not be present in the newest version of OMV, it carries over from older versions when you to a traditional update.


David B (reporter)

Is that possible? (Sorry about the separate post. I clicked "Add Note" too early and forgot to include this extra question.)

-Issue History
Date Modified Username Field Change
2017-02-26 18:36 David B New Issue
2017-02-26 18:36 David B Status new => assigned
2017-02-26 18:36 David B Assigned To => votdev
2017-02-27 08:54 votdev Note Added: 0004596
2017-03-04 19:14 David B Note Added: 0004626
2017-03-15 00:23 David B Note Added: 0004657
2017-03-15 00:24 David B Note Added: 0004658
2017-03-20 08:15 votdev Status assigned => closed
2017-03-20 08:15 votdev Resolution open => no change required
+Issue History