6100 Bricked again…..???
-
@stephenw10 need to attach console…..will let you know. Was doing management remotely via GUI
-
@stephenw10 last 1 just failed to boot entirely. It started and ran for a few minutes and then just failed. Sent in to Netgate for their analysis and the answer I received was “it failed” a hardware issue???
-
Yes, if there were no LEDs or the circle LED stays orange that's a lower level issue.
-
@stephenw10 so to be clear last night all was working fine. In the AM my internet switches had all defaulted to 192.168.XX and 6100 had stopped any functioning. I did a factory reset and only got the blue circle after attaching to a console basic errors appears to be boot error (see below):
SO what needs to be done??? Ticket in and is 2901643950Shell> 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:
Fv(1643501D-ABD6-4ECC-85DE-3D95D23423FE)
FS1: Alias(s):F0:
Fv(50E81C5A-EAB2-495C-871E-EF46044C8959)
Shell> bcfg boot dump
Option: 00. Variable: Boot0003
Desc - pfSense+ (mmcsd0p1)
DevPath - HD(1,GPT,5BF4CD1A-A988-11ED-8CEC-897F5BF3F01D,0x3,0x82000)/\EFI\free bsd\loader.efi
Optional- N
Option: 01. Variable: Boot0002
Desc - bootx64.efi
DevPath - PciRoot(0x0)/Pci(0x1C,0x0)/Msg(29,00)/Ctrl(0x0)/HD(1,GPT,5BF4CD1A-A9 88-11ED-8CEC-897F5BF3F01D,0x3,0x82000)/\EFI\BOOT\BOOTx64.efi
Optional- N
Option: 02. Variable: Boot0001
Desc - bootx64.efi
DevPath - PciRoot(0x0)/Pci(0x1C,0x0)/Msg(29,00)/Ctrl(0x0)/HD(1,GPT,5BF4CD1A-A9 88-11ED-8CEC-897F5BF3F01D,0x3,0x82000)/\EFI\BOOT\bootx64.efi
Optional- N
Option: 03. Variable: Boot0000
Desc - PXE-0
DevPath - Fv(E35C4A77-3D00-4337-A625-B980A9E00F6C)/\pxe_0.nsh
Optional- N
BootOrder0003:FS2:\pxe_0.nsh
Shell> echo %BootOrder0001%
%BootOrder0001%
Shell> %BootOrder0001%
'%BootOrder0001%' is not recognized as an internal or external command, operable program, or script file. -
Hmm, OK that's the output from Blinkboot trying to EFI boot.
The fact it's trying to PXE boot implies it can't find another bootable device. If you hit F2 when I asks to reach the boot menu do you see entries for emmc or ssd (if it has that).
It sounds like you lost power or had a power surge and it may have damaged the filesystem. It's unlikely it would have caused hardware damage. You may need to reinstall though.
Edit: It's actually trying to boot efi variable 0001 and failing. So I would try selecting 0003 from the boot menu if you can.
-
@stephenw10 so there were no outages, nor power surge as I do have a large UPS holding Unifi switches and numerous servers.......and nothing was logged either. That said, I have tried unsuccessfully to get the 6100 to accept the F2 boot. It just keeps cycling through the reboot/boot process any idea how to interrupt that process and/or reset?
-
You see the option menu though?:
Key Options: 'r' -- Clear boot order list. 'p' -- PXE boot. 'F2' -- Boot Manager Menu. Any key to continueIt should wait there for a few seconds after power cycling and you can hit F2.
Do you know why the switches defaulted if there wasn't a power issue?
-
@stephenw10 so it doesnt actually seems to stop. I tried to issue f2 or r and it doesnt accept it the boot menu just appears to accept something and keeps running....cant seem to interrupt it. I have set and reset the Putty settings with no help.
-
Ah so you see that option but are unable to actually select anything from it?
Are you using the USB console? You might try the RJ-45 console if you have an adapter. Otherwise I would try a different client if you can.
We have seen similar behaviour in macOS but putty is usually pretty reliable.
Have you used the console successfully before on that unit?
-
@stephenw10 yes I see it and no I have not used the console on this unit
-
One other thing you should try is a different USB cable. Surprisingly we have seen bad cables present like that. Though it's hard to imagine how that could be possible.....
