Jan 27 12:35:54 router kernel: /: inode 1286411: check-hash failed
Jan 27 12:35:54 router syslogd: last message repeated 1 times
Jan 27 12:35:54 router kernel: /: inode 1286412: check-hash failed
Jan 27 12:35:54 router syslogd: last message repeated 1 times
Jan 27 12:35:54 router kernel: /: inode 1286413: check-hash failed
Jan 27 12:35:54 router syslogd: last message repeated 1 times
No panic so far, without the cpu microcode. I'll look into that shortly.
Ian
On 2025-01-27 13:12, Patrick M. Hausen
wrote:
Hi all,Am 27.01.2025 um 18:38 schrieb Milan Obuch <freebsd-curr...@dino.sk>:On Mon, 27 Jan 2025 12:10:43 -0500 Ian FREISLICH <ianfreisl...@gmail.com> wrote:I recently bought one of those mini-pc firewall devices (Topton 12th gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg or buildkernel without getting a slew of these messages, inode number changing and a panic shortly thereafter. kernel: /: bad dir ino 4567815 at offset 0: mangled entry [...]Just a "me too" message - I did test another device with the same CPU, mine is SZBOX. [...]In the OPNsense community we had frequent reports of UFS corruption with Alder Lake and Raptor Lake CPUs. Lots of embedded devices of varying manufacture and quality in use, apparently. The problems were fixed in all cases that I am aware of by applying the current Intel microcode update (sysutils/cpu-microcode). Make sure to activate early loading via /boot/loader.conf(.local). HTH, kind regards, Patrick
