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 1QjA1k-0004jL-48 for garchives@archives.gentoo.org; Tue, 19 Jul 2011 13:07:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 553A021C30B; Tue, 19 Jul 2011 13:07:31 +0000 (UTC) Received: from mail2.viabit.com (mail2.viabit.com [65.246.80.16]) by pigeon.gentoo.org (Postfix) with ESMTP id 3243F21C025 for ; Tue, 19 Jul 2011 13:06:22 +0000 (UTC) Received: from [172.17.29.6] (unknown [65.213.236.242]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail2.viabit.com (Postfix) with ESMTPSA id 27B1837B2A for ; Tue, 19 Jul 2011 09:06:15 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orlitzky.com; s=mail2; t=1311080779; bh=6vxy++ZPX0ADOtzQOglt75nte7LYcMqhQOZ26hKDX4E=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=JRkERtWTUapRTNtCbV/oDVZ6AikD3JE4PkDsCpOkC97IECw0JH5SzAib8J2Sve0iz EtShJks94OmHTKm0mbHLzzW0ufMFQdUMVN4MgzYQp/yFZBPdpXSE4CB+wbo1xkMShW i1ae0sLP0BN5at/WpkYRTvAnQeHyoOxH5bn+SRhI= Message-ID: <4E25813D.7090003@orlitzky.com> Date: Tue, 19 Jul 2011 09:06:05 -0400 From: Michael Orlitzky User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110713 Lightning/1.0b3pre Thunderbird/3.1.10 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] Problems with Nvidia fake raid array References: <1311038774.7499.11.camel@laptop.limeyworld> <4E24EC18.1050403@orlitzky.com> <1311044885.7499.34.camel@laptop.limeyworld> In-Reply-To: <1311044885.7499.34.camel@laptop.limeyworld> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: d7189195f6a9bd893a8e6d9f2df41b1e On 07/18/2011 11:08 PM, Jeff Cranmer wrote: > > > Pardon my additional questions before taking the plunge here. > > So, given that I have three devices, /dev/sda, /dev/sdb and /dev/sdc, if > I run the command mdadm --assemble --scan, would this find all the > components and create a /dev/md0 disk without damaging the contents of > the original RAID array? If you've got the space and time, a backup can't hurt. Using --scan will make it check the config file, but right now, there's probably nothing useful in it. This looks like what you want to do to me: If the --scan option is not given, then only devices and identities listed on the command line are considered. The first device will be the array device, and the remainder will be examined when looking for components. but I'd figure out where that md0 is coming from (below) first. > The only item in /dev/mapper is th default 'control' entry. There is > a /dev/md0 item already listed, but presently when I try to mount it, it > reports that it is unable to read the superblock. Would the command > above fix this? Depends. Where'd the md0 come from? You probably have something in your logs or dmesg, unless that device was created manually on your old system. > Where is the config file mentioned in your e-mail, and do I need to edit > it first to add the three raid disks? It's /etc/mdadm.conf. You don't need it to create or use the array, but you'll want to run mdadm when the machine boots and the config file tells it what to do. Once the array is working, you can just do, mdadm --detail --scan >> /etc/mdadm.conf to populate it. I guess also check to make sure there's no default crap in there these days.