Solved Cannot boot: fsck error

Hi, I am using FreeBSD 13.0-RELEASE on a VMware virtual machine. This morning I ran freebsd-update fetch and freebsd-update install; after reboot, I got this error:
error1.PNG

I ran fsck -y and I got this:
error2.PNG


What else can I check to make this system working again?
Thank you very much
 
Hi Vladi. I booted with the ISO file you suggested, and surprisingy boot failed even in this case.
Here is the error I got:

error3.png


Thank you.
 
I booted with an older ISO (12.2-RELEASE), I mounted /dev/da0p2 and:

- I have no /mnt/boot/loader.conf
- this is rc.conf:

Code:
keymap="it"
hostname="server"
ifconfig_em0="inet 192.168.32.8 netmask 255.255.255.0"
defaultrouter="192.168.32.254"
sshd_enabled="YES"
moused_enabled="YES"
ntpd_enabled="YES"
ipv6_network_interfaces="none"
ipv6_activate_all_interfaces=NO"
ip6addrctl_enabled=NO
ip6addrctl_policy=ipv4_prefer
sendmail_enable=NO
portmap_enable=NO
clear_tmp_enable=YES
syslogd_flags="-ss"
icmp_drop_redirects="YES"
icmp_log_redirects="YES"
log_in_vain="YES"
kern_securelevel_enable="NO"
kern_securelevel="3"
nginx_enable="YES"
mysql_enable="YES"
php_fpm_enabled="YES"
postfix_enabled="YES"
scponlyc_enable=YES


- this is sysctl.conf

Code:
net.inet.tcp.blackhole=2
net.inet.udp.blackhole=1
net.inet.ip.random_id=1
kern.ipc.maxsockets=204800
kern.ipc.somaxconn=496
kern.maxfiles=204800
kern.maxfilesperproc=200000
net.inet.ip.portrange.first=1024
net.inet.ip.portrange.last=65535
net.inet.tcp.maxtcptw=40960
net.inet.tcp.msl=30000
 
I was asking for sysctl.conf and loader.conf because on your first post there's some Invalid Arguments for kqueues, umtxp and maxsockets (line 17)
Anyway from the liveCD run fsck on /dev/da0p2 and fix your filesystem.

Regarding maxsockets it must be set after maxfiles otherwise you will get Invalid Argument.
kern.ipc.maxsockets <= kern.maxfiles

 
Ok, it seems I figured out.
I noticed in boot process:

Code:
Autoloading module: _vmci.ko

...that module caused issues recently. So I completely removed that file, instead of simply (badly) renaming.
 
Don't remove it as in the next update it will be created again. If it's have any problem you can blacklist it to prevent it's loading.
 
Don't remove it as in the next update it will be created again. If it's have any problem you can blacklist it to prevent it's loading.
Hi VladiGB,
I have no "vmci" related entry in rc.conf; can I insert this line in loader.conf instead?

Code:
vmci_load="NO"
 
It's detected by the kernel and loaded as module. You can include it in module_blacklist to prevent it's autoloading.
/boot/loader.conf.local
module_blacklist="drm drm2 radeonkms i915kms amdgpu vmci"

This will prevent vmci.ko from /boot/kernel/vmci.ko to be autoloaded.

If you are sure that there's an issue with vmci in FreeBSD 13.0 you may post a bug report. Also during a boot from the LiveCD you can escape to loader prompt and set the variable of module_blacklist to include vmci and see if you get the same panic: page fault during the boot from the LiveCD.
 
Back
Top