FIXED: No Devices Matches MBR Identifier ▷ Set MBR ID

☰

Fixing the "No Devices Matches MBR Identifier" Boot Error: Encountering a boot error like "No Devices Match MBR Identifier" while trying to boot openSUSE or other Linux distros from a custom USB flash drive? This message typically indicates that the Disk Identifier (or Disk ID) stored in the Master Boot Record (MBR) does not match the identifier expected by the bootloader which is usually found in the /boot/grub/mbrid file.

This mismatch can happen if you manually wrote the ISO, cloned a drive, or used tools that changed the MBR without updating the associated GRUB configuration. Luckily, this problem is easy to fix. Below, I’ll show you two methods—one for Linux users and one for Windows users.

Fixing the "No Devices Match MBR Identifier" Error

Option 1: Get the MBRID (Disk Identifier) from Linux

Open a terminal and gain root privileges by typing:
sudo su
List all disks with:
fdisk -l
Locate your USB flash drive in the output. You’ll find a line like:
Disk identifier: 0x1234abcd
Copy this hexadecimal Disk ID.
Navigate to the GRUB directory and update the mbrid file:
```
echo -n -e '\x12\x34\xab\xcd' > /boot/grub/mbrid
```
Be sure to reverse the byte order when echoing (i.e., 0x1234abcd becomes \x12\x34\xab\xcd).

Option 2: Get the MBRID from Windows Using Set-MBRID.exe

If you’re working from a Windows machine, you can use a simple tool to extract and write the correct MBR identifier.

Download Set-MBRID.exe
Copy Set-MBRID.exe to the USB flash drive that contains your Linux installation.
Run the tool by double-clicking it. It will:
- Read the Disk Identifier of the USB drive
- Display the ID in a popup message box
- Create or overwrite the file located at:
  /boot/grub/mbrid with the correct MBR ID

Set-MBRID Disclaimer:

Set-MBRID.exe is provided WITHOUT ANY WARRANTY; not even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Use at your own risk. Always back up your data before using disk-level tools.

Final Thoughts

Correcting the MBRID mismatch is often the final step needed to get your custom Linux USB install to boot properly. Whether you prefer using Linux commands or a Windows utility, now you’ve got the tools to fix the "No Devices Match MBR Identifier" error and continue with your boot process.

If you're still having trouble or are unsure about byte order and file paths, feel free to ask in the comments or refer to your Linux distro’s documentation on GRUB and MBR configuration.