preloader
post-thumb

Last Update: October 11, 2024 5 min read


BYauthor-thumberic

|Loading...

Short answer: on my ThinkPad, Ubuntu installed without errors but the laptop then behaved as if there was nothing bootable on the drive. What got it working was going into ThinkPad Setup (F1 at power-on), setting Security > Security Chip to Disabled, and then reinstalling Ubuntu. If that doesn't do it for you, the next things to check are that the firmware boot mode (UEFI or Legacy) matches the mode the installer booted in, and Secure Boot. Both are covered below.

I'd installed Linux on Dell and HP machines before without this problem. On the ThinkPad:

  • Reinstalling Ubuntu on its own didn't help.
  • Trying to repair GRUB from the live USB didn't help either. (The command I used then, sudo grub-install --root-directory=/mnt/boot, was not the right one. See the GRUB section below for what to run instead.)
  • Searching around, other people with the same symptom suggested disabling the TPM. I did that, reinstalled, and Ubuntu booted normally from then on.

I've since confirmed it: the Security Chip (TPM) setting was the cause on this ThinkPad, and a reader left a comment thanking me for the post after hitting the same problem. It's surprising, because a normal Ubuntu install doesn't use the TPM, but on these machines it made the difference. If disabling it doesn't fix yours, work through the other checks below.

Step 1: get into ThinkPad Setup

Power on and press F1 when the Lenovo logo appears. Many ThinkPads show "To interrupt normal startup, press Enter". Enter gives you a menu where F1 opens Setup and F12 opens the one-off boot menu.

Other Lenovo laptops differ. IdeaPads and Yogas usually use F2 (sometimes Fn+F2) or the small Novo button on the side.

Step 2: disable the Security Chip (TPM)

Go to the Security tab and select Security Chip, then press Enter.

ThinkPad Setup Security tab with Security Chip highlighted

On my ThinkPad the Security Chip Type was TPM 2.0. Set Security Chip to Disabled. The help text on the right says this hides the security chip from the operating system.

ThinkPad Setup Security Chip screen: Security Chip Type TPM 2.0, Security Chip set to Disabled

Leave Physical Presence for Clear alone. Disabling the chip is not the same as clearing it. Clearing wipes the keys stored in the TPM, which you don't want if Windows or anything else relies on them.

Press F10 to save and exit, then reinstall Ubuntu (or repair GRUB, below).

Before you do this on a dual-boot machine: if Windows uses BitLocker or device encryption, hiding the TPM will make Windows ask for the BitLocker recovery key on its next boot. Get the key from your Microsoft account (or suspend BitLocker in Windows) first. Windows 11 also expects TPM 2.0, so you may need to switch it back on if you keep Windows. And if you chose Ubuntu's TPM-backed full disk encryption option in the installer, don't disable the TPM.

Step 3: check the boot mode (UEFI vs Legacy)

This is the most common reason for "installed fine, now no bootable device" on any brand, so check it if the TPM change alone doesn't fix yours.

In ThinkPad Setup, go to Startup. On my ThinkPad, UEFI/Legacy Boot was set to Legacy Only, with CSM Support set to Yes.

ThinkPad Setup Startup tab: UEFI/Legacy Boot set to Legacy Only, CSM Support Yes

The rule is simple: the installer must boot in the same mode you want Ubuntu to boot in. A UEFI install writes the bootloader to the EFI system partition and adds a UEFI boot entry. A Legacy (BIOS) install writes GRUB to the start of the disk. If you install one way and the firmware then starts in the other mode, it won't find anything to boot.

To see which mode the live USB booted in, open a terminal in the live session and run:

bash
[ -d /sys/firmware/efi ] && echo "UEFI" || echo "Legacy BIOS"

What to set:

UEFI/Legacy Boot setting
What happens
Use it when
UEFI Only
Firmware only starts UEFI bootloaders
Recommended for current Ubuntu releases on any ThinkPad that supports it
Both
Firmware tries both. The USB may start in either mode
Avoid while installing. You can end up installing in the wrong mode without noticing
Legacy Only
Firmware only starts BIOS (MBR) bootloaders
Older machines, or an existing install that was done in Legacy mode

