[patch] Ubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28

[thefuzz4]

When booting off of a fake-raid RAID5 drive boot fails due to the dm-raid4-5 module not being loaded before the device activation takes place.
This is due to a small typo in the dmraid initialization script and the initramfs hook script.

The patch (and fix) simply changes the two occurrences of 'dm-raid45' to 'dm-raid4-5' which then allows the module to be loaded and boot/raid initialization to take place.

The bug can be reproduced using a BIOS RAID5 setup, this is obviously quite hard to simulate from a testing point of view unless you already have this setup.

This bug is a regression from the previous release which used dmraid-1.0.0.rc14 and had the module name spelt correctly.
The debdiff patch attached to this bug report changes the package version number from dmraid-1.0.0.rc15-6ubuntu2 to dmraid-1.0.0.rc15-6ubuntu2

-----------

Original Bug report:

When trying to activate my dmraid with Jaunty I get the following from dmraid -ay
RAID set "nvidia_iicejhch" already active
ERROR: dos: reading /dev/mapper/nvidia_iicejhch[No such file or directory]

However in /dev/mapper the path does exist here is my output of ls /dev/mapper
control nvidia_iicejhch

As per the instructions sent to me from bug 315735 here is my output of dmraid -ay -vvv -d

WARN: locking /var/lock/dmraid/.lock
NOTICE: skipping removable device /dev/sdg
NOTICE: /dev/sdf: asr discovering
NOTICE: /dev/sdf: ddf1 discovering
NOTICE: /dev/sdf: hpt37x discovering
NOTICE: /dev/sdf: hpt45x discovering
NOTICE: /dev/sdf: isw discovering
NOTICE: /dev/sdf: jmicron discovering
NOTICE: /dev/sdf: lsi discovering
NOTICE: /dev/sdf: nvidia discovering
NOTICE: /dev/sdf: pdc discovering
NOTICE: /dev/sdf: sil discovering
NOTICE: /dev/sdf: via discovering
NOTICE: /dev/sde: asr discovering
NOTICE: /dev/sde: ddf1 discovering
NOTICE: /dev/sde: hpt37x discovering
NOTICE: /dev/sde: hpt45x discovering
NOTICE: /dev/sde: isw discovering
NOTICE: /dev/sde: jmicron discovering
NOTICE: /dev/sde: lsi discovering
NOTICE: /dev/sde: nvidia discovering
NOTICE: /dev/sde: pdc discovering
NOTICE: /dev/sde: sil discovering
NOTICE: /dev/sde: via discovering
NOTICE: /dev/sdd: asr discovering
NOTICE: /dev/sdd: ddf1 discovering
NOTICE: /dev/sdd: hpt37x discovering
NOTICE: /dev/sdd: hpt45x discovering
NOTICE: /dev/sdd: isw discovering
NOTICE: /dev/sdd: jmicron discovering
NOTICE: /dev/sdd: lsi discovering
NOTICE: /dev/sdd: nvidia discovering
NOTICE: /dev/sdd: nvidia metadata discovered
NOTICE: /dev/sdd: pdc discovering
NOTICE: /dev/sdd: sil discovering
NOTICE: /dev/sdd: via discovering
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: nvidia metadata discovered
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: nvidia metadata discovered
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: nvidia metadata discovered
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: not found nvidia_iicejhch
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: not found nvidia_iicejhch
NOTICE: added /dev/sdd to RAID set "nvidia_iicejhch"
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: found nvidia_iicejhch
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: found nvidia_iicejhch
NOTICE: added /dev/sdc to RAID set "nvidia_iicejhch"
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: found nvidia_iicejhch
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: found nvidia_iicejhch
NOTICE: added /dev/sdb to RAID set "nvidia_iicejhch"
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: found nvidia_iicejhch
DEBUG: _find_set: searching nvidia_iicejhch
DEBUG: _find_set: found nvidia_iicejhch
NOTICE: added /dev/sda to RAID set "nvidia_iicejhch"
DEBUG: checking nvidia device "/dev/sda"
DEBUG: checking nvidia device "/dev/sdb"
DEBUG: checking nvidia device "/dev/sdc"
DEBUG: checking nvidia device "/dev/sdd"
DEBUG: set status of set "nvidia_iicejhch" to 16
RAID set "nvidia_iicejhch" already active
INFO: Activating raid5_ls raid set "nvidia_iicejhch"
NOTICE: discovering partitions on "nvidia_iicejhch"
NOTICE: /dev/mapper/nvidia_iicejhch: dos discovering
ERROR: dos: reading /dev/mapper/nvidia_iicejhch[No such file or directory]
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "nvidia_iicejhch"
DEBUG: freeing device "nvidia_iicejhch", path "/dev/sda"
DEBUG: freeing device "nvidia_iicejhch", path "/dev/sdb"
DEBUG: freeing device "nvidia_iicejhch", path "/dev/sdc"
DEBUG: freeing device "nvidia_iicejhch", path "/dev/sdd"

