Boot is taking forever (systemd-fsck?)

Hund · 2013-02-10 00:16:03

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?

henk · 2013-02-10 06:20:02

Have you checked if your cpu supports virtualization?

https://wiki.archlinux.org/index.php/KVM

Hund · 2013-02-10 13:29:24

I guess it does. I got the Intel i5 2500K CPU. But I dont use it. Is it really relevant to my problem though?

Edit: I enabled the KVM option in BIOS and got rid of that messagea ateast. The origninal problem still exists.

Last edited by Hund (2013-02-10 13:53:26)

henk · 2013-02-10 20:22:30

Hund wrote:

got rid of that messagea ateast. The origninal problem still exists.

got rid of what??
I suppose the original problem is is the fact dat the boot proces stops for some minutes.
Maybe you should look at your boot log.

Last edited by henk (2013-02-10 20:23:04)

Hund · 2013-02-11 15:04:10

henk wrote:

Hund wrote:
got rid of that messagea ateast. The origninal problem still exists.
got rid of what??
I suppose the original problem is is the fact dat the boot proces stops for some minutes.
Maybe you should look at your boot log.

The kvm message.

lucke · 2013-02-11 15:27:08

Do you have quiet in the kernel line of your bootloader? If yes, then remove it and see where the boot stalls.

Hund · 2013-02-13 00:30:18

No, I dont.

# /dev/sda1
UUID=6b87ab54-bb70-4173-9a83-ecd739960d6f       /               ext4            rw,relatime,data=ordered,discard,noatime        0 1

jasonwryan · 2013-02-13 00:36:14

That's your fstab, not your kernel line in your {grub,syslinux,efistub} conf...

Hund · 2013-02-13 00:40:34

jasonwryan wrote:

That's your fstab, not your kernel line in your {grub,syslinux,efistub} conf...

lol, Im tired. Its the middle in the night here.

Im removing it and we'll se what happens.

Hund · 2013-02-13 00:50:26

I got to see some more messages about the boot as I expected, but it didnt solve my issue.

WonderWoofy · 2013-02-13 01:00:19

Why would removing quiet ever solve your issue? The idea was simply to give you more information as to why this might be happening. You might also want to look at the journal and find this delay and see what these logs tell you.

Hund · 2013-02-13 01:03:06

WonderWoofy wrote:

Why would removing quiet ever solve your issue? The idea was simply to give you more information as to why this might be happening. You might also want to look at the journal and find this delay and see what these logs tell you.

I misread it. It all makes sense now. It didnt show me any useful info anyway, the last entry was just "[ OK ] Reached target Sound Card.".

Is there anyway to disable the fsck check at every boot? Its just annoying anyway.

WonderWoofy · 2013-02-13 01:06:46

That is a really bad idea... but I would imagine if you mask the service it might stop it... or it might render your system borked... I dunno.

Hund · 2013-02-13 01:09:51

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.

Last edited by Hund (2013-02-13 01:11:33)

jasonwryan · 2013-02-13 02:02:02

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.

WonderWoofy · 2013-02-13 03:22:08

Yes, i find systemd quite great actually. I am sorry that your incompetence or lack of willingness to read the great documentation is holding you back. As jasonwryan has indicated, there are a number of other distributions that offer non systemd environments. I would recommend gentoo, as that is where many of our past anti-systemd users went after the change, but if you are struggling this much with Arch, I am sure that use flags will surely frustrate you more.

Hund · 2013-02-13 03:43:29

WonderWoofy wrote:

Yes, i find systemd quite great actually. I am sorry that your incompetence or lack of willingness to read the great documentation is holding you back. As jasonwryan has indicated, there are a number of other distributions that offer non systemd environments. I would recommend gentoo, as that is where many of our past anti-systemd users went after the change, but if you are struggling this much with Arch, I am sure that use flags will surely frustrate you more.

I probably rewrote this post 5 times. I only came up with 5 reasons to get me banned. But Im not gonna give you that.

I just wanna say Im tired of kids trolling like you. If you knew who I am, you wouldn't question my knowledge.

Have fun ruin the Arch community kido! Im out.

The Solutor · 2013-02-13 11:14:07

WonderWoofy wrote:

Yes, i find systemd quite great actually. I am sorry that your incompetence or lack of willingness to read the great documentation is holding you back. As jasonwryan has indicated, there are a number of other distributions that offer non systemd environments. I would recommend gentoo, as that is where many of our past anti-systemd users went after the change, but if you are struggling this much with Arch, I am sure that use flags will surely frustrate you more.

Is not so complicate, openrc is working already fine on arch, surely the result is worth the time spent reading the related thread in the AUR room.

Arch Linux

#1 2013-02-10 00:16:03

Boot is taking forever (systemd-fsck?)

#2 2013-02-10 06:20:02

Re: Boot is taking forever (systemd-fsck?)

#3 2013-02-10 13:29:24

Re: Boot is taking forever (systemd-fsck?)

#4 2013-02-10 20:22:30

Re: Boot is taking forever (systemd-fsck?)

#5 2013-02-11 15:04:10

Re: Boot is taking forever (systemd-fsck?)

#6 2013-02-11 15:27:08

Re: Boot is taking forever (systemd-fsck?)

#7 2013-02-13 00:30:18

Re: Boot is taking forever (systemd-fsck?)

#8 2013-02-13 00:36:14

Re: Boot is taking forever (systemd-fsck?)

#9 2013-02-13 00:40:34

Re: Boot is taking forever (systemd-fsck?)

#10 2013-02-13 00:50:26

Re: Boot is taking forever (systemd-fsck?)

#11 2013-02-13 01:00:19

Re: Boot is taking forever (systemd-fsck?)

#12 2013-02-13 01:03:06

Re: Boot is taking forever (systemd-fsck?)

#13 2013-02-13 01:06:46

Re: Boot is taking forever (systemd-fsck?)

#14 2013-02-13 01:09:51

Re: Boot is taking forever (systemd-fsck?)

#15 2013-02-13 02:02:02

Re: Boot is taking forever (systemd-fsck?)

#16 2013-02-13 03:22:08

Re: Boot is taking forever (systemd-fsck?)

#17 2013-02-13 03:43:29

Re: Boot is taking forever (systemd-fsck?)

#18 2013-02-13 11:14:07

Re: Boot is taking forever (systemd-fsck?)

Board footer