Arch Linux

zblach

Member

Registered: 2008-10-07

Posts: 23

dmraid + raid45 module

Hi,

I'm having a serious issue with arch and fakeraid 5.

dmraid requires a module called raid45. there are kernel patches for ubuntu, fedora, and the like, but not arch. I can't find anything in abs, help in the channel, or anything elsewhere. I know that this module has been replaced by raid456, but I don't know what to do from here.

attempting to boot fails to load raid45 and kicks me to ramfs.

i'm totally out of ideas. any hints from here?

-Z

itaylor

Member

From: Gainesville, FL

Registered: 2009-01-30

Posts: 5

Re: dmraid + raid45 module

Maybe try out: http://aur.archlinux.org/packages.php?ID=25654

The module has not been replaced by raid456 afaik. I don't think raid456 has anything to do with fakeraid.

Please give feedback.

mash

Member

Registered: 2012-12-02

Posts: 15

Re: dmraid + raid45 module

Hi,

I'm having the same problem.
I'm running an Intel Fake RAID5 which is unable to get activated in Arch using dmraid.
The RAID1 set on the same disks is running just fine.

Output from "dmraid -ay":

[root@s0nne mash]# dmraid -ay
RAID set "isw_dfejeicjje_Sol0" already active
ERROR: device-mapper target type "raid45" is not in the kernel
RAID set "isw_dfejeicjje_Sol1" was not activated
ERROR: device "isw_dfejeicjje_Sol0" is already being monitored
ERROR: device "isw_dfejeicjje_Sol1" could not be found
ERROR: dos: partition address past end of RAID device
RAID set "isw_dfejeicjje_Sol0p1" already active
RAID set "isw_dfejeicjje_Sol0p2" already active

The package mention by zblach is gone so i'm not sure what can be done...
Tnx for any help.

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,018

Website

Re: dmraid + raid45 module

Use mdadm, not dmraid. Make sure to add the shutdown hook to your initramfs.

---

blog | ±github

mash

Member

Registered: 2012-12-02

Posts: 15

Re: dmraid + raid45 module

Wow that was fast..

do i have to recreate the array with mdadm? I don't like to loose the data on the raid set..

That's what me mdadm gives:

[root@s0nne mash]#  mdadm --assemble --scan --verbose
mdadm: looking for devices for /dev/md/imsm0
mdadm: no RAID superblock on /dev/sdf1
mdadm: no RAID superblock on /dev/sdf
mdadm: no RAID superblock on /dev/sde1
mdadm: no RAID superblock on /dev/sde
mdadm: no RAID superblock on /dev/dm-2
mdadm: no RAID superblock on /dev/dm-1
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/sdd is busy - skipping
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdb is busy - skipping
mdadm: no RAID superblock on /dev/sda3
mdadm: no RAID superblock on /dev/sda2
mdadm: no RAID superblock on /dev/sda1
mdadm: no RAID superblock on /dev/sda
mdadm: looking for devices for /dev/md/Sol0
mdadm: Cannot assemble mbr metadata on /dev/sdf1
mdadm: Cannot assemble mbr metadata on /dev/sdf
mdadm: Cannot assemble mbr metadata on /dev/sde1
mdadm: Cannot assemble mbr metadata on /dev/sde
mdadm: Cannot assemble mbr metadata on /dev/dm-2
mdadm: Cannot assemble mbr metadata on /dev/dm-1
mdadm: Cannot assemble mbr metadata on /dev/dm-0
mdadm: /dev/sdd has wrong uuid.
mdadm: /dev/sdc has wrong uuid.
mdadm: /dev/sdb has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda3
mdadm: no recogniseable superblock on /dev/sda2
mdadm: no recogniseable superblock on /dev/sda1
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: looking for devices for /dev/md/Sol1
mdadm: Cannot assemble mbr metadata on /dev/sdf1
mdadm: Cannot assemble mbr metadata on /dev/sdf
mdadm: Cannot assemble mbr metadata on /dev/sde1
mdadm: Cannot assemble mbr metadata on /dev/sde
mdadm: Cannot assemble mbr metadata on /dev/dm-2
mdadm: Cannot assemble mbr metadata on /dev/dm-1
mdadm: Cannot assemble mbr metadata on /dev/dm-0
mdadm: /dev/sdd has wrong uuid.
mdadm: /dev/sdc has wrong uuid.
mdadm: /dev/sdb has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda3
mdadm: no recogniseable superblock on /dev/sda2
mdadm: no recogniseable superblock on /dev/sda1
mdadm: Cannot assemble mbr metadata on /dev/sda

Last edited by mash (2012-12-02 19:04:58)

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,018

Website

Re: dmraid + raid45 module

No idea how fakeraid with mdadm works -- i just know that your array should support it, and dmraid is dead.

https://bugs.archlinux.org/task/31236

---

blog | ±github

mash

Member

Registered: 2012-12-02

Posts: 15

Re: dmraid + raid45 module

