Thanks, that gave me an excuse to move to the 64 bit install. Everything went smoothly and populated /etc/rc.d appropriately. arri

It work!  :) Thank you!

Am also facing same issue after upgrading to 2.2 from 2.1.5. event_wait interrupted system call (code=4) Please help guys..

What pfSense version is the secondary running? If the versions are sufficiently different the pfsync protocol may not be the same which will prevent syncing. See: https://doc.pfsense.org/index.php/Redundant_Firewalls_Upgrade_Guide I think you're OK between 2.0.X (8.1) and 2.1.X (8.3) though. Steve

I'm also seeing this issue, also running a 'mismatched' architecture since the host is x64 and the VMs are x86. In some cases a clean install is more difficult (since that'd leave the customer without internet access in many cases to perform the reinstall, so it requires being there), so I tried other options that could be done remotelly. I eventually found out that disabling IP compression on the advanced ipsec options seems to have fixed the issue, went from at least a crash/reboot per hour to running more than 24h stable and counting, running both IKE v1 and v2 tunnels (so that's not the source of the issue in theory). Clean reinstall on proper arch is probably the best solution long-term anyway, but if the issue is with IPcomp then disabling it might help others who are now facing issues. Will update if I see any more crashes.

If it's a USB CD-ROM, check the port it's in. If it's a USB 3.0 port, try a USB 2.0 port instead. A USB memstick would be faster/easier than a CD anyhow though

Many thanks Steve, just saw this, no, I hadn't cleared the CHS settings, I'll try again this aft if I get chance. I did set all to Auto for the drive, assuming it would rescan the disk afresh, but if it still holds that config, that would prevent boot. I'll report back with results.

Yep ^ that. You don't need to open the .img file. Once you've removed it from the gzip (.gz) you write the .img file to the USB drive. Steve

Many thanks :)

Do a fresh install, restore config backup.

I should had mention that before but I don't use transparent squid proxy. I do have a transparent setup for Dansguardian, which is on a different subnet. This is the order I did my install a month ago… squid, squidguard... got them running... then added dansguardian into the mix I have squid listening on my lan and loopback...  dansguardian is listening on my lan and upstreams to squid via 127.0.0.1 here is the nat I use for dansguardian KIDSNET TCP * * * 80 (HTTP) 127.0.0.1 8080 Dansguardian Transparent Proxy Re-Direct

Hello, I've reinstalled all over again, but first using my old installation I made two backups, one with and one without packages. I've followed the instructions given here, I've restored only the no packages backup and now I don't have orphan package configurations. But the main problem persists, "Unable to communicate with http://packages.pfsense.org. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity", so I cannot view or install any packages… I have checked it out almost everything, from the console everything seems to work fine, dns resolves OK when pinging even to packages.pfsense.org  (attached img) Thank you in advance for any advice or suggestions you may have...  

Could it be because Im trying to install 1.5 on an SSD drive?