UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY
clint.olsen at gmail.com
Mon Sep 22 00:31:56 UTC 2008
On Sep 21, Jeremy Chadwick wrote:
> You could also consider using clri(8) to clear the inode (190). Do this
> in single-user while the filesystem is not mounted. After using clri,
> run fsck a couple times.
Booting single-user and running fsck again seems to have corrected these
errors. For some reason it said another disk was not properly dismounted
(/dev/ad0s1d - /home) and so it's running fsck in the background since I
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the freebsd-stable