Accidentally hit the power off button when the system was idling at the logon screen, now i've got the UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY error. I've run fsck -y for around 20 times now, how long will it take to repair itself? it seems like every single file on the disk is corrupt, yet from a single forced shutdown? I'm 110% sure its not my HDD thats damaged. Is this normal though?
681 views and no replies??? I've noticed I have the option of installing OPENSTEP on a number of different filesystems (previously I was using the default), could I install it to a less.... crashy filesystem? Which one should I choose?
Well, your FS was borked beyond repair I suppose. Time to reinstall after recovering your files if you hadn't backed up beforehand.
Unfortunately due to it's age, NeXTSTEP/OPENSTEP has a really basic UFS and is prone to problems because of the lack of journaling. As far as I know you can't install on another FS because they don't support the unix file protection/ownership. What filesystems were you thinking of ? I don't recall seeing an option to install to something with OS4.2 in a x86 VM.