On Mon, 9 Jan 2017 20:35:16 +0300, Andrei Borzenkov wrote:
$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/
I tried to upload the output from journalctl -b to susepaste.org but the site haven't accepted it. I guess it's too much to paste in. The whole log file is ~1 MB and it contains 11678 lines. I have sent the log to your email too, I don't know if you've received it.
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.
I have uploaded it to susepaste.org: http://susepaste.org/02e27f89 Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org