You are not logged in.
I am having issues after the last update. First, I made a mistake of holding back the filesystem package. Because of this (at least I think so) I was having an error that said it could not boot because at boot it said "/sbin/init does not exist". I solved this by upgrading the filesystem package by chrooting from a live arch usb. Now I am having an issue where my system hangs at boot, I believe it is right after systemd runs fsck although I might be wrong. But after maybe 5 minutes it just starts as usual... my ususal boot time is less than a minute. What should I do?
This is from a thread i accidentally hijacked:
Try systemctl --failed and or examine the journal for clues.
Post fstab. Are all of the disks referred to there available when you boot? If systemd can't find them, it will basically wait until it times out and I think that's about 5 minutes and then it will continue booting (assuming it isn't missing anything critical, of course).
My fstab:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda6
UUID=5dc84b70-a9f9-42eb-981c-40e84f7e9e75 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda6
UUID=5dc84b70-a9f9-42eb-981c-40e84f7e9e75 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda5
UUID=f7bccd4f-4b47-4dbb-a8f8-d8e374bb9867 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda7
UUID=07dcd099-50c4-4c35-a102-10a39b74ac0b none swap defaults 0 0
Would deleting the second /dev/sda6 fix it?
Last edited by life_enjoyer (2013-06-10 20:24:14)
A R C H
R
C
H
Offline
Output of systemctl --failed:
0 loaded units listed. pass --all to see loaded but inactive units, too.
A R C H
R
C
H
Offline
I don't know if deleting the second sda6 will fix it but it surely can't hurt. Why do you have it twice?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I don't know if it would cause this problem, but your root partition should not be listed twice in fstab. Do you also have a boot partition, or is that also on sda6?
EDIT: also, why do you describe the boot hand as where you "believe" it is? What are the last boot messages you see?
Last edited by Trilby (2013-06-08 02:18:23)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
You say that you cannot boot because /sbin/init cannot be found. Of late, this is a result of people fudging up the filesystem update. That is, they do the first few steps, but not the last one. But then you go on to say something about your fstab and then give the "output" of "systemctl --failed". Where are you getting this systemctl output from if your system is not booting. Sometimes people get confused, thinking that not getting to the graphical interface is not booting, but in your case a failure to find /sbin/init will really not boot.
So what is it that you are actually experiencing... you are causing great confusion I think... at least in my head.
Offline
Deleting the second entry didnt solve it. Sorry for the uncertainty I was lazy to restart and was going off of memory... it hangs right after:
systemd-fsck[214]: /dev/sda5: clean, (block and file numbers go here)
WonderWoofy, did you read my whole post?
I said I think i fixed the first issue and now it boots but really slowly
Last edited by life_enjoyer (2013-06-08 03:18:29)
A R C H
R
C
H
Offline
I did now.... sorry about that.
Offline
Also no, i do not have a separate /boot partition...
A R C H
R
C
H
Offline
Offline
Thanks jasonwryan So my exact boot time was 1 minute and 34.151 seconds (which is not unbearable but like i said it used to be in a matter of seconds)... The kernel took 2.790 seconds and userspace took 1 minute and 31.361 Output of systemd-analyze blame :
922ms systemd-logind.service
832ms systemd-modules-load.service
774ms systemd-fsck@dev-disk-by\x2duuid-f7bccd4f\x2d4b47\x2d4dbb\x2da8f8\x2dd8e374bb9867.service
614ms udisks2.service
545ms dev-mqueue.mount
509ms sys-kernel-debug.mount
499ms dev-hugepages.mount
499ms systemd-udev-trigger.service
497ms systemd-vconsole-setup.service
478ms systemd-remount-fs.service
477ms tmp.mount
439ms systemd-tmpfiles-setup-dev.service
365ms dhcpcd.service
218ms temp-links-catalyst.service
192ms upower.service
169ms polkit.service
165ms systemd-journal-flush.service
151ms systemd-sysctl.service
149ms systemd-udevd.service
113ms systemd-update-utmp.service
105ms gpm.service
68ms home.mount
68ms systemd-tmpfiles-setup.service
57ms systemd-random-seed-load.service
30ms systemd-user-sessions.service
1ms sys-kernel-config.mount
Now maybe I am wrong, but these don't add up to 1 min 31 seconds...It actually adds to about 9 seconds which is probably my old boot time.. What am I missing here?
Last edited by life_enjoyer (2013-06-09 03:36:53)
A R C H
R
C
H
Offline
I turned boot to verbose and found that it was hanging at:
[***] A start job is running for dev-disk-by \x2duuid-07<a lot more numbers and letters go here>.device
But what does this mean? And what can i do to solve it? And why is systemd-analyze blame not correctly tracking the time?
Last edited by life_enjoyer (2013-06-09 04:06:18)
A R C H
R
C
H
Offline
Check that disk for errors?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Check that disk for errors?
How exactly?
A R C H
R
C
H
Offline
How exactly?
`man fsck`
All the best,
-HG
Offline
Solved it. Simply removed my swap. I don't know what went wrong but I must have done something with my swap space; I was trying to increase it while i was on the live usb but it did not occur that this would be an issue.... I would still like to know why systemd did not find how long it took. Is it a bug?
A R C H
R
C
H
Offline
Systemd takes issue if things listed in the fstab are not exactly as you say they are. But if you use nofail then it won't cause these hangs.
If you want more swap space, then all you need to do is use a swap file (assuming you are not on btrfs). But in reality, mass use of swap is typically an indication not that you need more swap, but that you should increase the amount of RAM in your system. Of course, using it for hibernation does not apply to that.
Offline
Thanks to all of you... I wanted to make an account on this forum and figured this problem was a good excuse...
A R C H
R
C
H
Offline