I have completely removed all of the dmraid packages and reinstalled them as well. I believe that I am using the appropriate repo's for this however I am not certain here is my /etc/apt/sources.list file

# added by the release upgrader
deb cdrom:[Kubuntu 9.04 _Jaunty Jackalope_ - Beta amd64 (20090324.2)]/ jaunty main restricted
# deb cdrom:[Kubuntu 8.10 _Intrepid Ibex_ - Release amd64 (20081029.1)]/ intrepid main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://us.archive.ubuntu.com/ubuntu/ jaunty main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty universe
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty universe
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-backports main restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ intrepid-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository. This software is not part of Ubuntu, but is
## offered by Canonical and the respective vendors as a service to Ubuntu
## users.
# deb http://archive.canonical.com/ubuntu intrepid partner
# deb-src http://archive.canonical.com/ubuntu intrepid partner

deb http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-src http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb http://security.ubuntu.com/ubuntu jaunty-security universe
deb-src http://security.ubuntu.com/ubuntu jaunty-security universe
deb http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-src http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb http://moblock-deb.sourceforge.net/debian jaunty main #MoBlock
deb-src http://moblock-deb.sourceforge.net/debian jaunty main #MoBlock
deb http://ppa.launchpad.net/openoffice-pkgs/ubuntu jaunty main #OpenOffice
deb http://download.virtualbox.org/virtualbox/debian jaunty non-free
deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu jaunty main
deb http://mirror.noreply.org/pub/tor jaunty main
deb-src http://mirror.noreply.org/pub/tor jaunty main

deb http://fr.archive.ubuntu.com/ubuntu jaunty main universe

I am running on the x64 version as well. Hope this helps if there is anything else I can provide to you please let me know and I will get you this information as quickly as possible. Thank you in advance for your assistance with this.

[Luke Yelavich (themuso)]

Could you please state what version of dmraid you are sing? To do this, run the command "apt-cache policy dmraid" and report back with the output you receive.

 affects ubuntu/dmraid
 status incomplete

[thefuzz4 (jason-hamilton)]

Right now so I can access my files on that drive I have temporarily installed the 14 version but at the time I did have the version 15 installed. With the 14 installed I can manually activate my raid. If you need me to install the 15 version for further testing just let me know and I'll put it in there right away. I am a software engineer so I understand how important repro steps are. Thanks for looking at this so quickly.

dmraid:
  Installed: 1.0.0.rc14-2ubuntu12.1
  Candidate: 1.0.0.rc15-6ubuntu1
  Version table:
     1.0.0.rc15-6ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        500 http://fr.archive.ubuntu.com jaunty/main Packages
 *** 1.0.0.rc14-2ubuntu12.1 0
        100 /var/lib/dpkg/status

[Luke Yelavich (themuso)]

Ok so did you try and use 1.0.0.rc15-6ubuntu1?

[thefuzz4 (jason-hamilton)]

