From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: raid1 grub ext4
Date: Thu, 14 Apr 2011 23:12:46 +0200 [thread overview]
Message-ID: <4DA7634E.2090506@binarywings.net> (raw)
In-Reply-To: <loom.20110414T221251-25@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2676 bytes --]
Am 14.04.2011 22:19, schrieb James:
>
>> *Head scratch* This, uhm, looks odd. No clue what to make of it.
>
> Ahhh,
>
> Don't give up just yet?
>
> I issued these commands:
>
> mdadm --create /dev/md127 --level=1 --raid-devices=2
> --metadata=0.90 /dev/sda1 /dev/sdb1
>
> mdadm --create /dev/md125 --level=1 --raid-devices=2
> --metadata=0.90 /dev/sda3 /dev/sdb3
> mdadm: /dev/sda3 appears to be part of a raid array:
> level=raid1 devices=2 ctime=Thu Apr 14 13:22:32 2011
> mdadm: /dev/sdb3 appears to be part of a raid array:
> level=raid1 devices=2 ctime=Thu Apr 14 13:22:32 2011
> Continue creating array? y
>
>
> mdadm --create /dev/md126 --level=1 --raid-devices=2
> --metadata=0.90 /dev/sda2 /dev/sdb2
>
> I'm not sure if I just wiped the drives clean (empty)?
>
> If so, I'll have to start over.....?
>
Ouch, I didn't think of that. Well, I guess it will not wipe it, it will
merely re-sync the disks. Since they have been mirrors of each other
before this action, you might be lucky and it keeps working.
> mdadm --detail /dev/md1
> mdadm: cannot open /dev/md1: No such file or directory
>
> same now for md2 and md3...
>
Well, at least you are rid of the duplicate arrays.
> Look (ma no hands!):
>
> livecd gentoo # mdadm --detail /dev/md125
> /dev/md125:
> Version : 0.90
> Creation Time : Thu Apr 14 14:15:21 2011
> Raid Level : raid1
> Array Size : 1948227584 (1857.97 GiB 1994.99 GB)
> Used Dev Size : 1948227584 (1857.97 GiB 1994.99 GB)
> Raid Devices : 2
> Total Devices : 2
> Preferred Minor : 125
> Persistence : Superblock is persistent
>
> Update Time : Thu Apr 14 15:51:46 2011
> State : clean, resyncing
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> Rebuild Status : 37% complete
>
> UUID : fa800cdb:33955cfd:cb201669:f728008a (local to host livecd)
> Events : 0.6
>
> Number Major Minor RaidDevice State
> 0 8 3 0 active sync /dev/sda3
> 1 8 19 1 active sync /dev/sdb3
>
>
[...]
> We'll see in a few hours....
>
>
> James
>
You can keep using it while it re-syncs. Re-syncing just means that you
do not have any redundancy, yet. You can still read/write on the array.
You will get or manipulate whatever mdadm thinks is the correct value
for each block. That's also what will end up on both disks, ultimately.
I guess you can even reboot but since your setup is not really
persistent, I wouldn't try it.
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-04-14 21:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 18:12 [gentoo-user] raid1 grub ext4 James
2011-04-11 20:18 ` Mick
2011-04-12 5:57 ` Stroller
2011-04-12 14:10 ` [gentoo-user] " James
2011-04-12 14:31 ` Peter Humphrey
2011-04-12 14:57 ` Dale
2011-04-12 15:16 ` Joost Roeleveld
2011-04-12 15:44 ` Peter Humphrey
2011-04-13 10:14 ` Alex Schuster
2011-04-11 20:49 ` [gentoo-user] " Neil Bothwick
2011-04-12 2:09 ` Mark Shields
2011-04-12 9:11 ` Neil Bothwick
2011-04-12 14:20 ` [gentoo-user] " James
2011-04-12 16:53 ` James
2011-04-13 9:46 ` Florian Philipp
2011-04-14 12:56 ` James
2011-04-14 13:14 ` Florian Philipp
2011-04-14 14:41 ` Paul Hartman
2011-04-14 13:10 ` James
2011-04-14 13:41 ` James
2011-04-14 14:11 ` Florian Philipp
2011-04-14 15:07 ` James
2011-04-14 15:52 ` Florian Philipp
2011-04-14 16:29 ` James
2011-04-14 19:49 ` Florian Philipp
2011-04-14 20:19 ` James
2011-04-14 21:12 ` Florian Philipp [this message]
2011-04-14 20:24 ` James
2011-04-14 14:13 ` Dale
2011-04-14 14:52 ` James
2011-04-14 16:14 ` Dale
2011-04-14 16:34 ` James
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=4DA7634E.2090506@binarywings.net \
--to=lists@binarywings.net \
--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