You are not logged in.

#1 2017-04-05 14:54:00

zekebsatx
Member
Registered: 2016-01-29
Posts: 66

[SOLVED] Boot failure

This is a Dell XPS 13 2016 model.   Updated yesterdat, tried my first reboot since that update this morning.  Now the boot hangs before a TTY so I can't get to a console.  The last message is

  Started Manage, Install and Generate Color Profiles.  

I tried to edit my systemd boot kernel parameters to add

 systemd.unit=graphical.target 

because I read that might get me to a terminal, but I can't edit the boot entry.

I am hoping I can recover with out a reinstall!

Last edited by zekebsatx (2017-04-05 16:02:52)

Offline

#2 2017-04-05 15:08:45

loqs
Member
Registered: 2014-03-06
Posts: 17,414

Re: [SOLVED] Boot failure

If you can not access a terminal with ctrl+alt+F2 then use boot media and chroot into the system and post the journal from a failed boot.
Please also post the pacman.log for the update that you attribute this issue to.
I would have expected changing the target to graphical.target would not achieve anything as that is the default target.
Systemd#Change_default_target_to_boot_into Did you perhaps mean multi-user.target or rescue.target?

Offline

#3 2017-04-05 15:28:55

zekebsatx
Member
Registered: 2016-01-29
Posts: 66

Re: [SOLVED] Boot failure

loqs wrote:

post the journal from a failed boot.

I am not sure where to find this?
/var/log/journal/system.journal is not a text file.

loqs wrote:

Did you perhaps mean multi-user.target or rescue.target?

I think I meant rescue.target.  Doesn't matter because I must have disabled editing the boot parameters somehow - I can't seem to get the prompt to edit at the boot entry menu.

Offline

#4 2017-04-05 15:35:28

loqs
Member
Registered: 2014-03-06
Posts: 17,414

Re: [SOLVED] Boot failure

Systemd#Filtering_output
Edit:
Pastebin_clients to upload the logs from the console.

Last edited by loqs (2017-04-05 15:46:50)

Offline

#5 2017-04-05 16:02:27

zekebsatx
Member
Registered: 2016-01-29
Posts: 66

Re: [SOLVED] Boot failure

Thanks!  Just looking through the journal led me to the unit that was failing - it was SDDM. 
I disabled the service and it completed the boot!

Not sure what happened to sddm yet, but thanks for the help, I learned something very important about the journal!

Offline

Board footer

Powered by FluxBB