Likely Resolution of the Edge 71 Error 1962 No Operating System Found

  • Note: 3-1-2026:  Placed a disk with an already successfuly booted install of Ubunu Linux installed on another machine and this Edge71 booted up.

PERP:  On one particular computer I installed ubuntu linux from a usb flash drive with the erase and install option. When done it prompts to remove the usb install media and when it tries to boot of of the hard drive it does not find a bootable disk

This usually means Ubuntu did install to the disk, but the firmware is not actually booting from its bootloader (GRUB) or is not seeing the disk as bootable at all.

To narrow it down, I need a bit more detail:

  • What exact message do you see after POST? (“No bootable device”, “No operating system found”, error code, etc.).

  • What computer/model and approximate age is it? (e.g., Lenovo Edge 71, HP desktop, laptop brand).

  • In its firmware/BIOS setup, is the disk visible and listed in the boot order? Is it set to UEFI, Legacy/CSM, or a mix?

While you check that, here is the usual quick path to confirm and repair:

  1. Boot from the same Ubuntu USB, choose “Try Ubuntu”.

  2. In the live session, run lsblk and confirm your internal disk (likely /dev/sda or /dev/nvme0n1) has Ubuntu partitions (ext4, EFI, etc.).?

  3. If the disk is present and looks fine, then:

    • If the machine is UEFI:

      • Ensure firmware is set to UEFI (not Legacy-only), Secure Boot preferably off, and that the Ubuntu entry (or an EFI file on the disk) is in the boot list.

      • If there is a “Select an UEFI file as trusted for executing” option under Security, point it to the \EFI\ubuntu\grubx64.efi on the internal drive, then put that new entry first in boot order.??

    • If it’s Legacy/BIOS:

      • Make sure boot mode is Legacy (or CSM) and the internal HDD/SSD is first in the boot order.?

      • From the live session, you can reinstall GRUB to the disk MBR:

        • sudo mount /dev/sdaX /mnt (replace sdaX with your Ubuntu root partition)

        • sudo grub-install --target=i386-pc /dev/sda

        • sudo chroot /mnt update-grub?

If instead the internal disk does not appear in lsblk or the BIOS/firmware, the problem is lower-level (cable/port, SATA mode like RAID/Optane/RST instead of AHCI, or the drive itself).

Reply with:

  • Exact model of the computer.

  • Exact boot error text.

  • Whether BIOS shows the drive and in which boot mode (UEFI vs Legacy).

With that I can give you a very specific set of steps rather than general possibilities.

It messages "no bootable device". It is a Lenovo Edge 71. The disk is visible in BIOS. There is no setting in BIOS for UEFI or CSM.

On the Edge 71 this almost always means Ubuntu was installed in EFI mode, but the machine can only actually boot in Legacy/BIOS mode, so the disk has no Legacy GRUB in the MBR and the firmware declares “no bootable device”.

What’s going on on this Edge 71

  • Edge 71 is effectively a Legacy?only box; there is no real UEFI/CSM toggle in BIOS despite some Lenovo docs implying UEFI.

  • If the installer boots in UEFI mode, it creates an EFI System Partition and installs GRUB?EFI to it, leaving the disk MBR without boot code; a Legacy BIOS like yours then sees the disk but finds no bootable code and throws “no bootable device”.?

You already confirmed:

  • Disk is visible in BIOS.

  • There is no UEFI/CSM option.
    So the fix is to ensure Ubuntu (and GRUB) are installed in Legacy mode and GRUB is written to the disk’s MBR.

Fix path A: Reinstall Ubuntu in Legacy mode (cleanest)

  1. Recreate the USB installer in pure BIOS/Legacy?bootable form:

    • Use Ventoy or Balena Etcher instead of Rufus; Rufus often defaults to UEFI?only images that confuse the Edge 71.?

  2. Boot the Edge 71 and tap F12, then explicitly choose the USB entry that looks Legacy (no “UEFI:” prefix; usually just the USB name).

  3. In the installer, again choose Erase disk and install Ubuntu (single?OS).

  4. Let it finish, remove USB when prompted, and it should now boot directly from the HDD because GRUB has been installed to the MBR in Legacy mode.

