Ubuntu 23.04安装失败，出现subiquity错误求助

Hey there, sorry to hear you're stuck with this subiquity autoinstall error while setting up Ubuntu 23.04. Let's walk through some troubleshooting steps to get this sorted out.

First, let's recap the error logs you shared—these show that the installer (subiquity) is failing when trying to apply your autoinstall configuration across multiple modules like Early, Reporting, Userdata, Package, Debconf, and Kernel:

Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Early/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Early/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Reporting/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Reporting/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Error/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Error/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Userdata/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Userdata/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Package/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Package/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Debconf/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Debconf/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Kernel/apply_autoinstall_config
Apr 27 14:27:14 ubuntu subiquity_event.3285[3285]: subiquity/Kernel/apply_autoinstall_config

Here are actionable steps to diagnose and fix the issue:

• Validate your autoinstall YAML file syntax
  The most common cause here is a malformed autoinstall.yaml file. YAML is super picky about indentation (use 2 spaces per level, no tabs) and syntax. You can use a tool like yamllint (install it locally with sudo apt install yamllint) to scan your config file for errors. Double-check that all keys are properly nested, strings with special characters are quoted, and there are no missing colons.

• Verify module-specific configurations
  The logs flag issues across multiple modules. For each one:

  • Userdata: Ensure any scripts you've included are valid shell/bash code, with proper shebangs (#!/bin/bash) and no syntax errors.
  • Package: Check that all package names are spelled correctly (Ubuntu 23.04 uses the same package names as Jammy for most packages, but some might differ). Avoid typos or deprecated package names.
  • Debconf: Make sure the debconf settings match the exact questions the packages expect. You can use debconf-show <package-name> on an existing Ubuntu system to verify valid settings.
  • Kernel: If you're specifying kernel parameters, ensure they're valid for Ubuntu 23.04's kernel version.

• Simplify your config and test incrementally
  If you're not sure which module is causing the problem, start with a minimal autoinstall config (only essential settings like disk partitioning, user creation, and locale) and see if the installation completes. Then, add one module at a time, testing after each addition to pinpoint the faulty section.

• Check your installation media
  Corrupted installation media can cause unexpected subiquity errors. Re-download the Ubuntu 23.04 ISO, verify its SHA256 hash against the official value, and re-create your bootable USB (use tools like Rufus or the dd command on Linux/macOS) to ensure no corruption occurred during the process.

• Access detailed subiquity logs
  The event logs you shared are helpful but don't show the exact error message. During the installation failure, switch to a TTY terminal by pressing Ctrl+Alt+F2, then navigate to /var/log/subiquity/ and check files like subiquity-server.log or autoinstall.log. These will have the specific error details (like "invalid key in config" or "package not found") that will point you directly to the problem.

Give these steps a try—chances are the issue is a small syntax mistake in your autoinstall config or a corrupted media file. Let me know if you need help decoding the detailed logs!

备注：内容来源于stack exchange，提问作者mahbob