May 13May 13 Hello all, is anyone having a bios issue with the MSI bios not allowing the selected nvme drive as a boot option after running the "Internal boot" wizard and rebooting?I have secure boot disabled and AHCI enabled but I still get select the nvme as a boot option after running the wizard, rebooting and going to bios. Uploading Attachment...
May 13May 13 Author I've runfdisk -l /dev/nvme0n1fdisk -l /dev/nvme1n1and run the internal boot wizard multiple times, but the bios won't detect the (nvme1n1) as a UEFI boot drive no matter what I do. Does anyone have experience with MSI bios that can help? Edited May 13May 13 by Nanuk_
May 13May 13 9 minutes ago, Nanuk_ said:I've runfdisk -l /dev/nvme0n1fdisk -l /dev/nvme1n1and run the internal boot wizard multiple times, but the bios won't detect the (nvme1n1) as a UEFI boot drive no matter what I do.Does anyone have experience with MSI bios that can help?The drives don't have the correct partitions hence why the bios does not allow you to boot from them. What does it say when you run the internal boot wizard. root@R420:~# fdisk -l /dev/sddDisk /dev/sdd: 111.79 GiB, 120034123776 bytes, 234441648 sectorsDisk model: V Series SATA SSUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: gptDisk identifier: 22742608-C068-4121-818F-C1A2624DD3D2Device Start End Sectors Size Type/dev/sdd1 2048 4095 2048 1M BIOS boot/dev/sdd2 4096 1048575 1044480 510M EFI System/dev/sdd3 1048576 33554431 32505856 15.5G Linux filesystem/dev/sdd4 33554432 234441614 200887183 95.8G Linux filesystem
May 13May 13 14 minutes ago, Nanuk_ said:Are you able to open another web connections and check the fdisk -l for the drive as it looks like it has work ok apart from changing the boot order.When you rebooot it will take longer as it copies the files from the flash.
May 14May 14 Author Actually this was the fdisk result for both nvme before the reboot. I SSHd into the server and ran it once the reboot button showed up. Edited May 14May 14 by Nanuk_
May 14May 14 The devices are not being partitioned; please post the diags after trying to create a boot pool but before rebooting.
May 15May 15 Author orion-diagnostics-20260515-1653.zipUploading Attachment...orion-diagnostics-20260515-1658.zip Edited May 15May 15 by Nanuk_
May 15May 15 Partition for one of the devices is invalidMay 15 16:53:07 Orion mkbootable: writing GPT on device (nvme1n1), with boot area size 16384 MiBMay 15 16:53:07 Orion root: #007Caution: invalid backup GPT header, but valid main header; regeneratingMay 15 16:53:07 Orion root: backup header from main header.May 15 16:53:07 Orion root: May 15 16:53:07 Orion root: Caution! After loading partitions, the CRC doesn't check out!May 15 16:53:07 Orion root: #007Warning! Main partition table CRC mismatch! Loaded backup partition tableMay 15 16:53:07 Orion root: instead of main partition table!May 15 16:53:07 Orion root: May 15 16:53:07 Orion root: Warning! One or more CRCs don't match. You should repair the disk!May 15 16:53:07 Orion root: Main header: OKMay 15 16:53:07 Orion root: Backup header: ERRORMay 15 16:53:07 Orion root: Main partition table: ERRORMay 15 16:53:07 Orion root: Backup partition table: OKMay 15 16:53:07 Orion root: May 15 16:53:07 Orion root: Invalid partition data!Try this: wipe both devices first:blkdiscard -f /dev/nvme0n1blkdiscard -f /dev/nvme1n1Reboot and try again, if it still fails, post new diags
May 20May 20 Author Yes, it worked. Looks stable so far except for a few missing docker containers. But that's probably because I moved some stuff around to make room on the nvme before moving them back after converting it to a bootable partition.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.