On Sat, 1 Jul 2017 14:44:19 +0300, Andrei Borzenkov wrote:
01.07.2017 13:03, Istvan Gabor пишет:
On Sat, 1 Jul 2017 09:31:10 +0300, Andrei Borzenkov wrote:
01.07.2017 01:56, Istvan Gabor пишет:
Hello:
I have installed openSUSE Leap 42.2 on a standalone hard disk. Then I connected to the system 2 other hard disks which have several raid 1 (mirror) arrays. When I boot Leap 42.2 it doesn't activate the raid arrays. How can I enable raid (mdraid) in Leap 42.2?
What is the content of /etc/mdadm.conf?
There is no /etc/mdadm.conf file yet. In this case I would expect that the raid devices are assembled with default names like md127 md126 etc.
Yes, me too. Quickly testing in VM - it does assemble array without mdadm.conf (foreign devices are assembled in auto-read-only mode).
And --detail --scan outputs nothing.
# mdadm --detail --scan #
It seems to me that mdadm service is not running.
There is no such thing as "mdadm service".
OK, I understand. What triggers then recognition and assembly of the arrays at boot? Wols writes that kernel boot parameters and grub but I never edited them. You wrote earlier that is should be fully automatic by udev rules. Might this be an udev issue, similar I had before? https://lists.opensuse.org/opensuse/2017-01/msg00438.html This time it's better, because at least mdadm.conf triggers array assembly. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org