Yes with the 15 installed I got the errors reported above. I completely removed the packages and reinstalled them several times to see if they would work but no go. The only way I could get the dmraid with version 15 to run was to use kernel 2.6.27-7 or the 2.6.27-11. But when using 2.6.28-11 the dmraid modules with version 15 it would not mount the drives. Thanks.

[Will (anon4321)]

I have also encountered this problem.

dmraid output:
ubuntu@ubuntu:/dev/mapper$ sudo dmraid -ay
RAID set "nvidia_aecdafjf" already active
ERROR: dos: reading /dev/mapper/nvidia_aecdafjf[No such file or directory]

Contents of /dev/mapper:
ubuntu@ubuntu:/dev/mapper$ ls
control nvidia_aecdafjf

dmraid verbose output:
ubuntu@ubuntu:/dev/mapper$ sudo dmraid -ay -vvv -d
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: nvidia metadata discovered
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: nvidia metadata discovered
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: nvidia metadata discovered
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching nvidia_aecdafjf
DEBUG: _find_set: not found nvidia_aecdafjf
DEBUG: _find_set: searching nvidia_aecdafjf
DEBUG: _find_set: not found nvidia_aecdafjf
NOTICE: added /dev/sdc to RAID set "nvidia_aecdafjf"
DEBUG: _find_set: searching nvidia_aecdafjf
DEBUG: _find_set: found nvidia_aecdafjf
DEBUG: _find_set: searching nvidia_aecdafjf
DEBUG: _find_set: found nvidia_aecdafjf
NOTICE: added /dev/sdb to RAID set "nvidia_aecdafjf"
DEBUG: _find_set: searching nvidia_aecdafjf
DEBUG: _find_set: found nvidia_aecdafjf
DEBUG: _find_set: searching nvidia_aecdafjf
DEBUG: _find_set: found nvidia_aecdafjf
NOTICE: added /dev/sda to RAID set "nvidia_aecdafjf"
DEBUG: checking nvidia device "/dev/sda"
DEBUG: checking nvidia device "/dev/sdb"
DEBUG: checking nvidia device "/dev/sdc"
DEBUG: set status of set "nvidia_aecdafjf" to 16
RAID set "nvidia_aecdafjf" already active
INFO: Activating raid5_ls raid set "nvidia_aecdafjf"
NOTICE: discovering partitions on "nvidia_aecdafjf"
NOTICE: /dev/mapper/nvidia_aecdafjf: dos discovering
ERROR: dos: reading /dev/mapper/nvidia_aecdafjf[No such file or directory]
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "nvidia_aecdafjf"
DEBUG: freeing device "nvidia_aecdafjf", path "/dev/sda"
DEBUG: freeing device "nvidia_aecdafjf", path "/dev/sdb"
DEBUG: freeing device "nvidia_aecdafjf", path "/dev/sdc"

Output of apt-cac...

[thefuzz4 (jason-hamilton)]

Ok I just updated today and got a Kernel update. In hopes that maybe the new kernel will place nice with my dmraid I let apt-get also update my dmraid to the .15 version. However it still fails with the new kernel. Just wanted to post this in here to let you know. Thanks.

[thefuzz4 (jason-hamilton)]

One other item. I am currently working on a rebuild of my machine that I am testing this on. My thought was that maybe my upgrade from 8.10 to 9.04 had something to do with this. Due to the slow download speeds of the individual packages I downloaded the alternate install cd. That wasn't the bad idea for the upgrade. The bad idea came when I decided to move the .iso to a network drive and then mount it from there. The problem arose when the upgrade decided to rebuild my network adapter and I lost network connection and then the errors were flying left and right. I did run dpkg --configure -a and apt-get install -f to the point of where no more errors were displayed and kdm finally decided to launch so I thought that might have fixed it. But there are some other items in the system acting a little quirky here and there so I'm going to see what happens with a rebuild and find out if dmraid will run that way. I will post my results of this after the rebuild is complete. Thank you.