This is usually the fastest way if you don’t care about keeping the current install.

Fix path B: Convert current install from EFI to Legacy (no reinstall)

If you want to salvage the existing install:

  1. Boot from the Ubuntu USB, choose Try Ubuntu.

  2. In the live session, identify the root partition:

    • lsblk → find your disk (likely /dev/sda) and the main ext4 partition (for example /dev/sda2).?

  3. Mount it and chroot:

    • sudo mount /dev/sda2 /mnt (replace with your root).

    • If you have a separate /boot or others, mount them under /mnt too.

    • for i in /dev /dev/pts /proc /sys; do sudo mount --bind $i /mnt$i; done

    • sudo chroot /mnt

  4. Install Legacy GRUB into the MBR:

    • grub-install --target=i386-pc /dev/sda

    • update-grub

  5. Exit chroot, unmount, reboot, remove USB.

    • The BIOS should now see the disk as bootable and GRUB should load.

This is effectively what Boot?Repair did for the person in the UbuntuForums thread with this exact Edge 71 symptom; converting the install to Legacy mode fixed “This is not a bootable disk”.?

One quick check before spending time

Before doing either path, also rule out the silly case where GRUB got written to the USB:

  • Boot again with the USB inserted, see if you get a GRUB menu and can boot the installed system from there.?

  • If it only boots when the USB is present, then GRUB was likely installed on the USB and not /dev/sda, and reinstalling GRUB to /dev/sda as in path B is the right move.?

If you tell me:

  • How you created the USB (Rufus options, etc.).

  • Output of lsblk from a live session.

I can give you an exact set of commands tailored to your current partition layout (e.g., whether you have a useless EFI System Partition to ignore or reuse).

Please update for the following update response: It messages error 1962 no operating system found It is a Lenovo Edge 71. The disk is visible in BIOS. There is no setting in BIOS for UEFI or CSM.

Error 1962 on the Lenovo ThinkCentre Edge 71 after an Ubuntu "erase and install" means the installer created an EFI System Partition but no GRUB code in the disk's MBR, and since this BIOS is Legacy-only (no UEFI/CSM toggle), it can't find boot code and throws the error even though the disk is visible.

Why this happens on Edge 71

The Edge 71 BIOS (even latest 9QKT39A from 2012) is effectively Legacy/BIOS-only despite Lenovo calling it "UEFI"—it lacks proper EFI boot support, so Ubuntu installers defaulting to EFI mode leave the MBR empty and unbootable.?

Quickest fix: Reinstall in Legacy mode

  1. Recreate USB installer with Ventoy or Etcher (avoid Rufus UEFI defaults).

  2. Power on, tap F12 at Lenovo logo, select the Legacy USB entry (no "UEFI:" prefix).

  3. Install with Erase disk and install Ubuntu.

  4. Remove USB when prompted—it now boots via Legacy GRUB in the MBR.

Salvage current install: Install Legacy GRUB manually

Boot the Ubuntu USB in Legacy mode (F12), choose Try Ubuntu:

sudo apt update && sudo apt install boot-repair boot-repair

  • Choose Recommended repair. It detects the EFI issue, converts to Legacy GRUB on MBR (/dev/sda), and fixes.

Or manually (if no network):

lsblk # note root partition, e.g. /dev/sda2 sudo mount /dev/sda2 /mnt sudo mount --bind /dev /mnt/dev sudo mount --bind /proc /mnt/proc sudo mount --bind /sys /mnt/sys sudo chroot /mnt grub-install --target=i386-pc /dev/sda update-grub exit sudo reboot # remove USB

This writes GRUB to the MBR exactly as Boot-Repair does.?

Verify success

After fix, in running Ubuntu: ls /sys/firmware/efi should fail (confirms Legacy mode).?

If Boot-Repair paste shows EFI remnants post-fix, purge them with GParted (delete fat32 ESP, resize root partition) but usually unnecessary. This resolved the identical "installs but disk is not bootable" on Edge 71.

