ROOT MOUNT ERROR
-
I'm thinking your sata hardware isn't compatible with the freebsd. Thats why I'm thinking a pci or pcie sata adapter will at least get you booted up. Problem is, after that will your Ethernet ports be compatible? Are they also bleeding edge tech that only NASA has a working driver for?
-
I noted also that pfsense 2.03 is based on Freebsd 8.1
and pfsense 2.1 is based on Freebsd 8.3Perhaps 8.3 has support for your hardware rolled into it better than 8.1?
-
P.S. It sure is acting like it doesn't know what to do with the hardware on your board.
Did they just design this board last week and send it out yesterday?
Crazy idea… Do you have an old PCI or PCIe or USB3 > sata adapter?MOBO has pci and pcie. Am using the two pci for my NIC WAN/LAN interface. I have no problem there though. My real problem is whenever "I" is presented and the system would install pfsense to the HD, I was presented a target disk with USB (the installer) as the only option to install with. The HDD is not there as a selection. Kind of wirdo mobo. But it seems my only problem is what to do in order that the pfsense would recognize the hdd as a target hdd to install.
Is there any unix command to handshake the hdd and the pfsense installer?
-
If pfsense can't see the HD on that SATA port because your chipset isn't supported by BSD 8.1, I imagine it wouldn't present it as a choice after the "I".
-
I don't know if
gpart show -l
will show your big HD or not.
If it does, maybe you can work this out with a not quick and easy install.
-
I too recently ran into this issue setting up my new PFSense box. I could boot up the to main menu screen where I could select option 1-8 and I tried a wide variety of fixes listed in this thread.
The issue finally ended up being that I could not boot past the dreaded "Boot Mount Error" while my external CD/DVD drive was connected to any of the USB 3.0 ports.
As soon as I used a USB 2.0 port and selected option 3 (boot from USB connected device) everything ran fine.
I believe we are seeing a FreeBSD drive issue where the USB 3.0 port is running in USB 2.0 compatibility and the drivers don't know how to manage that.
The solution is to use a USB 2.0 port with your USB 2.0 CD/DVD drive and select option 3 from the boot up menu.
If someone has a USB 3.0 CD/DVD drive it would be good to test it with USB 3.0 and USB 2.0
BTW … My hardware is as follows:
Jetway HBJC200F99-525-B
http://www.newegg.com/Product/Product.aspx?Item=N82E16856107095
General
Brand Jetway
Model HBJC200F99-525-B
Color BlackCPU Supported
CPU Type Intel Atom D525 (1.8GHz, Dual-Core)Chipset
South Bridge ICH9RMemory Supported
Memory Slots 2 x 204Pin DDR3 1066
Max Memory 4GBExpansion Slots
PCI 1
Mini PCI-E x1 1Storage
SATA 6 x SATA 3.0Gb/s
SATA RAID RAID 0, 1, 5, 10Graphics
Onboard Video Intel GMA 3150Audio
Onboard Audio VIA VT1705 (6 Channel)Network
LAN 2 x Intel 82574L (Dual 10/100/1000Mbps)Extension Bays
Slim ODD
1 x Blank Bay
2.5" Internal Bays 1Front Panel Ports
Front USB 2 x USB 2.0 (not exposed)Back Panel Ports
PS/2 1
COM 1
VGA 1 x D-sub
Rear USB
3 x USB 2.0
2 x USB 3.0
RJ45 2
Rear Audio Ports 3 jacks -
In my case it was simpler.
My USB CD drive was recognized as cd0, so I typed the following command and he continued to installation.cd9960:/dev/cd0
Good luck!
-
I ran into this issue when trying to automate building PfSense on Hyper-V with Packer.
When I added a DVD Drive to IDE Controller 0 at location 1. It Failed.
When I added a DVD Drive to IDE Controller 1 at location 0. It Succeeded.
When I added a DVD Drive to IDE Controller 1 at location 1. It Succeeded.So my conclusion is try to use any other location for the DVD controller, if you receive this error message. On a physical machine swap it to the next available port.
-
Same issue with me now too.
Install is fine, but with any sudden power off, the device is dead.
Running latest pfsense on Sophos hardware.
-
You should start a new thread for this and detail exactly what you're seeing.
It's unlikely the root cause of this is the same after 10 years!Steve
-
@stephenw10 Ok thanks, have done.
