Problem installing. Mount error.

Status
Not open for further replies.

saverman

Cadet
Joined
Oct 11, 2014
Messages
2
I just tried to install my first FreeNAS server but I can't get it running. Installation goes fine but afterwords I get the error message below. Any ideas on what to do? It's the latest version and I've tried both using USB and installing to a hard drive rom a CD but both ends up the same way.

mountroot >
panic: mount root: unable to (re-)mount root.
cpuid = 0
KDB: stack backtrace
dp_trace_self_wrapper() at db_trace_self_wrapper+02xa/frame 0xffffff800024c740
kdb_backtrace() at kdb_backtrace+0x37/frame 0xffffff800024c800
pacnig() at panic+0x1ce/frame0xffffff800024c900
vfs_mountroot() at vfs_mountroot+0x1583/frame 0xffffff800024cb10
start_init() at start_init+0x4d/frame 0xffffff8000cba0
fork_exit() at fork_exit+0x11f/frame 0xffffff800024cbf0
form_trampoline() at form_trampline+0xe/frame0xffffff800024cbf0
— trap 0, rip = 0, rsp = 0xffffff800024ccb0, rbp = 0 —
kdb:ent: panic
[ thread pid 1 tid 100002 ]
Stopped at kdb_enter+0x3b: movq $0,0xaed112(%rip)
db>
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
You know the forum rules that you probably clicked through without reading when you registered, and are also a red link at the top of every page here? You should read those. Especially the part about listing your hardware, since I'd be willing to bet this is a hardware problem.
 

saverman

Cadet
Joined
Oct 11, 2014
Messages
2
Sorry about that! And for the late reply. I was hoping to get it out there quickly as I don't have much spare time to do this in, something that's reflecting on my late reply as well.

The hardware is the following:

Motherboard: Intel DQ45CB
RAM: 8GB (not sure about the brand at the moment, sorry. Doubt it's the reason, though.)
Hard drive: Hitachi 7k750-750 hts727575a9e362. USB-drive: SanDisk (not sure what model)

That's everything that's installed at the moment. When you say that you think this is hardware related and since the hard drive and USB drive installs ends up the same way, my first guess is that it might be a BIOS setting, right? No idea what it could be, though. You?
 
Status
Not open for further replies.
Top