I have no idea how to get into the shell…there’s an option under Exit in the BIOS to boot into an EFI shell via USB, but I don’t think that’s the right thing because there’s no shell on the USB, just the firmware and sas2flash. Do I need to download the thing from here and put that on the drive as well?
Either way, when I select the EFI option it tells me to turn Secure Boot off, but I don’t see an “off” option in the Secure Boot settings, just “Custom,” which as far as I can tell only allows me to delete keys, which seems like the opposite of what I want, and the default option. According to this, setting it to “Other OS” disables Secure Boot, but it’s already set to that and it’s giving me the error message that Secure Boot is turned on.
So I don’t need the Shell_Full.efi file that’s linked to in that Super User answer?
Okay, but…how? The option to launch EFI from USB sounds like it expects the shell file to be on the USB and won’t launch because Secure Boot is on, even though according to that Asus page it shouldn’t be, and I’m not sure how else to begin the process?
Correct, device names like /dev/sda can and do change every time the system starts. You cannot rely on those between boots, instead, always cross-check with the serial numbers or UUID’s.
If a drive reported 8 smart errors they won’t magically go away. Go through every drive with smartctl -a /dev/sdX replacing X for the device names in use during that current boot. You will eventually find it, when you do, note down the serial.
Regarding SMART tests; they run in the background and as previously mentioned take many hours to complete (typically 12 to 24). If you reboot the system while one is running the test will fail.
I know the serial of the drive that initially reported errors, that’s how I know it’s the same drive that’s throwing errors now. But it was listed as FAULTED, with 18 read errors, and the VDEV was listed as DEGRADED. But now it’s showing that it’s completely fine, and none of the drives have any errors, even as I continue to get emails about the ATA error count increasing.
Try it…
Boot to UEFI Shell from the boot menu. map to list file systems. Hopefully your USB with sas2flash.efi and the firmware is fs0. fs0: to go there and dir to list files and confirm.
If it’s not the USB drive, try fs1:.
Then follow the instructions to flash.
Should SecureBoot get in the way, disable it. It is useless for TrueNAS anyway.
Secure boot should not prohibit invoking the shell from the boot menu. You are not booting from a medium. You are invoking the builtin UEFI shell. Try it.
Theoretically yes, seeing your screen shot that looks like a seriously locked down system not supporting the most fundamental functions of any modern UEFI based platform.
So we at least know the reason for all the confusion and frustration.
See my previous post and the linked one by @PK1048 for yet another way to go about flashing your HBA.
Can anyone think of any reason why @koberulz shouldn’t use remove the keys (by changing Secure Boot Mode from Standard to Custom? Secure Boot State should say Setup in that case.
Unless you’re dual booting Windows and have a Bitlocker encrypted volume I don’t see why the current keys are important. If the needs change and Windows is required, just create new keys and reenable Secure Boot.
Just make sure you have an up-to-date configuration file from your TrueNAS install if you don’t already have that, just in case.
