@Cameron_D Welcome to the Rockstor community.
Did you by chance reboot when you thought the update was done. We have has a number of folks reboot mid update; unfortunately this will likely leave the system in an indeterminate state re the package versions. We don’t yet give a good / accurate indication of if an update is ongoing.
Re:
This could be the above rebooting during update or we have had a few reports on the forum of failed samba updates from upstream. Take a look at for example:
We have a ‘pale’ search icon in the top right of the Web-UI of the forum for other instances of this.
This is again likely due to a failed or interrupted update. Mounts normally take place on boot so this is consistent with a reboot mid update or a failed package update.
These can be averted by simply refreshing the page within your browser. They come from a difference in what is cached in the browser and what is likely updated on the server end. The browser refresh forces retrieval of the newer version of Web-UI code that likely came with the update and has yet to be retrieved by the browser.
The output, as the error message suggests, of:
systemctl status smb.service
# and
journalctl -xe
should help to diagnose what’s happened here. Not also that if you were upgrading from a very old version then that may well cause other issues. But for now if you post the output, run as the root users, of the above 2 commands that may help to see whats gone wrong.
Also
yum update
may well also help in this situation, and if not then it may shed more light on the failed update.
Hope that helps.