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

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

[Chris Chabot]

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

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

[Neil Brown]

On Monday July 8, chabotc@xs4all.nl 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?
> 
No.

(if you use raid5, you care about your data, and if you care about
your data, you don't use a drive with bad blocks.  Atleast, that is my
logic.)

NeilBrown

Invalid argument error on raid5 create

[bo]

Neil,

I am trying to create the RAID 5 array with

>mdadm -C /dev/md0 -l5 -n6 -x1 -prs /dev/hd[bcdefgh]

However, I am getting the following error message;

>mdadm: RUN_ARRAY failed: Invalid argument

Because I used these devices as raid1, I ran ">mdadm --zero-superblock
/dev/hdx" on all of these
devices. But no help. Even I tried with "mkraid & raidtab" it still has the
same error.
Also, I tried with -f option, and with or without space between option and
its value on mdadm -C.

All of these devices are used as the whole disk without partition.

I had no problem with RAID 0 or 1.

Any clue?

Thanks,

Bo

Re: Invalid argument error on raid5 create

[Neil Brown]

On Monday July 8, bo@sosnetwork.net wrote:
> Neil,
> 
> I am trying to create the RAID 5 array with
> 
> >mdadm -C /dev/md0 -l5 -n6 -x1 -prs /dev/hd[bcdefgh]
> 
> However, I am getting the following error message;
> 
> >mdadm: RUN_ARRAY failed: Invalid argument
> 
..
> 
> Any clue?

Maybe the raid5 personality isn't loaded into the kernel...
What does 
  cat /proc/mdstat
say?
Are there any message in
   dmesg
after the failure?

NeilBrown

Re: Invalid argument error on raid5 create

[bo]

Neil,

You are right.
I found my kernel image did not configure the RAID 5.

Thanks a lot,

Bo
----- Original Message ----- 
From: "Neil Brown" <neilb@cse.unsw.edu.au>
To: "bo" <bo@sosnetwork.net>
Cc: <linux-raid@vger.kernel.org>
Sent: Monday, July 08, 2002 10:01 PM
Subject: Re: Invalid argument error on raid5 create


> On Monday July 8, bo@sosnetwork.net wrote:
> > Neil,
> > 
> > I am trying to create the RAID 5 array with
> > 
> > >mdadm -C /dev/md0 -l5 -n6 -x1 -prs /dev/hd[bcdefgh]
> > 
> > However, I am getting the following error message;
> > 
> > >mdadm: RUN_ARRAY failed: Invalid argument
> > 
> ..
> > 
> > Any clue?
> 
> Maybe the raid5 personality isn't loaded into the kernel...
> What does 
>   cat /proc/mdstat
> say?
> Are there any message in
>    dmesg
> after the failure?
> 
> NeilBrown
> 

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

[Danilo Godec]

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.