Originally Posted By: TigerJimmy
I'm 11.5 hours into a manual fsck on a 60GB drive. Quite a few duplicate/bad blocks so far. Dead or dying drive, right?

Dunno. But as usual, a serial port log will tell the true story. No point in even speculating without first looking there.

11.5 hours is too long. Something else is wrong. If you are doing this from (J)emplode, then the app may simply have gotten confused.

Use the serial port and control^C, and kick off the fsck by hand from the command line.

-ml