Bad block on IDE drive causes it to be kicked out of the array

I have two raid 5 arrays here on IDE drives (each consiting out of 4 IDE
disks).

The first drive in the second array has 6 bad sectors / bad blocks on it,
and during reconstruction after creating the array these bad blocks are
found, and the disk is kicked out of the array (and the initial background
resync is terminated).

The rest of the disk is just fine, and its had these bad blocks since who
knows how long without any problems

is there any way to create the array, and just mark these blocks bad in the
file system, as you would with a 'normal' drive?

Any info is greatly apreciated,

(ps, i did find some emails on the list about the same problem w/ scsi
drives, but low level formatting the drive and causing the blocks to be
relocated by the scsi hardware solved the problem there.. unfortunatly that
dont work for my IDE drives ;-/)

    -- Chris

On Mon, 8 Jul 2002, Chris Chabot wrote:

is there any way to create the array, and just mark these blocks bad in the
file system, as you would with a 'normal' drive?

Not on RAID5. At least no easy way... You could possibly find out which
filesystem blocks lay on the physically bad blocks and you could probably
mark them as bad on the filesystem level.

   D.