HELP ! Can anyone tell what is my problem?

[leyley]

root mount waiting for :usbus4
uhub4:8 ports with 8 removable, self powered
trying to moutn root from ufs:/dev/ad6s1a
Root mount error
if you have invalid mount option, reboot, and first try the following from the loader prompt:

set vfs.root.mountfrom.options=rw
and then remove invalid mount options from /etc/fstab

Loader variables:
vfs.root.mountfrom= ufs:/dev/ad6s1a
vfs/root.mountfrom.options=rw

Manual root filesystem specification:
<fstype>: <device>Mount <device>using filesystem <fstype>eg ufs:/dev/da0s1a
eg cd9660:/dev/acd0

this is equivalent to :mount -t cd9660 /dev/acd0</fstype></device></device></fstype>

When i boot the pfsense that stuck on above information, anyone can tell me what is the problem. im the beginner.
it is need to reformat or direct run on usb thumbdrive?

[podilarius]

On the menu you need to press 3 to boot off USB. Once you have that up then you need to add the following to /boot/loader.conf.local

kern.cam.boot_delay=10000

[leyley]

after press 3 my problem still occur :(

[wallabybob]

Some possibilities:
1. FreeBSD can't find a disk ad6
2. FreeBSD can't find a UFS formatted disk ad6s1 (slice 1 on ad6)
3. You have hit a bug in the FreeBSD startup code that stops it recognizing a disk with a unit number "too high".

Some actions you could take:
1. At the mountroot> prompt follow the suggestion and type a question mark to see what disks are available. (Perhaps your disk has moved to another device number (e.g. 4) because you changed some BIOS option(s) or moved the connector from motherboard to disk.) If the system reports a disk adxs1a then follow the directions to mount it and then edit /etc/fstab to correct the location of the root file system.
2. Move the hard drive to a connector with a lower unit number, preferably in the range 0 to 3 (inclusive). You will likely still get a mountroot error because /etc/fstab will probably point to the wrong location of the root file system. Correct as described immediately above.

If this is too complicated it would help to provide the output from the ? response to the mountroot> prompt and the startup output so we can what disks are actually detected on startup.