Analyze output of midclt call datastore.query sharing.cifs_share | jq
Identify entries that do not have base64(?) encoded string in cifs_share_acl - items that look like “S-1-1-0:ALLOWED/0x0/FULL” are bad now
In Shares UI, edit Share ACL on the items. Just click “Save” on each of them.
Analyze output of midclt call datastore.query sharing.cifs_share | jq and ensure that all entries have encoded string instead of “S-1-1-0:ALLOWED/0x0/FULL” format
Thank you @snorpleblar This caught me out - upgraded to 25.10.1 a few days back (my config goes back years). All working fine (mostly; CPU graph issues are back) - made a minor SMB change, was not expecting it not to start again. Thank goodness for this post, to decrypt what was wrong, and what I had to do - I would never had got there on my own. I am getting more used to the shell to fix stuff - but this felt avoidable.