From owner-freebsd-questions@FreeBSD.ORG Wed Sep 25 05:24:02 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1D24F11D for ; Wed, 25 Sep 2013 05:24:02 +0000 (UTC) (envelope-from tyler@tsweet.net) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AF5FF27DD for ; Wed, 25 Sep 2013 05:24:01 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id x12so5560439wgg.8 for ; Tue, 24 Sep 2013 22:23:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=34pmVsKuvtnzoOWRxOr0szZH9PTDvmaOKIX73kyNh8Y=; b=f4ADE0wRaWt6lP00lCCnNg03l7SJ7SVEfdD7y2P7o7lGdwYhAfpErDhFs6jpj0NpKR 2keCY3R2ql3AKZRAQRCBrrqJ9DYSYUrpHr6I+Wss3431GuXuQeYarXh9bUWdTfxrS74R Y8GfpirKjYPkf3WzgtpKtvEEFM2hiOLQZHSNS5qL4++vLOR8Ub+TGJfgRT5iEWKVmV9L VMETDVgMT1VD0bGHZeCqvc/hywkYt8dnBCEQMmqrMRbILI6pbauZW3fhGt82pgJJpUeU nFkxIOsjfqBRHnraqhtQ/hiO5jU5/DCNfW/C4GPJTRwZVg4uaEPUOtt55smOyQH4Knj+ IOiw== X-Gm-Message-State: ALoCoQn7baVOyJxvF+jv92rMJvT0299InkXo5LoF+wcJaqd/QcxDBKdcVNMORV9bpuMrjzL0mSN0 X-Received: by 10.180.90.19 with SMTP id bs19mr20911236wib.15.1380085184068; Tue, 24 Sep 2013 21:59:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.12.194 with HTTP; Tue, 24 Sep 2013 21:59:03 -0700 (PDT) X-Originating-IP: [67.212.118.60] From: Tyler Sweet Date: Tue, 24 Sep 2013 23:59:03 -0500 Message-ID: Subject: FreeBSD 8.4 Boot failure To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2013 05:24:02 -0000 Hello all, Not sure if this is the correct list. I've run into a problem with one of my servers where it no longer boots. It uses GPT and ZFS for root. Recently, I did an upgrade from 8.2 up to 8.4. That went fine, and I rebooted a few times after that to finish installing updates. During those reboots, I also updated ZFS to the most recent version to take advantage of dedupe and the new compression algorithm. The server has two zpools, zroot which has the system on it, and data, which has everything else (except /usr/home, which is on zroot). I followed this guide a long, long time ago: https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 While deleting several large files, the system stopped responding to SSH/HTTP/everything except ping. Thinking it was just taking a long time to finish, I let it sit for about a day. When it didn't recover, I had to do a hard power-off, as it wasn't accepting key strokes at the console. When it boots back up, it gets past POST and then goes to a black screen with just a spinner in the upper left-hand corner. No text, no logo, nothing else. The spinner used to spin around a few times, now it does nothing. I've managed to get boot zpools loaded up in the fixit console, they don't show any errors. I tried reinstalling the boot blocks from both the fixit live filesystem and also mounting zroot and using the files there in case they were different. Neither one seems to change anything. I've let it sit at the (mostly) blank screen for two hours with no change. I'm at the end of my wits, and haven't been able to find any information as to what could be causing this. There are no error messages at the console, and the only output is that frozen spinner. >From what I remember, I didn't change anything on the zroot zpool during the upgrade, only the data zpool to enable the new compression and dedupe on a couple file systems where they would be useful. I've checked /boot/loader.conf and /etc/fstab, and neither one has changed since it was last working. My only though is if the zroot zpool was borked somehow, but it still loads up without any issue in the fixit console (Though I had to use the -f flag on both zpools when I first loaded them, as they were "still in use" from when the server crashed). All the disks appear to be fine. The server still boots from USB and CD without throwing any errors. Does anyone have any ideas as to what the problem could be, or how I could troubleshoot this Further?