I don't understand what the problem is.
This is perfectly expected behaviour. -m 14800 is a hard/slow hash type.
Everything that you just described seems to be expected.
The only way to fix it is to:
1. use better GPUs and a higher amount of GPUs
2. do not try to attack a slow hash by brute-forcing it (brute-force/mask attack should always be your last and desperate option... this is true for all hash types and especially for slow hashes)
Maybe I just didn't understand what you are trying to say... but if your only "problem" is that it is running with "just" a few H/s than this is not a problem at all, this is just a proof how slow/hard this hash type is.
This is perfectly expected behaviour. -m 14800 is a hard/slow hash type.
Everything that you just described seems to be expected.
The only way to fix it is to:
1. use better GPUs and a higher amount of GPUs
2. do not try to attack a slow hash by brute-forcing it (brute-force/mask attack should always be your last and desperate option... this is true for all hash types and especially for slow hashes)
Maybe I just didn't understand what you are trying to say... but if your only "problem" is that it is running with "just" a few H/s than this is not a problem at all, this is just a proof how slow/hard this hash type is.