Boot is taking forever (systemd-fsck?)

Question

Im sorry for the bad topic.
When I boot Arch it stops and shows me this message for about 5 minutes or so (It feels like forever):
/dev/sda1: clean, 113567/640848 files, 662474/2561272 blocks
[ 1.582745] kvm: disabled by bios
systemd-fsck[242]: /dev/sda2: clean, 90976/640848 files, 505908/2558464 blocks
I dual boot with Windows and I reboot my computer on a daily basis (Im a gamer) so its driving me crazy.
I have googled it and read a bunch of topics for the past three days now.. Whats wrong?

Answer 1

Hund wrote:
Bah.. Whats up with the systemd thingy anyway? Whats the benefits with it? So far Ive just seen a bunch of bugs. Arch used to work flawless for me, but ever since the switch to systemd it all went south. Boot hangs, shutdown hangs, no network at boot and autmounting my Samba share doesnt work.. Yay!
Edit: Atleast I solved the network at boot a few days ago. But I have no idea how I did it tbh.. Arch used to be so simple! But now with this systemd piece of shit? Its a mess.
The experience of most people is that sysytemd has introduced benefits; most of the issues that you are describing are probably fixable by some simple configuration changes.
In any event, we have grown rather tired of the petulant "systemd is a piece of shit"-type rants that a minority feel compelled to vent; please don't bother. If you don't like it, install something else.
FWIW: anyone who starts a sentence about a rolling release with a fond nostalgia for the past is clearly deluding themselves; change is at the core of Arch, deal with it.