@PiBa: @theaudioguy: and it now works. Why do people keep replying to something already fixed ?? I'm not sure why hardware offloading would fix it so I replied with the expectation that if it stopped working he would have something to go on.  It could also help if someone came along with the same issue they would have other options to try.  If it's fixed, great.  If not we'll hear back and the conversation can continue.  It's no big deal.

@ricle: There is no abnormaly killed but after reboot it's still the old version! I don't have anything open, only the terminal is used. If you connect to the console and manually tell it to boot from the other slice, does it show the new version? If so, does it keep booting the new version after a reboot? @ricle: There must be a way to make upgrades saver because it becomes unuseable if every upgrade brings new troubles. As u can see in the posts there are many people with different troubles when running upgrades! That is one of the reasons we are removing NanoBSD. It was intended to help with issues such as this but it never quite did. Even back when it was first added there were issues and confusion at times which led to it not being reliable, and it never did quite get to where it promised to be. And because it gets run primarily on CF/SD media, some of the failures are bad disks, but some people have a hard time believing that since when the disk is rewritten it sometimes works (because the disk remapped bad spots when fully rewritten), and so on.

Thanks. You are correct, I was confusing the legend for messages.

Have the same problem. Your solution didn't help to me. Any ideas? UPD: Solved using this post

The "garbage" in your case was SoftRAID metadata from an earlier installation. The default kernel in pfSense probes for that metadata and if it detects a broken RAID array on the disk it's going to cause problems. There's a pfSense wiki article describing a workaround that can be used with the install disk/image as well to prevent the graid driver from trying to use the broken RAID metadata: https://doc.pfsense.org/index.php/Boot_Troubleshooting#.22Fake.22_RAID_cards_with_a_GRAID_error

VirtualBox is saying the VDI is inaccessible?  Maybe someone here can help pitch in but that's a VirtualBox issue, not pfSense.  You could try to regenerate the UUID for the VDI file or create a new VM and attach it if the VM config is messed up but you'll need more than "inaccessible" as an error.  It may say something like "Parent UUID does not match" or a result code of E_FAIL (0x8004005) which will give you something to go on.  Again, though, those are VirtualBox error codes and would need to be brought up in their forums I would think.

From what I understand, those particular files are repository DBs and are rebuilt when the list is fetched.  The problem stems that if there is a problem communicating (like I had) they would be deleted when you tried to re-pull the list.  Once it came back (still don't know why) it rebuilt those 2 files.  I understand some are specific, like local.sqlite, and can't be swapped out but the repo ones shouldn't matter.

OK, well thank you for confirming.

Update: Tried a Microsoft USB to Ethernet adapter, no go (driver from the looks). Then tried connecting the AX88178A via a powered USB hub - and it works! During boot it detects the hub, then the AX88178A connected to it. Not an ideal solution - I'd be interested to hear other people's thoughts on a possible solution without the powered hub. Cheers! -T

Solved it by using a different USB stick. It's unfortunate, but oh well.

Massively late reply…... Still looks like they just don't send you an IP address so it just keeps asking. No clue what that could be be.  :-\ Steve

That type of panic is due to a filesystem issue. You can either boot to single user mode and run "fsck -y /" a few times and then reboot, or you can reinstall from a USB memstick with a pfSense ADI installer image. If you need help with either of those tasks, drop a line to our support team and they can get you more specific instructions.

Hi Guys, I tried to run this command but heres what I got rm: /tmp/radiusd_start.lock: No such file or directory any ideas? Thanks

note that your interface name on that hardware may not be igb0, so make sure it is whatever the correct hardware interface name should be before saving.

Tried with another adapter, this time USB2 (the other was USB3). Now the system survives reboots. I will check and let you know. Best regards Kostas

Not enough information to say why. You'll need to look at the logs and describe in much more detail exactly how the clients are failing. The default configuration has unbound configured to use DNSSEC, crypto operations require an updated and accurate clock, so that could be part of it. I have an ALIX 2D3 here as well running 2.3.4 but it doesn't have any problems even with a default configuration with unbound and DNSSEC. It's possible there is something about your particular environment which is preventing it from working.

Thanks for getting back to me so quickly… The Frontier tech said he could not bridge the modem that I have it being DSL and Arris type...I was finally able to get on the pfS setup access areas to start configuration and checked the loop back and network intrusions but never made it past any other screens to configure anything else, will do today. Their router-modem did let me create rules and port forwarding but it did not help with the normal operation and pass through of signal through my access gateway, still red and yellow lights so I know it is being throttled somewhere..( I will try and reinstall pfS to see if maybe something was missed, although all packages installed correctly and it worked with my Charter cable modem-router I bought at Walmart)... NAT could not be changed on my end EVEN BY THE TECH GUY HERE NOW...they say Geek Squad OR THE HIGH PRICE BUSINESS TECHS would have to go into the hidden pages and reset NAT etc... I was hoping a work around was known I could do in Arris setup access area page(s) I'm allowed in, would another over the counter or brand DSL router-modem allow me to change NAT etc...  Thanks for your time and efforts too!