This is all assuming it’s a spinning disk and not an SSD, so ignore me if that’s the case:
Given SAS drives are usually used in data centre storage array applications and 3TB disks have been kinda small for that use case for a fair while, there’s a fairly high chance it was in heavy use for a good number of years. I’d bet it’s probably well on its way to being a paperweight regardless of your connectivity situation.
If you do get it hooked up, don’t store anything on it you wouldn’t be okay losing.
So
300×1024×1024= 314,572,800kb
Assuming something like 200 bytes per log line
x5 = 1,572,864,000 logs
Assuming this is your standard console port with a 60fps frame rate lock:
÷60fps ÷ 60 seconds ÷ 60 minutes ÷ 24h = 303.407… days
You would need to play for nearly a year solid to generate that many logs at a rate of one per frame.
Given that’s probably not what’s happened, this is a particularly impressive rate of erroring