My computer crashes because it can't start nmbd

This my problem for about the past month: I turn on my computer, and them after about 10 minutes, the system suddenly shuts down. In the messages that appear while the computer is shutting down, the last one is “Couldn’t start nmbd”, as if that were the problem.

I’ve been assuming that IS the problem, since all the other shutdown messages are [OK]. The thing is, I don’t even turn smb.service on (through systemd). There is something in my smb.conf that is misconfigures, so “systemctl start nmb.service” returns an error message and nmbd doesn’t get started.

For that reason I have put Samba aside for a while, and never attempt to start it up. BUt something in the system seems to be starting it up, but when nmbd doesn’t start, it brings down the whole system in an unholy crash.

What could be the answer to this conundrum? The time between sign-on and system crash is about 10 minutes.

Do you have anything mounted with cifs/samba in /etc/fstab? If so, the _netdev option won’t delay startup and the “nofail” option won’t keep Fedora from booting over failure to mount it.

May want to look at:
systemctl status nmb.service smb.service

To look at the prior boots logs for nmb & smb services
journalctl -b -1 -u nmb.service -u smb.service

or just look at the full log assuming you want to start where the computer shutdown
journalctl -b -1 -r


Any possibility the shutdown is not related to nmb? Like a thermal shutdown, or oom?

1 Like