On Mon, 9 Jan 2017 16:21:34 +0300, Andrei Borzenkov wrote:
On Mon, Jan 9, 2017 at 4:12 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Mon, Jan 9, 2017 at 3:38 PM, Istvan Gabor <suseuser04@gmail.hu> wrote:
How can I start md service in Leap 42.2?
MD devices are expected tp be assembled incrementally by udev rules. See /usr/lib/udev/rules.d/64-md-raid-assembly.rules. Try commands from these rules manually.
I looked at 64-md-raid-assembly.rules file but I don't know how to manually run the commands. I guess this is the command you mean: /sbin/mdadm --incremental --export $devnode --offroot ${DEVLINKS} I don't know what to take for $devnode and ${DEVLINKS}. I found that /dev/disk/by-uuid has only a few devices. It should have much more.
If commands work, it probably means for some reason rules are not applied, in which case booting with "udev.debug"
This is udev.log-priority=debug, sorry.
(and omitting "quiet" to be sure) on kernel command line may provide some hints.
OK, I booted with this kernel parameter. What to look for? And a very strange thing happened. I ran cfdisk. When I exited cfdisk (without writing anything) a lot of md devices have been created but only having one disk of the arrays: # cat /proc/mdstat Personalities : md6 : inactive sdb6[3](S) 20972752 blocks super 1.0 md7 : inactive sdb7[3](S) 31455164 blocks super 1.0 unused devices: <none /dev/disk/by-uuid has been populated too. What next? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org