Even more fun.
I boot to emergency.
Manually start each local-fs.target.wants/* then local-fs.target
It waits a long tome for something, then it "works" but does not mount my lvm filesystems.
I try again for default.target, and this time local-fs.target fails with a dependency, and the system hangs again.
syslog is not available at the time of the hang.
What ever is the first fail, is lost when the console scrolls.
I's looking a lot like I must do a full reinstall of this system.

I believe DBelton is correct about it probably being an 'fsck' pause (I wish plymouth would show some type of indicators). You could try either hitting <ESC> (that usually switches back and forth between plymouth & a console screen) or hitting <Tab> during grub's boot screen, and editing the boot line to remove (temporarily) rhgb (which will show you the 'old style' boot screen, with various messages).

It is a warning that is telling you that the hardware doesn't exist, which would make a lot of sense. The VIA Padlock Security Engine is only on VIA x86 processors. Do you have a VIA processor in your machine?