Flatcar: Packet c3.medium.x86 instances can't find root device because of ahci module failure

Description

While the first boot works fine after the installation, following reboots get stuck in the initramfs because the root partition cannot be found. Reloading the ahci kernel module resolves this.

Impact

Flatcar Container Linux is not working on these instances (and maybe others).

Environment and steps to reproduce

Set-up: Select Flatcar for a c3.medium instance on Packet
Task: Reboot
Action(s): Login via the OOB console and wait for the dracut shell after some minutes (up to 15) and press Enter (only 5 minutes time) to enter the shell which shows that /dev/disk-by-label is empty a. To resolve this, unload and load the ahci module, check that /dev/disk-by-label has the root partition, then exit to continue the boot
Error: This seems to be the related error message: ata10.00: both IDENTIFYs aborted, assuming NODEV

Expected behavior The module works so that the root partition can be found

Additional information @marga-kinvolk Did I miss something?

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 18 (18 by maintainers)

Most upvoted comments

Because after those 28 minutes, there’s a couple of seconds when the normal GRUB screen is visible (the one that says Flatcar A and Flatcar B) and after that the boot starts with all its boot output. Also, we can see timing in the kernel logs and it matches the timing of it getting started after those 28 minutes.

margamanterola on Jul 8, 2020