[thefuzz4 (jason-hamilton)]

ok I can confirm that after a complete system rebuild this is still a problem. Let me know what else I can do to help diagnose and fix this. Thanks.

[storm (yostorm)]

i have the same problem.

I upgraded to the 9.04 final.

dmraid -ay

RAID set "isw_bbafiecdbg_Volume0" already active
ERROR: dos: reading /dev/mapper/isw_bbafiecdbg_Volume0[No such device or address]

dmraid -ay -vvv -d

WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sdd: asr discovering
NOTICE: /dev/sdd: ddf1 discovering
NOTICE: /dev/sdd: hpt37x discovering
NOTICE: /dev/sdd: hpt45x discovering
NOTICE: /dev/sdd: isw discovering
NOTICE: /dev/sdd: isw metadata discovered
NOTICE: /dev/sdd: jmicron discovering
NOTICE: /dev/sdd: lsi discovering
NOTICE: /dev/sdd: nvidia discovering
NOTICE: /dev/sdd: pdc discovering
NOTICE: /dev/sdd: sil discovering
NOTICE: /dev/sdd: via discovering
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: isw metadata discovered
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
DEBUG: _find_set: searching isw_bbafiecdbg
DEBUG: _find_set: not found isw_bbafiecdbg
DEBUG: _find_set: searching isw_bbafiecdbg_Volume0
DEBUG: _find_set: searching isw_bbafiecdbg_Volume0
DEBUG: _find_set: not found isw_bbafiecdbg_Volume0
DEBUG: _find_set: not found isw_bbafiecdbg_Volume0
NOTICE: added /dev/sdd to RAID set "isw_bbafiecdbg"
DEBUG: _find_set: searching isw_bbafiecdbg
DEBUG: _find_set: found isw_bbafiecdbg
DEBUG: _find_set: searching isw_bbafiecdbg_Volume0
DEBUG: _find_set: searching isw_bbafiecdbg_Volume0
DEBUG: _find_set: found isw_bbafiecdbg_Volume0
DEBUG: _find_set: found isw_bbafiecdbg_Volume0
NOTICE: added /dev/sdc to RAID set "isw_bbafiecdbg"
DEBUG: _find_set: searching isw_bbafiecdbg
DEBUG: _find_set: found isw_bbafiecdbg
DEBUG: _find_set: searching isw_bbafiecdbg_Volume0
DEBUG: _find_set: searching isw_bbafiecdbg_Volume0
DEBUG: _find_set: found isw_bbafiecdbg_Volume0
DEBUG: _find_set: found isw_bbafiecdbg_Volume0
NOTICE: added /dev/sdb to RAID set "isw_bbafiecdbg"
DEBUG: checking isw device "/dev/sdb"
DEBUG: checking isw device "/dev/sdc"
DEBUG: checking isw device "/dev/sdd"
DEBUG: set status of set ...

[thefuzz4 (jason-hamilton)]

If you go download the .deb file for the .14 version and manually install it then reboot and do a sudo dmraid -ay it will mount it then do a sudo mount -a. You will need to do this each time though. As of right now there is not a fix for this with the .15 version. Feel free to email me any questions.

Jason Hamilton

Sent from my Verizon Wireless BlackBerry

Notice of Confidentiality: The information included and/or attached in this electronic mail transmission may contain confidential or privileged information and is intended for the addressee only. Any unauthorized disclosure, reproduction, distribution or the taking of action in reliance on the contents of the information is prohibited. If you believe that you have received the message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.

-----Original Message-----
From: storm <email address hidden>

Date: Thu, 23 Apr 2009 23:20:42
To: <email address hidden>
Subject: [Bug 356503] Re: Kubuntu Jaunty 9.04 dmraid fails with Kernel 2.6.28

i have the same problem.

I upgraded to the 9.04 final.

dmraid -ay

RAID set "isw_bbafiecdbg_Volume0" already active
ERROR: dos: reading /dev/mapper/isw_bbafiecdbg_Volume0[No such device or address]

