We only create a new FCV document on a clean startup (the server has no non-local databases).

However, it is possible that on an unclean shutdown (and no journaling), the creation of the admin.system.version collection makes it into the WT checkpoint but not the insertion of the FCV document. This means that on startup recovery, we never create the missing FCV document and end up fasserting instead.

I think we should modify wt_nojournal_fsync.js to ensure that the FCV document makes it into the checkpoint before sending the kill -9.