How to boot SG4860 into USB installer?
-
OK - was able to deal with F12 issue by using a third party terminal app.
So it turns out that the SG-4860 is not "seeing" the USB drives (tried all 3, after reimaging using etcher)
The default order of booting is exactly as you have indicated.
However, when I hit F12, choice #1 does not show up at all - i.e. there is no listing for USB MSC Drive Generic Flash Disk 8.07. The first choice is AHCISo that explains why the installer is not booting
Now how can I fix it? -
Not sure. Did you try both USB ports?
Does the unit boot at all? When booted and you insert one do you get console messages about da0 or da1 being inserted?
- Halt system 15) Restore recent configuration
- Ping host 16) Restart PHP-FPM
- Shell
Enter an option: ugen0.4: <generic mass="" storage="">at usbus0
umass1 on uhub1
umass1: <generic 0="" 4="" mass="" storage,="" class="" 0,="" rev="" 2.00="" 1.06,="" addr="">on usbus0
da1 at umass-sim1 bus 1 scbus7 target 0 lun 0
da1: <generic flash="" disk="" 8.07="">Removable Direct Access SPC-2 SCSI device
da1: Serial Number 8291C764
da1: 40.000MB/s transfers
da1: 7681MB (15730688 512 byte sectors)
da1: quirks=0x2 <no_6_byte>GEOM: da1: the secondary GPT header is not in the last LBA.
GEOM: diskid/DISK-8291C764: the secondary GPT header is not in the last LBA.What about a mouse or something?
- Halt system 15) Restore recent configuration
- Ping host 16) Restart PHP-FPM
- Shell
Enter an option: ugen0.4: <logitech optical="" usb="" mouse="">at usbus0
ugen0.4: <logitech optical="" usb="" mouse="">at usbus0 (disconnected)Sounds like you might have broken USB ports.</logitech></logitech></no_6_byte></generic></generic></generic>
-
You led me to the answer. I had followed the online instructions, which indicated that the topmost USB port should be used. When I switched the USB stick to the bottom port, it worked, and I was able to boot into the installer. I proceeded with the install and it seems to have been successful. However, the console output became completely garbled after the reboot, and I am not sure how to fix that. Was able to log into the default user name/password at 192.168.1.1, and then recover a configuration from backup. Now up and running!
Thanks for your help. If you have any pointers about the garbled console output, it would probably be a good thing for me to know, fo the next time I have to rely on the console.
-
Sounds like your config might have the wrong console baud rate or something. Everything on the SG-4860 should always be 115200.
It's at the bottom of System > Advanced.
-
Thanks. It was set correctly there, but I suspect it might not have been set correctly in the terminal app. Have disconnected, so will try that again next time
One more wrinkle I can't figure out: when the system rebooted, I was not longer to access it by its internal name on the domain (pfsense.lan). Everything else .lan is working (e.g. NAS.lan, etc), but not the pfsense device itself. Can still access it no problem via its IP address. This has persisted despite rebooting the device and all network hardware. Any suggestions?
-
Does it not resolve or not connect? Is there a host name override for it?
-
Does it not resolve or not connect? Is there a host name override for it?
It does not resolve at all. There is a host name override for it in DNS resolver, and it is also set under system – general setup. It had always worked prior to reinstalling 2.4.0 on ZFS (it worked on 2.4.0 on UFS - I can't imagine why that would be the issue). I even tried generating a new cert, but no success. It is not a showstopper, as I can access directly via the IP address, but it is curious.
-
Actually, now I can't access anything .lan.
Not sure what is going on here. -
Seems to be only my main computer that can't access the .lan addresses. Other devices on the network can.
-
-
Glad it's all working.