dmraid -ay -vvv -d

WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sdd: asr discovering
NOTICE: /dev/sdd: ddf1 discovering
NOTICE: /dev/sdd: hpt37x discovering
NOTICE: /dev/sdd: hpt45x discovering
NOTICE: /dev/sdd: isw discovering
NOTICE: /dev/sdd: isw metadata discovered
NOTICE: /dev/sdd: jmicron discovering
NOTICE: /dev/sdd: lsi discovering
NOTICE: /dev/sdd: nvidia discovering
NOTICE: /dev/sdd: pdc discovering
NOTICE: /dev/sdd: sil discovering
NOTICE: /dev/sdd: via discovering
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: isw metadata discovered
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via di...

[storm (yostorm)]

thefuzz4, it's realy help me, thank you

[murray (murray-noddle)]

I get the exact same error as thefuzz4.
I'm not rly that desperate to fix it though, but it would be nice to be able to use my raid ;-P

If anyone needs me to post any debug info or something for further verification or anything, just tell me.

[Jaroslav Sedlacek (yarda)]

Hello, I am experiencing similar, but maybe not exactly the same problem.
I just upgraded fron 8.10 to 9.04 and cannot access my fakeraid disks with dmraid.
I tried following:

sudo dmraid -ay

RAID set "isw_eagedjaiic_Volume0" already active
ERROR: dos: reading /dev/mapper/isw_eagedjaiic_Volume0[No such device or address]

sudo dmraid -s
*** Group superset isw_eagedjaiic
--> Active Subset
name : isw_eagedjaiic_Volume0
size : 1953536512
stride : 128
type : raid5_la
status : ok
subsets: 0
devs : 3
spares : 0

This looks similar to your problems so I tried following:

sudo dmraid -an
ERROR: dos: reading /dev/mapper/isw_eagedjaiic_Volume0[No such file or directory]

sudo dmraid -ay
ERROR: device-mapper target type "raid45" is not in the kernel
RAID set "isw_eagedjaiic_Volume0" was not activated

This raid set was working fine couple of hours ago on 8.10...
Now I am a little bit sad missing my data ...

[storm (yostorm)]

2 Jaroslav Sedlacek.

I have the same problem last time, so I do like this - https://bugs.launchpad.net/ubuntu/+bug/150531/comments/5

[thefuzz4 (jason-hamilton)]

As I've mentioned before make sure that you download and install the .14 version of dmraid then reboot. After you are done rebooting exec sudo dmraid -ay and then sudo mount -a. After that you should have access to your raid volumes once more. Please be aware that you will have to go sift through the ubuntu packages on the web site to find the .14 version of dmraid then once you have just use gdebi to install it. After each reboot you will need to use dmraid -ay and mount -a to bring your raid back on line.

Ubuntu developers please be aware that this is still very much a problem. Thank you.

[Jaroslav Sedlacek (yarda)]

Thank for the comments. I compiled a proxcedure thatr works for me (even with the latest dmraid 1.0.0rc15-6):

After booting up in command line (as a root or with sudo):
modprobe dm-raid4-5
dmraid -an
dmraid -ay
mount -a

The problem is evident. The module dm-raid4-5 is not pre-loaded in the kernel and dmraid utility is not able to autoload it.

[clas (clausholst)]

@ Jaroslav

Works for me too! Thanks man...

[thefuzz4 (jason-hamilton)]

I can still confirm that this is a problem. I tried installing the updates again the other day to see if they were fixed however it still would not mount my raid and resulted with the same error that I started the bug with.

[Christopher Story (kc5hhq)]

I upgraded from 8.10 to 9.04 yesterday and I am encountering this bug. I am able to get the array online by running dmraid -ay then exit, which boots the server normally. But, in the event of a power failure this server would be offline until I could physically access it. Does anyone know if this is still an issue or if a fix is available?

[Danny Wood (danwood76)]

