Problems with signatures and SMB

Good afternoon everyone.

Since the last update I did on OMV8, I haven't been able to update again; it kept giving me a signature error! I think I managed to solve it, I'm waiting for another update to verify that everything is ok.

Another problem I had with this update was SMB. It indicates it's working, but when I try to access the folders through Windows, nothing appears in Explorer. Anyone have any help?

My God, such a stupid problem and so easy to solve. When I got the answer I immediately thought, what big ears I have...!!!

OMV changed the validation rules in an update, not because Samba "suddenly" stopped supporting +.

In your case, the shared folder had the logical name +Operadores.

This name was probably accepted when the configuration was created in a previous version. Later, after updating/migrating to a more recent version of OMV8, the backend started validating this field more restrictively. When Samba was regenerated, OMV read the Shared Folder, via +Operadores, and aborted with:

The value '+Operadores' is not a valid share name.

That is, the problem appeared when OMV needed to regenerate the smb.conf. Until that moment, the old Samba file could continue to function, even containing a configuration that the current version of OMV no longer accepted.

The OMV documentation confirms that Shared Folders are objects of the internal database and that services like Samba use these references to generate their respective configurations.

OpenMediaVault That's also why it seemed strange: the smbd service could continue "running," but when OMV tried to apply/recreate the configuration, the validation failed before writing the 52 shares.

Problem solved.