Ubuntu
linux-source-2.6.20 package

Bug #97655
Comment #39

Comment 39 for bug 97655

Revision history for this message

Zach Retzlaff (zach-retzlaff) wrote on 2007-09-09:

#39

Thanks to all who have diligently posted on this bug, and thanks in advance to anyone who can offer me further assistance. I have only been able to get as far as patching (I think) Linux kernel 2.6.22.1 with Heinz Mauleshagen's dm-raid45-2.6.22.1 patch.

Kernel Source:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.1.tar.bz2

dmraid45 Post and Patch Source from Heinz Mauelshagen:
https://www.redhat.com/archives/dm-devel/2007-July/msg00099.html
http://people.redhat.com/heinzm/sw/dm/dm-raid45/dm-raid45-2.6.22.1-20070724.patch.bz2

Kernel Patching How-To Followed:
http://www.howtoforge.com/kernel_compilation_ubuntu
* I skipped the step on re-linking /bin/sh from /bin/dash to /bin/bash, as I didn't think this was necessary. Am I wrong?

My custom 2.6.22.1 kernel ("custom kernel") has been installed, more or less successfully from what I can tell. I have omitted all wireless networking modules from the compilation, which I don't think should have any impact on the issue at hand.

These are the issues:

1. Booting to my custom kernel fails while initializing dmraid, and I have to boot to my previous kernel instead (2.6.18-generic), remove dmraid, then boot back to my custom kernel for further troubleshooting.
2. "dmraid -r" shows my installed devices, but "dmraid -ay" returns the all too common " "raid45" not in kernel" error.
3. modprobe on any combination of dm-raid4-5, dm-raid45, dmraid45, etc. of course returns "Module <xyz> not found."
4. "dmesg | grep raid" returns "...raid45: unknown target type".
5. "lsmod | grep raid" or just manually scanning the results of lsmod returns nothing related to dmraid or my raid devices.

I think that's a fairly complete synopsis. Here is my configuration, followed by some (hopefully) useful output...

Config:

Mobo: ASUS M2NPV-VM AM2 NVIDIA GeForce 6150 (NB GeForce 6150, SB nForce 430) on-board support configured for RAID5.
CPU/RAM: Adequate / N/A
Boot HDD: Pri Master IDE
RAID Config: Athena Power 5.25" Backplane, supports quad 2.5" SATA drives.
RAID HDD's: 4 TOSHIBA MK1637GSX 160GB 5400 RPM 8MB Cache SATA 3.0Gb/s Notebook Hard Drives

The RAID HDD's are detected in gparted as unallocated, and parted returns the following for all four drives (/dev/sda - sdd):

"Error: Unable to open /dev/sd[a-d] - unrecognised disk label."

Useful Output:

root@IN-FS-N01:~# dmraid -r
/dev/sda: nvidia, "nvidia_cgcdfabe", raid5_ls, ok, 312581806 sectors, data@ 0
/dev/sdb: nvidia, "nvidia_cgcdfabe", raid5_ls, ok, 312581806 sectors, data@ 0
/dev/sdc: nvidia, "nvidia_cgcdfabe", raid5_ls, ok, 312581806 sectors, data@ 0
/dev/sdd: nvidia, "nvidia_cgcdfabe", raid5_ls, ok, 312581806 sectors, data@ 0

root@IN-FS-N01:~# dmraid -ay
ERROR: device-mapper target type "raid45" not in kernel

root@IN-FS-N01:~# modprobe dm-raid45
FATAL: Module dm_raid45 not found.
root@IN-FS-N01:~# modprobe dm-raid4-5
FATAL: Module dm_raid4_5 not found.
root@IN-FS-N01:~# modprobe dmraid45
FATAL: Module dmraid45 not found.
root@IN-FS-N01:~# modprobe dmraid
FATAL: Module dmraid not found.

root@IN-FS-N01:~# dmesg | grep raid
[ 9.228000] device-mapper: table: 254:0: raid45: unknown target type
[ 671.080000] device-mapper: table: 254:0: raid45: unknown target type
[ 749.464000] device-mapper: table: 254:0: raid45: unknown target type
[ 3583.988000] device-mapper: table: 254:0: raid45: unknown target type

root@IN-FS-N01:~# lsmod | grep raid
<no results>

I have no idea how to edit /usr/share/initramfs-tools/hooks/dmraid to include dmraid4-5.ko as suggested by Tormod Volden above, nor how to determine whether grub needs patching. Nevertheless, maybe this will be useful as well:

/usr/share/initramfs-tools/hooks/dmraid:
#!/bin/sh

PREREQ=""

prereqs()
{
echo "$PREREQ"
}

case $1 in
# get pre-requisites
prereqs)
        prereqs
        exit 0
        ;;
esac

. /usr/share/initramfs-tools/hook-functions

if [ -x /sbin/dmraid ]; then
        manual_add_modules dm-mod
        manual_add_modules dm-mirror
        copy_exec /sbin/dmraid sbin
fi

exit 0

And just for kicks...I think I also got these errors when installing my custom kernel:

root@IN-FS-N01:~# sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.22.1-custom
find: /lib/firmware/2.6.22.1-custom: No such file or directory
find: /lib/firmware/2.6.22.1-custom: No such file or directory
find: /lib/firmware/2.6.22.1-custom: No such file or directory
find: /lib/firmware/2.6.22.1-custom: No such file or directory
find: /lib/firmware/2.6.22.1-custom: No such file or directory
find: /lib/firmware/2.6.22.1-custom: No such file or directory

Any insight would be greatly appreciated. Thanks, all!

