After performing an in-place upgrade from 2015 SP1 to 2018 SP1, the server's NSS32 pool/volume does not mount.
The pool is listed as unmounted NSSMU, but attempts to mount it display a "pool not active" message.
The volume is not listed
The NSS documentation for OES 2018 has a lot to say about virtually everything BUT the impact of upgrading to 2018 on NSS32 pools .
I have two more OES 2015 servers with NSS32 pools and an OES 2015 server with an NSS64 pool.
I suspect that I would not have this issue with the NSS64 pool, but I'm not will to risk it until until this issue is resolved.
I have a support ticket (101236485541) but my support is 12x5, so I have to wait until Monday for their response.
Any constructive thoughts are welcome, especially if they're germane to this problem.