Cannot start replica set member or run repair

Ops and Admin Replication
1

After getting below errors I remove server from replication But still cannot start or run repair

2020-04-30T09:55:27.777+0100 I  SHARDING [repl-writer-worker-1] Marking collection service-cases.case as collection version: <unsharded>
2020-04-30T09:55:27.781+0100 E  STORAGE  [repl-writer-worker-8] WiredTiger error (-31802) [1588236927:781053][4724:0x7fb2815c7700],
 file:service.45user.45accounts/index-58--9181491801672360292.wt, WT_SESSION.open_cursor: __desc_read, 
351: service.45user.45accounts/index-58--9181491801672360292.wt does not appear to be a WiredTiger file: WT_ERROR: non-specific WiredTiger error 
Raw: [1588236927:781053][4724:0x7fb2815c7700], file:service.45user.45accounts/index-58--9181491801672360292.wt, WT_SESSION.open_cursor: __desc_read, 
351: service.45user.45accounts/index-58--9181491801672360292.wt does not appear to be a WiredTiger file: WT_ERROR: non-specific WiredTiger error
2020-04-30T09:55:27.781+0100 E  STORAGE  [repl-writer-worker-8] Failed to open a WiredTiger cursor. Reason: UnknownError: -31802: 
WT_ERROR: non-specific WiredTiger error, uri: table:service.45user.45accounts/index-58--9181491801672360292, config: overwrite=false
2020-04-30T09:55:27.781+0100 E  STORAGE  [repl-writer-worker-8] This may be due to data corruption. Please read the documentation 
for starting MongoDB with --repair here: http://dochub.mongodb.org/core/repair
2020-04-30T09:55:27.781+0100 F  -        [repl-writer-worker-8] Fatal Assertion 50882 at src/mongo/db/storage/wiredtiger/wiredtiger_session_cache.cpp 101
2020-04-30T09:55:27.781+0100 F  -        [repl-writer-worker-8] 


2020-04-30T15:40:32.062+0100 F  STORAGE  [initandlisten] An incomplete repair has been detected! This is likely becausrepair operation unexpectedly failed before completing. MongoDB will not start up again without --repair.
2020-04-30T15:40:32.062+0100 F  -        [initandlisten] Fatal Assertion 50922 at src/mongo/db/storage/storage_engine_.cpp 85
2020-04-30T15:40:32.062+0100 F  -        [initandlisten]

***aborting after fassert() failure

can you please assist

2

Hi @lital_yeheskel,

If you’ve already run repair. You’ll probably have to restore from backup. I assume this is not a replica set?

You’ll want to check your storage for errors before this. As this could be disk level corruption.

3

repair is not working and monodb cannot be started.
please advice

4

Check your storage for errors and recover from a backup.

5

If you hadn’t removed it you could have cleared the data directory and synchronized.

As you have removed it. Remove the files in the data directory, start it and add it as you would a new member.

6

Thanks for your fast good info.
It was an encryption issue (could say storage issue) that we didnt managed to recover.
due to that i didn’t managed to repair mongo or start the service.
eventually i needed to reinstall mongo and add the node again.