[SOLVED] Unable to boot after CLI shutdown

cortezthekiller · 2013-09-15 18:40:15

Fresh install Archlinux (3.8.4-1-ARCH) + KDE

From KDE console, I did a shutdown with the following command

# shutdown -h -P now

I observed the following messages on the screen (no errors apparently):

[ OK ] Stopped Getty on tty1.
[ OK ] Stopped K Display Manager.
          Stopping Permit User Sessions...
[ OK ] Stopped /etc/netctl/wireless generated by archboot setup.
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Sockets.
[ OK ] Closed LVM2 medatada daemon socket.
[ OK ] Closed Device-mapper event daemon FIFOs.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped target System Initialization.
          Stopping Setup Virtual Console...
[ OK ] Stopped Setup Virtual Console.
[ OK ] Stopped target Encrypted Volumes.
          Stopping Apply Kernel Variables...
[ OK ] Stopped Apply Kernel Variables.
          Stopping Load Kernel Modules...
[ OK ] Stopped Load Kernel Modules.
[ OK ] Stopped target Swap.
[ OK ] Deactivated swap /dev/disk/by-uuid/1f32953-22b4-4591-8f0d-e1a41e33015b.
[ OK ] Stopped target Local File Systems.
          Unmounting /boot...
          Unmounting /home...
          Unmounting Temporary Directory...
[ OK ] Stopped target Remote File Systems
[ OK ] Failed unmounting /boot.
[ OK ] Failed unmounting /home.
[ OK ] Failed unmounting Temporary Directory.
[ OK ] Stopped target Local File Systems (Pre).
          Stopping Remount Root and Kernel File Systems...
[ OK ] Stopped Remount Root and Kernel File Systems.
          Starting Save Random Seed...
          Starting Update UTMP about System Shutdown.
[ OK ] Reached target Shutdown.

But the PC does not power off, it hangs at the last message and I had to press the power off button.

When I started the PC again I got plenty of errors of type “failed to mount /boot “, “Dependency failed for local file systems” and so on.

Then, I boot from CD and changed root to try to mount the existing partitions of my HD:

/dev/sda1 --> boot
/dev/sda2 --> swap
/dev/sda3 --> root
/dev/sda4 --> home

Partitions were successfully mounted

What I did next was to install again the bootloader (syslinux) and try to reboot the system

This time I got the following boot sequence:

Booting the kernel 
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...done.
:: performing fsck on ‘/dev/sda3’
ROOT_ARCH: clean, 161613/3203072 files, 1465739/12800000 blocks
:: mounting ‘/dev/sda3’ on real root
:: running cleanup hook [udev]
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.

sh: can’t access tty; job control turned off
[rootfs /] #

And the cursor gets stuck at the rootfs promtpt, no chance to type anything ...

I’ve googled for this error and came up with this link: https://bbs.archlinux.org/viewtopic.php?id=146388

But editing the kernel parameters as stated in the link did not fix my problem, it just brought me back to the situation where it failed to mount the local filesystems

I installed archlinux & KDE from scratch again . But performing a CLI shutdown got me into the very same problem again ....
I’ve revised the mkinitcpio.conf and I seem to have all the hooks (using the default config by the way). ¿Could be related to KDE?
No idea how to proceed now.

EDIT: corrected typos

Last edited by cortezthekiller (2013-09-17 21:58:10)

cortezthekiller · 2013-09-15 19:55:02

I don't know if this issue could be related to Bug report 35237

I've just realized that after the shutdown command, there's some failures unmounting the file systems (even though the messages start with "OK") :

[ OK ] Failed unmounting /boot.
[ OK ] Failed unmounting /home.
[ OK ] Failed unmounting Temporary Directory.

jrmrjnck · 2013-09-16 00:14:23

I don't have a solution, but I am wondering why your kernel is out of date if it's a fresh install. The latest is 3.10.10-1.

cortezthekiller · 2013-09-16 07:08:08

