I was doing incremental upgrades so I would not have issues going from 13.1 13.2 When I got it to only RC2 the system rebooted by itself and I ended ip with dirty drive, go figure.
I ran fsck and got this and bottom it is kept marked dirty this ** /dev/nvd0p2 (NO WRITE) is the EFI partition ..
what damage control is needed to fix this? because now it is no longer allowing anything to be written to drives no more upgrades etc.
[
I ran fsck and got this and bottom it is kept marked dirty this ** /dev/nvd0p2 (NO WRITE) is the EFI partition ..
what damage control is needed to fix this? because now it is no longer allowing anything to be written to drives no more upgrades etc.
Code:
userx@FreeBeSD:~$ sudo freebsd-update -r 13.2-RC3 upgrade
userx@FreeBeSD:~$ sudo fsck
** /dev/nvd0p5 (NO WRITE)
** SU+J Recovering /dev/nvd0p5
USE JOURNAL? no
** Skipping journal, falling through to full fsck
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
DIRECTORY CORRUPTED I=11858972 OWNER=root MODE=40700
SIZE=1024 MTIME=Apr 3 07:42 2023
DIR=/var/db/freebsd-update
UNEXPECTED SOFT UPDATE INCONSISTENCY
SALVAGE? no
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=12019252 OWNER=root MODE=100644
SIZE=720 MTIME=Apr 3 07:47 2023
RECONNECT? no
CLEAR? no
UNREF FILE I=12019324 OWNER=lightdm MODE=100600
SIZE=2 MTIME=Apr 3 07:46 2023
CLEAR? no
UNREF FILE I=12019326 OWNER=lightdm MODE=140777
SIZE=0 MTIME=Apr 3 07:46 2023
CLEAR? no
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
681644 files, 6798197 used, 22142202 free (62394 frags, 2759976 blocks, 0.2% fragmentation)
** /dev/nvd0p2 (NO WRITE)
** Phase 1 - Read FAT and checking connectivity
** Phase 2 - Checking Directories
** Phase 3 - Checking for Lost Files
442 files, 44 MiB free (45301 clusters)
MARK FILE SYSTEM CLEAN? no
***** FILE SYSTEM IS LEFT MARKED AS DIRTY *****
[