Problem with fsck : continued


Hi,

Thanks for the support so far. FreeBSD is working beautifully, both on the server as well as client workstations. Except for fsck. I am writing from India, where the electrical power scenario makes up for any possible lack of frustration.

My server faces unscheduled power cuts and consequent improper shutdown 2-3 times every day. This is what I have placed in my server's rc.conf :

fsck_y_enable="YES"
background_fsck="NO"

Most of the time when the system comes up on its own without first being subjected to single-user mode operations, half the services (including squid, webmin, vsftpd, svscan and - most significantly - getty for the local console) fail to start up, although fsck does run automatically in the foreground - with the y[es] argument enabled - on all partitions listed in fstab on system restart (i.e. restoration of electricity). The only solution I know is to first go into single-user mode and run fsck on the commandline for all partitions, after which the server comes up quite nicely.

This would be okay if I could leave a console attached to the server, in which case I could run fsck interactively in single-user mode and get the system up again. For daily operations however, my organisation would much prefer to have the server working without a console attached.

So now the question is if I can get FreeBSD 6.0 to run fsck automatically on restart in such a manner that all services come up consistently. I am even willing to have fsck run in the foreground upon EACH restart, irrespective of whether the previous shutdown was proper or improper. How do I do this ?

Thanks for any help. Attached at the bottom is the previous communication.

Manish Jain
goodredhat@xxxxxxxxx





On Thursday 26 January 2006 19:39, manish jain wrote:
> I recently persuaded my organisation to shift our main
> server from Linux to FreeBSD 6.0. We are now facing a
> problem with fsck. After improper shutdown, we need
> fsck to run automatically and non-interactively in the
> foreground upon restart. Enabling background fsck lets
> the system come up but fails to properly start a few
> network services.
When you say you enabled it, do you simply mean you did nothing at all, or did you add an extra fsck -B somewhere.
Background fsck is enabled by default, and it runs 60 seconds after all other initialization. Partitions can only be deferred for background checking if they support it, and are in a mountable state. These partitions are simply skipped in the pre-mount fsck check.
All it does is recover lost space. It shouldn't have any impact other than a general slowdown.



---------------------------------

What are the most popular cars? Find out at Yahoo! Autos
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Booting Problem After Power Loss (fsck)?
    ... The server was totally idle when the power was cut, ... FreeBSD community and a new start on computing, ... >>Booted into single-user mode and ran 'fsck' - the latest output to ... > and no disk activity I suggest that you break to debugger hitting ...
    (freebsd-questions)
  • SOLVED! : Please help - URGENT - disk/fsck problems!
    ... > server down before the outage occurred), ... > disk problems and suggested I run fsck. ... No employee or agent is authorized to conclude any binding agreement on behalf of Watkins Contracting, L.P., with another ... presented in this email are solely those of the author and do not necessarily represent those of Watkins Contracting, ...
    (freebsd-questions)
  • Re: Please help - URGENT - disk/fsck problems!--SOLVED!
    ... > server down before the outage occurred), ... > disk problems and suggested I run fsck. ... No employee or agent is authorized to conclude any binding agreement on behalf of Watkins Contracting, L.P., with another ... presented in this email are solely those of the author and do not necessarily represent those of Watkins Contracting, ...
    (freebsd-questions)
  • Re: error ouput of fsck
    ... Also the other server had this sudden diffrent output ... RECONNECT? ... UNREF FILE I=659457 OWNER=admin MODE=140755 ... I tried to do fsck.. ...
    (freebsd-questions)
  • RE: Problem with fsck : continued
    ... Problem is not with FreeBSD or fsck, it's your electrical power ... There is FreeBSD port system software that works with different UPS ... My server faces unscheduled power cuts and consequent improper ...
    (freebsd-questions)