Will some one explain how raid5 handles bad blocks?
--
sysuh
mingo,
Thank you very much for your help.
I now recovered almost all data. No need to recreate the raid
array, or the ext2 filesystem.
The program, e2fsck, is good. It recovered the filesystem
successfully. I answered "no" on its question:
Clone duplicate/bad blocks? No
On Tue, Sep 07, 1999 at 06:29:21PM +0200, [EMAIL PROTECTED] wrote:
>
> On Wed, 8 Sep 1999 [EMAIL PROTECTED] wrote:
>
> > I have the exactly same problem. My startup message was as follows:
> >
> > Sep 7 12:28:41 yfs kernel: md: kicking non-fresh sdc1 from array!
> > Sep 7 12:28:41 yfs ke
Thus spoke Martin Bene ([EMAIL PROTECTED]):
>>My problem is that I can't recover the original full config.
>>No matter how I change the order of the raidtab, the disconnected-
>>and-later-reconnected disk is not included in the raid config.
>>
>>The appended is my raidtab. The reconnected disk is
As described in the RAID5.HOWTO, I disconnected one of the SCSI disks.
The raid runs Ok after the rebooting.
My problem is that I can't recover the original full config.
No matter how I change the order of the raidtab, the disconnected-
and-later-reconnected disk is not included in the raid confi
