My omv goes into hypernate via autoshutdown when I shutdown my windows pc. When I restarted Win was also my omv smb drive immediately mounted again, ran for years flawlessly. I think since one of the salt updates about a month ago I have to restart the server every time so I can access my OMV under Windows again.
smb drive is no longer accessible after an autoshutdown/hibernate since one of the last updates
-
- OMV 5.x
- LooR
-
-
restarting the smb daemon also helps but why is that necessary now?
-
restarting the samba service didnt work on my side.
I used
sudo service smbd stop
to stop
then
sudo service smbd start
to start but I'm getting an error
"
Job for smbd.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status smbd.service" and "journalctl -xe" for details.
"
Any ideas what may be the problem ? It started after the latest updates.
-
See "systemctl status smbd.service" and "journalctl -xe" for details.
That would be a staring point.
Try to restart smbd and then check the journal for entries
systemctl start smbd.service
journalctl -u smbd.service
-
That would be a staring point.
Try to restart smbd and then check the journal for entries
systemctl start smbd.service
journalctl -u smbd.service
journalctl returns this.
any ideas?
Isn't this common after the latest updates? we can't be the only ones effected.
"
smbd.service: Main process exited, code=dumped, status=6/ABRT
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit smbd.service has exited.
--
-- The process' exit code is 'dumped' and its exit status is 6.
raspberrypi systemd[1]: smbd.service: Failed with result 'core-dump'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit smbd.service has entered the 'failed' state with result 'core-dump'.
raspberrypi systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: A start job for unit smbd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit smbd.service has finished with a failure.
--
-- The job identifier is 1816 and the job result is failed.
raspberrypi polkitd(authority=local)[13936]: Unregistered Authentication Agent for unix-process:13931:13
raspberrypi CRON[14031]: pam_unix(cron:session): session opened for user root by (uid=0)
raspberrypi CRON[14032]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
raspberrypi CRON[14031]: pam_unix(cron:session): session closed for user root
lines 1457-1485/1485 (END)
"
-
Isn't this common after the latest updates? we can't be the only ones effected.
If this would be a common problem after 20th May, there would be many more issues on the forum.
The output is not really helpful for me.
Try to disable and enable smb in the GUI of OMV. Any error messages?
-
I tried enabling samba trough web GUI and got an error msg.
Is this useful?
"
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; omv-salt deploy run --no-color samba 2>&1' with exit code '1': raspberrypi:
"
-
Sorry, I have no idea how to find the root cause of the issue. Maybe somebody else will chime in.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!