Bad Blocks on SCSI Drive

Bad Blocks on SCSI Drive

Post by Geoffrey L. Matrangola x » Sat, 05 Nov 1994 04:10:15



I've got a SCSI hard drive w/ a bad block.  It gets reported int to
/usr/var/adm/messages as a sector, but e2fsck -b wants a file with a
list of bad blocks!  How do I convert?  Are there any plans to change the
e2 file system in Linux to automaticly mark bad blocks as bad when they
are encountered by the driver.

-Geoff

 
 
 

Bad Blocks on SCSI Drive

Post by Toon van der P » Mon, 07 Nov 1994 23:30:37



Quote:>I've got a SCSI hard drive w/ a bad block.  It gets reported int to
>/usr/var/adm/messages as a sector, but e2fsck -b wants a file with a
>list of bad blocks!  How do I convert?  Are there any plans to change the
>e2 file system in Linux to automaticly mark bad blocks as bad when they
>are encountered by the driver.

I should leave that to the SCSI-device.
SCSI-devices can remap bad blocks automatically.
As far as I know this is configurable.
At least for my SCSI-disk it was.
And it was turned off as the factory default!

Utilities exist to change the configuration of SCSI-devices.
Look around on bulletin boards for SCSICNTL.EXE or something like that.
Linux comes with a utility like that too. I have no experience
with it though.

Good luck,
Toon.
--
Toon van der Pas                                     Tel.: +31 3403 53162

3994 WP  Houten

 
 
 

1. SCSI drive with bad-blocks

We bougth here a 1G scsi drive for an AcerPower 433 computer in our lab.
The computer has an integraged SCSI interface (a 152x job) and an IDE
interface. Everything worked fine for a few weeks but now reading some
specific files hangs the SCSI interface (I need to reboot using the reset
button). The scsi driver prints the message:

  nele kernel: scsi0: resetting for second half retries.

and I cannot access the disk anymore. After reading the SCSI-HOWTO it
seems that the most probable cause for this are bad-blocks.

My questions are:

1.- SCSI drives have an internal list of bad-blocks (true?) how do I
force a disk check to update that list?

1a- If I should use an utility to check for bad-blocks, would it crash
also since the problem ocurrs at the kernel level?

2.- Is this normal? I formated the drive and received no error messages
and now I am encountering all this problems. What can be creating this
errors, can heat be a problem?

3.- Isn't device drivers reentrant? Why would the kernel block any
further access to the disk? I guess the problem is with the SCSI interface.  

4.- Am I wrong to assume that the problem is related to bad-blocks?

Phew!! Thats it... Thanks for any help you can give me with this. I am
using kernel 1.2.8.

                          Victor Sanchez
                          U. Tecnologica de Panama
                          C. I. Automatizacion y Robotica.

2. gtk+ 1.2.8 won't complete './configure'

3. Finding out if there are bad blocks in the bad blocks list

4. Implementing a bit of HTTP w/ telnet and GET / request

5. How do you add a bad block to e2fs bad block list?

6. how do you add a ether interface

7. Bad block on drive using RAID-1

8. Win95 Devices equivalent

9. Help for newbie, repair bad super blocks on SCSI hardrive

10. 3.2.4 w/ bad blocks & a scsi hd

11. Bad Blocks on IDE drive, fsck doesn't fix it

12. Bad blocks on SCSI disk and Linux

13. The good, the bad & the ugly (or VM, block devices, and SCSI :-)