I believe the solution I found online was to delete the lockfile, however Railway doesn't offer support for S/FTP into a volume or a service so that's not an option.
Thing is this started happening right after the downtime was over so I'm assuming it's because my service went offline unexpectedly and now the data is corrupted somehow?
Crashes upon redeploy, thing is I destroyed the MongoDB service (without the volume) and reattached the volume to a new service and the error still occurs