I checked the boot log via journalctl -b and although i removed the dmraid package it looks like the device-mapper (where ever this is coming from) still needs this module to load that device...

Dec 03 00:36:09 s0nne kernel: device-mapper: table: 254:1: raid45: unknown target type
Dec 03 00:36:09 s0nne kernel: device-mapper: ioctl: error adding target to table

maybe that's the reason why the device keeps being busy

later in the process I see this (not sure whether this is related):

Dec 03 00:36:09 s0nne systemd-udevd[242]: '/usr/bin/multipath -c /dev/sda' [299] terminated by signal 11 (Segmentation fault)
Dec 03 00:36:09 s0nne systemd-coredump[300]: Process 299 (multipath) dumped core.
Dec 03 00:36:09 s0nne systemd-udevd[302]: failed to execute '/usr/lib/udev/socket:/org/kernel/dm/multipath_event' 'socket:/org/kernel/dm/multipath_event': No such file or directory
Dec 03 00:36:09 s0nne systemd-udevd[236]: '/usr/bin/multipath -c /dev/sdf' [306] terminated by signal 11 (Segmentation fault)
Dec 03 00:36:09 s0nne systemd-coredump[308]: Process 306 (multipath) dumped core.
Dec 03 00:36:09 s0nne systemd-udevd[251]: '/usr/bin/multipath -c /dev/sdd' [307] terminated by signal 11 (Segmentation fault)
Dec 03 00:36:09 s0nne systemd-coredump[309]: Process 307 (multipath) dumped core.
Dec 03 00:36:09 s0nne systemd-udevd[239]: '/usr/bin/multipath -c /dev/sdb' [310] terminated by signal 11 (Segmentation fault)
Dec 03 00:36:09 s0nne systemd-coredump[311]: Process 310 (multipath) dumped core.
Dec 03 00:36:09 s0nne systemd-udevd[276]: '/usr/bin/multipath -c /dev/sdc' [313] terminated by signal 11 (Segmentation fault)
Dec 03 00:36:09 s0nne systemd-coredump[314]: Process 313 (multipath) dumped core.
Dec 03 00:36:09 s0nne systemd-udevd[316]: failed to execute '/usr/lib/udev/socket:/org/kernel/dm/multipath_event' 'socket:/org/kernel/dm/multipath_event': No such file or directory
Dec 03 00:36:09 s0nne systemd-udevd[319]: failed to execute '/usr/lib/udev/socket:/org/kernel/dm/multipath_event' 'socket:/org/kernel/dm/multipath_event': No such file or directory
Dec 03 00:36:09 s0nne systemd-udevd[242]: '/usr/bin/multipath -c /dev/dm-0' [333] terminated by signal 11 (Segmentation fault)
Dec 03 00:36:09 s0nne systemd-udevd[237]: '/usr/bin/multipath -c /dev/dm-1' [334] terminated by signal 11 (Segmentation fault)
Dec 03 00:36:09 s0nne systemd-coredump[337]: Process 333 (multipath) dumped core.
Dec 03 00:36:09 s0nne systemd-coredump[332]: Process 331 (multipath) dumped core.
Dec 03 00:36:09 s0nne systemd-coredump[336]: Process 335 (multipath) dumped core.
Dec 03 00:36:10 s0nne systemd-coredump[339]: Process 334 (multipath) dumped core.

Any idea what I can do?

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,018

Website

Re: dmraid + raid45 module

remove multipath-tools.

---

blog | ±github

mash

Member

Registered: 2012-12-02

Posts: 15

Re: dmraid + raid45 module

That did change nothing.. :-/

Same boot messages..
Same message when trying to rebuild the Array..

lsblk gives me:

[root@s0nne mash]# lsblk
NAME                             MAJ:MIN RM   SIZE RO TYPE   MOUNTPOINT
sda                                8:0    0 238.5G  0 disk   
|-sda1                             8:1    0     4G  0 part   [SWAP]
|-sda2                             8:2    0 234.5G  0 part   /
`-sda3                             8:3    0  1007K  0 part   
sdb                                8:16   0   1.4T  0 disk   
`-isw_dfejeicjje_Sol0 (dm-0)     254:0    0   256G  0 dmraid 
  |-isw_dfejeicjje_Sol0p1 (dm-1) 254:1    0   156G  0 dmraid 
  `-isw_dfejeicjje_Sol0p2 (dm-2) 254:2    0   100M  0 dmraid 
sdc                                8:32   0   1.4T  0 disk   
`-isw_dfejeicjje_Sol0 (dm-0)     254:0    0   256G  0 dmraid 
  |-isw_dfejeicjje_Sol0p1 (dm-1) 254:1    0   156G  0 dmraid 
  `-isw_dfejeicjje_Sol0p2 (dm-2) 254:2    0   100M  0 dmraid 
sdd                                8:48   0   1.4T  0 disk   
`-isw_dfejeicjje_Sol0 (dm-0)     254:0    0   256G  0 dmraid 
  |-isw_dfejeicjje_Sol0p1 (dm-1) 254:1    0   156G  0 dmraid 
  `-isw_dfejeicjje_Sol0p2 (dm-2) 254:2    0   100M  0 dmraid 
sde                                8:64   1   7.6G  0 disk   
`-sde1                             8:65   1   7.6G  0 part   /run/media/mash/28021E6C021E3F6E

