September 11, 2026
13 min read
By Kokil Thapa | Last reviewed: September 2026
An Ubuntu Installation Troubleshooting Guide saves hours when a clean install stalls before the desktop appears. You verified the ISO checksum, wrote a bootable USB, and still hit a black screen, a frozen spinner, or a cryptic partition error. That pattern is normal. I've seen it on client laptops, office PCs, and fresh VPS images during Linux server setup work. Most failures fall into five buckets: bad media, firmware settings, storage layout, graphics drivers, and post-install boot order. This guide walks through each one with copy-paste commands and the checks I run on production Ubuntu 24.04 LTS and 22.04 LTS systems in 2026.
Quick answer: Start this Ubuntu Installation Troubleshooting Guide by verifying the ISO SHA256 hash, recreating the boot USB with Balena Etcher or Rufus, disabling Secure Boot or enrolling the shim key, checking UEFI vs Legacy mode matches your disk, freeing partition space, and running the installer with nomodeset if the screen freezes.
Why does Ubuntu installation fail on bootable USB media?
Boot media problems cause more failed installs than anything else. The installer never loads, or it loads once and never again. Treat the USB stick as suspect until you prove otherwise.
Verify the ISO before you write anything
Download Ubuntu Desktop or Server from the official site only. After download, compare the SHA256 hash. On Linux or WSL:
sha256sum ~/Downloads/ubuntu-24.04.3-desktop-amd64.iso
Match the value listed on ubuntu.com/download/desktop. A single corrupted byte can produce random installer crashes that look like hardware faults.
Recreate the USB with a proven tool
On Windows, use Rufus with GPT partition scheme for UEFI systems. On macOS or Linux, Balena Etcher or dd work well. Avoid generic "multiboot" tools unless you know they support your Ubuntu release.
sudo dd if=~/Downloads/ubuntu-24.04.3-desktop-amd64.iso of=/dev/sdX bs=4M status=progress conv=fsync
Replace /dev/sdX with your USB device. Use lsblk first. Writing to the wrong disk wipes data permanently.
Test the USB on a second machine
If the stick boots elsewhere, your target PC has firmware or storage issues. If it fails everywhere, recreate media. Our bootable USB creation guide covers tool-specific settings that prevent silent write failures.
- Try a USB 2.0 port on the rear I/O panel. USB 3 hubs often fail early boot.
- Disable "Fast Boot" in BIOS. It skips USB enumeration.
- Remove other USB devices during install. Some webcams and dongles conflict.
- Use a different stick. Cheap flash wears out and corrupts writes silently.
How do you fix Secure Boot and UEFI errors during Ubuntu installation?
Modern PCs ship with UEFI firmware and Secure Boot enabled. Ubuntu supports both, but vendor implementations vary. Mismatch between firmware mode and partition table causes the classic "No bootable device" message.
Confirm UEFI vs Legacy (CSM) mode
Open firmware setup at power-on. Common keys: F2, F10, Del, Esc. Look for "Boot Mode" or "CSM". For GPT disks on hardware from 2015 onward, use UEFI without CSM. For older MBR-only layouts, Legacy may be required. Mixing modes breaks dual-boot setups fast.
Secure Boot options that actually work
Ubuntu ships signed shim and GRUB binaries. Most Dell, Lenovo, and HP machines install fine with Secure Boot on. If the installer refuses to proceed, try these in order:
- Update firmware to the latest vendor release.
- Temporarily disable Secure Boot, install Ubuntu, then re-enable it after updates.
- Clear old UEFI keys if you previously ran another OS installer.
- Ensure EFI System Partition (ESP) exists and is FAT32, typically 512 MB.
Official background lives in the Ubuntu UEFI wiki. For dual-boot with Windows, read our dual-boot Ubuntu with Windows guide before you shrink partitions.
| Symptom | Likely cause | Fix |
|---|---|---|
| Black screen after "Install Ubuntu" | Secure Boot + old GPU | Disable Secure Boot or use nomodeset |
| "No EFI partition" warning | MBR disk in UEFI mode | Repartition with GPT + ESP |
| GRUB not in boot list | Fast Boot hides entries | Disable Fast Boot, run efibootmgr |
| Windows Boot Manager only | Boot order wrong | Pick ubuntu entry in UEFI menu |
| Shim verification failed | Corrupt ESP or USB | Recreate ESP, rewrite USB |
Check existing EFI entries from a live session
Boot "Try Ubuntu" and open a terminal:
sudo efibootmgr -v
lsblk -f
sudo blkid | grep -i vfat
You should see an ESP mounted at /boot/efi after install. If efibootmgr lists no Ubuntu entry, the installer did not register GRUB. Reinstall GRUB from chroot as described later in this guide.
What causes the Ubuntu installer to freeze or hang at specific stages?
Installer hangs feel random until you map them to a stage. Each stage loads different kernel modules and drivers. Knowing the stage narrows the fix.
Freeze at language or logo screen
This usually means graphics initialization failed. At the GRUB menu, highlight "Try or Install Ubuntu", press E, and append:
nomodeset
Press F10 to boot. If that works, install proprietary drivers after first boot. NVIDIA and some AMD laptops need this step. Our Ubuntu GNOME desktop guide covers post-install driver setup.
Hang at "Getting ready" or update download
The installer pulls packages if networking works. A captive portal or flaky Wi-Fi stalls progress. Use Ethernet for the install pass. Or skip updates during install and run sudo apt update && sudo apt upgrade afterward.
Freeze during partitioning scan
Broken partition tables, failing SSDs, and encrypted drives confuse the partman scanner. Boot the live ISO, then inspect disks:
sudo fdisk -l
sudo dmesg | tail -50
sudo smartctl -a /dev/nvme0n1
Look for I/O errors in dmesg. Replace failing hardware before you install. For BitLocker or LUKS volumes, decrypt or shrink from the native OS first.
Virtual machines have their own quirks. If you are testing in VirtualBox or VMware, see our guides for VirtualBox Ubuntu install and VMware Workstation setup. Enable VT-x or AMD-V in BIOS first.
How do you troubleshoot partition and disk errors when installing Ubuntu?
Partition errors block the install or erase the wrong data. Always back up before you repartition. On production servers I maintain, we snapshot VPS disks before any layout change.
Insufficient free space
Ubuntu Desktop wants at least 25 GB for a comfortable root partition. Server installs can run smaller but leave room for logs and updates. Check free space from the live environment:
sudo parted /dev/nvme0n1 print free
Shrink Windows from its own Disk Management tool before you touch partitions in the Ubuntu installer. Never shrink NTFS from Linux without running ntfsfix and a Windows chkdsk pass first.
"Unable to install alongside" message
The installer auto-resizes when it sees unallocated space. If every byte is allocated, pick "Something else" for manual partitioning. A typical UEFI desktop layout:
- ESP: 512 MB, FAT32, mount
/boot/efi - /: ext4, 40 GB or more, mount
/ - swap: equal to RAM up to 8 GB, or use a swap file later
- /home: optional separate ext4 for user data
On servers that will run PHP or Laravel, I allocate separate /var when logs grow fast. See Ubuntu server setup for PHP apps for sizing notes.
RAID, LVM, and encryption gotchas
Software RAID and LVM confuse beginners. If you did not set them up on purpose, choose the plain ext4 option. For full-disk encryption, pick "Encrypt the new Ubuntu installation" during setup. Store the recovery key offline. Losing it means losing data.
When migrating an old server, our website migration service often starts with a clean Ubuntu base and a controlled data import. That beats fighting a broken partition map on a live disk.
What should you check when Ubuntu installs but will not boot?
Install completes, you reboot, and land on a blank screen or Windows again. Post-install boot issues are fixable without starting over.
Pick the right boot entry once
Open the one-time boot menu. Common keys: F12, F11, Esc. Select the entry that mentions ubuntu or your disk model. If it boots, enter firmware setup and move Ubuntu above Windows Boot Manager.
Reinstall GRUB from live USB
Boot the live ISO. Open terminal and identify the root partition:
lsblk -f
sudo mount /dev/nvme0n1p2 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
grub-install
update-grub
exit
sudo reboot
Adjust partition numbers to match your system. The ESP is usually p1 on NVMe drives.
Kernel panic or initramfs drop to shell
Usually means the wrong UUID in /etc/fstab or a missing driver for your storage controller. From the initramfs prompt, run ls /dev/sd* to see if disks appear. Regenerate initramfs after fixing fstab:
sudo update-initramfs -u
For servers running web stacks, I verify boot stability before installing Nginx, PHP, or MySQL. Follow LEMP stack setup on Ubuntu only after clean reboots pass three times.
First boot housekeeping
After a successful install, run updates and install basic tools:
sudo apt update && sudo apt full-upgrade -y
sudo apt install curl git ufw -y
Harden the box before exposing it to the internet. Our initial Ubuntu server setup guide and UFW firewall tutorial cover the first-hour checklist. Sites on shared EC2 infrastructure — like the sister legal-tech portals I deploy with Deployer 7 — all start from this same baseline.
If you are new to the platform, start with the Ubuntu installation guide for beginners and the download and installation walkthrough. They cover baseline steps this troubleshooting guide assumes you already attempted.
How do you diagnose Ubuntu install logs when nothing obvious works?
When standard fixes fail, logs tell the truth. The installer writes to several locations you can read from a live session or tty.
Installer logs on the live system
Press Ctrl+Alt+F2 during install to reach a tty. Log in if prompted, then:
sudo tail -100 /var/log/installer/syslog
sudo cat /var/log/installer/media-info
Search for ERROR, GRUB, and partman lines. Copy relevant sections before rebooting. Paste them into our JSON formatter tool only if you are parsing structured output from cloud-init on VPS installs.
Hardware and memory tests
Random crashes during file copy often trace to bad RAM or overheating. Boot memtest from GRUB if available. Let it run at least one full pass. Clean laptop vents and retry on mains power. I've wasted hours chasing "driver bugs" that were failing DIMMs.
Cloud VPS and dedicated server specifics
Providers like DigitalOcean, Hetzner, and local Nepali hosts expose serial console and recovery ISOs. If SSH never arrives after install, open the provider console first. Rebuild from snapshot only after you capture logs. For Laravel production boxes, read deploy Laravel on Ubuntu VPS with Nginx after the OS layer is stable.
Need hosting picked and configured correctly from day one? Domain registration and hosting setup covers DNS, VPS sizing, and the split between managed and self-administered servers. Typical VPS costs in Nepal run Rs 1,500–5,000/month (~USD 11–37) depending on RAM and SSD.
Reference docs for deeper reading live at help.ubuntu.com. Pair that with our Ubuntu security hardening guide and file permissions explainer once the system boots.
On the Adventure Third Pole Trek booking platform, the production Laravel app runs on Ubuntu with the same install-and-harden workflow described here. A clean base OS makes PHP 8.3+, MySQL, and queue workers predictable. Skipping troubleshooting at install time creates mystery failures six months later.
Key Takeaways
- Verify ISO SHA256 and rewrite the USB before you touch BIOS settings.
- Match UEFI/GPT or Legacy/MBR end to end; never mix partition styles.
- Use nomodeset for early boot freezes; fix GPU drivers after install.
- Keep 512 MB ESP, 25 GB+ root, and backups before manual partitioning.
- Reinstall GRUB from chroot when the install succeeds but boot fails.
- Read
/var/log/installer/syslogbefore rebuilding the entire machine.
People Also Ask
Why does Ubuntu say "grub-install failed" during installation?
GRUB install fails when the EFI System Partition is missing, full, or formatted wrong. It also fails if Secure Boot blocks unsigned bootloaders on odd firmware. Boot live media, confirm a FAT32 ESP exists, and rerun grub-install from chroot. Disable Secure Boot temporarily if the error persists after two attempts.
Can I install Ubuntu without losing Windows?
Yes, with dual-boot on separate partitions. Shrink Windows from Disk Management, leave unallocated space, then choose "Install alongside" in the Ubuntu installer. Back up important files first. Partition mistakes are the main data-loss risk, not the bootloader itself.
What Ubuntu version should I install in 2026?
Ubuntu 24.04 LTS is the current long-term support desktop and server release. It receives security updates for years. Use 22.04 LTS only if vendor software mandates it. Both work with PHP 8.3+, Node.js 26 LTS, and modern web stacks.
How long should a normal Ubuntu installation take?
Desktop install on SSD hardware takes 15–30 minutes including updates. Slow USB 2.0 sticks or large update downloads extend that to an hour. If progress sits unchanged for more than 20 minutes at one percentage, treat it as a hang and apply stage-specific fixes from this guide.
Get a clean Ubuntu base before you deploy
Most production pain traces back to a rushed install. This Ubuntu Installation Troubleshooting Guide gives you a repeatable path from failed boot media to a stable server ready for Nginx, PHP, queues, and TLS. If you want the OS layer, firewall, and deploy pipeline done correctly the first time, contact us for server setup and ongoing support or explore support and maintenance options. For the full install walkthrough, read the Ubuntu desktop complete guide and server setup guide next.
Frequently Asked Questions
A step-by-step path for fixing Ubuntu installs that stall before the desktop appears—black screens, frozen spinners, partition errors, and post-install boot failures. It groups most problems into bad media, firmware settings, storage layout, graphics drivers, and boot order.
Boot media causes more failed installs than anything else. The installer never loads, or it loads once and never again. Verify the ISO SHA256 hash against ubuntu.com, recreate the stick with Rufus on Windows or Balena Etcher on macOS and Linux, and test on a second machine. Use a rear USB 2.0 port, disable Fast Boot in BIOS, remove conflicting dongles, and swap worn flash drives. A single corrupted byte in the ISO can produce crashes that look like hardware faults.
Confirm firmware boot mode matches your disk: UEFI with GPT on hardware from 2015 onward, Legacy with MBR on older layouts. Mixing modes breaks dual-boot setups fast. Ubuntu ships signed shim and GRUB binaries, so Dell, Lenovo, and HP machines often install fine with Secure Boot on. If the installer refuses, update firmware, temporarily disable Secure Boot, clear old UEFI keys, and ensure a 512 MB FAT32 EFI System Partition exists. From a live session, run efibootmgr and lsblk to confirm Ubuntu registered in the boot list.
Each stage loads different kernel modules, so the freeze location narrows the fix. A hang at the language or logo screen usually means graphics initialization failed. Stalls at Getting ready often trace to captive portals or flaky Wi-Fi during update downloads. Freezes during partitioning scan suggest broken partition tables, failing SSDs, or encrypted BitLocker or LUKS volumes. Boot the live ISO and inspect disks with fdisk, dmesg, and smartctl. Replace failing hardware or decrypt encrypted volumes from the native OS before you retry the install.
Always back up before repartitioning. Ubuntu Desktop wants at least 25 GB free; check from the live environment with parted print free. Shrink Windows from its own Disk Management tool and leave unallocated space. Never shrink NTFS from Linux without ntfsfix and a Windows chkdsk pass first. If Install alongside fails, pick Something else and set a 512 MB FAT32 ESP, a 40 GB or larger ext4 root, optional swap equal to RAM up to 8 GB, and optional separate /home. Avoid accidental RAID or LVM unless you planned them.
Open the one-time boot menu with F12, F11, or Esc and select the entry mentioning ubuntu or your disk model. If it boots once, move Ubuntu above Windows Boot Manager in firmware setup. When GRUB is missing, boot live media, mount root and the ESP, chroot, and rerun grub-install plus update-grub. Kernel panic or an initramfs shell usually means a wrong UUID in fstab or a missing storage driver. Fix fstab, then regenerate initramfs with update-initramfs -u. Verify three clean reboots before installing Nginx, PHP, or MySQL.
Press Ctrl+Alt+F2 during install to reach a tty, then read the last 100 lines of /var/log/installer/syslog and the full media-info file. Search for ERROR, GRUB, and partman lines and copy relevant sections before rebooting. Random crashes during file copy often trace to bad RAM or overheating, so run memtest from GRUB for at least one full pass. On VPS installs through DigitalOcean, Hetzner, or local Nepali hosts, open the serial console if SSH never arrives, capture logs, and avoid rebuilding from snapshot until you understand the failure.
GRUB install fails when the EFI System Partition is missing, full, or formatted wrong, or when Secure Boot blocks unsigned bootloaders on odd firmware. Boot live media, confirm a FAT32 ESP exists using lsblk and blkid, then rerun grub-install from a chroot environment. Disable Secure Boot temporarily if the error persists after two attempts. Recreate a corrupt ESP and rewrite the USB if shim verification failed. The installer did not register GRUB when efibootmgr lists no Ubuntu entry after a seemingly successful pass.
Yes, with dual-boot on separate partitions. Shrink Windows from Disk Management, leave unallocated space, then choose Install alongside in the Ubuntu installer. Back up important files first because partition mistakes are the main data-loss risk, not the bootloader itself. Match UEFI and GPT end to end, keep a 512 MB ESP, and read a dual-boot guide before shrinking partitions. Clearing old UEFI keys and fixing boot order prevents landing back in Windows Boot Manager after every reboot.
Ubuntu 24.04 LTS is the current long-term support desktop and server release with years of security updates. Use 22.04 LTS only if vendor software mandates it.
Desktop install on SSD hardware takes 15 to 30 minutes including updates. Slow USB 2.0 sticks or large update downloads can extend that to an hour. If progress sits unchanged for more than 20 minutes at one percentage, treat it as a hang and apply stage-specific fixes from this guide rather than waiting indefinitely.
On GPT disks in UEFI mode, allocate a 512 MB FAT32 EFI System Partition mounted at /boot/efi, an ext4 root partition of 40 GB or more at /, optional swap equal to RAM up to 8 GB, and an optional separate /home for user data. Never mix UEFI with MBR or Legacy with GPT. For full-disk encryption, pick Encrypt the new Ubuntu installation during setup and store the recovery key offline. On servers running PHP or Laravel, consider a separate /var when logs grow quickly.
At least 25 GB free for a comfortable root partition. Server installs can run smaller but should leave room for logs, updates, and application data.
Typical VPS costs in Nepal run Rs 1,500 to 5,000 per month, roughly USD 11 to 37, depending on RAM and SSD size. Providers expose serial console and recovery ISOs when SSH never arrives after install. Snapshot VPS disks before any layout change on production servers, the same practice I use before deploying Laravel, WordPress, or eCommerce stacks. Capture installer logs before rebuilding so you do not lose diagnostic detail.
At the GRUB menu, highlight Try or Install Ubuntu, press E, append nomodeset to the linux line, and press F10 to boot. This bypasses early graphics initialization that fails on NVIDIA and some AMD laptops, especially when Secure Boot and old GPU firmware combine badly. If the screen works with nomodeset, complete the install and add proprietary drivers after first boot. Also try disabling Secure Boot temporarily and updating firmware if nomodeset alone does not help.
0 Comments
Leave a comment
Your email is not published. Comments appear once they have been read. Sign in to have your details filled in.
