On Fri, Jan 11, 2019 at 02:03:44PM +1300, Richard Hector wrote:
According to dmesg, this is where it appears to hang:
[ 2.717311] device-mapper: uevent: version 1.0.3
[ 2.717398] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23)
initialised: dm-d
e...@redhat.com
[ 2.978281] clocksource: Switched to clocksource tsc
[ 121.459392] md: linear personality registered for level -1
[ 121.460391] md: multipath personality registered for level -4
[ 121.461444] md: raid0 personality registered for level 0
dmesg is the wrong tool for this, as it only shows kernel messages and
the delay is probably not in the kernel. try "journalctl -b", which will
show both kernel messages and other logs for the current boot.