View previous topic :: View next topic |
Author |
Message |
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Tue Jun 10, 2008 1:59 am Post subject: RAID1 Install issues [solved] |
|
|
This is getting me quite frustrated, so I'm posting here now.
I'm installing Gentoo on a RAID1 setup using 3 partitions: boot, swap & root. All RAID1 partitions. I've followed the install instructions from http://gentoo-wiki.com/HOWTO_Gentoo_Install_on_Software_RAID in combination with the general instructions provided by the Gentoo Handbook.
My bootloader is working fine because things do start to happen, but when mdadm starts, it spits out a message stating 0 devices scanned and added, despite /etc/mdadm.conf being setup correctly (2 devices listed as wildcards then 3 arrays listed).
What the hell am I doing wrong? Thanks.
Last edited by RFLudwick on Sat Jun 14, 2008 6:13 pm; edited 1 time in total |
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Tue Jun 10, 2008 2:16 am Post subject: |
|
|
Here's my /etc/mdadm.conf:
Code: |
DEVICE /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb1 /dev/sdb2 /dev/sdb3
ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md2 devices=/dev/sda2,/dev/sdb2
ARRAY /dev/md3 devices=/dev/sda3,/dev/sdb3
|
I have also commented out the following lines in the same file:
Code: |
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=...
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=...
ARRAY /dev/md3 level=raid1 num-devices=2 UUID=...
|
|
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Tue Jun 10, 2008 3:05 am Post subject: |
|
|
I run software RAID on several of my machines, but I don't use /etc/mdadm.conf or the mdadm init script on any of them.
If things are setup properly, the kernel will assemble your arrays without help from userspace.
Code: | md: Autodetecting RAID arrays.
md: Scanned 4 and added 4 devices.
md: autorun ...
md: considering sdb2 ...
md: adding sdb2 ...
md: sdb1 has different UUID to sdb2
md: adding sda2 ...
md: sda1 has different UUID to sdb2
md: created md2
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
md2: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sdb2
raid0: comparing sdb2(120583808) with sdb2(120583808)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sda2
raid0: comparing sda2(120583808) with sdb2(120583808)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 241167616 blocks.
raid0 : conf->hash_spacing is 241167616 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 4 bytes for hash.
md: considering sdb1 ...
md: adding sdb1 ...
md: adding sda1 ...
md: created md1
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md1 active with 2 out of 2 mirrors
md: ... autorun DONE. |
|
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Tue Jun 10, 2008 4:25 am Post subject: |
|
|
Hm... Alright. But that doesn't really help me, how did you set it up? |
|
Back to top |
|
|
vince Tux's lil' helper
Joined: 12 Dec 2002 Posts: 78
|
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Tue Jun 10, 2008 7:56 pm Post subject: |
|
|
RFLudwick wrote: | how did you set it up? |
Just the basics that are covered by the guide :
The md and raid1 modules must be compiled-in
The array(s) must be created with version 0.9 persistent superblocks
The partitions must be marked type fd (Linux raid autodetect) |
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Wed Jun 11, 2008 4:12 am Post subject: |
|
|
Alright, I've got 2 of 3 covered. My mdadm is creating the arrays as 1.0 superblocks, I believe. Is there any way to convert them to 0.9? |
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Wed Jun 11, 2008 4:13 am Post subject: |
|
|
Scratch that. I just checked and my superblocks are 0.9...
When I added
Code: | md=3,/dev/sda3,/dev/sdb3 |
to my grub config, at one point during load it said "unknown device /dev/sda3"
Any new ideas? |
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Wed Jun 11, 2008 5:26 am Post subject: |
|
|
I've tried using genkernel and even it won't boot, citing sda3 not found. I used dodmraid in the kernel config line and that didn't work either.
This makes no sense to me. I don't understand why it wouldn't be able to detect sda1/2/3 at the point where it doesn't detect... Whenever I load from the livecd, it mounts sda1/2/3 and sdb1/2/3. |
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Wed Jun 11, 2008 3:08 pm Post subject: |
|
|
RFLudwick wrote: | When I added
Code: | md=3,/dev/sda3,/dev/sdb3 |
to my grub config, at one point during load it said "unknown device /dev/sda3" |
You don't need that kernel parameter.
The error message is saying that your kernel doesn't have support for the controller that the harddrives are plugged into.
ps. This needs to be compiled into the kernel. Genkernel usually compiles SATA/SCSI drivers as modules. |
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Wed Jun 11, 2008 3:19 pm Post subject: |
|
|
Quote: | The error message is saying that your kernel doesn't have support for the controller that the harddrives are plugged into. |
That doesn't make sense because I'm pretty sure I compiled in support for SATA/SCSI on the kernel that I hand-configured...
Do you know whereabouts those options are? I just want to make sure I check all the places that I need to for those options. Thanks. |
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Wed Jun 11, 2008 3:32 pm Post subject: |
|
|
Code: | Device Drivers --->
SCSI device support --->
<*> SCSI disk support
<*> Serial ATA (prod) and Parallel ATA (experimental) drivers --->
<*> Depends on your hardware :) |
If you need help choosing the correct driver, post the output of "lspci". |
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Fri Jun 13, 2008 3:09 pm Post subject: |
|
|
I believe I've found the problem, but I'm not sure how to correct it.
When I load up the kernel config I manually created, the Serial ATA submenu has nothing in it... At all. No vendor-specific drivers. But when I load the genkernel config, the submenu is filled in. I believe this is why I couldn't properly compile in SATA drivers to load -- there weren't any to select.
Obviously, my question is: how do I get that submenu now on the kernel config I created? I'd rather not use genkernel... Oh, and you were right. All of the SATA drivers in the genkernel config were modules. |
|
Back to top |
|
|
danomac l33t
Joined: 06 Nov 2004 Posts: 881 Location: Vancouver, BC
|
Posted: Fri Jun 13, 2008 4:15 pm Post subject: |
|
|
Make sure you have "Prompt for development and/or incomplete code/drivers" under "General setup". |
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Fri Jun 13, 2008 7:10 pm Post subject: |
|
|
RFLudwick wrote: | When I load up the kernel config I manually created, the Serial ATA submenu has nothing in it... At all. |
Make sure your kernel includes PCI bus support. Most device drivers (not just SATA) depend on this.
Code: | Bus options (PCI etc.) --->
[*] PCI support |
|
|
Back to top |
|
|
RFLudwick n00b
Joined: 03 Apr 2007 Posts: 35
|
Posted: Sat Jun 14, 2008 6:13 pm Post subject: |
|
|
That was it, the PCI bus. A friend also told me to take a look at that.
I feel like such a n00b. Oh well. Raid is working, system will boot, all is well. Thanks for all the help fellas. |
|
Back to top |
|
|
|