I am currently on BIOS 02.06.E006. Thanks to @Fleshmauler I was able to find the BIOS system files but the only version of the bios that has a recovery file is 02.06.E007. The older versions do not contain a bios recovery image.
I’ve tried to set the jumper to BIOS recovery and recover it with the 02.06.E007 Recovery image on the USB stick but the system beeps 2 times then 2 times again and says “no recovery image found” right under the Platform ID in the picture above. I don’t know if that is because the BIOS I have is 006 and not 007 or what. I’ve tried to search for an 006 recovery image for my motherboard but could not find one.
I cannot access the Bios set up utility or access the EFI shell so I am unable to update the bios. It is very frustrating.
I’m lost as to what to try next besides take my motherboard out of the case and try to turn it on with the bare minimum as suggested earlier by @oxyde and @joeschmuck. I will do this in the coming days and see if I have better luck.
I really appreciate everyone’s help. If anything comes to mind, feel free to chime in or add it. I’m open to suggestions.
Did you verify that the files are showing on the USB stick, all in the root directory? I looked at the Startup.nsh file in Notepad and I didn’t see any obvious typos, that I noticed. It is a simple script
echo -off
# + ============================================================== +
# Copyright (c) 2018, Intel Corporation.
# This source code and any documentation accompanying it ("Material") is furnished
# under license and may only be used or copied in accordance with the terms of that
# license. No license, express or implied, by estoppel or otherwise, to any
# intellectual property rights is granted to you by disclosure or delivery of these
# Materials. The Materials are subject to change without notice and should not be
# construed as a commitment by Intel Corporation to market, license, sell or support
# any product or technology. Unless otherwise provided for in the license under which
# this Material is provided, the Material is provided AS IS, with no warranties of
# any kind, express or implied, including without limitation the implied warranties
# of fitness, merchantability, or non-infringement. Except as expressly permitted by
# the license for the Material, neither Intel Corporation nor its suppliers assumes
# any responsibility for any errors or inaccuracies that may appear herein. Except
# as expressly permitted by the license for the Material, no part of the Material
# may be reproduced, stored in a retrieval system, transmitted in any form, or
# distributed by any means without the express written consent of Intel Corporation.
# Module Name: startup.nsh
# Abstract: Script file for invoking iflash.
# + ============================================================== +
# Program all blocks of BIOS from capsule file
# + ============================================================== +
echo Flashing Romley Platform BIOS...
iflash32 /u /ni R02.06.0007Rec.cap
echo -on
I verified them showing on the stick on my windows computer. I copied and pasted them myself, unplugged, replugged, everything was there and then I plugged it directly to the mobo giving me trouble.
I would use notepad to open the Startup.nsh file on the USB and verify the contents match to the recovery image.
I am wondering if you got the NSH from outside BIOS recovery files directory somehow. The only difference is the file it calls. Recovery vs standard bios
Are you seeing
Flashing Romley Platform BIOS…
and then the missing file error?
I downloaded this one, directly from the intel site. I found an older recovery file from softpedia. I may try it but right now I’m no longer getting video for some reason. I don’t know why this happens.
I edited my post. It was my mistake posting the incorrect screenshot jumped the gun to show you. Ive been using the files from the recov folder the whole time for the usb.
Thank you for responding and for your time. My apologies about the delayed response, I had a trip and went out of town.
What do you mean I “just had the files on the USB.”?
The screenshot you shared, is exactly what I have at the root level of my USB.
I have found version R02.06.0002Rec.cap and the script matches the file size, still told me there was no recovery image.
I have tried with version R02.06.0007Rec.cap. I double checked the script to make sure it matched and it did. Also told me there was no recovery image. I have not tried to rename it, but I will try, though I am skeptical it will yield a different result.
@SmallBarky If you would be generous enough to spare some of your time I would be more than happy to instant message and video chat. The board and the booting is not consistent, and I would be really surprised if it was toast, but I’m not sure what else I could do at this point. Maybe it is.
I meant you had only those files on your USB and no folders.
Are you getting “Flashing Romley Platform BIOS…” on the screen and then it claims it can find the file? I think the script is supposed to display that on the screen. I am wondering if the script is even running or your motherboard is looking for the plain script and CAP file instead of the Recovery versions.
Otherwise. I think you have exhausted everything and it is dead. Time for new equipment.
What should my root folder on the USB look like then? I am not getting anything regarding “Flashing Romley Platform BIOS”
All it shows is this (see picture below. But underneath “Platform ID: 2600CP” It says “Recovery Image not found”. So it knows I’m trying to recover it, but it doesn’t recognize the recovery image:
Again, I am really grateful for everyone chiming in on this. If you would be so generous as to set up a video call or something I’d be happy to show you, but I do not expect that at all. The time and consideration given to me has been above and beyond already.
Naw you did everything right & copied the files over directly onto the USB with no additional folders or crap.
Only last thing I can possibly think of would be specific formatting of the USB itself, not just as fat32 but in terms of partion type (MBR vs GPT). Lotta older stuff wants MBR.
I’ve also had stupid situations in the past where fat32 partitions had to manually made to be 4GB or less to be detected by rando devices & have had to manually set that size thanks to modern day USBs not being crap. This was also likely related to devices expecting MBR honestly.
Outside of that? Can’t think of anything that’d help your motherboard detect the files if you’ve tried every USB slot.
The recovery script isn’t running off the USB. I think it is time to look for a replacement motherboard or a new system.
If you have the backed up TrueNAS configuration file, you should be able to do a new install and apply the configuration and have all your data, etc back.
You guys won’t believe it. After being on a trip and not having turned it on for at least 5 or 6 days, I decided to give this one last go per @Fleshmauler recommendation of of changing my usb to MBR. I did it, and I went to turn on my server, it beeped twice. Then it went through POST.
My bios has been cleared multiple times, so it gave me options to go to BIOS (F2) or 2 other options, I was shocked. I didn’t press anything and it booted into the EFI shell. At which point I ran the bios recovery for my BIOS. It was successful, the system rebooted.
