[solved] dmraid raid1 failed with "could not be found"

_pheinrich_ · 2015-12-29 10:50:17

Hi,

I have set up Arch linux in EFI mode with my Asus P8H77m-le mainboard.
Arch linux is up and running on my SSD drive.

Now I want to create an backup Raid1 with to old Seagate 80GB HDD's (for testing only).
The Raid1 is created via the UEFI Bios Manager.

/dev/mapper/ shows "control" only

Booting the Arch linux shows me this on lsblk

NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda       8:0    0  74,5G  0 disk
└─md126   9:126  0  74,5G  0 raid1
sdb       8:16   0  74,5G  0 disk
└─md126   9:126  0  74,5G  0 raid1
sdc       8:32   0 111,8G  0 disk
├─sdc1    8:33   0     1G  0 part  /boot
└─sdc2    8:34   0 110,8G  0 part  /

sda and sdb are the raid drives. Now I need to rum "dmraid -ay" to active the raid but this fails. Here some debug output.

[root@ARCH_MEDIA ~]# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 (rev c4)
00:1c.6 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation H77 Express Chipset LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09)
04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
05:00.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)

[root@ARCH_MEDIA ~]# dmraid -r
/dev/sdb: isw, "isw_ciggccdjch", GROUP, ok, 156301486 sectors, data@ 0
/dev/sda: isw, "isw_ciggccdjch", GROUP, ok, 156301486 sectors, data@ 0
[root@ARCH_MEDIA ~]# dmraid -l
asr     : Adaptec HostRAID ASR (0,1,10)
ddf1    : SNIA DDF1 (0,1,4,5,linear)
hpt37x  : Highpoint HPT37X (S,0,1,10,01)
hpt45x  : Highpoint HPT45X (S,0,1,10)
isw     : Intel Software RAID (0,1,5,01)
jmicron : JMicron ATARAID (S,0,1)
lsi     : LSI Logic MegaRAID (0,1,10)
nvidia  : NVidia RAID (S,0,1,10,5)
pdc     : Promise FastTrack (S,0,1,10)
sil     : Silicon Image(tm) Medley(tm) (0,1,10)
via     : VIA Software RAID (S,0,1,10)
dos     : DOS partitions on SW RAIDs

and the failing command with debug outout

[root@ARCH_MEDIA ~]# 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: 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: isw metadata discovered
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_ciggccdjch
DEBUG: _find_set: not found isw_ciggccdjch
DEBUG: _find_set: searching isw_ciggccdjch_DATA_MIRROR
DEBUG: _find_set: searching isw_ciggccdjch_DATA_MIRROR
DEBUG: _find_set: not found isw_ciggccdjch_DATA_MIRROR
DEBUG: _find_set: not found isw_ciggccdjch_DATA_MIRROR
NOTICE: added /dev/sdb to RAID set "isw_ciggccdjch"
DEBUG: _find_set: searching isw_ciggccdjch
DEBUG: _find_set: found isw_ciggccdjch
DEBUG: _find_set: searching isw_ciggccdjch_DATA_MIRROR
DEBUG: _find_set: searching isw_ciggccdjch_DATA_MIRROR
DEBUG: _find_set: found isw_ciggccdjch_DATA_MIRROR
DEBUG: _find_set: found isw_ciggccdjch_DATA_MIRROR
NOTICE: added /dev/sda to RAID set "isw_ciggccdjch"
DEBUG: set status of set "isw_ciggccdjch_DATA_MIRROR" to 16
RAID set "isw_ciggccdjch_DATA_MIRROR" was not activated
ERROR: device "isw_ciggccdjch_DATA_MIRROR" could not be found
INFO: Activating GROUP raid set "isw_ciggccdjch"
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "isw_ciggccdjch_DATA_MIRROR"
DEBUG: freeing device "isw_ciggccdjch_DATA_MIRROR", path "/dev/sda"
DEBUG: freeing device "isw_ciggccdjch_DATA_MIRROR", path "/dev/sdb"
DEBUG: freeing devices of RAID set "isw_ciggccdjch"
DEBUG: freeing device "isw_ciggccdjch", path "/dev/sda"
DEBUG: freeing device "isw_ciggccdjch", path "/dev/sdb"

Here is the dmesg output right after dmraid

[ 2329.469664] device-mapper: table: 253:0: mirror: Device lookup failure
[ 2329.470037] device-mapper: ioctl: error adding target to table
[ 2454.523589] r8169 0000:03:00.0 enp3s0: link down
[ 2454.523627] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 2454.523636] r8169 0000:03:00.0 enp3s0: link down
[ 2456.715790] r8169 0000:03:00.0 enp3s0: link up
[ 2456.715796] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 2734.416855] device-mapper: table: 253:0: mirror: Device lookup failure
[ 2734.417687] device-mapper: ioctl: error adding target to table
[ 2751.719147] device-mapper: table: 253:0: mirror: Device lookup failure
[ 2751.720035] device-mapper: ioctl: error adding target to table
[ 3084.960975] device-mapper: table: 253:0: mirror: Device lookup failure
[ 3084.961818] device-mapper: ioctl: error adding target to table

I have no idea why "Device lookup failure" appears ... maybe broken hardware ?!?

Last edited by _pheinrich_ (2015-12-29 11:32:54)

tom.ty89 · 2015-12-29 10:52:45

Why dmraid instead of mdadm?

_pheinrich_ · 2015-12-29 10:58:01

mdadm is for software raid managed by the os, right?

That whould be an option but I want to give dmraid(fakeraid) a try.

Last edited by _pheinrich_ (2015-12-29 10:58:22)

tom.ty89 · 2015-12-29 11:06:07

Nope. It has (better) support for fake raid for quite a while. Especially Intel fake raid.

P.S. dmraid is last updated upstream in 2010...

Last edited by tom.ty89 (2015-12-29 11:09:24)

_pheinrich_ · 2015-12-29 11:18:08

Yes I have seen that

And I have read something that mdadm will replace dmraid or include its functionality.

But if I have a look to https://wiki.archlinux.org/index.php/RA … he_Devices it seems that I always have to create an new array with mdadm?
I want to use the pre configured Array in my BIOS setup.

Is that not possible with mdadm? Do I have to switch to software raid then.
As you said in you post before it should be possible

tom.ty89 · 2015-12-29 11:22:29

No I think you can simply include the mdadm_udev hook in mkinitcpio.conf and regen initramfs, then everything should work automagically after a reboot.

Last edited by tom.ty89 (2015-12-29 11:24:45)

_pheinrich_ · 2015-12-29 11:32:35

Nice one

Raid Volume shows up under /dev/md/DATA_MIRROR_0

Arch Linux

#1 2015-12-29 10:50:17

[solved] dmraid raid1 failed with "could not be found"

#2 2015-12-29 10:52:45

Re: [solved] dmraid raid1 failed with "could not be found"

#3 2015-12-29 10:58:01

Re: [solved] dmraid raid1 failed with "could not be found"

#4 2015-12-29 11:06:07

Re: [solved] dmraid raid1 failed with "could not be found"

#5 2015-12-29 11:18:08

Re: [solved] dmraid raid1 failed with "could not be found"

#6 2015-12-29 11:22:29

Re: [solved] dmraid raid1 failed with "could not be found"

#7 2015-12-29 11:32:35

Re: [solved] dmraid raid1 failed with "could not be found"

Board footer