From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Fri, 10 Apr 2009 14:26:26 -0700 [thread overview]
Message-ID: <00f301c9ba23$032025f0$0a00a8c0@vorg> (raw)
In-Reply-To: 20090410205942.GC21242@cthulhu.home.robinhill.me.uk
Strange:
-----------------
sudo mdadm -D /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Fri Mar 27 16:49:37 2009
Raid Level : raid1
Array Size : 24418688 (23.29 GiB 25.00 GB)
Used Dev Size : 24418688 (23.29 GiB 25.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Fri Apr 10 12:58:59 2009
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 27ce9bd9:4ce6ceb2:670e265f:82e0c670 (local to host LLLx64-32)
Events : 0.38
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
-----------------
Seems ok, but then:
-----------------
sudo mdadm -E /dev/md0
mdadm: No md superblock detected on /dev/md0.
-----------------
----- Original Message -----
From: "Robin Hill" <robin@robinhill.me.uk>
To: <linux-raid@vger.kernel.org>
Sent: Friday, April 10, 2009 1:59 PM
Subject: Re: Converting system to raid
> As for the other reply, the sata drives each have 3 primary partitions
> all set to type fd and formated with ext3. I was going to try ext4 for
> the main storage of the newer system but I found there is a problem
> with kernels .27 and newer on nforce2 and newer boards. some sort of
> problem with the bios and apci. How do I find out which superblocks
> version is used?
>
Either "mdadm -D" on the array, or "mdadm -E" on one of the partitions
will show you the version.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
next prev parent reply other threads:[~2009-04-10 21:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 23:44 Converting system to raid Timothy D. Lenz
2009-04-10 9:10 ` KwangErn Liew
2009-04-10 9:55 ` CoolCold
2009-04-10 19:43 ` Timothy D. Lenz
2009-04-10 19:53 ` Robin Hill
2009-04-10 20:45 ` Timothy D. Lenz
2009-04-10 20:59 ` Robin Hill
2009-04-10 21:26 ` Timothy D. Lenz [this message]
2009-04-10 21:51 ` Robin Hill
2009-04-11 5:29 ` Timothy D. Lenz
2009-04-11 14:29 ` CoolCold
2009-04-11 18:47 ` Timothy D. Lenz
2009-04-12 0:53 ` Timothy D. Lenz
2009-04-12 11:11 ` Robin Hill
2009-04-12 19:55 ` Timothy D. Lenz
2009-04-14 9:30 ` Robin Hill
2009-04-17 0:47 ` Timothy D. Lenz
2009-04-17 7:49 ` Robin Hill
2009-04-11 14:36 ` Robin Hill
2009-04-11 15:04 ` jim owens
2009-04-11 15:44 ` Jeff Garzik
2009-04-11 17:40 ` jim owens
2009-04-12 11:11 ` Jeff Garzik
2009-04-12 16:43 ` jim owens
2009-04-12 17:18 ` Jeff Garzik
2009-04-10 13:22 ` Robin Hill
2009-04-10 19:22 ` Timothy D. Lenz
2009-04-10 19:50 ` Robin Hill
2009-04-11 4:40 ` Jon Lewis
2009-04-11 7:48 ` Jan Ceuleers
2009-04-11 8:50 ` Goswin von Brederlow
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='00f301c9ba23$032025f0$0a00a8c0@vorg' \
--to=tlenz@vorgon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.