Just updated the BIOS to v1.26. I have 3 MS-01's in a Proxmox HA cluster with Ceph and Thunderbolt networking. Before the upgrade I had 1 MS-01 that would kernel panic and crash randomly (typically once per day). Since the BIOS update, none of the MS-01's have crashed and have been rock solid now. Would recommend updating.
Minisforum MS-01 BIOS
- Thread starter the-last-englishman
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I don't understand why they aren't releasing these bios. Glad it fixed panics that had to be super frustrating.
I will update to the new bios when I get my next MS-01 that will be running Proxmox. I'll keep the one I have at where it is at since AFAIK there have been no issues and its running PFSense as my main firewall/router and I hate to have that break 
Thanks for sharing the update files and the process for this.
Next to-do is finally get the remote management working as well, I looked at these machines as capable server replacements, but I am missing certain things like iDRAC.
So Dell R210ii was replaced by one as a firewall and a Dell R710 will be replaced as a Hypervisor.
The only thing I cant do is mass storage, so I am keeping a Dell R730XD around for that.
Thanks for sharing the update files and the process for this.
Next to-do is finally get the remote management working as well, I looked at these machines as capable server replacements, but I am missing certain things like iDRAC.
So Dell R210ii was replaced by one as a firewall and a Dell R710 will be replaced as a Hypervisor.
The only thing I cant do is mass storage, so I am keeping a Dell R730XD around for that.
1.26 is now listed as an available BIOS download on Minisforum support.
People have mentioned that Alt+F5 will let you into an advanced menu next boot, but it doesn't seem to always work? It also seems to me that I can't access any other "advanced" page besides the first information page? Is there a BIOS mod available to unlock it permanently?
By the way, BIOS can also be updated from the UEFI shell. You have to also provide Shell.efi in addition to the firmware files, you can get it directly from (official) Tianocore EFI II project. Worked well.
By the way, BIOS can also be updated from the UEFI shell. You have to also provide Shell.efi in addition to the firmware files, you can get it directly from (official) Tianocore EFI II project. Worked well.
Last edited:
If anyone is reading this and the previous posts have not fully helped with regards to updating the MS-01 BIOS, here is what did the trick for me:
- Formatted USB Drive as FAT32 (using Rufus on Windows, using MS-DOS bootable option and selecting UEFI - this will land some un-necessary files on your USB drive like autorun, etc. but they won't hurt anything)
- Copied over the 1.26 BIOS files to the root of the USB Drive
- ***Downloaded shell.zip from the bottom of this site, extracted and copied shell.efi to the root of the USB Drive (prior to doing this, I could not boot off of the USB and nothing would happen when I selected the UEFI Shell from the BIOS menu, it would just flash briefly and do nothing. I'm sure you can get shell.efi from elsewhere but this worked for me). 10/26 EDIT: Official/Clean build of shell.efi here (courtesy of @Avamander)
- Either boot using F7 at MS-01 power-on or select the UEFI shell from the BIOS
- Change into your USB directory (you cannot use 'cd', 'dir' or 'ls' commands, simply type the drive letter designation and press enter (for me it was FS0: ) <-that's a zero at the end and not an O as in oscar.
- Type this file name and press enter to start the BIOS update: AfuEfiFlash.nsh
Last edited:
Any idea about x710 nvram / bootrom updates?
Bootutil detects it as 40g adapter and says no updates possible while nvram update tool tries to update, then fails after 30 minutes and nothing happens beside going to recovery mode on reboot 'due to multiple firmware restarts' (adapter still works)
Bootutil detects it as 40g adapter and says no updates possible while nvram update tool tries to update, then fails after 30 minutes and nothing happens beside going to recovery mode on reboot 'due to multiple firmware restarts' (adapter still works)
thank you, nvram update worked (pretty fast!) through efi shell
any idea about bootutil? it detects x710 adapters as 40gbe adapters and i226 adapters as 1gbe
Attachments
Did the same, worked.
Though it still complains about unsupported SFP+ module. Need to search if I can find a fix for that.
I have two MS-01, one is running Windows 11 and the other is running Unraid. I could not get either of the computers to boot the 1.26 Bios update via USB (I had not yet seen the method mentioned by “kenosborn” -- see above). I then tried updating inside windows by running the AfuWinFlash.bat and it worked with no problems. Then back to the MS-01 running Unraid via the bootable USB drive, and as before it would not run, it would only go into the splash screen for the MS-01 UEFI. Setting the UEFI to use the USB did not work even though the USB showed as bootable.
I removed Unraid from that computer, loaded an early version of Windows 11 (2021, less security steps to avoid) and easily updated the MS-01 Bios – cleaned the windows off the computer and reloaded Unraid. I spent less time removing and reinstalling than the time it took trying to use the USB drive. So, if the USB doesn’t work for you the Windows method works great – no other steps than running the .bat file.
I would try the “kenosborn” method first, but if you still have problems...
I removed Unraid from that computer, loaded an early version of Windows 11 (2021, less security steps to avoid) and easily updated the MS-01 Bios – cleaned the windows off the computer and reloaded Unraid. I spent less time removing and reinstalling than the time it took trying to use the USB drive. So, if the USB doesn’t work for you the Windows method works great – no other steps than running the .bat file.
I would try the “kenosborn” method first, but if you still have problems...
You can get an official/clean build of Shell.efi from EDK II repository:
You don't need more than Shell.efi at the root of your USB drive. Then you can execute everything else (be it UEFI or Intel NVM update).
I had a tough time trying to update a Proxmox host. Here's what worked for me. No bootable USB. No Shell.efi. Just format USB as FAT32 and extract the BIOS files to that USB.
- COLD boot the MS-01 (turn on from power off) and when the Minisforum logo appears, hit the DEL key.
- Select the option for UEFI shell from the menu that appears
- Type "FS0:", "FS1:" etc, and at each device, do "ls" so you can see if it's your USB drive
- Run the BIOS update script by typing the name and hitting enter: "AfuEfiFlash.nsh"
Hi all
Is there a Intel Network microcode to update for the MS-01 ?
I have unstable issues on my 2 MS-01 (One Intel i5, other I9) with proxmox when network link is down on the switch.
If I shutdown the port (switch update for example), the 2.5 Gig ethernet goes down. Normal at this stage, but my MS-01 reboot...
I'm using one ethernet port for VPRO/MEBX and one port for the normal proxmox LAN
Is there a Intel Network microcode to update for the MS-01 ?
I have unstable issues on my 2 MS-01 (One Intel i5, other I9) with proxmox when network link is down on the switch.
If I shutdown the port (switch update for example), the 2.5 Gig ethernet goes down. Normal at this stage, but my MS-01 reboot...
I'm using one ethernet port for VPRO/MEBX and one port for the normal proxmox LAN
The 1.26 BIOS includes the Intel microcode, from the release notes:
*****************************************
* BIOS Release Notice *
*****************************************
Release Date:
2024/10/14
BIOS Version:
1.26
BIOS Checksum:
91A0
BIOS Description:
1.Update microcode
2.C-State is supported
I haven't run an MS-01 prior to 1.26 so I have no personal baseline. I could share my idle temps (with no running VM's, etc.) if that is helpful at all to compare, lmk.