Dear maintainers,
I would appreciate a version update for the smartmontools, because of the missing "farm" attribute.
proto_typ - in the meantime - please let us know if you found a work around to get the "farm" values from the disks (without using them in another system where the latest smartmontools suite are installed
)
Sorry for the late reply. Only the mentioned method from the last post. Didn't want to break anything, so I did not check my drives yet.
OMV already displays the Power on hours information. You can find the information in the SMART section, click a device and press the details button. I don't know if these are the values that can be resetted. But it's definitively not fetched with the -l farm command line argument.
There was another article on this today. It only concerns the Seagate hard drives. smartctl can read the SMART values. There are also FARM values. IMHO these are not well documented. However, they also provide a ‘Power on Hour’ for the hard drives.
These vendor-specific FARM (Field Access Reliability Metrics) values were introduced in smartctl almost 2 years ago:
Änderungssatz 5462 – smartmontools
And they can differ from the normal SMART, as seen in the news articles.
So if it is not possible to upgrade the version I have to find another way, too check my drives. Would be more convenient to leave them in the case.
Yesterday I have read some shady things about Seagate drives:
tldr: Used hard drives were sold as new and the SMART values were reset beforehand. Some hard drives have been running for several hundred hours. So-called FARM values were not reset. FARM values can also be read out via smartmontools. Can be read out with the following code using smartmontools:
smartctl -l farm /dev/sdX | grep ‘Power on Hours’I have tried to check the SMART and FARM values, but I can't get the FARM values, since smartmontools did introduce them in version 7.4. We are still on 7.3.
Is there any way to get smartmontools 7.4.x installed to check my HDDs?
The update destroyed the web interface. Now I get the error Failed to connect to socket: No such file or directory after logging into the web interface.
EDIT: Just a typo - change a ; to , in line 24 at the end. Then restarted engined and it is working again.
Go to line 24 in /usr/share/openmediavault/engined/inc/90autoshutdown.inc.
Change this
"regex" => "/^(\d{4}-\d{2}-\d{2}.\d{2}:\d{2}:\d{2}).+?autoshutdown\[\d+\]: (?|(\w+)$|root: (\S+): '(\S+): (.*)'$)/";
to this
"regex" => "/^(\d{4}-\d{2}-\d{2}.\d{2}:\d{2}:\d{2}).+?autoshutdown\[\d+\]: (?|(\w+)$|root: (\S+): '(\S+): (.*)'$)/",
Restart via systemctl restart openmediavault-engined.service
Should be changed here too:
______________________________
Yep, same on my end. Did the update via Web interface and now I stuck on the login screen.
Input: systemctl status openmediavault-engined.service
Output:
openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request
Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2025-01-13 00:34:07 CET; 38s ago
Duration: 37ms
Process: 21225 ExecStart=/usr/sbin/omv-engined (code=exited, status=0/SUCCESS)
Main PID: 21227 (code=exited, status=255/EXCEPTION)
CPU: 65ms
Jan 13 00:34:07 serverA systemd[1]: Starting openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request...
Jan 13 00:34:07 serverA systemd[1]: openmediavault-engined.service: Supervising process 21227 which is not our child. We'll most likely not notice when it exits.
Jan 13 00:34:07 serverA systemd[1]: Started openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request.
Jan 13 00:34:07 serverA systemd[1]: openmediavault-engined.service: Main process exited, code=exited, status=255/EXCEPTION
Jan 13 00:34:07 serverA systemd[1]: openmediavault-engined.service: Failed with result 'exit-code'.Input: omv-engined -d -f
Output:
PHP Parse error: syntax error, unexpected token ";", expecting "]" in /usr/share/openmediavault/engined/inc/90autoshutdown.inc on line 24The update process of "autoshutdown" left me on the Web interface and saying "Lost connection".
Display MoreThe last command above will only show the line containing pam_tally or pam_tally2 (most probably pam_tally2). We now know how many lines to replace. Here, I've been lazy, because I suspected that those lines were in the openmediavault related files (I checked using cat openmediavault* | grep pam_faillock) and it was the case. Then you just have to use nano or other on the openmediavault files and to replace each instance of pam_tally2.so by pam_faillock.so.
After that, you can rerun sudo apt --fix-broken install (it should not fail). Then you rerun sudo apt full-upgrade.
I hope it can help…
Happy new year.
This was one last key information after upgrading from OMV 5.x to 6.x. Something went wrong in the process of upgrading and I couldn't log into the webGUI due to the "Pam"-issue. Thanks!
Hey,
ich habe ein Problem mit dem NUT-Plugin.
OMV-Version: 4.1.14-1
NUT-Plugin: openmediavault-nut 4.0.13-1
Seit dem Upgrade auf OMV 4 bekomme ich jeden Tag folgende Mail:
Does not exist Service nut-monitor
Date: Sat, 23 Mar 2019 08:00:58
Action: restart
Host: elvegust
Description: process is not running
Your faithful employee,
MonitKurz darauf startet der Prozess dann doch und ich erhalte folgende Nachricht:
Exists Service nut-monitor
Date: Sat, 23 Mar 2019 08:01:28
Action: alert
Host: elvegust
Description: process is running with pid 4960
Your faithful employee,
Monit
Hatte schon probiert das Plugin später zu starten, aber leider ohne Erfolg. Vielleicht habe ich nicht die richtige Stelle gefunden (/etc/rc0.d).
Lief unter OMV 3 ohne diese Benachrichtigungen. Server läuft nicht 24/7 und startet jeden Morgen neu. Bekomme also jeden Tag diese beiden Benachrichtigungen.
VIelleicht hat von euch jemand eine Idee.
Edit:
Konnte die Benachrichtigungen stoppen.
Habe in der monitrc den Delay auf 300 gesetzt. D. h. bei jedem Neustart müssen erst 5 Minuten vergehen, bis der Monit sich meldet. Ist für mich ausreichend.
Pfad: /etc/monit/monitrc
Anpassung der Starteigenschaft:
set daemon 30 with start delay 300