@Avngl said in PFSense Crashing:
https://pastebin.com/S40pQ2iH
Backtrace:
db:0:kdb.enter.default> bt
Tracing pid 19 tid 100147 td 0xfffffe00925b1e40
kdb_enter() at kdb_enter+0x32/frame 0xfffffe00b20229d0
vpanic() at vpanic+0x163/frame 0xfffffe00b2022b00
panic() at panic+0x43/frame 0xfffffe00b2022b60
ffs_blkfree_cg() at ffs_blkfree_cg+0x67b/frame 0xfffffe00b2022c10
ffs_blkfree() at ffs_blkfree+0xa9/frame 0xfffffe00b2022c70
indir_trunc() at indir_trunc+0x395/frame 0xfffffe00b2022d80
handle_workitem_freeblocks() at handle_workitem_freeblocks+0x263/frame 0xfffffe00b2022de0
process_worklist_item() at process_worklist_item+0x24c/frame 0xfffffe00b2022e60
softdep_process_worklist() at softdep_process_worklist+0xed/frame 0xfffffe00b2022eb0
softdep_flush() at softdep_flush+0x11f/frame 0xfffffe00b2022ef0
fork_exit() at fork_exit+0x7f/frame 0xfffffe00b2022f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00b2022f30
--- trap 0xa5a5a5a5, rip = 0xa5a5a5a5a5a5a5a5, rsp = 0, rbp = 0xa5a5a5a5a5a5a5a5 ---
Panic:
bad block 5378932792, ino 18910211
<3>pid 19 (bufdaemon), uid 0 inumber 18910211 on /: bad block
bad block 5378523376, ino 18910211
<3>pid 19 (bufdaemon), uid 0 inumber 18910211 on /: bad block
bad block 5378568272, ino 18910211
<3>pid 19 (bufdaemon), uid 0 inumber 18910211 on /: bad block
dev = ufsid/6622adeb206dea9a, block = 4, fs = /
panic: ffs_blkfree_cg: freeing free block
cpuid = 2
time = 1714060853
KDB: enter: panic
It's a filesystem error. You are running UFS so the first thing I would do is force a fsck:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html?highlight=fsck#manual-filesystem-check
But that bad block error could well be a failing drive. Check the SMART data from it.
Steve