Very Computer

by **Greg Tupp** » Wed, 15 Oct 1997 04:00:00

I have a bad block in my /var directory. Each time I run fsck I get,

# fsck /var
** /dev/rwd0s3f
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes

CANNOT READ: BLK 64
CONTINUE? [yn] y

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 96,
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? [yn] y

CLEAN FLAG NOT SET IN SUPERBLOCK
FIX? [yn] y

245 files, 1418 used, 47813 free (109 frags, 5963 blocks, 0.2% fragmentation)

***** FILE SYSTEM WAS MODIFIED *****

I am still able to use the disk, but each time I boot I have problems.
I would like to map the bad block out and do not know how. Is there
a utility the will do this?

Greg Tupper

by **J Wuns** » Sun, 19 Oct 1997 04:00:00

> I am still able to use the disk, but each time I boot I have problems.
> I would like to map the bad block out and do not know how. Is there
> a utility the will do this?

Option #1 (preferrable): throw the disk into the bit-bucket,
Option #2: bother to see whether you could get ancient
bad144(8) working with it,
Option #3: badsect(8) (probably worthless since your bad
block is inside the metadata region of the
filesystem).

--
cheers, J"org

Never trust an operating system you don't have sources for. ;-)

Very Computer

Bad block in /var,fsck fails.

Bad block in /var,fsck fails.

Bad block in /var,fsck fails.