Thanks to all who have diligently posted on this bug, and thanks in advance to anyone who can offer me further assistance.  I have only been able to get as far as patching (I think) Linux kernel 2.6.22.1 with Heinz Mauleshagen's dm-raid45-2.6.22.1 patch.

Kernel Source:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.1.tar.bz2

Kernel Patching How-To Followed:
http://www.howtoforge.com/kernel_compilation_ubuntu
*  I skipped the step on re-linking /bin/sh from /bin/dash to /bin/bash, as I didn't think this was necessary.  Am I wrong?

My custom 2.6.22.1 kernel ("custom kernel") has been installed, more or less successfully from what I can tell.  I have omitted all wireless networking modules from the compilation, which I don't think should have any impact on the issue at hand.

These are the issues:

1.  Booting to my custom kernel fails while initializing dmraid, and I have to boot to my previous kernel instead (2.6.18-generic), remove dmraid, then boot back to my custom kernel for further troubleshooting.
2.  "dmraid -r" shows my installed devices, but "dmraid -ay" returns the all too common " "raid45" not in kernel" error.
3.  modprobe on any combination of dm-raid4-5, dm-raid45, dmraid45, etc. of course returns "Module <xyz> not found."
4.  "dmesg | grep raid" returns "...raid45: unknown target type".
5.  "lsmod | grep raid" or just manually scanning the results of lsmod returns nothing related to dmraid or my raid devices.

I think that's a fairly complete synopsis.  Here is my configuration, followed by some (hopefully) useful output...

Config:

Mobo:  ASUS M2NPV-VM AM2 NVIDIA GeForce 6150 (NB GeForce 6150, SB nForce 430) on-board support configured for RAID5.
CPU/RAM:  Adequate / N/A
Boot HDD:  Pri Master IDE
RAID Config:  Athena Power 5.25" Backplane, supports quad 2.5" SATA drives.
RAID HDD's:  4  TOSHIBA MK1637GSX 160GB 5400 RPM 8MB Cache SATA 3.0Gb/s Notebook Hard Drives

The RAID HDD's are detected in gparted as unallocated, and parted returns the following for all four drives (/dev/sda - sdd):

"Error: Unable to open /dev/sd[a-d] - unrecognised disk label."

Useful Output:

root@IN-FS-N01:~# dmraid -ay
ERROR: device-mapper target type "raid45" not in kernel

root@IN-FS-N01:~# dmesg | grep raid
[    9.228000] device-mapper: table: 254:0: raid45: unknown target type
[  671.080000] device-mapper: table: 254:0: raid45: unknown target type
[  749.464000] device-mapper: table: 254:0: raid45: unknown target type
[ 3583.988000] device-mapper: table: 254:0: raid45: unknown target type

root@IN-FS-N01:~# lsmod | grep raid
<no results>

root@IN-FS-N01:~# lsmod
Module                  Size  Used by
ipv6                  272996  10 
ppdev                  10500  0 
capability              6024  0 
commoncap               8576  1 capability
cpufreq_powersave       2944  0 
cpufreq_ondemand        9484  0 
cpufreq_stats           7360  0 
cpufreq_conservative     8328  0 
freq_table              6048  2 cpufreq_ondemand,cpufreq_stats
cpufreq_userspace       5408  0 
button                  9104  0 
dock                   10784  0 
battery                11268  0 
container               5632  0 
video                  17800  0 
ac                      6404  0 
sbs                    19720  0 
sbp2                   24456  0 
lp                     12708  0 
serio_raw               8324  0 
i2c_nforce2             7296  0 
parport_pc             37668  1 
af_packet              24840  2 
shpchp                 34836  0 
parport                37832  3 ppdev,lp,parport_pc
k8temp                  6912  0 
psmouse                40208  0 
pcspkr                  4352  0 
i2c_core               26368  1 i2c_nforce2
pci_hotplug            32960  1 shpchp
evdev                  11392  4 
joydev                 11584  0 
ext3                  134024  1 
jbd                    60328  1 ext3
mbcache                 9860  1 ext3
dm_mirror              17408  0 
dm_log                 11264  1 dm_mirror
dm_mod                 58944  2 dm_mirror,dm_log
sg                     36892  0 
ide_disk               18560  3 
ata_generic             8708  0 
sd_mod                 30464  0 
usbhid                 29664  0 
hid                    29056  1 usbhid
ohci1394               36784  0 
ieee1394               96440  2 sbp2,ohci1394
forcedeth              50440  0 
sata_nv                20740  0 
libata                127472  2 ata_generic,sata_nv
scsi_mod              147340  4 sbp2,sg,sd_mod,libata
ohci_hcd               23044  0 
amd74xx                15516  0 [permanent]
ide_core              116804  2 ide_disk,amd74xx
ehci_hcd               36108  0 
usbcore               137736  4 usbhid,ohci_hcd,ehci_hcd
thermal                14600  0 
processor              32200  1 thermal
fan                     6020  0

/usr/share/initramfs-tools/hooks/dmraid:
#!/bin/sh

PREREQ=""

prereqs()
{
        echo "$PREREQ"
}

case $1 in
# get pre-requisites
prereqs)
        prereqs
        exit 0
        ;;
esac

. /usr/share/initramfs-tools/hook-functions

if [ -x /sbin/dmraid ]; then
        manual_add_modules dm-mod
        manual_add_modules dm-mirror
        copy_exec /sbin/dmraid sbin
fi

exit 0

And just for kicks...I think I also got these errors when installing my custom kernel:

Any insight would be greatly appreciated.  Thanks, all!

Ubuntulinux-source-2.6.20 package

Comment 39 for bug 97655

Ubuntu
linux-source-2.6.20 package