How to Create a Zip Archive on Ubuntu that is Compatible with Windows

Research Links

Ubuntu Linux zip files often fail to open in Windows due to incompatible character encodings, long file paths exceeding 260 characters, or the use of password protection features that default to Linux-only encryption. To fix this, use 7-Zip on Windows, re-create the archive using zip -r -k archive.zip folder/ in Linux to ensure compatibility, or ensure filenames lack special characters like '  ….. more


Yes, 7-Zip archives (.7z) created on Ubuntu are generally compatible with Windows. 7-Zip is a cross-platform tool, and its file format works across Linux, Windows, and macOS. 

Here are the key details regarding compatibility:

Compatibility Notes

  • Native Compatibility: 7-Zip is open-source and designed to work across platforms. Archives created with p7zip (the command-line port in Linux) or the newer native Linux version of 7-Zip can be opened on Windows using the 7-Zip application.
  • Windows 11 Support: Windows 11 now has native support for extracting 7-Zip archives, meaning you might not even need to install third-party software on the Windows side.
  • File Permissions & Attributes: While the archive will open, be aware that Linux-specific file attributes (like read/write/execute permissions) may not translate directly to Windows.
  • Best Practice for Compatibility: When creating archives that need to be used on both systems, stick to standard settings. If you use specialized compression methods available in newer Linux 7-Zip versions, older Windows 7-Zip versions might need to be updated to extract them. 

To install 7-Zip on Ubuntu, open the terminal (Ctrl+Alt+T) and run sudo apt update followed by sudo apt install p7zip-full. This provides command-line support for various formats via the 7z command. To add support for RAR files, run sudo apt install p7zip-rar

Key Commands:

  • Install: sudo apt install p7zip-full p7zip-rar
  • Compress Files: 7z a archive.7z /path/to/files
  • Extract Files: 7z x archive.7z
  • List Contents: 7z l archive.7z 

For users needing the latest 7-Zip features, the official binary can be downloaded directly from the 

7-Zip website.


Standard Install Disk Partition of Ubuntu Linux of an Erase and Install Instance

  • GAI: what does a standard install disk partition of ubuntu linux look on an erase and install instance?

When selecting the "Erase disk and install Ubuntu" option in the Ubuntu installer (a "clean install"), the installer automatically partitions the entire drive using the GPT (GUID Partition Table) scheme for modern UEFI systems. It typically creates two or three main partitions to manage boot files, the operating system, and memory. 

Here is what a standard, modern (22.04/24.04) "Erase and Install" partition layout looks like:

Typical Modern Layout (UEFI) 

/dev/sda1 (or nvme0n1p1): EFI System Partition (ESP)

  • Size: ~512 MB to 1 GB
  • Filesystem: FAT32
  • Purpose: Contains the bootloader (GRUB) and EFI files.

/dev/sda2 (or nvme0n1p2): Root Partition (/)

  • Size: Remaining space on the disk
  • Filesystem: EXT4
  • Purpose: Contains the OS, applications, and user files.

Swap:

  • Modern Behavior: Modern Ubuntu versions typically do not create a separate swap partition. Instead, they create a swap file (e.g., /swapfile) located inside the root (/) partition

Notes

  1. EFI = Extensible Firmware Interface
  2. UEFI = Unified Extensible Firmware Interface

An EFI partition (or EFI System Partition, ESP) is a small, FAT32-formatted partition on a hard drive or SSD required by UEFI-based computers to boot the operating system. It holds bootloaders, drivers, and system utilities. EFI stands for Extensible Firmware Interface, which is the predecessor to the modern Unified Extensible Firmware Interface (UEFI). 

Key Details About Linux EFI Partitions:

  • Purpose: The UEFI firmware reads this partition to find and load the bootloader (e.g., GRUB, systemd-boot) to start Linux.
  • Size & Filesystem: It is typically 100MB to 500MB, formatted with FAT32.
  • Mount Point: In Linux, it is usually mounted at /boot/efi.
  • Requirement: Mandatory for booting in native UEFI mode, not required for legacy BIOS/MBR.
  • Multi-boot: A single EFI partition can store bootloaders for multiple operating systems, including Windows and various Linux distributions. 

