Path: utzoo!attcan!uunet!husc6!bbn!rochester!ritcv!cci632!ccicpg!felix!zemon
From: randy@gtuplab.UUCP (Randal Abler)
Newsgroups: comp.unix.ultrix
Subject: fsck <=> disk problem
Message-ID: <38555@felix.UUCP>
Date: 25 May 88 21:20:26 GMT
Sender: zemon@felix.UUCP
Reply-To: randy@gtuplab.UUCP (Randal Abler)
Organization: Georgia Tech Microprocessor Lab
Lines: 18
Approved: zemon@felix.UUCP
Reply-Path:


	I have a VAXstation II running Ultrix, and am having trouble
	dealing with Bad Blocks on a third party drive.  My question
	for the net is:
	When fsck reports a bad block, say  BLK 243125 for example,
	how does that map into the logical block numbers for the drive?
	Do I just add the partition table offset for that partition on the
	drive?   Given the correct logical block number, I should be able
	to map out that block.  

	Vital Statistics:
	Drive Controller    Dilog DQ686  (ESDI controller)
	Disk Drive	    Maxtor 4380E (320MB, 5.25" ESDI Disk)

						Randy Abler
						EE-CERL
						Georgia Tech             
						gtuplab!randy