When i attempt to do a pkg_upgrade -a on my system, the system will often apparently crash and reboot always after i have walked away, and come back and see the system rebooted and and the boot halted with a demand to run fsck manually, indicating the system likely crashed abnormally. I have never before seen the system crash like this and it has happened twice already when running pkg_upgrade. As the pkg_upgrade process takes an hour, i am often not there to see whatever has happened. I have looked into doing a kernel dumpon command to capture some diagnostic information, however it says it needs a device the size of physical memory, which is over 500 MB. Given the kernel is only a few megabytes, is that really necessary if I just want to capture some diagnostic information about what it was doing when it crashed.
Also I have wondered what could cause this. The system is used for other disk intensive activity and i have never before seen this happen. Could it be replacing libraries while the system is running is causing something to screw up?
Also I have wondered what could cause this. The system is used for other disk intensive activity and i have never before seen this happen. Could it be replacing libraries while the system is running is causing something to screw up?