From owner-freebsd-questions@FreeBSD.ORG  Tue Jan  7 10:53:10 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CCA1CF1A
 for <freebsd-questions@freebsd.org>; Tue,  7 Jan 2014 10:53:10 +0000 (UTC)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 89C591A52
 for <freebsd-questions@freebsd.org>; Tue,  7 Jan 2014 10:53:10 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-149-155.dynamic.qsc.de
 [92.195.149.155])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx02.qsc.de (Postfix) with ESMTPS id 9257B279BD;
 Tue,  7 Jan 2014 11:52:39 +0100 (CET)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id s07AqGF4007663;
 Tue, 7 Jan 2014 11:52:16 +0100 (CET) (envelope-from freebsd@edvax.de)
Date: Tue, 7 Jan 2014 11:52:16 +0100
From: Polytropon <freebsd@edvax.de>
To: eras mus <erasmu@gmail.com>
Subject: Re:
Message-Id: <20140107115216.1f06587d.freebsd@edvax.de>
In-Reply-To: <CALeO_hN81jxUvf_Q4kLHL0+wWxn-7V42=CeFsxod6fawbFB2PA@mail.gmail.com>
References: <CALeO_hORJin5OOkA45fG+HFrai6XhPpOob4u-NhnJkLGyorvhA@mail.gmail.com>
 <20140106182826.28018a2f@X220.alogt.com>
 <CALeO_hMOhe_Cf0NQa6p0wrHC7LdA7r6SwkZCOUrqjYUO=sPUYA@mail.gmail.com>
 <alpine.BSF.2.00.1401061303340.24851@mail.fig.ol.no>
 <CALeO_hO=NaErzsY3N0KuDmzE_WkMwms9pp-L14h=Hb0eheCKtQ@mail.gmail.com>
 <20140107085545.06310df9.freebsd@edvax.de>
 <CALeO_hN81jxUvf_Q4kLHL0+wWxn-7V42=CeFsxod6fawbFB2PA@mail.gmail.com>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Polytropon <freebsd@edvax.de>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 10:53:10 -0000

On Tue, 7 Jan 2014 15:46:36 +0530, eras mus wrote:
>   So in single user mode ran fsck. The fsck commands runs fine util it
> comes for /usr. After giving these messsage http://pastebin.com/jujRwp6g It
> is waiting for more than a hour.No other output. Is it  normal phenomena?
> Will it take more time.

That is an interactive prompt. You are supposed to enter Y or N
because a _change_ to the file system has to be authorized by
the operator.

	** /dev/ad4s1e
	** Last mounted on /usr
	** Phase1 - check Blocks and Sizes
	INCORRECT BLOCK COUNT I-5823(12224 should be 13344)
	CORRECT ?[yn]

You can, however, use

	# fsck -yf /usr

to automatically answer "YES", but be sure to _know_ what this
will cause! See "man fsck" for details.

The reason: fsck can automatically repair some kinds of file
system defects. Some "bigger" defects need more changes to the
file system, this _could_ damage files, and in ultra-worst case,
cause data loss. That's why the operator is _prompted_ to make
a decision. In some very exceptional cases it might be better
to _not_ apply the modification and relapse to forensic tools
in the first place. This will probably not required in your
case. :-)



> Please Note: As some one adviced here for memory check. Out of 4 RAMS tried
> removing RAM  one by one and checked whether system is hanging. It still
> hangs .

Use a memtest-CD to make sure. You can test all RAM bars separately
_and_ in the desired combination.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...