Can boot into single user mode on the same machine/hard drive.Can you boot from usb/dvd then mount/chroot into your system ?
Thanks. So I was able to mount usingWhen you can boot into single user mode. It means the kernel can get loaded, and you are able to go to a shell and fix the problems.
Things you can try:
-Mount root filesystem
-Use chroot
-Perform freebsd-upgrade
-Do a pkg update& upgrade.
-Reinstall bootcode with "gpart bootcode"
zfs mount -a
Thanks. Good suggestions. Couldn't find much under/var/log/messagesBefore doing any complicated things that change the state (and may sweep the problem under the rug), diagnose what the problem is. To begin with: when the system panics, what does the console show? What is the call stack? That tells you what part of the kernel is unhappy, which is already valuable. Perhaps even more important: What process caused the panic? I think the normal panic output on the console shows the current process ID and name.
Next question: What action causes it? If you can boot into single user mode, stay there for a while, and try several things. For example: Is your storage OK? Are there disk errors? What unusual stuff do you see in dmesg or /var/log/messages? Are your file systems in good health? Are all the expected peripherals present?
Think back: What was the most recent configuration change you made before it started crashing?
Having explored single user mode, try bringing the system to multi-user mode but do NOT start X windows or the GUI. Does it still work? Is normal user login possible? You said above that multi-user mode crashes, but I don't know whether you really mean GUI login there.
chroot / /usr/local/bin/zsh
This worked but somehow when I try setting zfs fa to writeable using this it doesn't workSomething like,
Code:chroot / /usr/local/bin/zsh
zfs set read-only=off zroot/ROOT/default
mount -t zfs zroot/ROOT/default /
Meaning the same system/BE that would normally crash if going into multiuser ? If we see where the GPF is happening we may be able to narrow it down. Any special driver being loaded in loader.conf or by rc.conf (graphics driver) ?Can boot into single user mode on the same machine/hard drive.
Don't think I've changed them recently/boot/loader.conf
&
/etc/rc.conf
Could be a cause.
Yes, same system crashing in multiuser. Tried changing BE but multiuser mot working.Are you able to take picture of that fault and share?
Meaning the same system/BE that would normally crash if going into multiuser ? If we see where the GPF is happening we may be able to narrow it down. Any special driver being loaded in loader.conf or by rc.conf (graphics driver) ?
If you had chrome crashing prior to this boot issue it could be a HW problem. Can you do a memtest+ ram test booting usb ?
dumpon -l
shows you if you have any dump devices configured. Depending on your disk layout (gpart show
) you need to select swap partition with dumpon
and add at least dumpdev="AUTO"
in rc.conf.So I tried mounting zfs latest poolWhen you can boot into single user mode. It means the kernel can get loaded, and you are able to go to a shell and fix the problems.
Things you can try:
-Mount root filesystem
-Use chroot
-Perform freebsd-upgrade
-Do a pkg update& upgrade.
-Reinstall bootcode with "gpart bootcode"
A module loaded in loader.conf might have changed during a package upgrade or similar.Don't think I've changed them recently
Yea this could be likely - but how do I check?A module loaded in loader.conf might have changed during a package upgrade or similar.
Just comment out everything not 100% required in loader.conf would be worth a try.Yea this could be likely - but how do I check?
My Mobile camera pictures are apparently too large to upload here:/If I can share my 2c, please don't do a kitchen sink approach to this problem and for sure don't start reinstalling stuff. GPF trap in kernel is for sure not due to bad bootcode. You are already in single mode, you're long gone after bootcode.
If you share that picture, we can see what's happening. From there we can navigate and give you better suggestions.
Current process: 49022 (rm)
Trap no =9
Panic: general protection fault
......
....
Fatal trap 9: general protection fault while in kernel mode
......
.....
Warning !drm_modeset_is_locked)...
So I was able to see dmesg logs. It seems like it's the graphic drivers. Starts withWell, not ideal, but you did share already important part: "drm_modeset_is_locked". This is graphics driver related stuff. As I mentioned in my first reply here - locate video-driver specific lines in /boot/loader.conf and /etc/rc.conf , comment them out and try booting again.
Also most likely some part of the system did get updated then.
!drm_modeset_is_locked(.... failed at /wrkdirs/user/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.113_8/drivers/GPU/drm/drm_atomic_helper.c:669
Kernel trap 12 with interrupts disabled
Fatal trap 12 : page fault while in kernel mode
cpuid=0; apic Id= 00
Fault virtual address= .....
I vaguely remember installing drm-510-kmod from ports back in the day . I tried `make deinstall delete` by going into ports... Seemed to delete it.What is the graphics card you use and which driver ?
Do you load the driver from loader.conf or rc.conf.
....
#i915kms_load="YES"
fuse_load="YES"
#kern.vty=vt
.....
kld_list="/boot/modules/i915kms.ko"
#gnome
dbus_enable="YES"
hald_enable="YES"
slim_enable="YES"
.....