Can't boot after installation

[flxldwg]

Hi there,

after a few hours of trying I finally installed the latest FreeNAS. After the installation complete notification I reboot and the message shown to me is:

Code:

>> FreeBSD EFI boot block
Loader path: /boot/loader.efi

Initializing modules: ZFS UFS
Load Path:  \EFI\BOOT\BOOT.X64.EFI
Load Deivice: PciRoot (0x0) /Pci (0x1f, 0x2)/Sata (0x5,0x0)/HD(1,GPT,47e45d3c-dd0e-11e8-8ed1-4c72b920f453,0x28,0x82000)
Probing 6 block devices .....* done
ZFS found the following pools: freenas-boot
UFS found no partitions

I'm trying to boot from a mSATA SSD.

Hardware:

Intel Executive Series DQ77KB
Intel Core i5-3470T
12 GB RAM (1600 MHz)


Could s/o please tell me how to handle this?

Thanks.

 

[Chris Moore]

Hi there,

Could s/o please tell me how to handle this?

Thanks.

Did you look at the resources:

Hardware Requirements
http://www.freenas.org/hardware-requirements/

Did you read the manual?
http://doc.freenas.org/11/freenas.html

Updated Forum Rules 4/11/17
https://forums.freenas.org/index.php?threads/updated-forum-rules-4-11-17.45124/

Slideshow explaining VDev, zpool, ZIL and L2ARC
https://forums.freenas.org/index.ph...ning-vdev-zpool-zil-and-l2arc-for-noobs.7775/

Terminology and Abbreviations Primer
https://forums.freenas.org/index.php?threads/terminology-and-abbreviations-primer.28174/

Why not to use RAID-5 or RAIDz1
https://www.zdnet.com/article/why-raid-5-stops-working-in-2009/

FreeNAS® Quick Hardware Guide
https://forums.freenas.org/index.php?resources/freenas®-quick-hardware-guide.7/

Hardware Recommendations Guide Rev 1e) 2017-05-06
https://forums.freenas.org/index.php?resources/hardware-recommendations-guide.12/

 

[flxldwg]

Some of them, yes. Didn't find an awnser.

 

[flxldwg]

So, I read the stuff. Specially the troubleshooting part. I'm not sure if the problems described in troubleshooting do match with my problem. Because there is no "run_interrupt_driven_hooks" or "mountroot" something to see while booting.

 

[Chris Moore]

I'm trying to boot from a mSATA SSD.

So, I read the stuff.

It is most likely hardware incompatibility. It could be because of the system board, which it not in the hardware guide. I would suggest starting with hardware that is known to be compatible. Also, you should try legacy instead of UEFI.