Do you have an expansion card in the 1541? Which one? If you have the 4x1G card then you will have 6 igb interfaces in the 1541 and the config will just import without having to reassign anything. You'll simple have to move the cables across in the correct locations: https://docs.netgate.com/pfsense/en/latest/solutions/xg-1541/io-ports.html#optional-quad-port-expansion-cards Steve

@lonewolf007 said in Netgate Appliance - Intel: install pfsense+ (think it only works on Netgate's only appliance? See here : Migrate from pfSense CE software to Netgate pfSense Plus software! IMHO : get an TAC for a device and install + on it.

@rcoleman-netgate Running the force-update has done the trick. The SG-1100 is now running 22.01 using ZFS. Thankyou.

Thank you. Seems to be losing 1-2 sec per hour.

You got 2 Cores and 4GB Ram to...

@mkeenan I had a similar OS message recently. The shortest/safest path may well be to open a free ticket at go.netgate.com and have them send you the firmware, and install it via USB stick. I have gotten past odd warnings before but this time it borked and I had to recover manually. If you've installed a package from the current repo onto an old version that may try to install dependencies from the later version. Otherwise see https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html, maybe set to "previous version" and install that first, and work your way up. 2.4.4 is pretty old. I think I started with 2.4.2 on the one that had to be reinstalled. IIRC it worked to get to 21.02 but then even though it offered 21.05 it "installed" 22.01 and was left half upgraded with the wrong OS. HTH,

Hi folks, The problem was indeed a cable plugged into wrong switch port. The funny fact is that that mistake was actually done in January, but only now things started to break. Anyways... thanks everyone for assisting me. Best regards,

@jlpoole At least it's not VLAN0 tagged like it is on that AT&T connections (IIRC). Glad you were able to get your connection up!

Thanks for the suggestions everyone. I reached out to support and they helped me convert my old config. I think I'd be able to do it myself with this xml as a guide going forward.

Yeah, it certainly can be updated. Try running at the command line: pkg-static -d update That should show you errors indicating why it can't check for upgrades. Steve

Yeah, loader.conf.local is only added at install by the installer. So if you never had it in the first place it would never have been added. When you install 2.6 clean does it install and boot as expected? I assume it does as UFS? Does it as ZFS if you comment out the i915 lines before rebooting after the install? What you're hitting appears to be something unrelated to that issue. Steve

@stephenw10 i will take the m.2 to work and see if i can get the screw lose. the hight of the m.2 standoff seems not standard do you think you can find one that might fit? and i have only seen m.2 standoffs with a built in screw and not one that can get screwed into. @rcoleman-netgate i will try and get it loose tomorrow at work i have taken out the m.2 standoff as i stated to Steptemw10 above. will post again tomorrow if it is sucessful. but it would be good to know what kind of standoffs you guys use so we can get the same or close to same :)

@johnpoz Thanks, after doing a full power cycle as suggested in that thread, the upgrade worked.

Just for the record; The Netgate support team had replied to my message before I had even managed to log on to see the ticket, super super fast response. Downloaded the image, wrote to USB, re-installed and all seems to be good with the world. Thanks guys and girls.

@stephenw10 I think I'm affected by this bug, at least I can't get my MBT-4220 to boot anymore since attempting to upgrade to pfSense 2.6.0 The issue is, booting from a USB stick, and mounting the zfs partition on the regular boot drive, I can't find a /boot/loader.conf.local file, just a /boot/loader.conf So how do I disable the console driver from getting loaded? By removing/renaming the /boot/kernel/i915kms.ko file?

Nice catch!

@steveits said in firmware for 3100: https://www.netgate.com/tac-support-request already submitted a ticked and then it said to make an account. i redid the support ticket creation becouse i think i did not select the firmware access :) hope they get back to me soon

Thank you for the quick reply Steve, the upgrade to 22.01 went smooth. -Rico

@valien @valien If your setup is different from other´s testing environment you may get out also often other number. LAN: iperf server on linux server iperf sender on linux server dump GB switch pfSense is touring between them = raw routing throughput (LAN) The same set up with two Windows machines and copying many smaller some mid and one great cumulated all number you will be getting out something that is called "IMIX traffic" this is than more near the real world, traffic or situation you hit with your numbers or will be meeting. So if you are not complete clear about have a look on the IMIX traffic in your tech specs and all is fine, I mean you are more close to real world usage specs. IMIX: is maxing out at ~250 MBit/s so if you get 540 MBit/s you have some free space ahead for setting up rules installing packets and more.... WAN: Can be more different in all our (customers) use cases, So if they test to show us up numbers it can be more differeing from our home or worksplace netflow. Being fair Netgate 2100 for something like 100/50, 100/100 or to 200/200 MBit/s internet with low power consuming will be a rocket with some space to install packets.

@pfgateuser said in SG-3100 - Reboot loop - ufs_dirbad - 21.05.2: At what point in the startup process should I have been able to get to single user mode, and how? Here: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01-02861-g15adf50-dirty (Jul 18 2017 - 23:19:03) Marvell version: devel-17.1.1 Board: Rogue-1 SoC: MV88F6828 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU @ 1600 [MHz] L2 @ 800 [MHz] TClock @ 250 [MHz] DDR4 @ 800 [MHz] DDR4 32 Bit Width,FastPath Memory Access, DLB Enabled, ECC Disabled DRAM: 2 GiB MMC: mv_sdh: 0 DBG: Calling spi_flash_probe from env_relocate_spec() SF: Probing bus 0 cs 0 @ 20000000Hz mode 3 SF: Detected N25Q128 with page size 64 KiB, total 16 MiB PCI-e 0 (IF 0 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1 PCI-e 1 (IF 1 - bus 2) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 1: Host Mode Map: Code: 0x7fedc000:0x7ff97568 BSS: 0x7ffef600 Stack: 0x7f4cbf20 Heap: 0x7f4cc000:0x7fedc000 U-Boot Environment: 0x00100000:0x00110000 (SPI) Board configuration detected: Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x00 | | egiga1 | RGMII | 0x01 | | egiga2 | SGMII | In-Band | egiga0 [PRIME], egiga1, egiga2 Hit any key to stop autoboot: 0 Reset SCSI AHCI init for unit0 Target spinup took 0 ms. SATA link 1 timeout. Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: NT-32 Rev: 1.09 Type: Hard Disk Capacity: 30533.8 MB = 29.8 GB (62533296 x 512) Found 1 device(s). reading ubldr.bin 228648 bytes read in 10 ms (21.8 MiB/s) ## Starting application at 0x00200000 ... Consoles: U-Boot console Compatible U-Boot API signature found @0x7f4dc280 FreeBSD/armv6 U-Boot loader, Revision 1.2 (Tue Jul 10 10:26:23 EDT 2018 root@buildbot3) DRAM: 2048MB Number of U-Boot devices: 4 U-Boot env: loaderdev not set, will probe all devices. Found U-Boot device: disk Probing all disk devices... Checking unit=0 slice=<auto> partition=<auto>...disk0: read failed, error=1 Checking unit=1 slice=<auto> partition=<auto>... good. Booting from disk1s2a: Loading /boot/defaults/loader.conf console comconsole is invalid! no valid consoles! Available consoles: uboot /boot/kernel/kernel text=0xa9a600 data=0x11d4be8 data=0x0+0x54000 syms=[0x4+0xa9240+0x4+0xf4222] \ Hit [Enter] to boot immediately, or any other key for command prompt. Type '?' for a list of commands, 'help' for more detailed help. loader> boot -s