From: Alfred Isele <Alfred.Isele@fujitsu-siemens.com>
To: Donghui Wen <dhwen@protegonetworks.com>, linux-raid@vger.kernel.org
Subject: Re: unable to read superblock ?
Date: Wed, 11 Jun 2003 10:12:38 +0200 [thread overview]
Message-ID: <3.0.6.32.20030611101238.00a8f700@athen> (raw)
In-Reply-To: <004801c32e8b$1dac5170$4300a8c0@moon>
Hello!
Maybe you created the file system before creating the md device?
Regards
Alfred
At 06:29 09.06.03 -0700, Donghui Wen wrote:
>Hi, I have a machine setup as software-raid + ext3 + redhat ,
>but this morning, it seems the file system crash. here is
>the booting message, anyone has any idea how to fix it.
>
>Thanks!
>
>Donghui
>
>----------------------------------------------------------------------------
>------
>md: adding sda1
>md: created md2
>md: using <sdb1> <sda1>
>md: md2: raid array is not clean -- starting bacground reconstruction
>RAID level 1 does not need chunck size. Continuing anyway.
>md2: max total readahead window set to 124k
>
>raid1: device sdb1 operational as mirror1
>raid1: device sda1 operational as mirror 0
>raid1: raid set md2 mot clean, reconstructing mirror
>raid1: raid set md2 active with 2 out of 2 mirrors
>md: updating md2 RAID superblock device
>.
>.
>md: autorun DONE
>mounting root filesystem
>EXT3-fs: unable to read super block
>mount: error 22 mounting ext3
>pivotrot: oivot_root(/sysrot,/sysrot/initrd) failed :2
>freing unused kernal memory: 244k fred
>kernal panic: no init found. Try passing init= option to kernal
>
>-----------------------------------------------------------
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2003-06-11 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 13:29 unable to read superblock ? Donghui Wen
2003-06-11 8:12 ` Alfred Isele [this message]
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=3.0.6.32.20030611101238.00a8f700@athen \
--to=alfred.isele@fujitsu-siemens.com \
--cc=dhwen@protegonetworks.com \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).