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 1Qj05D-00089H-Og for garchives@archives.gentoo.org; Tue, 19 Jul 2011 02:30:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AFC0821C178; Tue, 19 Jul 2011 02:30:42 +0000 (UTC) Received: from mail2.viabit.com (mail2.viabit.com [65.246.80.16]) by pigeon.gentoo.org (Postfix) with ESMTP id 8CB6521C081 for ; Tue, 19 Jul 2011 02:29:45 +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 1106737AD8 for ; Mon, 18 Jul 2011 22:29:45 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orlitzky.com; s=mail2; t=1311042585; bh=60GRob7PqPsPmHyg/H2aj677Kdxh0gYQo1hcAL5eIV4=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ZCXycDF/e9DF47FMXI+wToPsKUaIDut2FHXKBgW1BvpN9y5O0qs9CvrgNTvbqGseq KlqlMLh9agT+YB04RFVoxID6LqFoetwuNakBNwnbynCvG5v8skw8XuKMLYxlpD63e6 Bk2eKoLM8Cj8Nkvg74W3zBGwDHrKoe8IeixoCWXg= Message-ID: <4E24EC18.1050403@orlitzky.com> Date: Mon, 18 Jul 2011 22:29:44 -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> In-Reply-To: <1311038774.7499.11.camel@laptop.limeyworld> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: e24dba5d2766bbca81c33b8c984a038c On 07/18/2011 09:26 PM, Jeff Cranmer wrote: > Hi all, > > After cleaning off my Opensuse O.S. and installing Gentoo, I'm having > trouble getting my 3-disk nvidia SATA raid5 array back on line. > > The gentoo OS is on a separate non-raid IDE disk, and I can see the > three individual disks which make up the raid array (/dev/sda, /dev/sdb > and /dev/sdc). Unfortunately, the system does not seem to be able to > detect the raid array, and dmesg shows no md disks detected or mounted. Make sure your kernel supports RAID, and RAID5 (they're separate options). Then emerge mdadm. Once you get it up and running once, you can dump the current config to /etc/mdadm.conf so you don't have to assemble it again. Then add mdadm to the boot runlevel. # mdadm --assemble --help Usage: mdadm --assemble device options... mdadm --assemble --scan options... This usage assembles one or more raid arrays from pre-existing components. For each array, mdadm needs to know the md device, the identity of the array, and a number of sub devices. These can be found in a number of ways. The md device is either given on the command line or is found listed in the config file. The array identity is determined either from the --uuid or --super-minor commandline arguments, from the config file, or from the first component device on the command line. The different combinations of these are as follows: 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. If an explicit identity is given with --uuid or --super-minor, then only devices with a superblock which matches that identity is considered, otherwise every device listed is considered. If the --scan option is given, and no devices are listed, then every array listed in the config file is considered for assembly. The identity of candidate devices are determined from the config file. If the --scan option is given as well as one or more devices, then Those devices are md devices that are to be assembled. Their identity and components are determined from the config file. If mdadm can not find all of the components for an array, it will assemble it but not activate it unless --run or --scan is given. To preserve this behaviour even with --scan, add --no-degraded. Note that "all of the components" means as many as were present the last time the array was running as recorded in the superblock. If the array was already degraded, and the missing device is not a new problem, it will still be assembled. It is only newly missing devices that cause the array not to be started.