If you change this setting after installing, you need to reinstall (or reinstall GRUB for the new mode). Changing it doesn't convert an existing install.

Step 4: Secure Boot

Secure Boot is under Security > Secure Boot (you can see it in the first screenshot), not on the Startup tab. An earlier version of this post put the Secure Boot note next to the Startup screenshot, which was misleading.

Stock Ubuntu boots fine with Secure Boot on, because it uses a Microsoft-signed shim. Secure Boot usually only gets in the way when:

  • you install third-party drivers (for example NVIDIA) and skip the MOK enrolment screen on the first reboot, or
  • the firmware is very old and its Secure Boot keys are out of date.

Secure Boot only applies in UEFI mode. With Legacy Only it has no effect. If you're stuck, turning it off is a reasonable test, but you can usually turn it back on once things work.

Step 5: repair the bootloader from the live USB

If you'd rather not reinstall, boot the Ubuntu USB in the same mode as your install, choose "Try Ubuntu", and open a terminal. Find your partitions first:

bash
lsblk -f

Then mount the installed system and reinstall GRUB from inside it. Replace the device names with yours (/dev/nvme0n1p2 for an NVMe root partition, /dev/sda2 for SATA, and so on):

bash
sudo mount /dev/nvme0n1p2 /mnt              # your Ubuntu root partition
sudo mount /dev/nvme0n1p1 /mnt/boot/efi     # UEFI only: the EFI system partition (vfat, ~512 MB-1 GB)
for d in /dev /dev/pts /proc /sys /run; do sudo mount --bind $d /mnt$d; done
sudo chroot /mnt

Inside the chroot:

bash
# UEFI install
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ubuntu
# or, for a Legacy (BIOS) install, point it at the whole disk, not a partition
# grub-install /dev/sda

update-grub
exit

Reboot without the USB.

Why the original command didn't work: --root-directory is an old option (current GRUB uses --boot-directory), and running grub-install from the live system without a chroot, an EFI directory or a target disk installs the wrong thing, or nothing useful.

If a UEFI install still isn't found, some firmware ignores the boot entry Ubuntu creates. Check what the firmware has with sudo efibootmgr -v. As a workaround, inside the chroot run:

bash
grub-install --target=x86_64-efi --efi-directory=/boot/efi --removable

That also installs GRUB to the fallback path \EFI\BOOT\BOOTX64.EFI, which UEFI firmware tries when it has no other entry. You can also press F12 at power-on and see whether "ubuntu" appears in the boot list.

Quick checklist

  1. F1 into ThinkPad Setup.
  2. Startup > UEFI/Legacy Boot: pick UEFI Only (or Legacy Only), not Both, and install in that mode.
  3. Security > Security Chip: try Disabled if the install still won't boot. Sort out BitLocker first if Windows is on the machine.
  4. Security > Secure Boot: turn off only as a test.
  5. F10 to save, then reinstall or repair GRUB from the live USB with the commands above.

Credits

Photo by Arthur Mazi on Unsplash

Comments (0)

Leave a Comment
Your email won't be published. We'll only use it to notify you of replies to your comment.
Loading comments...
Previous Article
post-thumb

Nov 28, 2024

Fixing Crackling VoIP Calls Behind a Meraki MX: Traffic Shaping Rules and a Voice VLAN

After moving an office's desk phones behind a Meraki MX64W, calls started crackling. Traffic shaping rules that prioritise voice and cap bulk traffic fixed it. Here are the exact rules, what to change in them, and the voice VLAN step.

Next Article
post-thumb

Jun 28, 2024

MetaTrader APIs for Algo Trading: MQL, the Python Package, ZeroMQ Bridges and Protocol Libraries Compared

The four realistic ways to drive MT4/MT5 from your own trading code, what each one costs you, and what I learned running a terminal-free protocol library and the official Python package against real broker accounts.

agico

We transform visions into reality. We specializes in crafting digital experiences that captivate, engage, and innovate. With a fusion of creativity and expertise, we bring your ideas to life, one pixel at a time. Let's build the future together.

Copyright ©  2026  TYO Lab · v0.0.39