From owner-freebsd-questions@FreeBSD.ORG Thu Sep 16 11:56:01 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 738141065673 for ; Thu, 16 Sep 2010 11:56:01 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 3061D8FC0A for ; Thu, 16 Sep 2010 11:56:01 +0000 (UTC) Received: from r55.edvax.de (port-92-195-157-147.dynamic.qsc.de [92.195.157.147]) by mx02.qsc.de (Postfix) with ESMTP id EDA1D1E769 for ; Thu, 16 Sep 2010 13:55:57 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id o8GBtvb5001467 for ; Thu, 16 Sep 2010 13:55:57 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 16 Sep 2010 13:55:57 +0200 From: Polytropon To: freebsd-questions@freebsd.org Message-Id: <20100916135557.e5cb35b7.freebsd@edvax.de> In-Reply-To: References: <4C906AB2.3030004@rawbw.com> <20100915121018.a3a1f275.freebsd@edvax.de> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: How to prevent system to launch interactive fsck after improper shutdown and reboot? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2010 11:56:01 -0000 On Wed, 15 Sep 2010 17:11:30 -0400 (EDT), doug@safeport.com wrote: > I have had two systems die with bad disks. Personally, I never had trouble with bad disks, but with defective file systems (origin unknown), and follow-up trouble caused by background fsck that prevented me many years from accessing my data. Going the "old fashioned" way brought everything back. Long story short: A present .snapshot from the 1st background fsck (which was introduced as default in 5.0, as far as I remember) caused fsck from working as expected; after removing this file, I got all the missing data back. Luckily, the problem didn't seem to be related to actual disk failure, as SMART data didn't give a hint about that. I did work with a 1:1 dd copy anyway. > Modern disks die silently which I think is too bad. You usally see messages in dmesg / console that indicate disk trouble. In mos cases, those messages say that the disk is already dying - it's too late for "repair". So time for backup and replacement. Seems that this is the result of continuing bigger and cheaper disks... > If this is > happening and you have data you want to recover you > might try booting in single user move and using fsck > manually on each slice. The fsck program operates on partitions, not on slices. Terminology, dear Watson. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...