Gentoo Archives: gentoo-user

From: Michael Orlitzky <michael@××××××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Problems with Nvidia fake raid array
Date: Tue, 19 Jul 2011 02:30:52
In Reply to: [gentoo-user] Problems with Nvidia fake raid array by Jeff Cranmer
1 On 07/18/2011 09:26 PM, Jeff Cranmer wrote:
2 > Hi all,
3 >
4 > After cleaning off my Opensuse O.S. and installing Gentoo, I'm having
5 > trouble getting my 3-disk nvidia SATA raid5 array back on line.
6 >
7 > The gentoo OS is on a separate non-raid IDE disk, and I can see the
8 > three individual disks which make up the raid array (/dev/sda, /dev/sdb
9 > and /dev/sdc). Unfortunately, the system does not seem to be able to
10 > detect the raid array, and dmesg shows no md disks detected or mounted.
12 Make sure your kernel supports RAID, and RAID5 (they're separate
13 options). Then emerge mdadm. Once you get it up and running once, you
14 can dump the current config to /etc/mdadm.conf so you don't have to
15 assemble it again. Then add mdadm to the boot runlevel.
17 # mdadm --assemble --help
18 Usage: mdadm --assemble device options...
19 mdadm --assemble --scan options...
21 This usage assembles one or more raid arrays from pre-existing
22 components. For each array, mdadm needs to know the md device, the
23 identity of the array, and a number of sub devices. These can be found
24 in a number of ways.
26 The md device is either given on the command line or is found listed
27 in the config file. The array identity is determined either from the
28 --uuid or --super-minor commandline arguments, from the config file,
29 or from the first component device on the command line.
31 The different combinations of these are as follows:
32 If the --scan option is not given, then only devices and identities
33 listed on the command line are considered.
35 The first device will be the array device, and the remainder will be
36 examined when looking for components.
38 If an explicit identity is given with --uuid or --super-minor, then
39 only devices with a superblock which matches that identity is
40 considered, otherwise every device listed is considered.
42 If the --scan option is given, and no devices are listed, then
43 every array listed in the config file is considered for assembly.
44 The identity of candidate devices are determined from the config file.
46 If the --scan option is given as well as one or more devices, then
47 Those devices are md devices that are to be assembled. Their identity
48 and components are determined from the config file.
50 If mdadm can not find all of the components for an array, it will
51 assemble it but not activate it unless --run or --scan is given. To
52 preserve this behaviour even with --scan, add --no-degraded. Note that
53 "all of the components" means as many as were present the last time the
54 array was running as recorded in the superblock. If the array was
55 already degraded, and the missing device is not a new problem, it will
56 still be assembled. It is only newly missing devices that cause the
57 array not to be started.


Subject Author
Re: [gentoo-user] Problems with Nvidia fake raid array Jeff Cranmer <jeff@××××××××××××××.com>