Relates to Failed shard recovery after hard shutdown.
It sounds like you have other lurking corruptions after your power outage. Unfortunately with zero replicas and storage that isn't resilient to powerloss there's no way to get out of this situation without losing yet more data. If it were me, I would start again.
Setting index.shard.check_on_startup: true will at least check the whole index for corruption at startup rather than waiting for a corruption to be detected during a merge. This'll take a while, and you should set it back to null afterwards otherwise that check will happen every time.
If you are using version ≥ 6.5 then the elasticsearch-shard tool will delete any corrupted segments, but as with elasticsearch-translog this entails arbitrary data loss.