I did a similar setup, but I used Linux raid-1 rather then the software
raid.

If I remember right, I tried the software raid, but I think you made it
further then I did.  I couldn't get the software raid working under the
live CD.

Sorry, no help other then to recommend Linux raid instead of the
software raid.  Usually the performance is better (from what I hear)
anyways.

--Kurt



Jarry wrote:

> Hi,
>
> I'm trying to install gentoo on a small server in full sw-raid1 setup,
> using info in http://www.gentoo.org/doc/en/gentoo-x86-tipsntricks.xml
>
> I have a similar setup with /boot / and swap on md. After creating md's
> I continued with installation using info in
> http://www.gentoo.org/doc/en/handbook/2005.0/index.xml
>
> I recompilled kernel with md-support (no modules), installed boot-loader
> (lilo, on /dev/md0), created /etc/fstab, emerged mdadm, etc, etc...
> Everything was OK until 10.d: Rebooting the System
>
> When booting into new system (this time from disks, not from
> installation cd), I got following messages:
> ---------------------------------------------------------------------
> ... <up to here everything normal, all md's correctly autodetected>...
>
> * mounting sysfs at sys ...
> can't create lock file /etc/mtab1008: Read only file-system
> (use -n flag to override)                           [!!]
>
> ...<again everything normal up to>...
>
> * checking root filesystem
> ext2fs_check_if_mount: No such file or directory while determining
> whether /dev/md1 is mounted
> fsck.ext3: No such file or directory while trying to open /dev/md1
> /dev/md1:
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contain an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate
> superblock: e2fsck -b 8193 <device>
>
> * Filesystem could not be fixed :-(                 [!!]
>
> Give root-password for maintenance
> (or type Control-D for normal startup):
> ---------------------------------------------------------------------
>
> Then I logged as root and tried that "e2fsck -b 8193 /dev/md1" with
> the same error. Rebooting did not change anything...
>
> BTW, I repeated the whole installation 3 times, even with different
> pair of disks (I thought there is some hw-error), but no difference...
> What now? Could someone tell me where the problem is?
>
> Thanks,
>     Jarry


-- 
gentoo-user@gentoo.org mailing list

Reply via email to