Pfsense console OS can't install

[samchen]

Platform: Denverton C3308
SSD 128G
Console OS: pfSense-CE-memstick-serial-2.4.2-RELEASE-amd64.img.gz

Use Transcend USB2.0 16G to install and get a problem

uhub0: 8 ports with 8 removable, self powered
ugen0.2: <jetflash mass="" storage="" device="">at usbus0
umass0 on uhub0
umass0: <jetflash 0="" 1="" mass="" storage="" device,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus0
da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
da0: <jetflash transcend="" 16gb="" 8.01="">Removable Direct Access SCSI-2 device
da0: Serial Number 4FXBZM9J
da0: 40.000MB/s transfers
da0: 15308MB (31352820 512 byte sectors)
da0: quirks=0x12 <no_6_byte,no_rc16>ses0 at ahciem0 bus 0 scbus1 target 0 lun 0
ses0: <ahci sgpio="" enclosure="" 1.00="" 0001="">SEMB S-E-S 2.00 device
ses0: SEMB SES Device
cd0 at umass-sim0 bus 0 scbus2 target 0 lun 1
cd0: <generic autorun="" disk="" 8.00="">Removable CD-ROM SCSI-2 device
cd0: Serial Number 4FXBZM9J
cd0: 40.000MB/s transfers
cd0: 11MB (22540 512 byte sectors)
cd0: quirks=0x10<10_BYTE_ONLY>
Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]…
/etc/rc: WARNINGrandom: unblocking device.

My console screen freezes in the following message:

Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]…
/etc/rc: WARNINGrandom: unblocking device.

But I can install successfully on VGA OS
VGA OS: pfSense-CE-memstick-2.4.2-RELEASE-amd64.img.gz

Refer to the following article:
https://doc.pfsense.org/index.php/Boot_Troubleshooting
https://utech2.wordpress.com/2016/08/24/install-pfsense-get-error/
http://minnowboard.57273.x6.nabble.com/MinnowBoard-Unable-to-Boot-Install-pfSense-td2364.html

Try many times and go to prompt then write set kern.cam.boot_delay="10000"
But there are not help for me. Have any other suggestions?</generic></ahci></no_6_byte,no_rc16></jetflash></jetflash></jetflash>

[jclear]

You really ought to supply some more hardware details, but maybe I can read between the lines.  Seems you have an Atom based box of some sort and apparently have a monitor directly attached (or else you use the term console different ways in the same context).  The simple answer is, don't use the serial image.

If the monitor is a temporary attachment to be replaced by an actual serial connection, then a few things.  It's not usual for boot sequences to start using all available outputs but eventually the serial image is going to switch to just the serial connection.  If your really are using a serial console and it's cutting out, then the most likely thing is the APU2 and pfSense have different serial speeds set and you'd have to reset you serial connection speed after it hits that point in the boot.  You'll need to look up what those are, but my vague recollection from setting up my APU2 a while ago is that they are not the same or I could be thinking of the net5501.  You can then change one or the other setting so they match and avoid that problem in the future.