Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Jun 2011 22:31:00 -0700
From:      Gary Kline <kline@thought.org>
To:        Chuck Swiger <cswiger@mac.com>
Cc:        FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG>
Subject:   Re: how do i fsck my server?
Message-ID:  <20110618053100.GA16059@thought.org>
In-Reply-To: <E72360F6-9DC3-4D6A-BD3E-E23D0E7E79E1@mac.com>
References:  <20110615195027.GA1196@thought.org> <E72360F6-9DC3-4D6A-BD3E-E23D0E7E79E1@mac.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 15, 2011 at 01:04:23PM -0700, Chuck Swiger wrote:
> Date: Wed, 15 Jun 2011 13:04:23 -0700
> From: Chuck Swiger <cswiger@mac.com>
> Subject: Re: how do i fsck my server?
> To: Gary Kline <kline@thought.org>
> Cc: FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG>
> X-Mailer: Apple Mail (2.1084)
> 
> On Jun 15, 2011, at 12:50 PM, Gary Kline wrote:
> > can anybody clue me in on why fsck on my server [yes, of course as root]
> > seem to refuse to WRITE?
> 
> Bad sectors on the hard drive are a somewhat common cause of this.
> 
> >  we had a power out locally and i caught my UPS at
> > the last second.  i powered off my server to save the battery, etc, and 
> > a few minutes ago when i ran 
> > 
> > # fsck -y /var
> > 
> > there were unresolved inconsistancies that fsck was not allowed to resolve.
> 
> Was /var mounted already?  You shouldn't be running fsck on a live filesystem; boot single user or from a FreeBSD CD, and run fsck that way.


	right.  i booted into single-user and fsck still gave me the NO
	WRITE response; then i did a

	# shutdown now to get a # prompt in single-user and got the same
	NO WRITE.  Only it did fix the errors.  dunno... strange.

> 
> > i tried to boot single use but the server (Dell 530) panicked.  so finally,
> > after deliberately crashing the box three times, fsck_ufs ran.  i was able to
> > ping outside.  
> > 
> > is there any way of scripting fsck *every* time i reboot this box?  i just
> > want to make abs certain that the filesystems are clean.  ---didn't fscking
> > used to be easier?
> 
> You can set fsck_y_enable="YES" in /etc/rc.conf, but it shouldn't be necessary.  The system can figure out for itself whether it shutdown cleanly or whether a fsck is necessary.
> 

	i	'll try that, thanks.  

	gary


> Regards,
> -- 
> -Chuck
> 

-- 
 Gary Kline  kline@thought.org  http://www.thought.org  Public Service Unix
           Journey Toward the Dawn, E-Book: http://www.thought.org
          The 8.51a release of Jottings: http://jottings.thought.org




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110618053100.GA16059>