[root@s0nne mash]# pacman -R dmraid
error: target not found: dmraid

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,018

Website

Re: dmraid + raid45 module

Check your initramfs for the dmraid hook.

---

blog | ±github

mash

Member

Registered: 2012-12-02

Posts: 15

Re: dmraid + raid45 module

Ok next try..

removed dmraid from /etc/mkinitcpio.conf
rebuild the image with mkinitcpio -p linux

error message from device-mapper is gone.. (check.. )

still the devices are busy:

mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/sdc1
mdadm: no RAID superblock on /dev/md/Sol0p7
mdadm: no RAID superblock on /dev/md/Sol0p6
mdadm: no RAID superblock on /dev/md/Sol0p5
mdadm: no RAID superblock on /dev/md/Sol0p3
mdadm: no RAID superblock on /dev/md/Sol0p2
mdadm: no RAID superblock on /dev/md/Sol0p1
mdadm: no RAID superblock on /dev/md/Sol0
mdadm: no RAID superblock on /dev/sde1
mdadm: no RAID superblock on /dev/sde
mdadm: no RAID superblock on /dev/md/sol1p2
mdadm: no RAID superblock on /dev/md/sol1p1
mdadm: no RAID superblock on /dev/md/sol1
mdadm: /dev/sdd is busy - skipping
mdadm: no RAID superblock on /dev/sdc3
mdadm: no RAID superblock on /dev/sdc2
mdadm: no RAID superblock on /dev/sdc1
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdb is busy - skipping
mdadm: no RAID superblock on /dev/sda3
mdadm: no RAID superblock on /dev/sda2
mdadm: no RAID superblock on /dev/sda1
mdadm: no RAID superblock on /dev/sda
mdadm: looking for devices for /dev/md/Sol0
mdadm: no recogniseable superblock on /dev/sdc1
mdadm: no recogniseable superblock on /dev/md/Sol0p7
mdadm: no recogniseable superblock on /dev/md/Sol0p6
mdadm: no recogniseable superblock on /dev/md/Sol0p5
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0p3
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0p2
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0p1
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0
mdadm: Cannot assemble mbr metadata on /dev/sde1
mdadm: Cannot assemble mbr metadata on /dev/sde
mdadm: Cannot assemble mbr metadata on /dev/md/sol1p2
mdadm: no recogniseable superblock on /dev/md/sol1p1
mdadm: Cannot assemble mbr metadata on /dev/md/sol1
mdadm: /dev/sdd has wrong uuid.
mdadm: no recogniseable superblock on /dev/sdc3
mdadm: no recogniseable superblock on /dev/sdc2
mdadm: no recogniseable superblock on /dev/sdc1
mdadm: /dev/sdc has wrong uuid.
mdadm: /dev/sdb has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda3
mdadm: no recogniseable superblock on /dev/sda2
mdadm: no recogniseable superblock on /dev/sda1
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: looking for devices for /dev/md/sol1
mdadm: no recogniseable superblock on /dev/sdc1
mdadm: no recogniseable superblock on /dev/md/Sol0p7
mdadm: no recogniseable superblock on /dev/md/Sol0p6
mdadm: no recogniseable superblock on /dev/md/Sol0p5
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0p3
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0p2
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0p1
mdadm: Cannot assemble mbr metadata on /dev/md/Sol0
mdadm: Cannot assemble mbr metadata on /dev/sde1
mdadm: Cannot assemble mbr metadata on /dev/sde
mdadm: Cannot assemble mbr metadata on /dev/md/sol1p2
mdadm: no recogniseable superblock on /dev/md/sol1p1
mdadm: Cannot assemble mbr metadata on /dev/md/sol1
mdadm: /dev/sdd has wrong uuid.
mdadm: no recogniseable superblock on /dev/sdc3
mdadm: no recogniseable superblock on /dev/sdc2
mdadm: no recogniseable superblock on /dev/sdc1
mdadm: /dev/sdc has wrong uuid.
mdadm: /dev/sdb has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda3
mdadm: no recogniseable superblock on /dev/sda2
mdadm: no recogniseable superblock on /dev/sda1
mdadm: Cannot assemble mbr metadata on /dev/sda

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,018

Website

Re: dmraid + raid45 module

You don't need to assemble anything manually -- mdadm does it for you via udev rules. I see partitioned MD devices in your output.

---

blog | ±github

mash

Member

Registered: 2012-12-02

Posts: 15

Re: dmraid + raid45 module

Thank you so much! It works now - the busy stuff resulted from the already working config..