Unsolved
This post is more than 5 years old
2 Posts
0
1882
October 18th, 2019 06:00
PowerEdge 2900 BIOS Upgrade
Im working on an PE2900 with a BIOS v 2.6.1. I've been running Debian Linux 7.2 Wheezy to run a printer RIP server software. We are in the process of upgrading the RIP software and require Debian Linux 9.6 Stretch. The problem I have is that the Debian 9.6 version doesn't seem to want to install and I was told that the BIOS may not allow it.
I checked the Service Tag, it list all the past updates for the computer. With the BIOS, last update date of 17 Dec. 2013 v2.6.1 is the latest in the list.
I found this https://www.dell.com/community/PowerEdge-Hardware-General/How-to-Update-the-BIOS-in-a-PowerEdge-2900/td-p/4270325 and provided this link to version 2.7.0, https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=5vwcm but the last update date on it is 11 Dec. 2013 and the version is 2.7.0; older date than the BIOS v2.6.1.
Anyone think that 2.7.0 is the solution for my install problem? The exact message during the Linux OS install is that it the isolinux.bin is missing or corrupted. But we have used this same installation media on a Dell PowerEdge T440 without any problem.
I know it's an older computer but it still runs well for our use.
TIA, Deo
0 events found
Daniel My
10 Elder
•
6.2K Posts
0
October 18th, 2019 09:00
Hello
2.7 should be the newer of the two. Release dates on download pages used to update any time a change was made to the software bundle in our change management system. We have added methods to make changes without changing the release date, so this isn't much of a problem with changes made recently. You should check the release notes to get the correct release date.
I don't know if updating the BIOS will fix the problem, I doubt it will. I suggest checking to make sure the version you are installing is compatible with BIOS and does not require UEFI. The 2900 does not have UEFI boot support. If you need to run an unsupported operating system then it is recommended to use a supported hypervisor and run the unsupported OS in a virtual machine.
Thanks
squigley
16 Posts
0
October 24th, 2019 06:00
Hi Deo,
I think you are on the right track trying to update the BIOS. isolinux.bin uses a "hybrid" format these days, so that the same boot files can be used on both CDRs and USB keys.
The issue seems to be that the BIOS is confused by this, as there's an issue with C/H/S addressing, causing the MBR to read the wrong blocks because it confuses heads-per-cylinder and sectors-per-head. On top of this there is UEFI code in there, which the older BIOS' will have no idea what it is.
There's more details here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857597 and here: https://lists.debian.org/debian-cd/2017/06/msg00012.html
I presume you are trying to boot the install off a USB key?
You have a couple of options; the first would be to update the BIOS to 2.7 (or whatever the latest/last released version is), which may fix the issue, but I don't have a lot of hope of it doing so.
An alternate option is to replace the isolinux.bin file on the USB key with an older one, or one specifically designed for USB booting, vs being a hybrid CD/USB format.
Or the option I recommend and would use however, is to PXE boot the installer, bypassing the need for the BIOS to understand a file on a CD or USB. There are instructions for setting up PXE booting of the Debian net installer here: https://wiki.debian.org/PXEBootInstall