From owner-freebsd-questions@FreeBSD.ORG Fri Nov 16 16:14:19 2012 Return-Path: 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 C41CD623 for ; Fri, 16 Nov 2012 16:14:19 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 7ED1E8FC14 for ; Fri, 16 Nov 2012 16:14:19 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id qAGGEH6h039870; Fri, 16 Nov 2012 09:14:17 -0700 (MST) (envelope-from freebsd@dreamchaser.org) Message-ID: <50A66659.5040406@dreamchaser.org> Date: Fri, 16 Nov 2012 09:14:17 -0700 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120609 Thunderbird/13.0 MIME-Version: 1.0 To: Warren Block Subject: Re: 9.0 crash, ssd or filesystem problem? References: <50A53FF1.7050806@dreamchaser.org> <50A602AB.2060307@dreamchaser.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Fri, 16 Nov 2012 09:14:17 -0700 (MST) Cc: FreeBSD Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: freebsd@dreamchaser.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 16:14:19 -0000 >>>> ~$ gpart show ada0 >>>> => 34 250069613 ada0 GPT (119G) >>>> 34 128 1 freebsd-boot (64k) >>>> 162 41943040 2 freebsd-ufs (20G) / >>>> 41943202 1048576 3 freebsd-swap (512M) swap >>>> 42991778 8388608 4 freebsd-ufs (4.0G) /var >>>> 51380386 4194304 5 freebsd-ufs (2.0G) /tmp >>>> 55574690 192216088 6 freebsd-ufs (91G) /usr >>>> 247790778 2278869 - free - (1.1G) >>> >>> It would not cause this problem, but those partitions are not aligned. >>> That would only affect speed, not reliability. >> >> geezes, it's not even on a 4K boundary from the get-go; >> not sure how that happened. >> let-alone the 1M boundary I just learned about. > > That's a normal install. It's fine for 512-byte devices. > I have other suggestions too, but let's save that until the problem is fixed. aaahhh. Vague recollections of getting this to boot up first time around. How about suggestions anyway, as I'm going to build an sata disk and move things to that as part of the process to see what's wrong. May as well get it right-ish the first time; then repartition the SSD. Thanks.