🚀 go-pugleaf

There are two ways to remedy this:

1) if you can find the stand-alone program rabads (or rqbads for q-bus
machines), boot it, and select 'init' on the drives affected; it will
scan the disk and do some bad block replacement.  Write down the block
numbers, convert to filesystem block #'s, and after rebooting use
ncheck,icheck,dcheck to find what file/directory contains those blocks;
those files/directories should be considered corrupt.

2) If you can't find rabads/rqbads, write a quick program to write
zeroes to the affected block; re-writing the damaged sectors will clear
the forced-error bit.  Then figure out the files/directories affected by
the problem and recreate them, as they are certainly corrupt.

BEWARE!  I am not speaking in any official capacity here; proceed at
your own risk.  You take full responsibility for any damages incurred.
--
John Kohl <jtkohl@ATHENA.MIT.EDU> or <jtkohl@MIT.EDU>
Digital Equipment Corporation/Project Athena
(The above opinions are MINE.  Don't put my words in somebody else's mouth!)