[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problema con software RAID



On Mon, Sep 27, 2004 at 10:49:12AM +0200, Alexis Roda wrote:
> Hola a todos,
> estoy intentando configurar un woody para montar dos discos IDE en RAID 
> 1 y tengo un problema.
> 
> He seguido el software-RAID-howto (la receta "Converting a non-RAID 
> RedHat System to run on Software RAID" adaptada a debian) 

Otra referencia interesante:

http://rootraiddoc.alioth.debian.org/

> y el sistema 
> arranca. Mi problema es con una "particion" en concreto (/dev/md5 = 
> /dev/hda7 + /dev/hdc7), al ejecutar el e2fsck sobre /dev/md5 para 
> corregir el tamaño me salen errores 

¿Para qué quieres corregir el tamaño? ¿No habrás jugado con e2fsadm?

> 
> e2fsck -f /dev/md5
> e2fsck 1.27 (8-Mar-2002)
> The filesystem size (according to the superblock) is 7897947 blocks
> The physical size of the device is 7895760 blocks
> Either the superblock or the partition table is likely to be corrupt!
> Abort<y>? no

o a lo mejor has dado formato a esa partición *antes* de añadirla al RAID en
vez de después. Extraído de

http://www.linuxjournal.com/article.php?sid=5653

en este caso para /dev/md0 en vez de /dev/md5,

------------------
Create an ext2 filesystem on /dev/md0 using the command mke2fs /dev/md0. Do
not mke2fs on the RAID-1 component partitions, in this case /dev/hda2 and
/dev/hdc2. If you do not create an ext2 filesystem on /dev/md0, then e2fsck
/dev/md0 will return an error message, something like this:

The filesystem size (according to the superblock) is
2104483 blocks. The physical size of the device is 2104384 blocks.
Either the superblock or the partition table is likely to be corrupt.

This is because mkraid writes the RAID superblock near the end of the
component partitions. e2fsck does not recognize the RAID superblock that has
caused the physical size to be smaller. You can mount /dev/md0 at this
point, and even use /usr, but the ext2 filesystem superblock contains
incorrect information. You may not notice problems but you should not use
the filesystem in this state. You will not be able to boot and mount
/dev/md0 unless you turn off the filesystem checking by making the
appropriate entry in fstab (e.g., /dev/md0 /usr ext2 defaults 1 0). The 0 at
the end of the line causes e2fsck to be skipped. Do not do this unless you
have to fix your RAID. Make /dev/md0 an ext2 filesystem. 
-----------------

Espero que te sirva de algo,

-- 
Agustin



Reply to: