Hi - thanks very much for this solution - I have had two systems - one running on a pi 3 and one off a pi 2. I’ve upgraded from a pi 2 to a 3B+, while at the same time upgrading to the latest volumio image 2.389 from 2.323. Mounting manually and adding the
vers=1.0,sec=ntlm,cache=none
option worked for me.
Worth mentioning that after a little more searching I found a discussion on the volumio github https://github.com/volumio/Volumio2/issues/1524 talking specifically about the 2.389 update. So bottom line - it might not be (just) the pi 3B problem, but instead a bug in 2.389.