If you are using a GPT disk, the EFI partition is assigned a specific GUID to help the system identify it.

The following is an Ubuntu Install USB stick partition set

Unit 34.1: WordPress Header like wpBeginner

wpBeginner header

Research Links

To create a WordPress header similar to WPBeginner without editing code, you can use drag-and-drop page builder plugins or your theme's built-in header customization options.

Here are the main approaches:

Using a Theme Builder Plugin (Recommended for advanced customization):

Plugins like SeedProd or Elementor (with an add-on like Boostify Header Footer Builder) offer extensive drag-and-drop functionality to design custom headers.

  • Install and activate your chosen builder plugin.
  • Navigate to the plugin's theme builder or header options in your WordPress dashboard.
  • Create a new header template and apply display conditions (e.g., "Entire Site").
  • Use the builder's elements (logo, navigation menu, search bar, etc.) to design the layout, style, and make it responsive.
  • Many builders also have options to make the header "sticky" on scroll.

Using your Theme's Customizer or Site Editor: Many modern themes, especially those supporting Full Site Editing (FSE), have options in the Appearance > Editor or Appearance > Customize sections.

  • Go to Appearance > Editor and select the "Header" template part.
  • Use the block editor to add a logo block, site title block, and navigation block.
  • Adjust styling like background color, font sizes, and layout to match the WPBeginner style.

Adding Code Snippets: If you only need to insert specific code (like tracking scripts or custom CSS) into the header, you can use the free WPCode plugin (formerly Insert Headers and Footers by WPBeginner) instead of modifying theme files.

  • Install and activate WPCode.
  • Go to Code Snippets > Header & Footer.
  • Paste your code into the "Header" box and save changes.

By utilizing these tools, you can replicate the desired header style without needing advanced coding knowledge.

  • GAI: Seedprod Starter Theme  – SeedProd's Starter Theme is a minimalist, responsive WordPress framework designed to be customized without code using their drag-and-drop Theme Builder. It serves as a foundation, including pre-built templates for headers, footers, single posts, and WooCommerce pages. The theme emphasizes speed, ease of use, and full visual control for designing custom WordPress sites………more
  • Seedprod Documentation
  • Wordpress.org: Website Builder by SeedProd — Theme Builder, Landing Page Builder, Coming Soon Page, Maintenance Mode
  • Seedprod pricing

Lenovo Thinkcenter Edge71 Ubuntu Install and Boot Fix error 1962 no operating system found

Research Links

Error 1962 (No Operating System Found) on Lenovo systems indicates the BIOS cannot detect a bootable drive, often due to improper boot order or missing CSM/Legacy mode. If CSM is missing, ensure the BIOS is set to UEFI, change boot priority to UEFI First, check SATA cables, and potentially restore default BIOS settings. 

 

Notes

  1. Unit had Win 10 installed. 
  2. Installed Ubuntu from USB flash install drive – after install error flagged
  3. error 1962 no operating system – occurs at boot up. 
  4. BIOS date: 2-14-2014    Version 9QKT37AUS
  5. I can not find: CSM (Compatibility Support Module) in the BIOS
  6. I tried the boot repair method: Ubuntu.com: Error 1962: no operating system found after installing 12.04 (Lenovo ThinkCentre) – see below.  This page has many other methods tried by flailing users.

I had the same issue and the following worked for me:

  1. Run ubuntu from installation disk
  2. install and run boot-repair (you need internet access)

    sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update
    sudo apt-get install -y boot-repair && (boot-repair &)
    
  3. just choose the "Recommended Repair"

  4. boot from harddisk installation
  5. repeat steps 1-3
  6. restart.

it should work now.  ( It does not work )

 

The following partition is what was on the Ubuntu 500GB Seagate that I installed Ubuntu on

  • SDA – is the 500 gb hard drive
  • SDB – is the 64 gb USB stick used for Ubuntu installations