1 |
On Sat, Apr 3, 2010 at 7:38 PM, Kerin Millar <kerframil@×××××.com> wrote: |
2 |
> On 04/04/2010 02:01, Mark Knecht wrote: |
3 |
>> |
4 |
>> Tried changing root=/dev/md0. No change. |
5 |
>> |
6 |
>> The actual failure message is the fairly standard |
7 |
>> |
8 |
>> VFS - Unable to mount root fs on unknown-block(9,0) |
9 |
> |
10 |
> [snip] |
11 |
> |
12 |
>> CONFIG_MD_RAID1=y |
13 |
> |
14 |
> That's all that needs to be enabled within the RAID section of the kernel. |
15 |
> However, all the other options that would normally be required to boot must |
16 |
> also be compiled in statically for things to work as expected (ATA/SCSI |
17 |
> controller driver, filesystem of choice, CONFIG_BLK_DEV_SD and so forth). It |
18 |
> seems that you may have overlooked something. However, it's impossible to |
19 |
> determine whether that's the case based on the information presented thus |
20 |
> far. |
21 |
> |
22 |
> I would suggest that you double-check your .config in full, or present it |
23 |
> here for review, along with the output of lspci -nn. |
24 |
> |
25 |
> Cheers, |
26 |
> |
27 |
> --Kerin |
28 |
|
29 |
Hi Kerin, |
30 |
Happy for any help I can get. |
31 |
|
32 |
Instead of the whole .config file here's a diff. Remember that the |
33 |
machine already boots non-RAID from /dev/sda and I'm trying to build |
34 |
my first RAID boot on /dev/sdb & sdc. |
35 |
|
36 |
First, here's the RAID I would like to boot from: |
37 |
|
38 |
keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3 |
39 |
mdadm: /dev/md3 has been started with 2 drives. |
40 |
keeper ~ # mdadm --detail /dev/md3 |
41 |
/dev/md3: |
42 |
Version : 1.01 |
43 |
Creation Time : Sat Apr 3 11:43:39 2010 |
44 |
Raid Level : raid1 |
45 |
Array Size : 52436092 (50.01 GiB 53.69 GB) |
46 |
Used Dev Size : 52436092 (50.01 GiB 53.69 GB) |
47 |
Raid Devices : 2 |
48 |
Total Devices : 2 |
49 |
Persistence : Superblock is persistent |
50 |
|
51 |
Update Time : Sun Apr 4 06:40:54 2010 |
52 |
State : clean |
53 |
Active Devices : 2 |
54 |
Working Devices : 2 |
55 |
Failed Devices : 0 |
56 |
Spare Devices : 0 |
57 |
|
58 |
Name : keeper:3 (local to host keeper) |
59 |
UUID : 6dcf5ddb:c4a2d5ea:ba59df10:f5473502 |
60 |
Events : 3703 |
61 |
|
62 |
Number Major Minor RaidDevice State |
63 |
0 8 19 0 active sync /dev/sdb3 |
64 |
1 8 35 1 active sync /dev/sdc3 |
65 |
keeper ~ # cat /proc/mdstat |
66 |
Personalities : [raid1] |
67 |
md3 : active raid1 sdb3[0] sdc3[1] |
68 |
52436092 blocks super 1.1 [2/2] [UU] |
69 |
|
70 |
unused devices: <none> |
71 |
keeper ~ # |
72 |
|
73 |
Here's the diff of the running kernel without RAID and the kernel I |
74 |
created while in the install chroot on the RAID device: |
75 |
|
76 |
keeper ~ # diff /usr/src/linux/.config /mnt/gentoo/usr/src/linux/.config |
77 |
4c4 |
78 |
< # Mon Mar 29 01:02:31 2010 |
79 |
--- |
80 |
> # Sun Apr 4 06:28:53 2010 |
81 |
893,912c893,906 |
82 |
< CONFIG_MD_LINEAR=m |
83 |
< CONFIG_MD_RAID0=m |
84 |
< CONFIG_MD_RAID1=m |
85 |
< CONFIG_MD_RAID10=m |
86 |
< CONFIG_MD_RAID456=m |
87 |
< # CONFIG_MULTICORE_RAID456 is not set |
88 |
< CONFIG_MD_RAID6_PQ=m |
89 |
< # CONFIG_ASYNC_RAID6_TEST is not set |
90 |
< CONFIG_MD_MULTIPATH=m |
91 |
< CONFIG_MD_FAULTY=m |
92 |
< CONFIG_BLK_DEV_DM=m |
93 |
< CONFIG_DM_DEBUG=y |
94 |
< CONFIG_DM_CRYPT=m |
95 |
< CONFIG_DM_SNAPSHOT=m |
96 |
< CONFIG_DM_MIRROR=m |
97 |
< # CONFIG_DM_LOG_USERSPACE is not set |
98 |
< CONFIG_DM_ZERO=m |
99 |
< CONFIG_DM_MULTIPATH=m |
100 |
< # CONFIG_DM_MULTIPATH_QL is not set |
101 |
< # CONFIG_DM_MULTIPATH_ST is not set |
102 |
--- |
103 |
> # CONFIG_MD_LINEAR is not set |
104 |
> CONFIG_MD_RAID0=y |
105 |
> CONFIG_MD_RAID1=y |
106 |
> # CONFIG_MD_RAID10 is not set |
107 |
> # CONFIG_MD_RAID456 is not set |
108 |
> # CONFIG_MD_MULTIPATH is not set |
109 |
> # CONFIG_MD_FAULTY is not set |
110 |
> CONFIG_BLK_DEV_DM=y |
111 |
> # CONFIG_DM_DEBUG is not set |
112 |
> # CONFIG_DM_CRYPT is not set |
113 |
> # CONFIG_DM_SNAPSHOT is not set |
114 |
> # CONFIG_DM_MIRROR is not set |
115 |
> # CONFIG_DM_ZERO is not set |
116 |
> # CONFIG_DM_MULTIPATH is not set |
117 |
914,915c908,909 |
118 |
< CONFIG_DM_UEVENT=y |
119 |
< CONFIG_BLK_DEV_DM_BBR=m |
120 |
--- |
121 |
> # CONFIG_DM_UEVENT is not set |
122 |
> # CONFIG_BLK_DEV_DM_BBR is not set |
123 |
2293,2298d2286 |
124 |
< CONFIG_XOR_BLOCKS=m |
125 |
< CONFIG_ASYNC_CORE=m |
126 |
< CONFIG_ASYNC_MEMCPY=m |
127 |
< CONFIG_ASYNC_XOR=m |
128 |
< CONFIG_ASYNC_PQ=m |
129 |
< CONFIG_ASYNC_RAID6_RECOV=m |
130 |
keeper ~ # |
131 |
|
132 |
One additional thing I thought of last night was some message that |
133 |
came up when I first built the RAID about the partitions having |
134 |
metadata and to be sure that the bootloader understands metadata. In |
135 |
the cool light of morning that seems fairly important. I am using |
136 |
grub-static on this machine. I assumed this would be OK but possibly |
137 |
it isn't? |
138 |
|
139 |
If rebuilding the RAID from scratch is important, or just makes |
140 |
things more straight forward, then don't hesitate to suggest it and |
141 |
I'll document the build step by step. This install isn't important. |
142 |
I'm just doing it to learn how to do RAID and most importantly to test |
143 |
the disk drives. I purchased other disk drives that aren't working |
144 |
with RAID at all so I wanted to test these a bit before I did anything |
145 |
real. The final install with be a 3 disk RAID1 but the 3rd drive |
146 |
hasn't arrived yet so none of this is critically important. |
147 |
|
148 |
Thanks! |
149 |
|
150 |
Cheers, |
151 |
Mark |