09.01.2017 18:07, Istvan Gabor пишет:
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}.
$devnode is name of device that is being scanned (i.e. array component). $DEVLINKS is list of device aliases.
I found that /dev/disk/by-uuid has only a few devices. It should have much more.
It really sounds like some udev problem.
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?
Upload output of "journalctl -b" somewhere, e.g. http://susepaste.org/
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:
Well, cfdisk likely triggered rescan of devices that in turn triggered events and udev processed them. Why only for half of components is a good question.
# 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?
mdadm --examine --scan -vv in addition to journalctl output would be good. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org