On Nov 10, 2004, at 11:51 PM, Eduardo Horvath wrote:

> Hm.  It appears that the trap happens before the FCode is done being
> interpreted.  I wonder if it could be a tokenizer issue.

Upon further investigation, it might be hardware.  What's odd is that I 
did a full format of this new drive before I started using it a few 
months ago and haven't seen any other warning signs.  Shouldn't it 
automatically reassign bad blocks like this?

   -- MW

# fsck /dev/sd0d
** /dev/rsd0d
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
13520 files, 200115 used, 2849319 free (1319 frags, 356000 blocks, 0.0% 
fragment
ation)

MARK FILE SYSTEM CLEAN? [yn] y


CANNOT WRITE: BLK 16
CONTINUE? [yn] y

THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 16, 17, 18, 19, 20, 21, 22, 
23, 24,
25, 26, 27, 28, 29, 30, 31,

CANNOT WRITE: BLK 2864
CONTINUE? [yn] y

THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 2864, 2865, 2866, 2867,

***** FILE SYSTEM MARKED CLEAN *****
#