Have you tried adding dm-raid4-5 to /etc/initramfs-tools/modules and then rebuilding the initramfs? (sudo update-initramfs -u -k all)

[Christopher Story (kc5hhq)]

I just tried that, but it does not fix my problem. I even re-installed dmraid and libdmraid with aptitude, but I am still encountering this problem. Thanks for the suggestion. Do you have any others?

[Danny Wood (danwood76)]

I have looked through the hooks and I can see there is a typo in the dmraid hook file.

Open up /usr/share/initramfs-tools/hooks/dmraid, so:
sudo gedit /usr/share/initramfs-tools/hooks/dmraid

look through that file, on line 23 it says force_load dm-raid45. This should of course be dm-raid4-5.

So if you change that to dm-raid4-5 then save it and update the initramfs with the above command it should work.
The rc14 version uses dm-raid4-5.

I am attaching a patch which will hopefully get uploaded upstream.

[Tormod Volden (tormodvolden)]

danwood76, nice catch! Some missing QA there. It would also need to be corrected in /sbin/dmraid-activate. Can you please make a debdiff for Jaunty, this should be SRU'ed as well.

[Danny Wood (danwood76)]

I will post the updated patch when I get homw from work.

kind regards,
Danny

[Christopher Story (kc5hhq)]

I tried your patch, but it did not seem to entirely fix my problem.

I am now receiving a message stating:

Checking file systems...
fsck 1.41.4
/dev/sdb: The file system size (according to the superblock) is 156528672 blocks
The physical size of the device is 73264338 blocks
Either the superblock or the partition table is likely to be corrupt!

/dev/sdb: UNEXEPECTED INCONSISTENCY; RUN fsck MANUALLY.
 (i.e., withou -a or -p options)
fsck died with exit status 4

File system check failed.

I am not sure if this is related to this bug report, but does anyone happen to know what damage a fsck will cause on a software raid array?

Thanks,
Chris

[Danny Wood (danwood76)]

You shouldnt be running fsck on the individual drives within an array but on the devices created by the raid sets.
dmraid devices are in /dev/mapper

[Christopher Story (kc5hhq)]

I ran an fsck on my actual array, but I am still encountering the same fsck error. Should any disk in the array be ignored for fsck checks, and fsck should focus on the actual array itself? Also, do you believe this is related to this bug report, or should I be looking elsewhere?

[Danny Wood (danwood76)]

Is fsck being invoked by the kernel during boot when you get this error?
If so it could be in your fstab possibly, I dont have a RAID1 array so I'm unsure if the UUIDs end up being the same for the array and the actual disks. This could be resolved by replcing UUIDs.
I dont believe this has anything to do with this bug.

[thefuzz4 (jason-hamilton)]

I can confirm that the fix provided by danwood76 corrected the problem for me and I am now running on the latest version of dmraid. Thank you very much for your help with this sir. From my end this bug is fixed. YEA!!!!!

[Tormod Volden (tormodvolden)]

Christopher, fsck is only run on the filesystems listed in /etc/fstab (and the root fs in the boot parameters, defined in /boot/grub/menu.lst) so check this first. There should be no reference to the raw devices (sda* sdb*) whatsoever. If the fs are all correctly listed by UUID the reason could be that the raw devices have not been ignored by udev. Check "ls -l /dev/disk/by-uuid" for this.

[Danny Wood (danwood76)]

Ok here is the debdiff for the two patches.

[biebel (badk666)]

Thanks! Works like a charm again now. Was getting pretty fed up with that !*#@ busybox on every boot.

[Tormod Volden (tormodvolden)]

For this to be fixed in Jaunty please follow this procedure: https://wiki.ubuntu.com/StableReleaseUpdates
The patch should normally be released and tested in Karmic first, however I don't see any dm-raid4-5 in the current Karmic kernel. So I wonder, does this raid type work for you in Karmic?

[Danny Wood (danwood76)]

I don't actually suffer from this bug (dont use RAID5), it was a mere observation due to interest.
So I cannot test in either.

