From: Maarten J H van den Berg <maarten@vbvb.nl>
To: debian-user@lists.debian.org, linux-raid@vger.kernel.org
Subject: Re: md: can not impport hdb1, has active inodes!
Date: Wed, 3 Mar 2004 02:11:35 +0100 [thread overview]
Message-ID: <200403030211.35753.maarten@vbvb.nl> (raw)
In-Reply-To: <4045288B.27321.2DA4EF3@localhost>
On Wednesday 03 March 2004 01:36, Chris Evans wrote:
> On 3 Mar 2004 at 10:40, Neil Brown wrote:
> > Wrong.
> > mkfs -t ext3 /dev/md0
> > then mount /dev/md0.
> > Once you have included /dev/hdc1 in an array, don't touch it again -
> > just access the array (/dev/md0).
>
> Sorry, I was being hasty in writing the Email, that's what I did,
> i.e. mkfs the /dev/md0 drive. That's not the problem.
Hope it's not too obvious, but...
Did you also actually _run_ lilo ?
Is fstab on /dev/md0 edited to reflect the new mountpoints ?
Not that it helps you here, but I followed the procedure -albeit not from the
same howto[1]- multiple times with many machines. It _should_ work...
[1] I used a howto by the name of Boot+root+raid+llilo. Maybe see if there
are any obvious differences between the two procedures / howtos...?
Maarten
next prev parent reply other threads:[~2004-03-03 1:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 22:17 md: can not impport hdb1, has active inodes! Chris Evans
2004-03-02 23:24 ` Cameron Moore
2004-03-03 0:36 ` Chris Evans
2004-03-02 23:40 ` Neil Brown
2004-03-03 0:36 ` Chris Evans
2004-03-03 1:04 ` Neil Brown
2004-03-03 1:13 ` Chris Evans
2004-03-03 1:24 ` Neil Brown
2004-03-03 9:11 ` Chris Evans
2004-03-03 15:36 ` Paul Clements
2004-03-04 18:56 ` Juri Haberland
2004-03-03 1:11 ` Maarten J H van den Berg [this message]
2004-03-03 1:20 ` Chris Evans
2004-03-03 2:36 ` Maarten J H van den Berg
2004-03-03 16:54 ` Chris Evans
[not found] ` <200403031109.17348.jguerin@cso.atmel.com>
2004-03-03 22:09 ` Chris Evans
2004-03-04 2:08 ` Maarten J H van den Berg
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=200403030211.35753.maarten@vbvb.nl \
--to=maarten@vbvb.nl \
--cc=debian-user@lists.debian.org \
--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).