# OS Imaging

| S. No. | Symptom | Additional Details | Common Checks | Log Files | **Remarks** |
| --- | --- | --- | --- | --- | --- |
| 1 | Windows Setup fails before completion | - Do **not** dismiss error dialogs immediately, as this may remove diagnostic information. - Use **iLO Remote Console** to access the system. - Press **Shift + F10** to open a command prompt in the Windows PE environment. | **Disk layout** – Confirm the primary disk is attached to the local RAID controller.  **AutoUnattend.xml** – Verify the file exists and defines required partitions:   - EFI System Partition (500 MB) - Microsoft Reserved Partition (128 MB) - Primary OS partition | Relevant setup logs may be found in:   - `X:\Windows\Panther` - `C:\$WINDOWS.~BT\Sources\Panther`   Key files:   - `setupact.log` - `setuperr.log` | Use logs to identify the specific failure stage and error code. |
| 2 | RHEL / Oracle Linux  (Autoinstall via Kickstart) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**   - Alt + F1: Installer UI - Alt + F2: Interactive shell - Alt + F3: Installation logs | **Key Logs:**   - `/var/log/anaconda/anaconda.log` - `/var/log/anaconda/syslog` - `/root/anaconda-ks.cfg` - `/root/original-ks.cfg` - `/root/post-ks.log` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to validate disk and network configuration before retrying installation. |
| 3 | Ubuntu Linux  (Autoinstall via Curtin and Subiquity) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**  - Alt + F2 or Ctrl + Alt + F2: Interactive shell - Installer runs on TTY1 | **Key Logs**   - `/var/log/installer/curtin-install.log` - `/var/log/installer/early-commands.log` - `/var/log/installer/subiquity-client*` - `/var/log/installer/subiquity-server*` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to check network and storage configuration, then review logs for errors. |
| 4 | SLES(AutoYaST Installation) | If the installation fails or hangs, the installer provides interactive consoles and log files for troubleshooting | **TTY Shortcuts:**  - Ctrl + Alt + F1: Installer UI - Ctrl + Alt + F2: Interactive shell - Ctrl + Alt + F3: Installation log output  **Common Checks:**  - Verify network connectivity and repository access. - Confirm AutoYaST XML profile is accessible and valid. - Validate disk selection and storage configuration. - Check registration settings if using SUSE Customer Center (SCC). | **Installer Logs:**  - `/var/log/YaST2/y2log` - `/var/log/YaST2/autoinstallation` - `/var/log/linuxrc.log`  **Post-Install Logs:**  - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` - `/var/log/zypper.log` | Use the interactive shell to validate network, storage, and repository access.  Review AutoYaST and YaST logs to identify profile validation, package installation, registration, or storage configuration failures. |
| 5 | Linux  Cloud-init / package install failures with SSL errors | Repo downloads fail during provisioning. Errors like `certificate is not yet valid`, `SSL certificate problem`, `yum/dnf metadata download failure`. Often seen during first boot of VM. | - Check system time using `timedatectl`. - Verify NTP sync (`chronyd` or `systemd-timesyncd`). - Validate outbound internet access. - Confirm DNS resolution. | - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` - `/var/log/messages` | Root cause is usually incorrect system clock (time drift or boot-time epoch issue). Fix by enabling NTP or correcting system time.  After correction, re-run cloud-init or reboot services if needed. |
