Project

General

Profile

Actions
Copy link

Bug #4822

closed

nanobsd corruption issues after unclean shut down when rw mounted and SU

Added by Kill Bill over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Very High
Assignee:
-
Category:
Operating System
Target version:
2.2.4
Start date:
07/09/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.3
Affected Architecture:
All

Description

https://forum.pfsense.org/index.php?topic=96326.0

Trying to mount root from ufs:/dev/ufs/pfsense0 [ro,sync,noatime]...
WARNING: / was not properly dismounted
Configuring crash dumps...
** SU+J Recovering /dev/ufs/pfsense0
** Reading 7565312 byte journal from inode 4.
** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
/dev/ufs/pfsense0: Block missing from ino 8254 at lbn 18
/dWARNING: /cf was not properly dismounted
ev/ufs/pfsense0: UNEXPECTED SU+J INCONSISTENCY
/dev/ufs/pfsense0: INTERNAL ERROR: GOT TO reply()
/dev/ufs/pfsense0: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
Filesystems are clean, continuing...
Mounting filesystems...
mount: /dev/ufs/pfsense0: R/W mount of / denied. Filesystem is not clean - run fsck. Forced mount will invalidate journal contents: Operation not permitted
mount: /dev/ufs/cf: R/W mount of /cf denied. Filesystem is not clean - run fsck.: Operation not permitted
Setting up memory disks... done.
Disabling APM on /dev/ad0
pwd_mkdb: /etc//pwd.db.tmp: Read-only file system

     ___
 ___/ f \
/ p \___/ Sense
\___/   \
    \___/

Welcome to pfSense 2.2.4-DEVELOPMENT  ...

cp: /var/db/pbi/keys/pfSense-BETA.ssl: Read-only file system
Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
done.
cap_mkdb: /etc/login.conf.db: Read-only file system
>>> Under 512 megabytes of ram detected.  Not enabling APC.

There is freezes forever, until you CTRL+C out of it and force the fsck to run manually.

^CJul  9 11:04:50 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
# /sbin/fsck -p -y /dev/ufs/pfsense0
** SU+J Recovering /dev/ufs/pfsense0
** Reading 7565312 byte journal from inode 4.
** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
/dev/ufs/pfsense0: Block missing from ino 8254 at lbn 18
/dev/ufs/pfsense0: UNEXPECTED SU+J INCONSISTENCY
/dev/ufs/pfsense0: INTERNAL ERROR: GOT TO reply()
/dev/ufs/pfsense0: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
# /sbin/fsck -y /dev/ufs/pfsense0
** /dev/ufs/pfsense0

USE JOURNAL? yes

** SU+J Recovering /dev/ufs/pfsense0
** Reading 7565312 byte journal from inode 4.

RECOVER? yes

** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
Block missing from ino 8254 at lbn 18
UNEXPECTED SU+J INCONSISTENCY

FALLBACK TO FULL FSCK? yes

** Skipping journal, falling through to full fsck

** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
11510 files, 732309 used, 1127049 free (2049 frags, 140625 blocks, 0.1% fragmentation)

***** FILE SYSTEM MARKED CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****
# /sbin/reboot

Wonderful. :-(

Actions
Copy link

Also available in: Atom PDF