On 11/08/11 04:41, [email protected] wrote: > misc#,Dz:C#! > > when the box with OpenBSD had a power failure and the system did not > unmount properly. > it sometimes gets stuck.The system is asking me to RUN fsck MANUALLY. > as a gateway ,so i can't go to fix it manually everytime.How do I advoid > this? > i want to disable it crumbling to single mode. thanks. > > /dev/rwd0e: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > AUTOMATIC FILE SYSTEM CHECK FAILED; HELP! > Enter pathname of shell or RETURN for sh: > > Best Regards > > Cosmo Wu
I have run a lot of OpenBSD gateway machines, I almost always power them down by wacking the power switch, not by orderly shutdown, and yet, only a very few times has one not come back up well and on their own. I tend to use very small (by modern standards) partitions (i.e., only a small part of a modern disk. No one says you have to allocate all 250G of a 250G disks. You can leave 246G unallocated!), so the fsck times will be tolerable. So, I suspect you are doing something OTHER than running just a gateway, something that is causing more disk activity than a typical gateway does. After your first post, you mentioned mrtg. Ah-hah. I think the answer is, move mrtg to another machine, let your gateway be a gateway. I think that will reduce your problem to manageable levels. The few times I had an OpenBSD gateway not come up on their own at a customer site (I can think of once), I had no trouble walking non-technical people through fsck over the phone. Nick.
