[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
fsck seg fault failure on vmware -i386?
I've had a running vmware (winXP/Vmware 7)system for several years
where I test and play prior to updating my home server...
kernel & userland @ --current (5.99.23)
No deep attachment to the VM and can of course rebuild, but...thought
someone might be interested in the failure?
Also I might learn something about fixing my system in the future?
The host OS hit a hard reset in the middle of a build.sh distribution
update. I ran scandisk on the host drives during reboot to make sure they
The build output was going to /usr/obj which is mapped onto /dev/rwd0e.
On reboot the machine drops from multi-user boot to single with
an error during the file system checks:
THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
ffs: /dev/rwd0e (/usr)
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
When I try to run fsck on /dev/rwd0e in single user
I receive the following:
/dev/wd0a on / type ffs (local)
# fsck /usr
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=224938 (4 should be 0)
CORRECT? [yn] y
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Count
UNREF FILE I=224938 OWNER=0 MODE=100644
fsck: /dev/rwd0e: Segmentation fault
Is there any other NetBSD-Fu I can use to fix this simply? 8-)
Main Index |
Thread Index |