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 1QjBZi-0001EO-JX for garchives@archives.gentoo.org; Tue, 19 Jul 2011 14:47:07 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DEAB621C34C; Tue, 19 Jul 2011 14:46:47 +0000 (UTC) Received: from mail-fx0-f52.google.com (mail-fx0-f52.google.com [209.85.161.52]) by pigeon.gentoo.org (Postfix) with ESMTP id 7355A21C19D for ; Tue, 19 Jul 2011 14:45:13 +0000 (UTC) Received: by fxd18 with SMTP id 18so144785fxd.11 for ; Tue, 19 Jul 2011 07:45:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:content-type; bh=eV6l9xuhFl1NASZ3EgjA79L4Q+2XES1H4boPicgKigw=; b=SCLxg/8+UuOZgHHSmgerD2R2thA/dJ9hCtTaVTH24qsBr0HfUYkjdAKJGylApFMMER 1fhFpIz24MC9NJ/W8xJA74/MuL+TGH9fddVurkiVDJBnkDwqSXpcJ/SEiAoe/TylsLo2 ZnWCNGHeseA3L6J+IPbJYm3DUxDeOXdG18UVY= Received: by 10.223.144.134 with SMTP id z6mr12059687fau.8.1311086712668; Tue, 19 Jul 2011 07:45:12 -0700 (PDT) Received: from localhost.localnet (p4FC7420D.dip0.t-ipconnect.de [79.199.66.13]) by mx.google.com with ESMTPS id 21sm6566fay.45.2011.07.19.07.45.10 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Jul 2011 07:45:11 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems with Nvidia fake raid array Date: Tue, 19 Jul 2011 16:45:09 +0200 Message-ID: <11113817.Azf3EOF3o3@localhost> User-Agent: KMail/4.7 rc2 (Linux/2.6.39.3; KDE/4.6.95; x86_64; ; ) In-Reply-To: <1558175.QojAWWvpoK@localhost> References: <1311038774.7499.11.camel@laptop.limeyworld> <4E25813D.7090003@orlitzky.com> <1558175.QojAWWvpoK@localhost> 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 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: X-Archives-Hash: fd2a052791d9b9522a99d293994405e4 On Tuesday 19 July 2011 16:36:20 you wrote: > On Tuesday 19 July 2011 09:06:05 Michael Orlitzky wrote: > > 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. > > mdadm? that is for linux software raid. > > He wants to use nvidia fakeraid. He needs dmraid for that. > > Build in the dmraid support. > emerge device-mapper > emerge dmraid > add device-mapper to boot runlevel > done > > If I remember correctly > > oh yeah - nvidia fakeraid is pretty fragile. You should plan to move away > from it. addendum: just saw that mdadm >=3 should be able to handle fake raid. My bad. -- #163933