From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QATsb-00085Q-OU for garchives@archives.gentoo.org; Thu, 14 Apr 2011 21:15:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 17DB31C0E4; Thu, 14 Apr 2011 21:13:01 +0000 (UTC) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by pigeon.gentoo.org (Postfix) with ESMTP id DE3011C0E4 for ; Thu, 14 Apr 2011 21:13:00 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id A459D203E1 for ; Thu, 14 Apr 2011 17:13:00 -0400 (EDT) Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 14 Apr 2011 17:13:00 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:date:from:mime-version:to:subject:references:in-reply-to:content-type; s=smtpout; bh=rjeR3zhvxUokY+iEV6NwmjTBAxY=; b=Jto1WK2KCekjcZSsICMwcz2PRK+T7b/3aYiUSHi+jUsOImm0N7NbpNsnFN9fRu9akpPCFRj9PB2qSxk7IpV3bZUR0d/Y+NZrT3z7/lpDRlcx/FBq/3I0cK4+gh6MfLoB9CxYL7YxFwdXpTcbC4ZeTTMjd8QipPIR7r7lt3IT+qE= X-Sasl-enc: 8ovyTaPUfoGiqm9/YKlo3xyO7+v+JArnMzj2rPYdNhW+ 1302815579 Received: from [192.168.5.18] (serv.binarywings.net [83.169.5.6]) by mail.messagingengine.com (Postfix) with ESMTPSA id C7490403B7E for ; Thu, 14 Apr 2011 17:12:58 -0400 (EDT) Message-ID: <4DA7634E.2090506@binarywings.net> Date: Thu, 14 Apr 2011 23:12:46 +0200 From: Florian Philipp User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110313 Lightning/1.0b3pre Thunderbird/3.1.9 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: raid1 grub ext4 References: <20110411214915.3f88106a@digimed.co.uk> <20110412101132.0ee9c8e8@zaphod.digimed.co.uk> <4DA570EB.2060904@binarywings.net> <4DA7008F.5030303@binarywings.net> <4DA71837.9030000@binarywings.net> <4DA74FE6.1080601@binarywings.net> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9B5542A6EEEFF219A804EECF" X-Archives-Salt: X-Archives-Hash: d4708c862f0d015ce6aab38e6d0cbcb5 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9B5542A6EEEFF219A804EECF Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 14.04.2011 22:19, schrieb James: >=20 >> *Head scratch* This, uhm, looks odd. No clue what to make of it. >=20 > Ahhh, >=20 > Don't give up just yet? >=20 > I issued these commands: >=20 > mdadm --create /dev/md127 --level=3D1 --raid-devices=3D2 > --metadata=3D0.90 /dev/sda1 /dev/sdb1 >=20 > mdadm --create /dev/md125 --level=3D1 --raid-devices=3D2=20 > --metadata=3D0.90 /dev/sda3 /dev/sdb3 > mdadm: /dev/sda3 appears to be part of a raid array: > level=3Draid1 devices=3D2 ctime=3DThu Apr 14 13:22:32 2011 > mdadm: /dev/sdb3 appears to be part of a raid array: > level=3Draid1 devices=3D2 ctime=3DThu Apr 14 13:22:32 2011 > Continue creating array? y >=20 >=20 > mdadm --create /dev/md126 --level=3D1 --raid-devices=3D2=20 > --metadata=3D0.90 /dev/sda2 /dev/sdb2 >=20 > I'm not sure if I just wiped the drives clean (empty)? >=20 > If so, I'll have to start over.....? >=20 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 =20 > mdadm: cannot open /dev/md1: No such file or directory >=20 > same now for md2 and md3... >=20 Well, at least you are rid of the duplicate arrays. > Look (ma no hands!): >=20 > 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 >=20 > Update Time : Thu Apr 14 15:51:46 2011 > State : clean, resyncing > Active Devices : 2 > Working Devices : 2 > Failed Devices : 0 > Spare Devices : 0 >=20 > Rebuild Status : 37% complete >=20 > UUID : fa800cdb:33955cfd:cb201669:f728008a (local to host li= vecd) > Events : 0.6 >=20 > Number Major Minor RaidDevice State > 0 8 3 0 active sync /dev/sda3 > 1 8 19 1 active sync /dev/sdb3 >=20 >=20 [...] > We'll see in a few hours.... >=20 >=20 > James >=20 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 --------------enig9B5542A6EEEFF219A804EECF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2nY1QACgkQqs4uOUlOuU/gAACeMfzrkM4VQUP3/jVFmMGmCbXg 1IkAmQHLHUP1qlUZYwx9wMdoNUMPJk04 =9jvt -----END PGP SIGNATURE----- --------------enig9B5542A6EEEFF219A804EECF--