From owner-freebsd-questions@FreeBSD.ORG Fri Dec 8 21:36:41 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F357316A40F for ; Fri, 8 Dec 2006 21:36:40 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD55D43C9D for ; Fri, 8 Dec 2006 21:35:40 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin05-en2 [10.13.10.150]) by smtpout.mac.com (Xserve/8.12.11/smtpout14/MantshX 4.0) with ESMTP id kB8Laeoq028469; Fri, 8 Dec 2006 13:36:40 -0800 (PST) Received: from [17.214.13.96] (a17-214-13-96.apple.com [17.214.13.96]) (authenticated bits=0) by mac.com (Xserve/smtpin05/MantshX 4.0) with ESMTP id kB8LacBW005192; Fri, 8 Dec 2006 13:36:39 -0800 (PST) In-Reply-To: <539c60b90612081321g79dc7068j1c0cb87d9724e571@mail.gmail.com> References: <539c60b90612081321g79dc7068j1c0cb87d9724e571@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Fri, 8 Dec 2006 13:36:37 -0800 To: Steve Franks X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: freebsd-questions@freebsd.org Subject: Re: acpi woes and dead filesystem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Dec 2006 21:36:41 -0000 On Dec 8, 2006, at 1:21 PM, Steve Franks wrote: > Now, I'm a bit of a tree-hugger, see, so I tend to like to suspend my > computers insted of leaving them on perpetually. You might try turning them off entirely...? > As such, tried acpiconf -s3 initially (others say unsupported). > Seemed to go down ok, but coming back up it reboots every time. Ho > hum. So I follow the handbook and go apm -Z, but that barely saves > any power (can still hear disk, fan, etc, although screen blanks (apm > -z also casues a reboot) Try updating your BIOS. Try to verify that all of the hardware you have installed actually supports going into power-saving mode-- I was surprised to discover that, for instance, some USB devices will prevent the system from entering S3 power-save mode. You might also try tweaking the BIOS settings, and see whether you can get S1 mode working first, before trying to get the deeper S3 mode going. > Reanabled acpi -s3, lo, it appears to work, except, first time, only X > comes back (not vtty's). Second time X doesn't come back either. Try > ctl-alt-del, try suspend button, etc, no choice but to power down. > > I should mention at this point, that being paranoid, I habitually set > all my fstab's to rw,sync, not just rw, which makes my next finding > somewhat suprising to me: > > Upon power up, I am informed my filesystem is toast, and all I get > is a shell. Did running "fsck" by hand fix it? Note that you really ought to mention some basic details, such as which version of FreeBSD you are running, and what your hardware is... > My question: besides searching for sympathy, does anyone know how to > truly protect a system against unplanned powerdown and/or crash during > disk acess? By using an external UPS, or a high quality RAID system which includes an internal battery to ensure the disk cache gets flushed.... -- -Chuck