New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to start initrd-switch-root.target issue #2455

Open
Libeccio84 opened this Issue Jun 10, 2018 · 12 comments

Comments

Projects
None yet
6 participants
@Libeccio84

Libeccio84 commented Jun 10, 2018

Hi all,
I am new to Container Linux and I have tried to install it on a VirtualBox VM starting from the CoreOS Production Image ISO (OS version 1745.5.0).

I started from the following cloud-config, then converted into an ignition.json as described in your guides.

passwd:
  users:
    - name: core
      ssh_authorized_keys:
        - ssh-rsa AAAAB3N[...]
networkd:
  units:
    - name: 00-static.network
      contents: |
        [Match]
        Name=enp0s8

        [Network]
        DHCP=no
        Address=192.168.2.11/24
    - name: 01-dhcp.network
      contents: |
        [Match]
        Name=en*

        [Network]
        DHCP=yes

etcd:
  version: 3.3.3
  discovery: https://discovery.etcd.io/e2db5a07d1cc8a4384f8c9f6113b8f91
  name: member01.etcd.net
  advertise_client_urls:       http://192.168.2.11:2379
  initial_advertise_peer_urls: http://192.168.2.11:2380
  listen_client_urls:          http://0.0.0.0:2379
  listen_peer_urls:            http://192.168.2.11:2380
  initial_cluster: member01.etcd.net=http://192.168.2.11:2380,member02.etcd.net=http://192.168.2.12:2380,member03.etcd.net=http://192.168.2.13:2380

Installation ended successfully, but after rebooting I faced this error:
screen shot 2018-06-10 at 20 11 49

Further Info:

  • if I omit networkd settings and etcd settings from ignition.json everything goes fine
  • if I configure networkd and I omit etcd settings, I face the same problem
  • if I omit networkd settings and etcd settings from ignition.json, I can successfully set up static IP address as in the presented ignition.json file after the installed OS boots up (adding .network files)

System configuration

  • RAM: 4 GB
  • 4 CPU
  • tried w/o UEFI as well as with it

Can someone help me?

Thanks in advance.

@ajeddeloh

This comment has been minimized.

Show comment
Hide comment
@ajeddeloh

ajeddeloh Jun 11, 2018

Can you provide the logs from the units it sugguests please? I assume you mean you're using an Ignition config generated from your posted CLC?

ajeddeloh commented Jun 11, 2018

Can you provide the logs from the units it sugguests please? I assume you mean you're using an Ignition config generated from your posted CLC?

@Libeccio84

This comment has been minimized.

Show comment
Hide comment
@Libeccio84

Libeccio84 Jun 12, 2018

Of course I did :) I have corrected the main post right now :)
Here is the output of systemctl status initrd-cleanup.service
screen shot 2018-06-12 at 09 39 43

Let me know if you need further info.
Thanks again.

Libeccio84 commented Jun 12, 2018

Of course I did :) I have corrected the main post right now :)
Here is the output of systemctl status initrd-cleanup.service
screen shot 2018-06-12 at 09 39 43

Let me know if you need further info.
Thanks again.

@kotaner

This comment has been minimized.

Show comment
Hide comment
@kotaner

kotaner Jun 12, 2018

Same exact problem here on 1745.5.0. We're installing onto baremetal (HP Blades) and getting this error.

kotaner commented Jun 12, 2018

Same exact problem here on 1745.5.0. We're installing onto baremetal (HP Blades) and getting this error.

@ajeddeloh

This comment has been minimized.

Show comment
Hide comment
@ajeddeloh

ajeddeloh Jun 12, 2018

Do you have the full logs from journalctl --no-pager?

Additionally do you know if this is a new issue with 1745.5.0? Can you also try alpha and/or beta?

ajeddeloh commented Jun 12, 2018

Do you have the full logs from journalctl --no-pager?

Additionally do you know if this is a new issue with 1745.5.0? Can you also try alpha and/or beta?

@glevand

This comment has been minimized.

Show comment
Hide comment
@glevand

glevand Jun 13, 2018

@Libeccio84, @kotaner Maybe adding this to the kernel command line will give more insight: systemd.log_level=debug systemd.log_target=console systemd.journald.forward_to_console=1.

glevand commented Jun 13, 2018

@Libeccio84, @kotaner Maybe adding this to the kernel command line will give more insight: systemd.log_level=debug systemd.log_target=console systemd.journald.forward_to_console=1.

@Libeccio84

This comment has been minimized.

Show comment
Hide comment
@Libeccio84

Libeccio84 Jun 19, 2018

Working on it, sorry for your waiting...

Libeccio84 commented Jun 19, 2018

Working on it, sorry for your waiting...

@christianhuening

This comment has been minimized.

Show comment
Hide comment
@christianhuening

christianhuening Aug 14, 2018

any news on this?

christianhuening commented Aug 14, 2018

any news on this?

@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Aug 14, 2018

Member

@christianhuening without further logs entries describing the root failure there are no meaningful/actionable followups from our (distro) side. The logs posted so far are just symptoms of something else going bad in the initramfs provisioning.

Also, at this time there is a new stable release which may be worthy to check in case of issues.

Member

lucab commented Aug 14, 2018

@christianhuening without further logs entries describing the root failure there are no meaningful/actionable followups from our (distro) side. The logs posted so far are just symptoms of something else going bad in the initramfs provisioning.

Also, at this time there is a new stable release which may be worthy to check in case of issues.

@christianhuening

This comment has been minimized.

Show comment
Hide comment
@christianhuening

christianhuening Aug 14, 2018

@lucab thanks, we're updating to latest:stable now and will get back here if it still is not working.

christianhuening commented Aug 14, 2018

@lucab thanks, we're updating to latest:stable now and will get back here if it still is not working.

@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Aug 14, 2018

Member

For anybody else seemingly hitting this, it would be interesting to know the following:

  • is it sporadically or reliably failing to boot?
  • does it also happen without any custom ignition configuration? if not, anything interesting in ignition logs?
  • from the emergency shell on boot failure, check journalctl --no-pager for meaningful log entries and attach them all
Member

lucab commented Aug 14, 2018

For anybody else seemingly hitting this, it would be interesting to know the following:

  • is it sporadically or reliably failing to boot?
  • does it also happen without any custom ignition configuration? if not, anything interesting in ignition logs?
  • from the emergency shell on boot failure, check journalctl --no-pager for meaningful log entries and attach them all
@christianhuening

This comment has been minimized.

Show comment
Hide comment
@christianhuening

christianhuening Aug 14, 2018

Ok, we found old ZFS labels on our disks (it's a test cluster with old hardware). we removed them and it worked.

christianhuening commented Aug 14, 2018

Ok, we found old ZFS labels on our disks (it's a test cluster with old hardware). we removed them and it worked.

@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Aug 14, 2018

Member

@christianhuening glad that you solved it. If you have time to record the details, we'll gladly take a mail to coreos-user ML describing what was wrong, how you figured it out and how it was resolved, so that other users in similar trouble can find the solution.

Member

lucab commented Aug 14, 2018

@christianhuening glad that you solved it. If you have time to record the details, we'll gladly take a mail to coreos-user ML describing what was wrong, how you figured it out and how it was resolved, so that other users in similar trouble can find the solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment