Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jun 2008 12:14:34 +0300
From:      Ivailo Tanusheff <i.tanusheff@procreditbank.bg>
To:        "Michael Grant" <mg-fbsd3@grant.org>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>, owner-freebsd-questions@freebsd.org
Subject:   Re: system needing fsck at reboot, manual intervention necessary
Message-ID:  <OFDB6B595C.033B9595-ONC2257465.0032625B-C2257465.0032BC0C@procreditbank.bg>
In-Reply-To: <62b856460806101706y6852c7e5k1922a3b39e628cb1@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

You may put fsck_y_enable="YES"  in /etc/rc.conf  file.
The other option is to modify /etc/rc.d/fsck which is not so good 
approach.

Regards,

Ivailo Tanusheff




"Michael Grant" <mg-fbsd3@grant.org> 
Sent by: owner-freebsd-questions@freebsd.org
11.06.2008 03:41

To
"FreeBSD Questions" <freebsd-questions@freebsd.org>
cc

Subject
system needing fsck at reboot, manual intervention necessary






One of my freebsd 6.3 boxes is crashing and when it reboots, it comes
up in single user mode.  Unfortunately, it's a remote box and I don't
have access to a history of the console and there's nothing in
/var/log/messages.  I think it's a hardware problem, or at least it
seems to be.  It's as if it's a bad power supply.

Anyway, what I'd like to know, where is the fsck that is done at
reboot such that I can modify it to do an fsck -y?  Some people will
argue this is dangerous, but I'm not sure what else one would do.  The
goal is to make it reboot without intervention.

Michael Grant
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"freebsd-questions-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?OFDB6B595C.033B9595-ONC2257465.0032625B-C2257465.0032BC0C>