[SOLVED] Unable to boot after installation

Sulice · 2013-10-22 12:54:56

Hello everyone,

I tried to set up a dual boot with my Win7 on my laptop (aspire one D270).
I followed the beginner's installation guide. My arch is on /dev/sda3. (no swap, just /)

After choosing the "arch linux, with linux core repo kernel" option in the grub, it stucks after the line
/dev/sda: clean, 35506/4800512 files, 569175/19200000 blocks

I believe it's the output of fsck. Why doesn't it go further ?

The curious thing is that I managed to have arch before on this laptop. It's just that one month ago, after an update, it did the same thing. As a newbie, I cleaned the partition and tried to install again (for the same result).

Any ideas ?

Solved : systemd was the cause of the issue.
Follow instructions of Silly7 to downgrade it to 204-3 for now.

Last edited by Sulice (2013-10-28 07:08:37)

karol · 2013-10-22 13:12:44

Can you switch to another console e.g. Alt-Ctrl-F2 or Alt-ctrl-F7?
Anything interesting in the logs?

Sulice · 2013-10-22 13:17:04

I cannot switch to another console. Where are located the logs ?

karol · 2013-10-22 13:19:00

Sulice wrote:

Where are located the logs ?

In /var/log . See if you can find anything via

# journalctl

when you chroot.

Sulice · 2013-10-22 13:21:54

/var/log is empty. (the output of journalctl is "No journal files were found.")

clfarron4 · 2013-10-22 13:28:11

Ok, when you get to GRUB, remove the the word quiet from the kernel line of the Arch entry and see what happens.

Trilby · 2013-10-22 13:28:19

Sulice wrote:

My arch is on /dev/sda3
...
/dev/sda: clean, 35506/4800512 files, 569175/19200000 blocks

Is that a typo? Does the output say /dev/sda3: clean ... or does it really say /dev/sda: clean?

If it is the latter, then either your bootloader configuration is pointing to the wrong root, or your fstab is wrong. If you can describe what comes before this line we can narrow down which of those is more likely.

Sulice · 2013-10-22 13:37:58

@Trilby : typo mistake. It's /dev/sda3

Without quiet, it displays :

:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
performing fsck on '/dev/sda3'
/dev/sda3: clean, <blablabla>
:: mounting '/dev/sda3' on real root
:: running cleanup hook [udev]

Welcome to Arch Linux!

And it stops. (I mean, it stays so)

Last edited by Sulice (2013-10-22 13:39:03)

clfarron4 · 2013-10-22 14:40:10

Do you have a Display Manager installed and did you enable it?

Sulice · 2013-10-22 15:33:13

It's a brand new installation. I don't have any display manager.
I installed : base, base-devel, vim, os-prober, grub

tompear · 2013-10-23 19:39:35

After last system update I have this problem too. Booting hangs on "Welcome to Arch Linux!".
I've added this to kernel parameters at boot time:

systemd.log_level=debug systemd.log_target=console

Now it shows one more line after Welcome, booting stops on "Set hostname to <sylwusia>"

Silly7 · 2013-10-24 16:29:54

I can also confirm that this happens to a D270 after the latest pacman -Syyu.

Sulice · 2013-10-24 16:45:21

I think it's a hardware issue. I did the installation again on 2 laptops and it didn't work only on my aspire one D270.
I have a long and painfull history of issues with my graphic card (GMA3600).
I think some (generic) drivers for this card where added around the 3.8 linux kernel but at that time arch was fully functionnal on the D270.

I don't see why, in a console, the graphic card could be a problem...

Last edited by Sulice (2013-10-24 16:52:19)

Silly7 · 2013-10-24 17:06:52

Yeah, its not a GFX problem, as my D270 runs stable of modesetting (See wiki).

I'd be interestedf about what your saying of 3.8 kernel and graphics though, but for now lets just get back to normal.

Can anybody else chime in about this issue?

Silly7 · 2013-10-24 17:10:17

Also, my Arch was running at 3.10 on my D270

WonderWoofy · 2013-10-24 17:14:29

Does tehscreen eventually just blank out? If so that might indicate that you need to implement early KMS...

Edit: In fact, can you get to a TTY and log in there? If not you need to solve the first step of getting the i915 kernel module to work properly. Then after that you can worry about Xorg and the xf86-video-intel driver. i915 and the Xorg driver are separate, though the Xorg driver depends on the i915 module being loaded and functional.

Last edited by WonderWoofy (2013-10-24 17:16:07)

Silly7 · 2013-10-24 17:37:37

WonderWoofy, no. it doesnt blank out, if you like, look up GMA3600 in the wiki , you'll fall in love.

the intel video driver doesnt work, see above.

It's also not a kernel issue, as i tried with 3.10 LTS just then.

Silly7 · 2013-10-24 18:02:42

I can share my pacman log if you like, i am currently looking through the logs where I started the system upgrade.

EDIT : Could it be a problem with Systemd? my log shows i went from 204-3 to 208-1

Last edited by Silly7 (2013-10-24 18:03:40)

Silly7 · 2013-10-24 21:05:15

It seems to me Systemd isnt the problem. How can I look at kernel logs? mine a blank in /var/log.

Sulice · 2013-10-24 21:27:32

In order to look at the kernel logs :
https://wiki.archlinux.org/index.php/Boot_Debugging

There are a lot of debug output. I don't know how to store them.

With "verbose ignore_loglevel" I can see that my last 3 lines are :

