When starting up a mongod with the shard server role, we check for the existence of a shard identity document on disk. If we cannot find it, we log:

 "Started with --shardsvr, but no shardIdentity document was found on disk. This most likely means this server has not yet been added to a sharded cluster"

Now that a config server will always have the shard role, it's not accurate to say "started with --shardsvr." We should reword the log to be less specific to the particular command line option and instead say something like "Started with shard role, but ..." and exclude the "This most likely means" sentence on a config server, since the config server will insert its own shard identity document on first step up to primary.