Skip to content
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

The ignition verification passed, but the system initialization failed. What should I do? #571

Open
n2aod opened this issue Dec 19, 2024 · 1 comment

Comments

@n2aod
Copy link

n2aod commented Dec 19, 2024

image

variant: fcos
version: 1.5.0

storage:
  disks:
    - device: /dev/nvme0n1
      wipe_table: true
      partitions:
        - label: UEFI
          number: 1
          size_mib: 1024
          start_mib: 0
          wipe_partition_entry: true
          type_guid: "c12a7328-f81f-11d2-ba4b-00a0c93ec93b"
        - label: SWAP
          number: 2
          size_mib: 32768
          start_mib: 1024
          wipe_partition_entry: true
          type_guid: "0657fd6d-a4ab-43c4-84e5-0933c84b4f4f"
        - label: ROOT
          number: 3
          size_mib: 0
          wipe_partition_entry: true
          type_guid: "4f68bce3-e8cd-4db1-96e7-fbcaf984b709"
  filesystems:
    - device: /dev/nvme0n1p1
      format: vfat
      path: /boot/efi
      wipe_filesystem: true
      label: UEFI
      with_mount_unit: true
    - device: /dev/nvme0n1p2
      format: swap
      wipe_filesystem: true
      label: SWAP
      mount_options:
        - "pri=10"
      with_mount_unit: true
    - device: /dev/nvme0n1p3
      format: btrfs
      path: /
      wipe_filesystem: true
      label: ROOT
      options:
        - "-ddup"
      mount_options:
        - "compress=zstd"
      with_mount_unit: true
  links:
    - path: /etc/localtime
      target: /usr/share/zoneinfo/Asia/Shanghai
      overwrite: true
      hard: false
      user:
        id: 0
      group:
        id: 0
  directories:
    - path: /data
      overwrite: true
      mode: 0755
      user:
        id: 1000
      group:
        id: 1000
  files:
    - path: /etc/hostname
      overwrite: true
      mode: 0644
      user:
        id: 0
      group:
        id: 0
      contents:
        inline: "fedora"
    - path: /data/welcome.txt
      overwrite: true
      mode: 0644
      user:
        id: 0
      group:
        id: 0
      contents:
        inline: "Hello Fedora CoreOS"
    - path: /etc/systemd/zram-generator.conf
      overwrite: true
      mode: 0644
      user:
        id: 0
      group:
        id: 0
      contents:
        inline: |
          [zram0]
          zram-size = ram / 2
          compression-algorithm = zstd
          priority = 100

kernel_arguments:
  should_exist:
    - "net.ipv4.ip_forward=1"
    - "net.ipv6.conf.all.forwarding=1"

systemd:
  units:
    - name: systemd-hostnamed.service
      enabled: true

passwd:
  users:
    - name: core
      ssh_authorized_keys:
        - "ssh-ed25519 123456"
      primary_group: core
      groups:
        - wheel
        - users
      uid: 1000
      home_dir: /home/core
      shell: /bin/bash
      system: false
  groups:
    - name: core
      gid: 1000

@n2aod
Copy link
Author

n2aod commented Dec 19, 2024

I guess it was my yaml file error that caused the system initialization failure. If necessary, I can provide the system log.

I have tried to delete many additional configurations, but the errors are similar to this. I guess maybe coreos does not support custom configuration root partitions, and ign can only format sda2 or nvme0n2 instead of customizing sda1 or nvme0n1. Is that right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant