Project

General

Profile

Actions

Bug #8257

closed

Discovery 2.0 "System halted" at boot

Added by Jorick Astrego over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
High
Category:
Image
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When booting a VM with the new discovery image (v1.9.91), it starts and stops imediately with the final line "System halted".

I cannot get any console output quickly enough to see why.

Any way to debug?


Files

Selection_325.png View Selection_325.png 11.9 KB screenshot Jorick Astrego, 11/17/2014 06:59 AM

Related issues 1 (0 open1 closed)

Related to Discovery - Tracker #8332: [Discovery 2.0] Usability alignment and autoprovisioningResolved11/10/2014

Actions
Actions #1

Updated by Lukas Zapletal over 9 years ago

Jorick, first of all thank you for testing the new discovery 2.0!

The standard debugging practice is to put fdi.ssh=1 fdi.rootpw=redhat on the kernel command line as noted in https://github.com/theforeman/foreman-discovery-image but you are right that due to nature of this nasty bug this will not help you.

Therefore the easiest way is to start with systemd interactive mode when it asks you for every action. As soon as journald starts up, you should see all the system logs on the tty1 (which will mess your interactive output actually a bit but its doable - keep pressing ENTER few times until you see the question again). To get this behavior put this to the kernel command line:

systemd.confirm_spawn=true

Ping me anytime on the IRC channel if you need further assistance.

Is it a VM or bare metal you are testing with?

Actions #2

Updated by Lukas Zapletal over 9 years ago

  • Related to Tracker #8332: [Discovery 2.0] Usability alignment and autoprovisioning added
Actions #3

Updated by Lukas Zapletal over 9 years ago

What's the status? I noticed we have this in our kickstart:

# This seems to cause 'reboot' resulting in a shutdown on certain platforms
# See https://tickets.puppetlabs.com/browse/RAZOR-100
echo " * disable the mei_me module" 
mkdir -p /etc/modprobe.d
cat > /etc/modprobe.d/mei.conf <<EOMEI
blacklist mei_me
install mei_me /bin/true
blacklist mei
install mei /bin/true
EOMEI

Actions #4

Updated by Jorick Astrego over 9 years ago

It took a bit of time as it's the end of the year rush as usual....

I tried with systemd.confirm_spawn=true but it doesn't work.

Actions #5

Updated by Jorick Astrego over 9 years ago

I see in the error it complains about "FATAL: No or empty root=argument"

I have this in my provisioning template with our own foreman url...

LABEL discovery2
MENU LABEL Foreman Discovery 2.0 CentOS7
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop
root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0
rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset
foreman.url=http://xyz fdi.ssh=1 fdi.rootpw=redhat systemd.confirm_spawn=true
IPAPPEND 2

Actions #6

Updated by Ohad Levy over 9 years ago

Jorick Astrego wrote:

I see in the error it complains about "FATAL: No or empty root=argument"

I have this in my provisioning template with our own foreman url...

LABEL discovery2
MENU LABEL Foreman Discovery 2.0 CentOS7
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop
root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0
rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset
foreman.url=http://xyz fdi.ssh=1 fdi.rootpw=redhat systemd.confirm_spawn=true
IPAPPEND 2

can you try removing all white spaces / new lines chars and try again?

Actions #7

Updated by Jorick Astrego over 9 years ago

DOH! How could I miss that. Just copy/paste without thinking....

Better add a delimiter "\\" in the for other people like me...

It's booting now but it get's stuck on:
"Confirmation question timed out, assuming positive response."
"Stared Create static device nodes in /dev."

I don't have any option to confirm anything and waited about 10 minutes but it didn't continue.

So the "systemd.confirm_spawn=true" doesn't work, after I removed it everything is fine now.

Actions #8

Updated by Lukas Zapletal over 9 years ago

  • Status changed from New to Resolved
  • Assignee set to Lukas Zapletal

Jorick, my bad! I am glad you sorted it out.

Where did you find the bit you copied from? Just to make sure all occurances gets fixed. I fixed the official README (actually it was missing the instructions): https://github.com/theforeman/foreman-discovery-image

I think it was just my email, I use mutt so I usually wrap lines.

Actions #9

Updated by Jorick Astrego over 9 years ago

No problem. I could have seen it myself.

Got the info from the mailinglist as I couldn't find the readme.

https://groups.google.com/forum/#!topic/foreman-users/MH6BwZvCfoU

Actions

Also available in: Atom PDF