Thanks Martin, here it is. http://sprunge.us/gfHW I suspect something goes wrong at shutdown. since i see running jobs runnig related to the lvm attached bellow. http://sprunge.us/efbg Alin On Thursday, 5 January 2017 20:43:02 GMT Martin Wilck wrote:
On Tue, 2017-01-03 at 17:35 +0000, Alin M Elena wrote:
The same setup as mine and the same problem after the update. however i think the solution is just a coincidence since I had both packages installed already.
WHat I have noticed howeever is that I get two jobs running one for udev (udev-settle) with a limit of 180s and the one for lvm activation of 90s.
now i speculate that whatever settle is doing has effect on lvm activation and is not finished in the 90s. I reduced the time in settle to 70s and after approx 2min i have the login screen up without the emergency systemd.
systemd-analyze blame 1min 50.210s lvm2-activation-net.service 1min 10.197s systemd-udev-settle.service 8.664s systemd-cryptsetup@cr_nvme \x2d2002538435b1b37d4\x2dpart2.service
my understanding is this can be cause by many things so once i get more time I may dig more.
lvm2-activation-net.service runs "vgchange -aay" after activation of "remote" (iscsi and fcoe) block devices. If this service hangs for so long, you may be facing some problem with one ore more devices not responding (not necessarily iscsi or fcoe devices). The fact that udev settle takes so long probably has a similar reason. You may want to paste "journalctl -ab" output somewhere.
Martin
-- Without Questions there are no Answers! _______________________________________ Dr. Alin Marin ELENA http://alin.elena.space/ _______________________________________