Date: Tue, 7 Jan 2014 11:52:16 +0100 From: Polytropon <freebsd@edvax.de> To: eras mus <erasmu@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Message-ID: <20140107115216.1f06587d.freebsd@edvax.de> In-Reply-To: <CALeO_hN81jxUvf_Q4kLHL0%2BwWxn-7V42=CeFsxod6fawbFB2PA@mail.gmail.com> References: <CALeO_hORJin5OOkA45fG%2BHFrai6XhPpOob4u-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%2BwWxn-7V42=CeFsxod6fawbFB2PA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140107115216.1f06587d.freebsd>