New install current v2.6.0 crash on Zimaboard 432

[JetBoater]

Hello - new Zimboard 432 running the latest pfsense image version 2.6.0-RELEASE (amd64) built on Mon Jan 31 19:57:53 UTC 2022 FreeBSD 12.3-STABLE.
System crash/hang .
I have tried reloading fresh image multiple times and using the onboard NIC'c
Is the following indicating bad storage on the board itself or a driver issue?
pfSense kernel: mmcsd0: Error indicated: 2 Bad CRC
pfSense kernel: sdhci_pci0-slot0: Controller timeout
pfSense kernel: sdhci_pci0-slot0: ============== REGISTER DUMP ==============
pfSense kernel: sdhci_pci0-slot0: Sys addr: 0x287f6610 | Version: 0x00001002
pfSense kernel: sdhci_pci0-slot0: Blk size: 0x00000080 | Blk cnt: 0x00000001
pfSense kernel: sdhci_pci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012
pfSense kernel: sdhci_pci0-slot0: Present: 0x1fff0000 | Host ctl: 0x00000025
pfSense kernel: sdhci_pci0-slot0: Power: 0x0000000b | Blk gap: 0x00000080
pfSense kernel: sdhci_pci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000007
pfSense kernel: sdhci_pci0-slot0: Timeout: 0x00000007 | Int stat: 0x00000000
pfSense kernel: sdhci_pci0-slot0: Int enab: 0x00000020 | Sig enab: 0x00000020
pfSense kernel: sdhci_pci0-slot0: AC12 err: 0x00000000 | Host ctl2:0x0000000b
pfSense kernel: sdhci_pci0-slot0: Caps: 0x546ec881 | Caps2: 0x00000807
pfSense kernel: sdhci_pci0-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000
pfSense kernel: sdhci_pci0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000
pfSense kernel: sdhci_pci0-slot0: ===========================================
pfSense kernel: sdhci_pci0-slot0: Tuning failed, using fixed sampling clock
pfSense kernel: mmcsd0: Error indicated: 1 Timeout
pfSense kernel: sdhci_pci0-slot0: Tuning failed, using fixed sampling clock
pfSense kernel: mmcsd0: Error indicated: 1 Timeout
pfSense kernel: mmcsd0: Setting erase start position failed Timeout

[JetBoater]

@jetboater I did just find this bug report https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238585 on FreeBSD 12.0 and trying the work around now.
By disabling TRIM in /boot/loader.conf.local add "vfs.zfs.trim.enabled=0"
I will update if this works.

[JetBoater]

@jetboater Same issue the fix did not work and still crashed/hung.

[stephenw10]

Are you booting from eMMC? If not you can probably just disable the controller.

There are some other Zimaboard threads here and I don't recall seeing that error. Mostly all issues with the Realtek NICs.

There was some Zotac boxes that had similar errors.

Edit: Like this one.

Steve

[JetBoater]

@stephenw10 Thanks, Yes, I have seen the NIC issues but do not have NIC issues yet. It boots fine just after a few hours crashes/hangs. The ssh connection hangs that I had a tail -f system.log file going. Many of the "pfSense kernel: mmcsd0: Setting erase start position failed Timeout" errors before it becomes unresponsive ssh or https. The errors are only on the console and not written to any log file. I will keep digging.

[stephenw10]

So are you booting from eMMC or from SSD? If you're not using the eMMC you can disable the controller.

[JetBoater]

@stephenw10 Yes, I am booting from the Emmc -- I have not attempted the SSD yet. Being a new board I wanted to get the built in storage stable if possible first before an added SSD.