From: Jesse Burkhardt <jesse@skybuilders.com>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-raid@vger.kernel.org
Subject: More: Fedora 2.0 - raid1 not working
Date: Tue, 09 Nov 2004 17:14:25 -0500 [thread overview]
Message-ID: <41914141.6030108@skybuilders.com> (raw)
In-Reply-To: <20041109194127.GA17963@middle.of.nowhere>
A little more info - this is excerpted from dmesg:
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdd3 ...
md: adding hdd3 ...
md: hdd1 has different UUID to hdd3
md: adding hda3 ...
md: hda1 has different UUID to hdd3
md: created md1
md: bind<hda3>
md: bind<hdd3>
md: running: <hdd3><hda3>
md: kicking non-fresh hdd3 from array!
md: unbind<hdd3>
md: export_rdev(hdd3)
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md1 stopped.
md: unbind<hda3>
md: export_rdev(hda3)
md: considering hdd1 ...
md: adding hdd1 ...
md: adding hda1 ...
md: created md0
md: bind<hda1>
md: bind<hdd1>
md: running: <hdd1><hda1>
md: kicking non-fresh hdd1 from array!
md: unbind<hdd1>
md: export_rdev(hdd1)
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md0 stopped.
md: unbind<hda1>
md: export_rdev(hda1)
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
md: raid1 personality registered as nr 3
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hda1 ...
md: adding hda1 ...
md: adding hdd1 ...
md: hda3 has different UUID to hda1
md: hdd3 has different UUID to hda1
md: created md0
md: bind<hdd1>
md: bind<hda1>
md: running: <hda1><hdd1>
md: kicking non-fresh hdd1 from array!
md: unbind<hdd1>
md: export_rdev(hdd1)
raid1: raid set md0 active with 1 out of 2 mirrors
md: considering hda3 ...
md: adding hda3 ...
md: adding hdd3 ...
md: created md1
md: bind<hdd3>
md: bind<hda3>
md: running: <hda3><hdd3>
md: kicking non-fresh hdd3 from array!
md: unbind<hdd3>
md: export_rdev(hdd3)
raid1: raid set md1 active with 1 out of 2 mirrors
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdd3 ...
md: adding hdd3 ...
md: hdd1 has different UUID to hdd3
md: md1 already running, cannot run hdd3
md: export_rdev(hdd3)
md: considering hdd1 ...
md: adding hdd1 ...
md: md0 already running, cannot run hdd1
md: export_rdev(hdd1)
md: ... autorun DONE.
Thanks again.
--
Jesse Burkhardt, Cambridge MA
jesse@skybuilders.com (w) 617-876-5680
aerogoose.com (h) 617-354-5523
prev parent reply other threads:[~2004-11-09 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 19:08 Fedora 2.0 - raid1 not working Jesse Burkhardt
2004-11-09 19:22 ` Jurriaan
[not found] ` <41911ACB.2070604@skybuilders.com>
2004-11-09 19:41 ` Jurriaan
[not found] ` <41911F09.2070403@skybuilders.com>
2004-11-09 19:57 ` Jurriaan
2004-11-09 22:14 ` Jesse Burkhardt [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=41914141.6030108@skybuilders.com \
--to=jesse@skybuilders.com \
--cc=linux-raid@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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).