I'm reviewing the code now… Is there a restart file with this case, or is it a fresh start?
If the latter, you may be able to turn libMesh::MeshCommunication::find_global_indices() into a no-op - just with a naked 'return;' at the top.
The goal of a partition-agnistoc node ordering is still something I'd like to achieve, but the current implementation has been the source of way too much woe. I'll revisit the discussion on the list from a few years ago and figure out what a proper path forward should be.
Is this mesh something I can get my hands on down the road for testing?