Members who want to help are not near your 'server'. How do you know it has dumped the memory ? To solve the problem you need to provide any error massages collected. If it is fresh install then may reinstall the same version (?) of OS first and then check for multi user login.Check for compatibility of machine (?).
fsck -y /
. Consider to enable soft update journaling or gjournal(8) as described in an article in the docs, if you do not already have this enabled.Boot into single user and disable all non-essential tweaks. Then by manually invoking single one's sequentially, you will find the misbehaving one. Looks like your UFS filesystem is not clean, which obviously happens on crash, but it could also be the root cause. Boot single user and repair itfsck -y /
. Consider to enable soft update journaling or gjournal(8) as described in an article in the docs, if you do not already have this enabled.
How old is this system? More specifically, how old is the harddrive?All the commands complete without any error!
tunefs -p
will tell you if journaling is enabled. Disable all non-essential tweaks, invoke them manually one after the other. Then you'll find the bad one.HiAccording to the screenshot your filesystem is corrupt (several mangled entries).
How old is this system? More specifically, how old is the harddrive?
recoverdisk /dev/adaX
w/o a destination, to see if you HDD is ok. Any S.M.A.R.T. messages? (sysutils/smartmontools)Now provide the specific error which is still there. If it is serious or require further action gurus here may help you. Any error need to be attended first before going spiral. Enjoy FreeBSD.Although the error still appears on the screen