From: Kurt Guenther <kurtg@serent.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problem with raid1: error while booting
Date: Tue, 12 Jul 2005 10:56:56 -0400 [thread overview]
Message-ID: <42D3DA38.206@serent.com> (raw)
In-Reply-To: <42D3710F.7020305@gmx.net>
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
next prev parent reply other threads:[~2005-07-12 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 7:28 [gentoo-user] problem with raid1: error while booting Jarry
2005-07-12 14:56 ` Kurt Guenther [this message]
2005-07-12 15:12 ` Jarry
2005-07-12 20:37 ` A. Khattri
2005-07-12 21:02 ` Richard Fish
2005-07-13 4:18 ` Jarry
2005-07-13 5:24 ` Richard Fish
2005-07-13 14:09 ` Jarry
2005-07-13 14:18 ` Mike Williams
2005-07-13 18:26 ` Richard Fish
2005-07-13 16:17 ` [gentoo-user] problem with raid1: error while booting - SOLVED ! Jarry
2005-07-13 18:45 ` Richard Fish
2005-07-14 6:37 ` Jarry
2005-07-13 18:40 ` [gentoo-user] problem with raid1: error while booting Richard Fish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42D3DA38.206@serent.com \
--to=kurtg@serent.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox