@johnpoz Thanks. I'll start down that road and see how it goes...

This was very helpful. Thank you.

@stephenw10 Thank you. I see your point regarding the ticket, I reviewed the information requested, it is the way to go, so thank you, if t this file will not work I will follow through.

@stephenw10 , I have removed few more and now have 1.8G available. I think it should be fine now. Thanks again for your guidance.

@stephenw10 i try on Edge/chrome and Firefox (inprivate and normally) nothings happends.

thanks, i send you NDI on chat

I assume if you just install and boot from an SSD it does boot OK?

Does that system claim to support NVMe drives? I don't see it in the specs.

You should, technically, be able to boot a bootloader from SSD and then boot from NVMe if it can see that. That combination is not something I've tried though.

No I didn't. Everything is back to normal (and understood ;) but I will have a look.

Thanks,

Yeah I would open a ticket about that. It should recognise the 7100 and setup the switch and VLANs etc so you can connect out on the default interfaces.

If that's not happening then it isn't recognising the hardware for some reason. That might mean the data passed by the bios is incorrect.

Also important to note is that coming from a pfSense version that old probably means it has an old Coreboot version and that will need to be updated. That must be done in an older pfSense version, 23.05.1 or earlier.

Steve

Not for that hubspot form. I had to add no-script exceptions but it worked fine after that.

Weird. Yeah nothing changed at the server end AFAIK.

@stephenw10 said in upgrade from 2.7.0 to 2.7.2 failed:

Run pkg-static -d update, see what error is shown.

The most common issue coming from 2.7.0 though is a cert issue. If it shows that try running certctl rehash and retesting.

I just had this error on a server that wouldn't update and "certctl rehash" fixed it.

Thank you for taking the time to post fixes, as it helps people years later!

It's because it's IGMP. There is a behaviour change there after a fix in pf:
https://redmine.pfsense.org/issues/15400.

Steve

Nope this is exactly the sort of edge case report that we want to see. You may well have found a bug if it was repeatable.

@fireix I understand when I was still in the field I was one time in a data center for over 18 hours straight working on this huge Cisco equipment that has a special service contact. We had to keep swapping drives and devices back and forth to get configuration and data off for the new drives it was a nightmare call and the parts were no longer made so they sent new stuff that required new cards to work. I felt like a zombie after I left. But it was accessible and running had iOS running and when I started it was completely dead and no parts could be ordered for it in the system, Our team had our hands full with it but we got it going. By the time I left all the needed was an activation code adapted and added to it for all the features it was using again.

Right. The FreeBSD base changed from 12 to 14 between pfSense 2.6 and 2.7. Older versions of both ESXi and the VM version within it do not support FreeBSD 14 so be sure both are new enough.

@stephenw10 thank you, sir.

What does pciconf -lv show?

None of that is especially new. I'd expect all of it to be supported.

Steve

No worries. 👍

@stephenw10 Yes, it's resolved - attributed to Devine Intervention.

@stephenw10 no more random drops. Thanks!