I'm going to buy and mine some of these again, I lost all my ORB a while back due to a computer breakdown, and bailed on Crypto, but I got the bug back again now, and am pleasantly surprised how strong ORB has stayed.....
Did your hard drive fail or was it some other type of issue with the system? If the hard drive is still functional even with a corrupt OS you may still have access to that wallet.dat file.
If the hard drive controller failed you can replace it with a controller from the same model and get things back also
Many modern drives store servo data in an EEPROM on the circuit board, so you'd have to swap that (tiny) chip too. That's a job which will require more than a screwdriver with a torx bit. Also, if it's SSD then things become infinitely more complex. I do agree that it's worth some effort to recover the wallet, especially for 5k ORB.
In the early days of ORB scrypt PoW mining I "lost" 2000+ ORB due to a silently corrupted wallet, but I didn't know it at the time; I didn't find out until a year or two later when I ran "checkwallet" and recovered the funds. By that time altcoins were on the decline and everything had lost a lot of value - if I had been able to sell them around the time they were mined, as I was doing at the time, I would have made at least an extra 2 BTC. They were virtually worthless by the time I recovered them.
I'm sure anyone who's been around for a while has bad luck stories like this.
edit: I remember now what likely happened. When a client builds the transaction, it marks each output as spent in the wallet, but if the transaction fails (eg it becomes too complex), the client doesn't roll back those changes to the wallet. So even though the transaction was never sent, the coins are considered spent, and do not show as available. It's not until checkwallet/repairwallet audits the wallet that it correctly picks up the coins as unspent. This issue wasn't specific to ORB as many alts used the same broad code base.
I now do a regular 'checkwallet' for all coin clients, and the occasional restart with the -rescan commandline switch.