[ 5.7848941] systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)

Welcome to Arch Linux!

[ 5.848068] systemd[1]: Set hostname to <arch>.

Last edited by Sulice (2013-10-24 21:30:59)

Silly7 · 2013-10-25 17:28:12

So.. I just reinstalled Arch from scratch, and im in the exact same posisition.

Whats happening?

Silly7 · 2013-10-25 19:08:36

Fixed!

The problem IS infact with systemd, for whatever reason I do not know.

I noticed that my desktop Arch is also running 204-3 of systemd, so i booted up a ArchISO and copied that systemd .tar.xz to a second USB drive, located in /var/cache/pacman/pkg.

After booting up the ArchISO from my first USB stick, mount your / on /mnt, and proceed to chroot in [arch-chroot /mnt /bin/bash]

Then locate your secondary USBs dev name [lsblk] and match the result based on size of your flash drive ( Mine was easy as it was 700mb drive ), then proceed to mount it on /usb. [mount /dev/sdX /usb]

Finally, cd into /usb and execute 'pacman -Ud systemd-204-3-etc.tar.xz' without quotes. Use -U to upgrade to a downgrade (Inception right? ) and add the 'd' to ignore dependancys, else it won't work.

After doing the above im able to get past systemd again. **PLEASE BACK UP YOUR SYSTEM BEFORE DOING THIS, IM NOT RESPONSIBLE IF IT GOES PEAR-SHAPED!**.

Sulice, if your still tuned in, can you tell me how it goes for you? If you need the systemd i can upload for you if you like .

Sulice · 2013-10-25 19:29:08

I'll try it tomorrow !
Could you upload it for me ? Thanks.

Silly7 · 2013-10-25 20:13:04

Sure, give me a couple of hours buddy.

cfr · 2013-10-26 02:22:08

Did you follow the instructions for the systemd upgrade in pacman's output? The big upgrade was probably to 207 but you seem to have gone from 204 to 208. Here's what I got in the upgrade to 207:

[2013-09-18 20:29] [ALPM] warning: /etc/systemd/logind.conf installed as /etc/systemd/logind.conf.pacnew
[2013-09-18 20:29] [ALPM] warning: /etc/systemd/journald.conf installed as /etc/systemd/journald.conf.pacnew
[2013-09-18 20:29] [ALPM-SCRIPTLET] ==> systemd 205 restructures the cgroup hierarchy and changes internal
[2013-09-18 20:29] [ALPM-SCRIPTLET]     protocols. You should reboot at your earliest convenience.
[2013-09-18 20:29] [ALPM-SCRIPTLET] ==> The "timestamp" hook for mkinitcpio no longer exists. If you used
[2013-09-18 20:29] [ALPM-SCRIPTLET]     this hook, you must remove it from /etc/mkinitcpio.conf. A "systemd"
[2013-09-18 20:29] [ALPM-SCRIPTLET]     hook has been added which provides this functionality, and more.
[2013-09-18 20:29] [PACMAN] upgraded systemd (204-3 -> 207-3)
[2013-09-18 20:29] [PACMAN] upgraded systemd-sysvcompat (204-3 -> 207-3)

Arch Linux

#1 2013-10-22 12:54:56

[SOLVED] Unable to boot after installation

#2 2013-10-22 13:12:44

Re: [SOLVED] Unable to boot after installation

#3 2013-10-22 13:17:04

Re: [SOLVED] Unable to boot after installation

#4 2013-10-22 13:19:00

Re: [SOLVED] Unable to boot after installation

#5 2013-10-22 13:21:54

Re: [SOLVED] Unable to boot after installation

#6 2013-10-22 13:28:11

Re: [SOLVED] Unable to boot after installation

#7 2013-10-22 13:28:19

Re: [SOLVED] Unable to boot after installation

#8 2013-10-22 13:37:58

Re: [SOLVED] Unable to boot after installation

#9 2013-10-22 14:40:10

Re: [SOLVED] Unable to boot after installation

#10 2013-10-22 15:33:13

Re: [SOLVED] Unable to boot after installation

#11 2013-10-23 19:39:35

Re: [SOLVED] Unable to boot after installation

#12 2013-10-24 16:29:54

Re: [SOLVED] Unable to boot after installation

#13 2013-10-24 16:45:21

Re: [SOLVED] Unable to boot after installation

#14 2013-10-24 17:06:52

Re: [SOLVED] Unable to boot after installation

#15 2013-10-24 17:10:17

Re: [SOLVED] Unable to boot after installation

#16 2013-10-24 17:14:29

Re: [SOLVED] Unable to boot after installation

#17 2013-10-24 17:37:37

Re: [SOLVED] Unable to boot after installation

#18 2013-10-24 18:02:42

Re: [SOLVED] Unable to boot after installation

#19 2013-10-24 21:05:15

Re: [SOLVED] Unable to boot after installation

#20 2013-10-24 21:27:32

Re: [SOLVED] Unable to boot after installation

#21 2013-10-25 17:28:12

Re: [SOLVED] Unable to boot after installation

#22 2013-10-25 19:08:36

Re: [SOLVED] Unable to boot after installation

#23 2013-10-25 19:29:08

Re: [SOLVED] Unable to boot after installation

#24 2013-10-25 20:13:04

Re: [SOLVED] Unable to boot after installation

#25 2013-10-26 02:22:08

Re: [SOLVED] Unable to boot after installation

Board footer