[Jaroslav Sedlacek (yarda)]

I tested the patche on Jaunty and works great.
I will try to install Karmic in following days to test the situation with RAID5 in Karmic.

[Will (anon4321)]

I too can verify that this fixes my issue reported early.

Thanks.

[David Santamaría Rogado (howl)]

The problem still there, the solution is the above patch. Is simple, the module changed its name in a kernel version and someone forget to update the initramfs hook, don't know why no to make and update with the fix and close this.

[tumsuden (scott-tumsuden)]

Hi - I recently upgraded from 8.10 to 9.04 and now I am having the same problem. I would like to just do a clean install of 9.04 from scratch but I cannot do so because it will not correctly recognize my NVIDIA fakeraid RAID5 array.

Is it possible to somehow install the patch into the 9.04 Server CD via some type of slipstream process? If so, could someone tell me how to do that?

Thanks!

[Pro Methean (pro)]

Rebooted a Juanty test machine that had had a recent kernel update. Uses dmraid and a raid 10 LSI Logic SAS1068E and ended up in busybox, with same /dev/mapper file not found error.

Same bug?

[quequotion (quequotion)]

just tried this patch on a system booting from a RAID:0 which also fails.

It was no use at all.

When I installed the patched dmraid only one of the kernel's initramfs was updated, the -rt kernel. it seems update-initramfs defaults to this behavior unless i specify "-k all"

Is there any way to work out all the kinks in dmraid?

Was Karmic's dmraid updated to fix such problems? I'm about to install the package and see...

The only way I can access the broken raid is to mount it from the live cd and chroot by the way....

[quequotion (quequotion)]

also, at boot dmraid is complaining that it can't find libdl.so.2, which is apparently part of libc6 (????) which is installed... the file is at /lib/libdl.so.2.....

[Tobias Krais (tux-spam)]

Hi together,

same bug here. Still exists in Karmic Koala. Why does nobody release the fix??

Greetings, Tobias

[Tobias Krais (tux-spam)]

See this: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/358255/comments/21

[Douglas Esanbock (douglas-esanbock)]

I just downloaded Ubuntu 10.04 alternate amd64. I have an NFORCE 590 board with Raid 5. The installation fails because it can't find the dmraid45 module. I will try debugging this some more and report back. But as of now, it looks like 10.04 + nvraid = fail.

[Phillip Susi (psusi)]

This bug seems to have been in an incorrect state and ignored for some time. The original issue seems to have been fixed in recent releases so I'm going to close it. If anyone is still having issues with raid5 on 10.04 and later, please open a new bug report.

[David Santamaría Rogado (howl)]

Sometime -> 2 years.

The incorrect state seems to be a very vague excuse considering the usual way to manage the bugs in ubuntu. For example, https://bugs.launchpad.net/ubuntu/+source/mldonkey/+bug/176895 Hardy is already in support time because it's LTS state, bug marked as fixed becuase, it's fixed in intrepid, and there is no issues about the bug report itself, even more, the exact reason and the way to solve it was given by users.

[Danny Wood (danwood76)]

The reason this patch was never accepted is not because of the incorrect status.
And its no vague excuse.

It could not be tested in karmic due to there not being a dm-raid-45 module there, this is the usual backporting process which stopped the whole system as originally we missed the initial 9.04 release window.

The backports system does break sometimes and this is an example.

David we are normal users ;-)!

[Danny Wood (danwood76)]

(By backport system I meant SRU system!)

[David Santamaría Rogado (howl)]

I know that you are normal users, but, with the ability to post changes in the packages, so with users I meant that the problem was solved and the only thing to do was to apply it.

The other bug I pointed wasn't solved because the importance was low, and the effects of it were all the apps that use ocaml broken. Another reason was that the bug was solved in the next release, but hardy is even supported already. I don't participate usually in ubuntu bug reports, but, the little times I have done, have been very disappointing.

Sorry about my bad mood.