Netgate 4100 Faild to boot ( Checking media [Fail]-ABD6-4ECC-85DE-3D95D23423FE )
-
Hope your all having a wonderful day, i have a Netgate 4100 that seems to have a failed boot, i believe its the local onboard storage that's failed but is there any documentation or recommended NVME devices that can be purchased to install the OS onto and just completely ignore the onboard flash ( If that's possible ) this device was not purchased as a MAX
I will paste the output from the serial console below.
Thanks in advance.
Output:
isSecurebootEnabled = 01 secureboot not enabled Loading Usb Lens... Provider: Insyde Software Version: 05.12.02.0040.0009.15 Product: BlinkBoot(R) Harrisonville USB Lens Licensee: Silicom Ltd. Start: 03/20/2018 End: 12/31/2099 Validating Signature... [Pass] Installing Usb Lens... Loading Nvme Lens... Provider: Insyde Software Version: 05.12.02.0040.0009.15 Product: BlinkBoot(R) Harrisonville NVMe Lens Licensee: Silicom Ltd. Start: 11/16/2020 End: 12/31/2099 Validating Signature... [Pass] Installing Nvme Lens... Loading Sata Lens... Provider: Insyde Software Version: 05.12.02.0040.0009.15 Product: BlinkBoot(R) Harrisonville SATA Lens Licensee: Silicom Ltd. Start: 03/20/2018 End: 12/31/2099 Validating Signature... [Pass] Installing Sata Lens... Loading SdMmc Lens... Provider: Insyde Software Version: 05.12.02.0040.0009.15 Product: BlinkBoot(R) Harrisonville SDxx/eMMC Lens Licensee: Silicom Ltd. Start: 03/20/2018 End: 12/31/2099 Validating Signature... [Pass] Installing SdMmc Lens... Mapping table FS2: Alias(s):F0: Fv(E35C4A77-3D00-4337-A625-B980A9E00F6C) FS4: Alias(s):F0: Fv(F9657F27-CAE7-4951-A406-D286157B63EF) FS3: Alias(s):F0: Fv(E7082AE5-3036-407A-8060-FDF027F74632) FS0: Alias(s):F0: Fv(1643501D-ABD6-4ECC-85DE-3D95D23423FE) FS1: Alias(s):F0: Fv(50E81C5A-EAB2-495C-871E-EF46044C8959) Locking SPI ... Launching Lock flash... Already Lock the SPI Error. 8BE4DF61-93CA-11D2-AA0D-00E098032B8C - BootNext - unable to set: Not Found Checking Hotkey... Key Options: 'r' -- Clear boot order list. 'p' -- PXE boot. 'F2' -- Boot Manager Menu. Any key to continue Error. C450ED8E-C3C2-4FE7-AEE6-D1C50ABB78CF - PXEVariable - unable to set: Not Found Error. C450ED8E-C3C2-4FE7-AEE6-D1C50ABB78CF - RestOrderVariable - unable to set: Not Found Shell> map -r Mapping table FS2: Alias(s):F0: Fv(E35C4A77-3D00-4337-A625-B980A9E00F6C) FS4: Alias(s):F0: Fv(F9657F27-CAE7-4951-A406-D286157B63EF) FS3: Alias(s):F0: Fv(E7082AE5-3036-407A-8060-FDF027F74632) FS0: Alias(s):F0: Fv(1643501D-ABD6-4ECC-85DE-3D95D23423FE) FS1: Alias(s):F0: Fv(50E81C5A-EAB2-495C-871E-EF46044C8959) Shell> bcfg boot dump Option: 00. Variable: Boot0001 Desc - bootx64.efi DevPath - PciRoot(0x0)/Pci(0x1C,0x0)/Msg(29,00)/Ctrl(0x0)/HD(1,GPT,53119E25-8838-11EC-8DEF-539C1F4371C1,0x3,0x64000)/\efi\boot\BOOTx64.efi Optional- N Option: 01. Variable: Boot0000 Desc - PXE-0 DevPath - Fv(E35C4A77-3D00-4337-A625-B980A9E00F6C)/\pxe_0.nsh Optional- N BootOrder0001:FS2:\pxe_0.nsh Shell> echo %BootOrder0000% %BootOrder0000% Shell> %BootOrder0000% '%BootOrder0000%' is not recognized as an internal or external command, operable program, or script file. Shell> BootOption1.nsh Shell> map -r Mapping table FS2: Alias(s):F0: Fv(E35C4A77-3D00-4337-A625-B980A9E00F6C) FS4: Alias(s):F0: Fv(F9657F27-CAE7-4951-A406-D286157B63EF) FS3: Alias(s):F0: Fv(E7082AE5-3036-407A-8060-FDF027F74632) FS0: Alias(s):F0: Checking media [Fail]-ABD6-4ECC-85DE-3D95D23423FE) LoadImage: Not FoundF0: Error reported: Not Found2-495C-871E-EF46044C8959) Loading Network Lens... Already startediable: Boot0001 Installing Network Lens... DevPath - PciRoot(0x0)/Pci(0x1C,0x0)/Msg(29,00)/Ctrl(0x0)/HD(1,GPT,53119E25-88EFI Network 1 for IPv4 (90-EC-77-32-8D-DC) \boot\BOOTx64.efi Optional- N Option: 01. Variable: Boot0000 Desc - PXE-0 DevPath - Fv(E35C4A77-3D00-4337-A625-B980A9E00F6C)/\pxe_0.nsh Optional- N BootOrder0001:FS2:\pxe_0.nsh Shell> echo %BootOrder0001% FS2:\pxe_0.nsh Shell> %BootOrder0001% Shell> lens -i network Loading Network Lens... Provider: Insyde Software Version: 05.12.02.0040.0009.15 Product: BlinkBoot(R) Harrisonville Network Lens Licensee: Silicom Ltd. Start: 03/20/2018 End: 12/31/2099 Validating Signature... [Pass] Installing Network Lens... Mapping table FS3: Alias(s):F0: Fv(E35C4A77-3D00-4337-A625-B980A9E00F6C) FS5: Alias(s):F0: Fv(F9657F27-CAE7-4951-A406-D286157B63EF) FS4: Alias(s):F0: Fv(E7082AE5-3036-407A-8060-FDF027F74632) FS0: Alias(s):F0: Fv(1643501D-ABD6-4ECC-85DE-3D95D23423FE) FS1: Alias(s):F0: Fv(50E81C5A-EAB2-495C-871E-EF46044C8959) FS2: Alias(s):F0: Fv(D6549619-FD0F-4464-B889-05D0A5D45666) Loading Network Lens... Already started Installing Network Lens... Loading Network Lens... Already started Installing Network Lens... EFI Network 2 for IPv4 (90-EC-77-32-8D-DB) -
Any NVMe SSD that physically fits should work. That means it must be B+M keyed. Most are only M keyed.
Try resetting the boot order using
rwhen the menu appears. It's not clear what happened there but it's trying to boot from a bad table entry. If the eMMC is still accessible it shouldd find it and create a new entry for it.Steve
-
Thanks, i had a Samsung 850 Evo kicking about
P/N:MZNLN120 Model:MZ-N5E120This does seem to be Msata !
Stuck that in the slot Pressed "r" then it booted into the Netgate installer, Got through that process and after slecting the console version i get a "no valid boot device found".
Is there any Recomended Drives that have worked and could share a link or models, im particularly interested in something that would last more than just over a year that this devices has been in place. if the drive is the issue in this case.
Thanks again
-
It must be an NVMe drive not mSATA. I don't have any specific recommendation. There are some others here on the forum though.
-
I have now received what should be the correct NVME but I’m now no longer getting console.
I’ve raised a ticket with netgate to see if it’s recoverable.
Thanks for your help
