siderolabs / siderolabs/docs

Linode / Akamai images unusable - results in kernel panic

Open
#92 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted need infrastructure
Dominant language
MDX
Stars
11
Forks
76
Avg merge
3d 5h
Merged PRs (30d)
26

Description

Bug Report

Description
  • Created the default Akamai image from Image Factory with all default, no additional command line param
  • Loaded the image into Linode
  • Create a linode instance using this image - Linode 2GB
  • Checking the LISH console, there is a kernel panic.
Logs

Output from Linode's LISH console

[    3.913359]  iso9660
[    3.913894]  ntfs3
[    3.914495]  romfs
[    3.915052]  fuseblk
[    3.915656]  udf
[    3.916263]  jfs
[    3.916780]  xfs
[    3.917325]  gfs2
[    3.917845]  gfs2meta
[    3.918372]  btrfs
[    3.918941]
[    3.919950] Kernel panic - not syncing: VFS: Unable to mount root fs on "/de)
[    3.921559] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.2-x86_64-linode164
[    3.923378] Hardware name: Linode Compute Instance, BIOS Not Specified
[    3.924844] Call Trace:
[    3.925517]  <TASK>
[    3.926117]  panic+0x30b/0x330
[    3.926951]  mount_root_generic+0x303/0x310
[    3.928007]  ? srso_return_thunk+0x5/0x5f
[    3.929045]  prepare_namespace+0x69/0x280
[    3.930102]  kernel_init_freeable+0x2a5/0x2f0
[    3.931215]  ? __pfx_kernel_init+0x10/0x10
[    3.932330]  kernel_init+0x1a/0x150
[    3.933280]  ret_from_fork+0x34/0x50
[    3.934284]  ? __pfx_kernel_init+0x10/0x10
[    3.935363]  ret_from_fork_asm+0x1a/0x30
[    3.936371]  </TASK>
[    3.937416] Kernel Offset: 0x21400000 from 0xffffffff81000000 (relocation ra)
[    3.939494] ---[ end Kernel panic - not syncing: VFS: Unable to mount root f-
Environment
  • Talos version: 1.94
  • Kubernetes version: [kubectl version]
  • Platform: Linode

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Image Factory default Akamai image creation steps and reproducing the boot on a Linode 2GB instance. Inspect the LISH console output, especially the kernel panic reporting that the root filesystem cannot be mounted. Done means the generated image boots successfully on Linode without the reported panic.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, linux
Domain
cloud, infrastructure, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.