WMS 2.0 corrupted MongoDB

We were having issues with our WMS 2.0 server so we restored the WMS 2.0 server from a previous backup that we thought was working but now we can’t seem to start the MongoDB service which in turn won’t start the Tomcat service as the Tomcat service is dependent upon the MongoDB service running. I’m looking at the logs in MongoDB and it seems to be that the database is corrupted somehow. If you look below, the database looked like it was trying to repair itself, but it failed at some point. As you see from the 2nd group of text. Can anyone tell me what version of MongoDB(I believe MongoDB is 4.2.1) belong on a WMS 2.0 environment please? And, could I just try to repair the MongoDB myself with the –-repair option?

2022-04-28T08:55:41.476-0400 I  STORAGE  [initandlisten] WiredTiger message [1651150541:476770][7032:140704155785680], txn-recover: Recovering log 63686 through 63690

2022-04-28T08:55:42.004-0400 E  STORAGE  [initandlisten] WiredTiger error (0) [1651150542:3864][7032:140704155785680], file:collection-6-6923312543607838408.wt, WT_CURSOR.insert: __wt_block_read_off, 274: collection-6-6923312543607838408.wt: read checksum error for 16384B block at offset 9970098176: calculated block checksum  doesn't match expected checksum Raw: [1651150542:3864][7032:140704155785680], file:collection-6-6923312543607838408.wt, WT_CURSOR.insert: __wt_block_read_off, 274: collection-6-6923312543607838408.wt: read checksum error for 16384B block at offset 9970098176: calculated block checksum  doesn't match expected checksum