Bug 633087

Summary: unable to boot with systemd, get a rescue shell
Product: [Fedora] Fedora Reporter: Sébastien Wilmet <swilmet>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 14CC: lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-12 19:54:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output none

Description Sébastien Wilmet 2010-09-12 19:45:26 UTC 
Created attachment 446797 [details]
dmesg output

Description of problem:
I'm not able to boot with systemd. With upstart there is no problem.
My computer is an Asus PRO50N (AMD Turion 64x2 processor).
There is a rescue shell so I was able to have the output of dmesg (see attachment) with "systemd.log_level=debug".

Also, with the rescue shell, halting the system doesn't work, the last message is "System halted." and nothing happens after that. But I think this issue is related with Bug 630935.

Version-Release number of selected component (if applicable):
systemd-9-3.fc14

How reproducible:
Always during boot with systemd.
  
Actual results:
Get a rescue shell.

Expected results:
Boot entirely without any problem.
Comment 1 Michal Schmidt 2010-09-12 19:54:47 UTC 
From the log:

init[1]: Failed to load configuration for default.target: No such file or directory
init[1]: Failed to load default target: No such file or directory

Probably a consequence of bug 627401. Please fix your /etc/systemd/system/default.target to point to an existing unit in /lib/systemd/system, such as graphical.target or multi-user.target.

> Also, with the rescue shell, halting the system doesn't work,
> the last message is "System halted." and nothing happens after that.

If you use just "halt", that's the expected result. You want "poweroff" or "halt -p".


Feel free to reopen if I guessed wrong.

*** This bug has been marked as a duplicate of bug 627401 ***
Comment 2 Lennart Poettering 2010-09-12 19:56:47 UTC 
Seems your /etc/systemd/system/default.target symlink does not exist or points to a not existing location.

Is this an upgrade from an older rawhide? If so, then please follow the recommendations from these two heads-up posts:

http://lists.fedoraproject.org/pipermail/devel/2010-August/140294.html
http://lists.fedoraproject.org/pipermail/devel/2010-August/140301.html

Or is this a post-alpha fresh install? if so, then anaconda created the wrong default.target symlink, and you should fix it manually:

ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
Comment 3 Sébastien Wilmet 2010-09-12 21:03:09 UTC 
It was a fresh install, and indeed the link was broken. Now it works, thanks.