Pfsense 2.3-RELEASE hangs when installing
-
Several months ago after running pfSense on a custom built box for about three months it suddenly stopped with a fatal trap
https://forum.pfsense.org/index.php?topic=108717.msg608089#msg608089
In an effort to try and diagnose what the problem was with the box, I tried testing the memory, but couldn't achieve any satisfactory results…
Eventually I tried installing FreeBSD 10.3-RELEASE amd64 and that came up without a problem, so I thought I'd try pfSense 2.3-RELEASE amd64 which is base on FreeBSD 10.3. Unfortunatly pfSense hung when booting up from the installation media. That was the same media which was used for installing FreeBSD.
Can I conclude that I have hit a bug in pfSense?
The system in question has 8GB of RAM and uses a Supermicro X10SBA motherboard with twin NICs
It halts after displaying
UART3
on bootup.
-
It would be helpful if you post a screenshot/log when booting with verbose mode enabled.
To obtain that info, press ESC while on "Welcome to pfSense" boot screen. Type boot -v and hit ENTER.Also, I'd recommend trying 2.3.1-RELEASE and 2.3.2-DEVELOPMENT snapshots, the issue might be fixed in any of those.
-
No OS-level changes of any significance for that type of thing between 2.3 and 2.3.2.
Yeah need to know where it stops. Verbose boot might be helpful.
-
It would be helpful if you post a screenshot/log when booting with verbose mode enabled.
To obtain that info, press ESC while on "Welcome to pfSense" boot screen. Type boot -v and hit ENTER.Also, I'd recommend trying 2.3.1-RELEASE and 2.3.2-DEVELOPMENT snapshots, the issue might be fixed in any of those.
Funnily enough in verbose mode it does not hang!
However when installing it stops at 5% when copying files to the target - I have a USB stick as target for my testing.
I will try a DEVELOPMENT snapshot and see how it goes.
-
The 20160621-0520 amd64 img stops at exactly the same point in the installation, ie after 5% when executing
/usr/bin/tar -C /mnt/ -xzpf /install/pfSense.txz
-
That is normal. I've tested on multiple virtual installations on different hardware and it takes from 1 to 5 minutes depending on the CPU. May take even longer on lower grade CPUs.
-
That is normal. I've tested on multiple virtual installations on different hardware and it takes from 1 to 5 minutes depending on the CPU. May take even longer on lower grade CPUs.
Actually, it did work eventually - took over half an hour, so it looked like a hang to me.
Sorry for any confusion.
-
It copies the bulk of the data at that point without moving the progress bar much. With a slow disk, and/or slow source medium, it'll take some time.