jrmrjnck wrote:

I don't have a solution, but I am wondering why your kernel is out of date if it's a fresh install. The latest is 3.10.10-1.

Thanks for the replay. The CD with the ISO was burned some months ago and I don't have a CD burner right now (the BIOS does not start from USB either). Should I perform a system upgrade right after the installation? I read it could bring "unforeseen consequences" and thought that it would be wise not to take that risk at the beginning.

jasonwryan · 2013-09-16 07:14:11

The first thing to do after an install is pacman -Syyu. Maintaining Arch is all about staying up-to-date, you may as well get in the habit from the get-go...

cortezthekiller · 2013-09-16 07:30:22

Thanks.
I've installed archlinux (with KDE) from CD again las night, I will upgrade the system as soon as I get back home.
But even after the upgrade, I won't feel very confident when performing a shutdown -h now ...

jasonwryan · 2013-09-16 07:34:56

You shouldn't use `shutdown -h` - you should use `systemctl poweroff` (you won't need to use sudo if you have an active logind session and are the only user logged in).

headkase · 2013-09-16 07:49:44

jasonwryan wrote:

You shouldn't use `shutdown -h` - you should use `systemctl poweroff` (you won't need to use sudo if you have an active logind session and are the only user logged in).

Shoud it really matter? See:

$ ls -l /usr/bin/shutdown 
lrwxrwxrwx 1 root root 9 May 30 10:25 /usr/bin/shutdown -> systemctl

shutdown symlinks to systemctl? They are the same??

jasonwryan · 2013-09-16 08:43:52

Should it matter? Not really. There is this:

man shutdown wrote:

NOTES
This is a legacy command available for compatibility only.

headkase · 2013-09-16 08:51:45

jasonwryan wrote:

Should it matter? Not really. There is this:
man shutdown wrote:
NOTES
This is a legacy command available for compatibility only.

Yes:

$ pacman -Ql systemd-sysvcompat
systemd-sysvcompat /usr/
systemd-sysvcompat /usr/bin/
systemd-sysvcompat /usr/bin/halt
systemd-sysvcompat /usr/bin/init
systemd-sysvcompat /usr/bin/poweroff
systemd-sysvcompat /usr/bin/reboot
systemd-sysvcompat /usr/bin/runlevel
systemd-sysvcompat /usr/bin/shutdown
systemd-sysvcompat /usr/bin/telinit
...

There are all the old sysv commands, symlinked to systemd.

Last edited by headkase (2013-09-16 08:53:41)

cortezthekiller · 2013-09-17 22:01:47

I tried to upgrade from 3.8.4 with pacman -Syu but it gave me several errors. Finally I've re-installed mys system from the latest iso (3.10.10) and everything seems alright. I've changed the subject to [SOLVED].

Arch Linux

#1 2013-09-15 18:40:15

[SOLVED] Unable to boot after CLI shutdown

#2 2013-09-15 19:55:02

Re: [SOLVED] Unable to boot after CLI shutdown

#3 2013-09-16 00:14:23

Re: [SOLVED] Unable to boot after CLI shutdown

#4 2013-09-16 07:08:08

Re: [SOLVED] Unable to boot after CLI shutdown

#5 2013-09-16 07:14:11

Re: [SOLVED] Unable to boot after CLI shutdown

#6 2013-09-16 07:30:22

Re: [SOLVED] Unable to boot after CLI shutdown

#7 2013-09-16 07:34:56

Re: [SOLVED] Unable to boot after CLI shutdown

#8 2013-09-16 07:49:44

Re: [SOLVED] Unable to boot after CLI shutdown

#9 2013-09-16 08:43:52

Re: [SOLVED] Unable to boot after CLI shutdown

#10 2013-09-16 08:51:45

Re: [SOLVED] Unable to boot after CLI shutdown

#11 2013-09-17 22:01:47

Re: [SOLVED] Unable to boot after CLI shutdown

Board footer