APU2 boot fail (Resolved)
-
Struggling with resolving this. Do not know how to get this to boot again.
PCEngines apu2
coreboot build 20160311
4080 MB ECC DRAMSeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
Found mainboard PC Engines PCEngines apu2
multiboot: eax=0, ebx=0
boot order:
1: /pci@i0cf8/usb@10/usb-@1
2: /pci@i0cf8/usb@10/usb-@2
3: /pci@i0cf8/usb@10/usb-@3
4: /pci@i0cf8/usb@10/usb-@4
5: /pci@i0cf8/@14,7
6: /pci@i0cf8/@11/drive@0/disk@0
7: /pci@i0cf8/*@11/drive@1/disk@0
8: /rom@genroms/pxe.rom
9: pxen0
10: scon1
11:
Found 21 PCI devices (max PCI bus is 03)
Copying SMBIOS entry point from 0xdffb7000 to 0x000f3110
Copying ACPI RSDP from 0xdffb8000 to 0x000f30e0
Copying MPTABLE from 0xdffdc000/dffdc010 to 0x000f2f30
Copying PIR from 0xdffdd000 to 0x000f2f00
Using pmtimer, ioport 0x818
Scan for VGA option rom
Running option rom at c000:0003Google, Inc.
Serial Graphics Adapter 08/22/15
SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (wiv@coreboot-Virtual-Machine) Sat Aug 22 09:25:30 UTC 2015
Term: 80x24
IO4 0
Turning on vga text mode consoleSeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
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: SATA SSD ATA-10 Hard-Disk (15272 MiBytes)
Searching bootorder for: /pci@i0cf8/@11/drive@0/disk@0
XHCI no devices found
Initialized USB HUB (0 ports used)
All threads complete.
Scan for option roms
Running option rom at c100:0003iPXE (http://ipxe.org) 00:00.0 C100 PCI2.10 PnP PMMpmm call arg1=1
pmm call arg1=0
+DFF497D0pmm call arg1=1
pmm call arg1=0
+DFE897D0 C100Searching bootorder for: /rom@genroms/pxe.rom
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
Space available for UMB: c2000-ef000, f0000-f2e90
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:7c00F1 pfSense
F6 PXE
Boot: F1
No /boot/loaderFreeBSD/x86 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot:
No /boot/kernel/kernelFreeBSD/x86 boot
Default: 0:ad(0,a)/boot/kernel/kernel
boot: -
Struggling with resolving this. Do not know how to get this to boot again.
PCEngines apu2
coreboot build 20160311
4080 MB ECC DRAMSeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
…Skip USB. (Some) APU2's have issues with it.
Looking at your firmware, you should be successfull with booting from SD or mSata.
Best like install a mSata, prepare a SD with writing a pfSense-image on it.
Boot. Install to mSata. -
I just set up my APU2C4 today and it would not install from the USB 3 port. It would boot from USB but it wouldn't finish the install. I had to hook up a usb 2 dongle to the internal USB header and boot from it to complete the installation to the msata drive.
Either figure out a way to boot from usb2 or do as @hda has suggested and get a msata drive. They're cheap for a small one.
-
This is an existing firewall which stopped working. Not a new install.
-
Best guess, unless someone has a bit more knowledge, is your boot device is corrupt. I hope you have your config backed up.
-
Well there's nothing to debug here, do a new install. It won't boot without kernel.
-
Yes was corrupt. Used this (http://www.ufsexplorer.com/) to browse the card but just garbage. Replaced for now. Had so many issues with the APU2. Nervous about using this device!
-
Yes was corrupt. Used this (http://www.ufsexplorer.com/) to browse the card but just garbage.
So you had a compact flash card die? With the price of SSD's so low why would you bother with compact flash?
-
No it was a 16gb msata SSD that came from pcengines
-
How long was it in service and did you have TRIM enabled?
-
Yes I had trim enabled. In-service for about six months.
-
That was the one sold by PC Engines? The initial revisions were completely broken.
-
Yes pcengines. Think I will be moving to supermicro platform. All my supermicro systems have had zero failures.
-
I meant the SSD… Supermicro won't exactly help with a faulty SSD.
-
ok. Maybe my issue that pfsense support though was the MB of the pcengines was really the ssd? or maybe both for this system.
db:0:kdb.enter.default> bt
Tracing pid 3499 tid 100150 td 0xfffff8006a6834b0
kdb_enter() at kdb_enter+0x3e/frame 0xfffffe012113f730
vpanic() at vpanic+0x146/frame 0xfffffe012113f770
panic() at panic+0x43/frame 0xfffffe012113f7d0
pmap_remove_pages() at pmap_remove_pages+0x736/frame 0xfffffe012113f8b0
vmspace_exit() at vmspace_exit+0x9c/frame 0xfffffe012113f8f0
exit1() at exit1+0x65f/frame 0xfffffe012113f980
sys_sys_exit() at sys_sys_exit+0xe/frame 0xfffffe012113f990
amd64_syscall() at amd64_syscall+0x40f/frame 0xfffffe012113fab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe012113fab0
–- syscall (1, FreeBSD ELF64, sys_sys_exit), rip = 0x8008fa14a, rsp = 0x7fffffffec48, rbp = 0x7fffffffec60 ---panic: bad pte va 8008a2000 pte 0
cpuid = 1
KDB: enter: panic
