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

CoreOS 2135.6.0 faild to boot and install on sda (VMWare) #2607

Open
mxb78 opened this issue Aug 16, 2019 · 1 comment

Comments

@mxb78
Copy link

commented Aug 16, 2019

Issue Report

Bug

OS not booting after install on /dev/sda.
"Failed to to start Clean up and Shutting down daemons" seen

Container Linux Version

2135.6.0

Environment

VMWare

Expected Behavior

OS should be up and running

Actual Behavior

Fails to boot properly. Want to drop to emergency shell with in 4min

Reproduction Steps

Try to install on VMWare

Other Information

bash-4.3# coreos-install -d /dev/sda -i coreos.ign -o vmware_raw
Downloading the signature for https://stable.release.core-os.net/amd64-usr/2135.6.0/coreos_production_vmware_raw_image.bin.bz2...
2019-08-16 19:09:01 URL:https://stable.release.core-os.net/amd64-usr/2135.6.0/coreos_production_vmware_raw_image.bin.bz2.sig [566/566] -> "/tmp/coreos-install.8Fiq7TkvD1/coreos_production_vmware_raw_image.bin.bz2.sig" [1]
Downloading, writing and verifying coreos_production_vmware_raw_image.bin.bz2...
2019-08-16 19:10:56 URL:https://stable.release.core-os.net/amd64-usr/2135.6.0/coreos_production_vmware_raw_image.bin.bz2 [447619561/447619561] -> "-" [1]
gpg: Signature made Tue Jul 30 09:05:44 2019 UTC
gpg: using RSA key FD986FB096482F906F55B2EA01C9CAE767B3CA0E
gpg: key 50E0885593D2DCB4 marked as ultimately trusted
gpg: checking the trustdb
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Good signature from "CoreOS Buildbot (Offical Builds) buildbot@coreos.com" [ultimate]
Installing Ignition config coreos.ign...
Success! CoreOS Container Linux stable 2135.6.0 (vmware_raw) is installed on /dev/sda

bash-4.3# fdisk -l
The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/sda: 30 GiB, 32212254720 bytes, 62914560 sectors
Disk model: Virtual disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 00000000-0000-0000-0000-000000000001

Device Start End Sectors Size Type
/dev/sda1 4096 266239 262144 128M EFI System
/dev/sda2 266240 270335 4096 2M BIOS boot
/dev/sda3 270336 2367487 2097152 1G unknown
/dev/sda4 2367488 4464639 2097152 1G unknown
/dev/sda6 4464640 4726783 262144 128M Linux filesystem
/dev/sda7 4726784 4857855 131072 64M unknown
/dev/sda9 4857856 9285631 4427776 2.1G unknown

Disk /dev/loop0: 375.1 MiB, 393285632 bytes, 768136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
bash-4.3# reboot

@lucab

This comment has been minimized.

Copy link
Member

commented Aug 17, 2019

@mxb78 thanks for the report. An emergency shell in initramfs is often the symptom of a wrong Ignition configuration.
Can you please double check your coreos.ign? We have an online validator at http://coreos.com/validate/ or ignition-validate at https://github.com/coreos/ignition/releases/tag/v0.33.0.
Additionally, checking journalctl at the emergency shell should provide more details about what's going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.