Update 2.3.3 -> 2.3.4 = No boot.

steve_v

APU2
Now that I have a console cable:

SeaBIOS (version ?-20160307_153453-michael-desktop64)
XHCI init on dev 00:10.0: regs @ 0xfeb22000, 4 ports, 32 slots, 32 byte contexts
XHCI    extcap 0x1 @ feb22500
XHCI    protocol USB  3.00, 2 ports (offset 1), def 0
XHCI    protocol USB  2.00, 2 ports (offset 3), def 10
XHCI    extcap 0xa @ feb22540
Found 2 serial ports
ATA controller 1 at 4010/4020/0 (irq 0 dev 88)
EHCI init on dev 00:13.0 (regs=0xfeb25420)
ATA controller 2 at 4018/4024/0 (irq 0 dev 88)
Searching bootorder for: /pci@i0cf8/*@14,7
Searching bootorder for: /rom@img/memtest
Searching bootorder for: /rom@img/setup
ata0-0: KingFast ATA-9 Hard-Disk (15272 MiBytes)
Searching bootorder for: /pci@i0cf8/*@11/drive@0/disk@0
Found sdcard at 0xfeb25500: SD card 00000 3765MiB
XHCI no devices found
Initialized USB HUB (0 ports used)
All threads complete.
Scan for option roms
PCengines Press F10 key now for boot menu:
Searching bootorder for: HALT
drive 0x000f2e90: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=31277232
drive 0x000f2e60: PCHS=0/0/0 translation=lba LCHS=956/128/63 s=7710720
Space available for UMB: c1000-ef000, f0000-f2e60
Returned 262144 bytes of ZoneHigh
e820 map has 7 items:
  0: 0000000000000000 - 000000000009f800 = 1 RAM
  1: 000000000009f800 - 00000000000a0000 = 2 RESERVED
  2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
  3: 0000000000100000 - 00000000dffae000 = 1 RAM
  4: 00000000dffae000 - 00000000e0000000 = 2 RESERVED
  5: 00000000f8000000 - 00000000fc000000 = 2 RESERVED
  6: 0000000100000000 - 000000011f000000 = 1 RAM
enter handle_19:
  NULL
Booting from Hard Disk...
Booting from 0000:7c00

F1  pfSense
F5  Drive 1

F6 PXE
Boot:  F1 
/boot/config: -S115200 -h
Invalid format

FreeBSD/x86 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot: 
No /boot/kernel/kernel

FreeBSD/x86 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot:

Huh?

Ed. Filesystem totally hosed. >:(
Reinstalling, pretty keen to know what went so horribly wrong here…

TnIan

Same exact issue here. What did you do with yours?

Stepinsky

Which bios version do you have? There are known problems with latest bios (4.6.x mainline branch) when accessing hard disks:

v4.6.x BIOSes need to have MSI disabled, due to signal races causing disk write commands timeouts.

Read more at pc engines github page.
Maybe your issue is related to this bug?