NCR 810 drivers are bad with disk errors

Jari Soderholm (
Tue, 12 Nov 1996 15:43:56 +0200 (EET)

I am having ugly problems with both ncr 810 drivers
in kernel 2.0.25.

Just happened a few days ago that some magical bad blocks
dropped into my disk and scsi drivers stopped working when they
met those blocks.

BSDI ported driver seems to little worse than the other.

When running for example badblocks utility v1.06 when it
met those errors on the disk it simply stuck or somecases
even crashed whole machine.

I wonder if these are known problems.

here is two announcement what i got when running badblocks
Only Drew Echard's driver was able to read these
BSDI ported simply stuck or crasched.

>Current error sd08:21 sense key medium error
>additinal sense indicates recorded entity not found
>scsidisk I/O error: dev 08:21: sector xxxxx

>Current error sd08:21 sense key medium error
>additinal sense indicates unrecovered read error
>scsidisk I/O error: dev 08:21: sector xxxxx

I have a feeling from long time use that there is
still some work left to do with Linux filesystems.
and driver interfaces.

Compared for example windows NT NTFS, linux ext2fs
seems to be more error prone and also and I wonder
why filesystem is not planned so that directory
listing would come with minimal head movement.

I once got "e2fsck -cf" run on entire disk, but it wasn't able
to transfer those broken files from area where those bad blocks
were so there was nothing to do.

Are there any tools for linux to format disk better
than mke2fs ?