Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 509646

Summary: XEN Dom0 + imsm + mdadm + efi
Product: Gentoo Linux Reporter: Garry Filakhtov <filakhtov>
Component: [OLD] Core systemAssignee: Garry Filakhtov <filakhtov>
Status: RESOLVED INVALID    
Severity: major CC: filakhtov
Priority: Normal    
Version: autobuilds   
Hardware: AMD64   
OS: Linux   
Whiteboard: imsm, mdadm, xen, hvm, dom0, efi
Package list:
Runtime testing required: ---

Description Garry Filakhtov 2014-05-05 21:13:18 UTC
I'm running Gentoo with 3.12.13 kernel.
Booting done via EFI Kernel Stub, without bootloader.
I have 4 disks in firmware RAID5 (Intel IMSM). Assemble done using mdadm inside initrd.
Regular system boot works just fine.

I need to setup XEN HVM.
Using XEN 4.3.1

Problems starts when I'm trying to boot system with xen-4.3.1.efi
Kernel boot ok, until it actually reaches mdadm assembly.
"mdadm --assemble --scan" Returns:
mdadm: no arrays found in config file or automatically

I have tried a lot of different methods - no luck:
Tried to add /etc/mdadm.conf to initrd
Tried to assemble array manually
Tried to precreate nodes

dmesg in xen contains absolutely no info about md support (as if it is disabled it in kernel, but same kernel boots okay w/o xen.efi)
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-05-05 22:06:08 UTC
This is a bug tracker, not a support forum. If you have a problem and want support, use our forums, IRC channels and mailing lists. If you have found a bug, report it here.
Comment 2 Garry Filakhtov 2014-05-05 23:23:27 UTC
(In reply to Jeroen Roovers from comment #1)
> This is a bug tracker, not a support forum. If you have a problem and want
> support, use our forums, IRC channels and mailing lists. If you have found a
> bug, report it here.

This is actually bug, as I assume in app-emulation/xen.
During boot w/ XEN, dmesg missing info abour RAID:

[    0.854639] md: md127 stopped.
[    0.855724] md: bind<sdc>
[    0.855763] md: bind<sdb>
[    0.855795] md: bind<sda>
[    0.855833] md: bind<sdd>
[    0.874157] md: md126 stopped.
[    0.874210] md: bind<sdd>
[    0.874244] md: bind<sdc>
[    0.874273] md: bind<sdb>
[    0.874302] md: bind<sda>
[    0.874494] md/raid:md126: device sda operational as raid disk 0
[    0.874495] md/raid:md126: device sdb operational as raid disk 1
[    0.874496] md/raid:md126: device sdc operational as raid disk 2
[    0.874496] md/raid:md126: device sdd operational as raid disk 3
[    0.874657] md/raid:md126: allocated 4332kB
[    0.874722] md/raid:md126: raid level 5 active with 4 out of 4 devices, algorithm 0
[    0.874723] RAID conf printout:
[    0.874723]  --- level:5 rd:4 wd:4
[    0.874724]  disk 0, o:1, dev:sda
[    0.874725]  disk 1, o:1, dev:sdb
[    0.874725]  disk 2, o:1, dev:sdc
[    0.874726]  disk 3, o:1, dev:sdd
[    0.874735] md126: detected capacity change from 0 to 750170144768
[    0.874750] RAID conf printout:
[    0.874752]  --- level:5 rd:4 wd:4
[    0.874753]  disk 0, o:1, dev:sda
[    0.874753]  disk 1, o:1, dev:sdb
[    0.874754]  disk 2, o:1, dev:sdc
[    0.874755]  disk 3, o:1, dev:sdd
[    0.878857] md: md126 switched to read-write mode.
[    0.878863] RAID conf printout:
[    0.878865]  --- level:5 rd:4 wd:4
[    0.878866]  disk 0, o:1, dev:sda
[    0.878867]  disk 1, o:1, dev:sdb
[    0.878868]  disk 2, o:1, dev:sdc
[    0.878868]  disk 3, o:1, dev:sdd
[    0.914597]  md126: p1 p2 p3 p4