Problem: I left on vacation and I left all my devices plugged in and online. During my absence the wonderful Florida power grid did it’s thing and intermittently decided to work. This brought my firewall down dirty and offline never to be seen again.
Model: NetGate APU4
I had to grab my handy USB to SERIAL cable and use putty to connect in. When connected it would just show the below and not progress. Note: remember to review your device manager and insure you’re typing in the correct COM port.
Configuring crash dumps...
** SU+J Recovering /dev/ufs/pfsense1
** Reading 13258752 byte journal from inode 4.
** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
/dev/ufs/pfsense1: Block missing from ino 133903 at lbn 13
/dev/ufs/pfsense1: UNEXPECTED SU+J INCONSISTENCY
/dev/ufs/pfsense1: INTERNAL ERROR: GOT TO reply()
/dev/ufs/pfsense1: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
Filesystems are clean, continuing...
mount: /dev/ufs/pfsense1: R/W mount of / denied. Filesystem is not clean - run fsck. Forced mount will invalidate journal contents: Op eration 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.
pwd_mkdb: /etc//pwd.db.tmp: Read-only file system
___/ f \
/ p \___/ Sense
Welcome to pfSense 2.2.3-RELEASE ...
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
32-bit compatibility ldconfig path: /usr/lib32
cap_mkdb: /etc/login.conf.db: Read-only file system
After reading through I figured I’d attempt to run fsck. However after running it I received:
^CAug 29 15:35:27 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Enter full pathname of shell or RETURN for /bin/sh: fsck
Aug 29 15:35:31 init: can't exec run fsck for single user: No such file or directory
Next I forced a file system check1)https://doc.pfsense.org/index.php/Forcing_a_Filesystem_Check
# touch /root/force_fsck
touch: /root/force_fsck: Read-only file system
# touch /root/force_fsck
After completing the above and rebooting it came right up with further issues. Saved me from having to flash the CF 🙂
Technology has always been a passion that I've enjoyed.
Latest posts by Mr-Moo (see all)
- Finding your node name Graylog 2.2.x - May 22, 2017
- Path to a syslog - November 18, 2016
- Parallels RAS Remote Desktop Client – mass management - November 13, 2016
Notes & References [ + ]