H81M-ITX not recognizing Linux boot mgr (SOLVED)
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=4511
Printed Date: 23 Jul 2025 at 12:55pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: H81M-ITX not recognizing Linux boot mgr (SOLVED)
Posted By: jsalk
Subject: H81M-ITX not recognizing Linux boot mgr (SOLVED)
Date Posted: 01 Mar 2017 at 1:12am
|
" rel="nofollow - I have a 5TB drive formatted GPT with Arch Linux. It boots just fine on one of these boards. Under boot options, it lists both ACHI and Linux Boot Manager. On a second system with the exact same board, processor and memory, it will not boot. Boot options list only ACHI. All the Bios setting seem the same. Why might it recognize the Linux boot option (UEFI) on one system and not the other which is exactly the same? - Jim
|
Replies:
Posted By: wardog
Date Posted: 01 Mar 2017 at 1:50am
|
" rel="nofollow - Where are you seeing/setting that? In the BIOSes boot order, or during POST using the F11 key? |
Posted By: parsec
Date Posted: 01 Mar 2017 at 2:17am
You're saying moving the same 5TB drive to the other PC is when you don't see the Linux Boot Manager Entry, correct? When you installed Linux, did you only have the 5TB drive connected and powered up, or were other drives connected to the board and operating? The 5TB drive is connected to a SATA port on both PCs? Same UEFI/BIOS version in both boards? You have the same CSM option settings on both boards? ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
jsalk wrote:Posted By: jsalk
Date Posted: 01 Mar 2017 at 3:24am
|
I created a "master" 5TB drive with UEFI Arch Linux. I used dd to clone it. I tried booting both the master and the clone on the original hardware setup with no problems. (When I built the original master drive, I only had one 5TB drive hooked up and booted off a live UEFI Arch Linux DVD.) I then built an exact copy of the hardware system...same motherboard, same memory, same processor and tried booting the master on it. It would not boot. Under the Boot menu in Bios, the original motherboard gave me two options - Linux Boot Manager and ACHI. On the new hardware, it only offers to boot ACHI (which will obviously not work). The drive was connected to the same SATA port on each board. I updated the Bios on both boards to the latest version. It appears I have the same CMS settings as well. After failing to get the drive to boot, I returned it to the original hardware set-up and it booted up just fine. So I am fairly confident there is no problem with the drive. I just don't know how Bios determines the boot options available. - Jim
|
Posted By: parsec
Date Posted: 02 Mar 2017 at 12:08pm
|
I'm not sure what is going on. You did not mention the video source for both PCs, I'm guessing it is the Intel iGPU? If not, are you using different video cards, or a video card in one PC and not the other? The video source, if not GOP compatible, a UEFI protocol, will not let the PC boot, all you'll get is a black screen, or message warning you the video source is not GOP compatible. Normally it should be the GPT formatting that causes the Linux Boot Manager entry to be shown in the boot order. That is how it works with Windows. GPT partitioning can use the EFI boot loader, and the entry in the boot order is Windows Boot Manager. That occurs in a Windows installation when there are two entries for the Windows installation media. One will have the prefix "UEFI:", and the other will be "AHCI:", for the EFI and Legacy boot loaders, respectively. Using the "UEFI:" boot order entry will cause the OS drive to be GPT formatted, and the EFI boot loader to be used. Any idea which entry was used for the Linux installation media when you created the master 5TB drive? You can put that media in both PCs now, and check what you get in the boot order. I can create a Windows installation media from an ISO file on one PC, and when used to install Windows on another, I will have both the "UEFI:" and "AHCI:" or "RAID:" entries, depending upon the SATA mode setting. Do you know if you are using a Linux EFI boot loader, rather than a "Legacy" boot loader in the Linux installation? Windows puts a MBR partition along with the GPT partition, in an installation using the EFI boot loader. That is supposedly not following the UEFI standards, but is done for compatibility with older, non-EFI compatible programs like Memtest. I think Linux also does this for compatibility. One possibility that is causing both disks to fail on the second PC, is an EFI security feature, the matching of GUIDs between systems. One or more of the GUIDs used on the first PC is not matching that of the second PC, so the GPT/EFI booting partition is not allowed to be used. Do you have the Secure Boot option enabled in the UEFI on these boards? One thing you can try on the second PC, is find the CSM option, usually in the Boot screen, or possibly the ACPI screen. CSM is enabled by default. Click on it to open its sub-option. Find the Launch Storage OpROM Policy option, and set it to UEFI Only. You must Save and Exit the UEFI to apply that option. Go directly back into the UEFI and check the boot order for the Linux Boot Manager entry. If setting that option setting fails for whatever reason, you may be automatically put right back into the UEFI again. You might find some information on this page helpful, which discusses UEFI booting and GPT partitioning in Windows and Linux: https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface" rel="nofollow - https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: jsalk
Date Posted: 11 Mar 2017 at 3:26am
|
OK...found the solution. For some reason, when you take a GPT drive with Arch linux that works on one board and drop it in a new set-up with the exact same hardware, the board does not detected a Linux boot partition. The solution was the following: Boot with a live CD. mount /dev/sda2 /mnt (this is the main linux partition) mkdir -p /mnt/boot mount /dev/sda1 /mnt/boot arch-chroot /mnt /bin/bash rm /boot/loader/loader.conf bootctl --path=/boot install This re-installs the linux boot files and the board will now recognize and boot from the Linux Boot Manager Then if I built another unit and installed this same drive, I would have to do the same thing again on the new board. Why the board needs to have the bootloader re-installed on a drive that already has one is beyond me. But hey, it works and that is all I was after. - Jim
|