[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bad hdisks blocks

I managed to deal with the problem in the same way... ie.  i just skipped a
few blocks and voila! :)
It's also interesting how when i created 3 partitions on the same
device...the start block on partition 3 overwrote the end block of
partition 2.  I had to leave a gap in between which resulted in a few more
unused blocks.

thanx for the help oki etc.

debian-user@lists.debian.org on 08/12/99 15:36:11

To:   debian-user@lists.debian.org
cc:    (bcc: Zane Drysdale/Diagnostic labs/64)
Subject:  Re: bad hdisks blocks

zdrysdal@diagnostic.co.nz wrote:
> is there anyway to label a particular block on a scsi hdisk as being bad?
> I am performing a mke2fs -c, which checks for bad blocks....in this
> particular case it has found a bad block and has aborted the mke2fs
process > with an error message.


I had the same problem, but mkfs didn't just quit, but hung the system.
I don't understand why. Long ago, I had the same experience; on
Slackware 3.4 I think. The disk had more bad sectors, but the
"formatting" was done correctly.

It seems that mkfs couldn't handle the SCSI time out.

Since I didn't know how to built a filesystem on this particular
bad-sector'ed disk, I just skipped the block, and everything was fine.
Of course, about 50MB was lost on my 300MB disk.


Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org <

Reply to: