Okay, well after 5 billion password checks, it found it. attack_batch stopped when it found the p/w.
Worked about 15000+ PMKs a second, or 1.3+ billion a day. Busted open an ATT### in a few days. Got 37.94% into my 10 billion database. Blobspace/essid only got to 126GB, not bad. Passwords were sequential 0 to 9.9 bill with padding, but somehow eval shows it only calculated to 3.8 bill until it found the p/w in the 5 bill range.
Oh well, job done.