We have reports of some new SSDs models which only support 4K sector reads. We hit this issue first in our integration with Google Compute Engine, and have read reports of new firmware to existing drives — so if you buy new drives of the same exact model, you may get drives that only support 4K sectors.
With a 4K device that does not support 512B reads, the server will be unable to read from the device after startup, and the server will terminate.
To work-around immediately, please set the disable-odirect true statement in the storage stanza. Although this turns on the Linux page cache - increasing latency distributions - you will be able to start and operate your server.
We have completed a permanent fix which will be in our next maintenance release. Please contact support if you run into this problem so we are certain to test against your drive model.