@newtperc -- It isn't the zeros that means this isn't the solution, it is that the last command on that line is "grep fsck" which means that the only command mentioning "fsck" was the command searching for "fsck" In other words, "fsck" itself isn't running and isn't causing the problem. I've had the error a couple times, and after panicking over potentially lost files, it was mostly resolved by a reboot. (I use sleep for weeks at a time, and normally do not reboot unless forced)