After Seamonkey browser crash, fsck_ffs is taking forever

[Thomas Mueller]

Running FreeBSD 9.2-STABLE, my (Mozilla) Seamonkey web browser got bogged down on the zinio.com site, linked from an email.  Now, booting from a USB stick, either FreeBSD 9.2-STABLE amd64 or NetBSD 6.1-STABLE i386, fsck_ffs just takes a long time, making me wonder if it's caught in a loop.

device fault writing fsbn 742111051  (or other number, and some of the other message are for reading instead of writing) : this was with NetBSD.  

But I see some possible slow progress as some lines show a fix applied.

Now it's been going 23 hours straight from NetBSD 6.1-STABLE i386 USB stick.  Now I am running Linux from System Rescue CD 3.6.0 installed to USB stick, on other computer, and am using Midori web browser and webmail, hope this will be sent plain-text and not multipart/alternative but not sure if I can control that.

This is the partition mounted as /home, where most of the user data is, and I was able to copy (rsync) out most of the user data to a partition on a Western Digital MyBook 3 TB USB 3.0 drive.

Main hard drive is Western Digital Caviar Green 3 TB.

How long should I let this continue?  I could copy out as much more useful data as I can, and then reformat (newfs) and then copy back, or possibly use the USB 3.0 hard drive partition as /home (but then I can't use it on any other computer).

I intend, after fsck_ffs -y from NetBSD terminates, or I terminate it with Ctrl-C, to open the computer and look for dust or loose connection.  I think I will do the latter this evening (like about 16 hours from now).

This hard drive was bought late May 2011, now barely inside the three-year warranty.

Maybe I should buy another hard drive just in case, Western Digital, Green or maybe Red or Black?

I would also very much like to know how to block annoyance web domains such as *.doubleclick.net .

Tom