Subject: Lost target files until reboot
To: None <current-users@NetBSD.ORG>
From: brian <bwildasi@csulb.edu>
List: current-users
Date: 07/01/1997 21:49:40
Sorry for posting twice. The first test case was too long!

Does any one know how to fix disk-write problems that fsck sends to the
console? ...ie, certain blocks that can't be written.

> > # fsck -fy
> > ** /dev/rsd2a
> > ** 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
> > 6901 files, 88196 used, 28499 free (331 frags, 3521 blocks, 0.3%
> > fragmentation)
> > MARK FILE SYSTEM CLEAN? yes
> > CANNOT WRITE: BLK 16
> > CONTINUE? yes
> > 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 208
> > CONTINUE? yes
> > THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 208,209,
> 
> This problem looks VERY bad. Can you try on of the disk partitioners
> which does write integrity tests? Stress the drive and see how it
> does.
> 
> Also, I think you should probably send EMail to current-users, as 
> this problem might not be mac specific (it might be...).


Any help is appreciated!

Sincerely...brian w.
bwildasi@csulb.edu