5 hours ago
I'm on an Intel MacBook Pro with AMD GPU and running hashcat v6.2.6-1259, built from source. It was eventually able to crack a real-world WPA2 hash, but instead of taking ~2 hours as estimated, it took a couple days. Hashcat would be making great progress, and then, suddenly, progress percentage would stop increasing, fans would slow down, and GPU utilization (? Hardware.Mon.#01 & #02.: Util) would drop to 0%
Even leaving hashcat alone overnight, it did not start making progress again. The abort trigger temp was not exceeded, the battery did not get low, and I prevented the MacBook from going to sleep. Eventually, I started checkpointing every 10–20%, but sometimes hashcat would stall after the request, and I'd have to quit, restore, and try again. I think it finally recovered the password at 78% from a restore point of around 60%.
The initial command I used was
I am now working on a different hash, which again has a reasonable estimated time to completion, but hashcat is again dying on me. I requested a checkpoint at 10%, and it kept going rapidly until 19.42%, but now it's stopped. ps says the process is in uninterruptible wait.
What other possibilities are there for what's going on, or where can I find additional clues? Is there something I should look for in the session log file?
Even leaving hashcat alone overnight, it did not start making progress again. The abort trigger temp was not exceeded, the battery did not get low, and I prevented the MacBook from going to sleep. Eventually, I started checkpointing every 10–20%, but sometimes hashcat would stall after the request, and I'd have to quit, restore, and try again. I think it finally recovered the password at 78% from a restore point of around 60%.
The initial command I used was
Code:
hashcat --session name -D 2,1 -d 1,2 -m 22000 hash.hc22000 -a 6 dict.txt ?mask
I am now working on a different hash, which again has a reasonable estimated time to completion, but hashcat is again dying on me. I requested a checkpoint at 10%, and it kept going rapidly until 19.42%, but now it's stopped. ps says the process is in uninterruptible wait.
What other possibilities are there for what's going on, or where can I find additional clues? Is there something I should look for in the session log file?