• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
The Blog of Jorge de la Cruz

The Blog of Jorge de la Cruz

Everything about VMware, Veeam, InfluxData, Grafana, Zimbra, etc.

  • Home
  • VMWARE
  • VEEAM
    • Veeam Content Recap 2021
    • Veeam v11a
      • Veeam Backup and Replication v11a
    • Veeam Backup for AWS
      • Veeam Backup for AWS v4
    • Veeam Backup for Azure
      • Veeam Backup for Azure v3
    • VeeamON 2021
      • Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM)
      • Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GVP v2
      • VBO v6 – Self-Service Portal and Native Integration with Azure Archive and AWS S3 Glacier
  • Grafana
    • Part I (Installing InfluxDB, Telegraf and Grafana on Ubuntu 20.04 LTS)
    • Part VIII (Monitoring Veeam using Veeam Enterprise Manager)
    • Part XII (Native Telegraf Plugin for vSphere)
    • Part XIII – Veeam Backup for Microsoft Office 365 v4
    • Part XIV – Veeam Availability Console
    • Part XV – IPMI Monitoring of our ESXi Hosts
    • Part XVI – Performance and Advanced Security of Veeam Backup for Microsoft Office 365
    • Part XVII – Showing Dashboards on Two Monitors Using Raspberry Pi 4
    • Part XIX (Monitoring Veeam with Enterprise Manager) Shell Script
    • Part XXII (Monitoring Cloudflare, include beautiful Maps)
    • Part XXIII (Monitoring WordPress with Jetpack RESTful API)
    • Part XXIV (Monitoring Veeam Backup for Microsoft Azure)
    • Part XXV (Monitoring Power Consumption)
    • Part XXVI (Monitoring Veeam Backup for Nutanix)
    • Part XXVII (Monitoring ReFS and XFS (block-cloning and reflink)
    • Part XXVIII (Monitoring HPE StoreOnce)
    • Part XXIX (Monitoring Pi-hole)
    • Part XXXI (Monitoring Unifi Protect)
    • Part XXXII (Monitoring Veeam ONE – experimental)
    • Part XXXIII (Monitoring NetApp ONTAP)
    • Part XXXIV (Monitoring Runecast)
  • Nutanix
  • ZIMBRA
  • PRTG
  • LINUX
  • MICROSOFT

Supermicro: How-to fix unable to mount ISO on IPMI when using SMB

26th August 2025 - Written in: utilities

Greetings friends, these latest days I am upgrading my home lab environment to be ready for the upcoming Veeam Software Appliance. Whilst doing this, of course you would like to attach some .iso to your different Supermicro. But whilst doing it so, I faced a weird problem using the HTML5 iKVM Interface for Supermicro IPMI, I have a valid license for all my hosts and I remember this always worked.

The problem I was facing it was a bit invisible, as I was adding the correct host, path to the ISO, correct user/pass (optional, but in my case required), but nothing was happening, just getting this message over and over without anything happening:

I couldn’t find the reason, as some other Supermicro Hosts do not have this problem. The window remain like this, without the usual message about the ISO being mounted:

Re-Introducing SMB v1.x

This can be the reason why, as I have not upgraded my Supermicro e300-9d-8cn8tp for a while, because it is not common to upgrade BIOS/Firmware of servers that often, so I am currently running the next:

01.31.03
04/15/2020
BIOS Version: 1.4
BIOS Build Time: 01/06/2021
Redfish Version: 1.0.1

So, in this particular BIOS and Firmware, SMB v1 is still required in order to mount an .iso using the HTML5 iKVM IPMI. I have heard that using the Java version of the IPMI, or IPMIview 2.0 from Supermicro can help getting rid of this and other problems, but I do not have either Java, or IPMIview 2.0 installed. So let’s move on the resolution from the unit serving my SMBs.

How-to enable, briefly, SMB v1 on a QNAP

This is of course against all modern recommendations, and it should be followed temporarily and under supervision, so we mount our ISOS, perform the work and return it back to the secure and supported SMB v3 only. On our QNAP, let’s go to Control Panel > Network & File Permissions > Win/Mac/NFS/WebDAV, inside the first tab called Microsoft Networking (SMB), click in Advanced Options, and finally let’s select the lowest version of SMB to v1.

Let’s click apply, and just like that, without even need to reload the Supermicro iKVM HTML5, we can just mount it again and see it is mounted properly:

And from here, we can now boot normally and invoke the Boot Menu so we can select the virtual CD:

And that’s it, problem solved for this particular Supermicro, with what it seems old BIOS/Firmware. I hope this is helpful for you, I would upgrade the BIOS to the latest version to see if the problem is fixed on newest releases.

UPDATE

With the latest release of BIOS and IPMI, you can successfully mount SMB v3 🙂 So I hope it is useful in any case, as not every day one updates servers.

01.74.13
08/02/2023
BIOS Version: 2.2
BIOS Build Time: 09/03/2024
Redfish Version: 1.8.0

Filed Under: utilities Tagged With: sueprmicro SMB 1, supermicro, supermicro ISO, supermicro SMB v1, supermicro virtual cd

Reader Interactions

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

  • E-mail
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • YouTube

Posts Calendar

August 2025
M T W T F S S
 123
45678910
11121314151617
18192021222324
25262728293031
« Jul    

Disclaimer

All opinions expressed on this site are my own and do not represent the opinions of any company I have worked with, am working with, or will be working with.

Copyright © 2025 · The Blog of Jorge de la Cruz