Skip to main content

Force Dell BIOS Upgrade

I just experienced a problem upgrading a Huawei N8300 OceanStor NAS Engine node (OEM'ed Dell PowerEdge R710 server).

Running the linux binary update file looked good and it asked me to reboot. After reboot the same old v2.1.15 BIOS was there, not the latest v6.4.0 (as of writing this small post).

Next up was creating a FreeDOS Bootable ISO with the bios update program included (see this page for how to do that in Windows). Running the BIOS upgrade program from FreeDOS (virtual media and DRAC) I got this error:

Cannot use a "Dell System PowerEdge R710" BIOS in a " -  "
Pres any key to exit.
ROM update not performed.


After some googleing I found the solution on Dell Community Forum - use the /FORCETYPE option.

So to force the update, I just ran the update package with that option (I had renamed the file for 8.3 DOS filename):
R710-640.exe /FORCETYPE

And thats it. v6.4.0 BIOS up and running :)
Labels:

Comments

georgia said…
I've been looking for information on BIOS passwords, and your article was just what I needed. Thanks for sharing your knowledge!

November 6, 2023 at 10:37 AM
Post a Comment

Popular posts from this blog

How to configure multiple VLANs on QNAP TS-869U

It's unbelievable that QNAP still doesn't support multiple VLANs on a single bond0 interface via GUI when they now just released the QTS v4.1.0 NAS Operation System for QNAP. The underlying Linux OS (QTS) does support it, and there should at least not be any problems with Intel chipsets. Some are reporting problems with Marvell.. but I haven't tried. I wanted to use the QNAP as a iSCSI storage for my LAB using a second interface while having full redundancy and get max bandwith (2x1GbE) for my ESXi hosts, and I didn't want that interface routed. At the same time I of course need the possibility to manage the QNAP system via the main interface, which is routed. This CLI "hack" will at configure the QNAP for a second VLAN interface that will be persistent during reboots. It's not been verified that it works after an upgrade of the firmware, but I presumed it will. To get this to work I presume you already have the following working: Network onfigured...
5 comments
Read more

Typing @-character is delayed with Asus GPU TweakII and scandinavian keyboard layout (at least norwegian)

After I reinstalled my computer a while back, I noticed that one characters (the @-sign) had a long delay before showing up after I had hit the key on the keyboard. And I noticed it wasn't every time I had turned on my computer it was "slow". Imagine how frustrating it is to write your email address in a normal pace on the keyboard, just to find it spelled firstname1977gma@il.com instead of firstname1977@gmail.com ? Hitting ' @ 'had 0.5 to 1 second delay before it showed up on my screen, while the characters after displayed instantly. The computer in question runs english Windows 10 x64 with an NVidia GTX1070 card from Asus, and using a norwegian/scandinavian keyboard (Logitech G710+, but model isn't the problem). Throubleshooting led me to narrow the problem down to my ASUS GPU TweakII v1.4.0.8 (older version probably have the same problems). When I started the program, which was set to auto-start, I was suddenly no able to type @ as fast and often as ...
Post a Comment
Read more

Upgrade Brocade VDX from USB

Brocade VDX NOS 2.0.x and NOS 2.1.x admin guide and cli ref says this is the command to update the NOS firmware on VDX: firmware download usb directory firmware/nos2.1.0 It's not. Drop the 'firmware/' in the path. Correct and working (from 2.0.0 to 2.1.0 at least) is: firmware download usb directory nos2.1.0 I believe you need to have a Brocade USB. Perhaps it works with other sticks with the same folder layout, I don't know. And by the way, there are no release.plist file in the root of the nos2.1.0 folder. Brocade USB folder layout - one folder 'brocade' in the root and four subfolders: brocade/ config firmware firmwarekey support Updated 20120809.
4 comments
Read more