View previous topic :: View next topic |
Author |
Message |
jostrn n00b
Joined: 06 Oct 2006 Posts: 16 Location: Munich, Bavaria, Germany
|
Posted: Mon Feb 25, 2013 4:58 pm Post subject: [solved] My new kernels don't support software raid (md) |
|
|
Hi guys,
my system runs well with kernel 3.7.1-hardened-r1, a software raid 1 and lvm above it.
Since some time i try to upgrade to more recent kernels (3.7.5-hardened, 3.7.8-hardened, and 3.7.9-hardened), but they do not boot. As far as i understand, my newer kernels don't support the raid anymore:
3.7.1-r1-hardened:
Quote: | Hint: use parameter scandelay[=seconds] if you need waiting here
mdadm: /dev/md/myhost:3 has been started with 2 drives
mdadm: /dev/md/myhost:2 has been started with 2 drives
Scanning for and activating Volume Groups
3 logical volume(s) in volume group "vg1" now active |
3.7.9-hardened:
Quote: | Hint: use parameter scandelay[=seconds] if you need waiting here
Scanning for and activating Volume Groups
No volume groups found
No volume groups found
Determining root device...
!! Block device /dev/mapper/vg1-root is not a valid root device... |
In the shell i see that there are no /dev/md devices. mdadm --assemble --scan returns nothing.
I compiled the 3.7.9-kernel with the same .config file as the 3.7.1-r1 kernel.
Do you have any ideas or suggestions?
Last edited by jostrn on Wed Feb 27, 2013 1:35 am; edited 1 time in total |
|
Back to top |
|
|
kiksen Guru
Joined: 24 Jun 2002 Posts: 401 Location: Denmark
|
Posted: Mon Feb 25, 2013 6:38 pm Post subject: |
|
|
Could you post the result of
grep MD .config
from your linux directory?
/Kiksen |
|
Back to top |
|
|
jostrn n00b
Joined: 06 Oct 2006 Posts: 16 Location: Munich, Bavaria, Germany
|
Posted: Mon Feb 25, 2013 6:53 pm Post subject: |
|
|
sure
Code: | myhost linux-3.7.9-hardened # grep _MD .config
# CONFIG_TCP_MD5SIG is not set
# CONFIG_SCTP_HMAC_MD5 is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=m
# CONFIG_MD_RAID0 is not set
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_MDIO_BITBANG=m
# CONFIG_USB_MDC800 is not set
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y |
Because it didn't work i also modified /etc/genkernel.conf as follows without any recognized effect:
Code: | # Add in LVM support from static binaries if they exist on the system, or
# compile static LVM binaries if static ones do not exist.
LVM="yes"
# Includes mdadm/mdmon binaries in initramfs.
# Without sys-fs/mdadm[static] installed, this will build a static mdadm.
MDADM="yes"
# Specify a custom mdadm.conf.
# By default the ramdisk will be built *without* an mdadm.conf and will auto-detect
# arrays during bootup. Usually, this should not be needed.
MDADM_CONFIG="/etc/mdadm.conf" |
|
|
Back to top |
|
|
kiksen Guru
Joined: 24 Jun 2002 Posts: 401 Location: Denmark
|
Posted: Mon Feb 25, 2013 7:11 pm Post subject: |
|
|
You actually have an /etc/mdadm.conf file? I'm pretty sure I'm running without.
I'm home at the moment and not running RAID. I'll check my box when I get to work. I'm on 3.8.0 there with mdadm (and have passed 3.7.9). I'll be back...
/Kiksen |
|
Back to top |
|
|
jostrn n00b
Joined: 06 Oct 2006 Posts: 16 Location: Munich, Bavaria, Germany
|
Posted: Mon Feb 25, 2013 11:16 pm Post subject: |
|
|
Yes, i have an /etc/mdadm.conf since and because i have ugly /dev/md127 ... devices. mdadm.conf unfortunately didn't fix this so far.
I merged and compiled 3.8.0-hardened, this time with the default from /etc/kernels/kernel-config-x86_64-3.8.0-hardened but i get the same result as reported above for 3.7.9-hardened:
Quote: | Hint: use parameter scandelay[=seconds] if you need waiting here
Scanning for and activating Volume Groups
No volume groups found |
|
|
Back to top |
|
|
kiksen Guru
Joined: 24 Jun 2002 Posts: 401 Location: Denmark
|
Posted: Tue Feb 26, 2013 7:02 am Post subject: |
|
|
OK, back at work.
In fact I do have an /etc/mdadm.conf. Besides the comments have:
ARRAY /dev/md125 UUID=8a3e64d1:7a70d43f:cb201669:f728008a
ARRAY /dev/md126 UUID=5d9dfa43:252db61b:cb201669:f728008a
ARRAY /dev/md4 UUID=a1a2e0a0:33cd3a12:cb201669:f728008a
I too have the ugly names.
The relevant part of my kernel config:
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
I'm running RAID 0 and 1.
I haven't run any hardened kernels, so I don't know if that makes a difference. Besides the additional kernel modules you have enabled the hardened part is what stands out.
No other ideas for now...
/Kiksen |
|
Back to top |
|
|
jostrn n00b
Joined: 06 Oct 2006 Posts: 16 Location: Munich, Bavaria, Germany
|
Posted: Wed Feb 27, 2013 1:33 am Post subject: |
|
|
Quote: | I haven't run any hardened kernels, so I don't know if that makes a difference. Besides the additional kernel modules you have enabled the hardened part is what stands out.
No other ideas for now... |
Today i tried kernel-genkernel-x86_64-3.8.0-gentoo with the default config and i got the same result as for the hardened versions
The problems arised after i changed /etc/genkernel.conf as written above and i abdicated using genkernel with --lvm --mdadm. I removed the settings from genkernel.conf, compiled 3.8.0-hardened with genkernel --lvm --mdadm and the new kernel now works
Thx for your support, it helped me a lot to isolate the problem. |
|
Back to top |
|
|
kiksen Guru
Joined: 24 Jun 2002 Posts: 401 Location: Denmark
|
Posted: Wed Feb 27, 2013 7:12 am Post subject: |
|
|
Your welcome. Glad you found a solution |
|
Back to top |
|
|
|