You should see some output from Coreboot when you first power it up on the serial console even if you have no OS installed.
Open a ticket with us if you are unable to connect to it: https://go.netgate.com

Steve

Did you get this working?

You should configure the switch to pass those VLANs if you need to use one of the LAN ports. Or you could use the OPT port to link to your switch.
By default the internal switch is in port based vlan mode which will pass the tagged traffic to the internal port but it's better to set it to 802.1q mode and specify which LAN port to use.

Steve

I think this was an SG-1100.
The SG-1100 does not support AES-NI directly because they are x86 instructions and the SG-1100 is ARM based. It does have equivalent hardware instructions though. We are currently working to enable that.

Steve

Theoretically that might be possible. However no-one has tested that card in a 7100, and certainly not one with modified firmware. It's impossible to say if it would work there.

Steve

Thank you very much for the help, Gertjan. That worked. Now, I can get into the pfSense web interface and I also learned something.

Thanks again.

I contacted support and re-imaged the device. That fixed the issue.

@jimp Thank you!

@lavila said in XG-1541 - SSD Boot Errors:

What would be the best way to test if this is an issue with the drive? (All the SMART tests show as passed or no SMART errors detected)

SMART is a decent indicator, especially if you've manually run a long test and checked the results and logs after. It's not perfect, but if it does find a problem then it's almost certainly a legitimate problem. You could boot from a drive diagnostic test disk and run it, but it may not be any more accurate. Not sure which disks you have in there, but disk manufacturers used to all have their own tests you could get from them.

Any commands to determine if this is a filesystem issue vs a hardware issue?

You could run a filesystem check on the disk, though if it failed to find the loader that's a bit more extreme and outside the scope of the filesystem itself. If the disk is not currently a part of the mirror, you may have to run fsck manually on the disk slice(s) (e.g. fsck -y -t ufs /dev/ada0p2)

If it is an issue with the SSD and we just need to replaced. Will the mirror will be automatically started from drive2 back to drive1? Or will I need to re-install pfSense and restore configs

The mirror wouldn't automatically be added to a fresh disk, you'd have to add the disk in using the controls on Diag > GEOM Mirrors.

You should send a message in to support. Since this is potentially a hardware problem on a Netgate device, it wouldn't be an issue that requires a subscription for assistance. https://go.netgate.com

Hmm, interesting. I would not have expected that either. That was a very old version though.
I don't recall there ever being an issue that presented like that but maybe with the newer pfSense/FreeBSD version it was tickling something. Nothing in the release notes between those versions that looks significant.

Anyway glad you are seeing expected speeds. 😀

Steve

@Gertjan i restored from usb and rebuilt the entire network again,

Even with Squid and Snort/Suricata you don't require huge space. The 256GB drive we fit is more than adequate.

Steve

When I had this problem, I found out Windows 7 was configured to not look for a driver on Windows Update. It led me to the option to enable that and then it worked and found COM3

Yeah I'm not aware of any compatibility issues with m.2 cards in the SG-5100 as long as you realise that NVMe is not SATA.

Steve

What is your available WAN bandwidth? Do you have a lot of traffic between internal interfaces?

Steve

@Amorris or (any one here) could you please give a link to 1Gbps SPF modules that you are using? I have no success to find this.

yes

SOLVED - Port Negotiation on ISP Equipment

The cause of the problem was a port negotiation issue between the SG-1100 and the ISP Proxim Radio. When the Proxim radio was set to either auto or 1000 baseT the speed issue would appear, however when the ISP set the radio to only run at 100 baseT the problem went away.

This was a very odd problem, the issue could be consistently triggered by setting the radio to gigabit.

I feel like there is either a underlying problem with the ISP equipment or wiring to the radio.

Has anyone seen anything like this before?

Thank you @stephenw10 for your help.