Oh, I'm really sorry, I forgot to reply.
. I typed that command in multi user mode and it showed several commands all of the as far as I can remember defaulted to 'no'. Since I am in single user mode now, I ran that command, and it takes me through but I don't know how to use it. The man page is not helpful.
sudo fsck_ffs /dev/ada0a:** /dev/ada0a (NO WRITE)
** SU+J Recovering /dev/ada0a
USE JOURNAL? no
** Skipping journal, falling through to full fsck
SETTING DIRTY FLAG IN READ_ONLY MODE
UNEXPECTED SOFT UPDATE INCONSISTENCY
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
UNALLOCATED I=6414210 OWNER=operator MODE-100600
SIZE= 4096 MTIME=Mar 15 16:33 2022
FILE=/var/db/entropy/saved-entropy.1
UNEXPECTED SOFT UPDATE INCONSISTENCY
REMOVE? no
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPER BLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
594331 files, 6852664 used, 10157318 free, (20758 frags, 1267070 blocks, 0.1% fragmentation)Answer yes.
Here you go.
head -1000 ? 100 lines is not enough, 1000 should be enough (limiting output is needed, so it's a little bit of guessing game doing this remotely). sudo startx, after that, I installed sddm and by running sudo sddm as a workaround. Now, I shutdown the VM a couple of times through the Virtual Box instead from doing it inside the guest because FreeBSD was not responding(It happens when I try to run mpv or vlc media players). And now I can't open sddm too! sudo fsck it seems to me that it has gotten much worse. This is the output:** /dev/ada0a (NO WRITE)
** SU+J Recovering /dev/ada0a
USE JOURNAL? no
** Skipping journal, falling through to full fsck
SETTING DIRTY FLAG IN READ_ONLY MODE
UNEXPECTED SOFT UPDATE INCONSISTENCY
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=6410741 (432 should be 424)
CORRECT? no
INODE 6414181: FILE SIZE 156495872 BEYOND END OF ALLOCATED FILE, SIZE SHOULD BE 229736
ADJUST? no
** Phase 2 - Check Pathnames
DIRECTORY CORRUPTED I=5294874 OWNER=jack MODE=40755
SIZE=1024 MTIME=Mar 15 21:26 2022
DIR=/usr/home/jack/.config/session
UNEXPECTED SOFT UPDATE INCONSISTENCY
SALVAGE? no
UNALLOCATED I=6414210 OWNER=operator MODE-100600
SIZE= 4096 MTIME=Mar 15 22:00 2022
FILE=/var/db/entropy/saved-entropy.2
UNEXPECTED SOFT UPDATE INCONSISTENCY
REMOVE? no
UNALLOCATED I=6900994 OWNER=_tor MODE-100600
SIZE=0 MTIME=Mar 15 22:04 2022
FILE=/var/db/tor/state
UNEXPECTED SOFT UPDATE INCONSISTENCY
REMOVE? no
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT FILE I=6921337 OWNER=_tor MODE=0
SIZE=0 MTIME=Mar 15 22:04 2022 COUNT 0 SHOULD BE -1
ADJUST? no
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPER BLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
594465 files, 6853308 used, 10126075 free, (19451 frags, 1263328 blocks, 0.1% fragmentation)Um, well you see, writing 1000 lines is not exactly a trivial task, so I'm sorry, I won't be able to fulfill your wish. I pasted the 100 lines of output into a file and then copied that file to my host and the copied it again from host to another VM where I am running the FreeBSD forums. Now since I have lost sddm too (see my earlier post), how can I send it?
strings /var/crash/vmcore.3|head -1000 > vmoutput and copy that file from the VM. Once or twice, while rebooting, I ended up in single user mode. While booting FreeBSD sometimes it reboots again. It was too fast for me to read(next time, I'm gonna record it) but it probably dumps something and the reboots.
We don't know what state is your VM in, it's hard to say what you should or should not do in your particular case. However, you should not run fsck on live system when / is mounted. Also FreeBSD will detect corrupted FS upon boot and will try to fix it automatically. If it fails to do so it drops the boot and lets you interact with it.bsduck says to run fsck, while _martin says not to.
So I followed this thread
. But anyways, here is the requested file.I painfully type them, word for word.
How is ZFS better than UFS? I thought it took more space. Anyways, if it is better I might use it when I install FreeBSD as main OS(now, it is just a 'side OS').
Sometimes you don't know if one is joking on internet or not.
panic: ufs_dirbad: /: bad dir ino 400652 at offset 4608: mangled entry
cpuid = 0
time = 1647226871
KDB: stack backtrace:
#0 0xffffffff80c57525 at kdb_backtrace+0x65
#1 0xffffffff80c09f01 at vpanic+0x181
#2 0xffffffff80c09d73 at panic+0x43
#3 0xffffffff80f0c11f at ufs_lookup_ino+0xe7f
#4 0xffffffff80cc9f2d at vfs_cache_lookup+0xad
#5 0xffffffff80ccdeed at cache_fplookup_noentry+0x1ad
#6 0xffffffff80ccb5f2 at cache_fplookup+0x322
#7 0xffffffff80cd666f at namei+0x6f
#8 0xffffffff80cf40df at kern_statat+0xcf
#9 0xffffffff80cf47bf at sys_fstatat+0x2f
#10 0xffffffff8108baac at amd64_syscall+0x10c
#11 0xffffffff8106243e at fast_syscall_common+0xf8
Uptime: 1h5m48sBy the features and options it provides. It's a bit heavier on resources but considering benefit/cost it's way more on benefit side. That's my personal opinion.
Is it possible to fix? Sometimes the VM is unresponsive, even after leaving it alone for couple of minutes. What do I do then?
fsck-ed it, now i can start sddm. but what about the problem / not being dismounted properly?also just immediately after fsck-ing it, it crashed once!
13.0-RELEASE-⋯. <https://forums.freebsd.org/posts/523465>-n can be used on a mounted file system, do so can be meaningless†-n is omitted, the utility will not attempt any repair.13.1-BETA⋯, it should be reclassified to 13.1-RELEASE.Don't delete the thread, it may help others googling around. No need to share more strings. I'd suggest to look into why you can't read the dump (insufficient space in /var maybe?) and check what directory is affected.