How to repair kernel panic?

unicorn

I get a kernel panic and automatically reboot, how to fix it? thanks!

unicorn

I use a 2TB HDD, I don't want to reinstall FreeBSD. Is it possible to let my system back to normal?

MG_

When does it happen? Is there any relation to particular hardware or program activity? Is it a GENERIC kernel or customized? If it really seems to
happen at random moments, I would suspect the RAM.
If you don't want to go kernel debugging, few options are left.
1 thing you could try is repeat the sittuation from a remote terminal, so everything until the kernel going down stays on screen.
Assuming this is a PC, you could also try to rule out pieces of hardware. Disconnect everything that isn't required to boot the system.

unicorn

I use external disk, maybe it's damaged

unicorn

I bought a m.2 nvme ssd, and I had instslled freebsd on it, but when using it occasionly went error and I had to force shut down by pressing power button.After reboot it can't mount ufs:/dev/da1p2. I tried ufs:/dev/da0p2,it says something and let me enter full path something like that

unicorn

after I unplug the flash disk, da1 turns to da0, I changed them in fstab and system can boot. But system went wrong about once an hour, what's wrong with my m.2 which is also an external disk?

MG_

unicorn I have the same behaviour with a Aorus Elite v2 motherboard. When I have a USB-c SSD connected, it changes the device order. Any device on it causes da0 to be occpupied, even without a visible volume. After the kernel, the system seems to forget the device we're booted from and drops to the post-kernel bootmenu where you have to give the /dev entry of the partition, which was different before the kernel loaded. I think it's obfuscation of what should be considered the PC-standard for device priority.

I have a similar thing with a old Acer laptop with a SD-cardreader. Even if there's no card in it, da0 still exists, so any external bootdevice that is added becomes da1 in all cases. A default FreeBSD install doesn't get this properly.

This would actually require a type of conditional expression in the fstab file. Don't know if that's possible...