From owner-freebsd-stable@FreeBSD.ORG Thu Dec 12 15:33:59 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 29FB8FD7 for ; Thu, 12 Dec 2013 15:33:59 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 7347A1C81 for ; Thu, 12 Dec 2013 15:33:57 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA08192; Thu, 12 Dec 2013 17:33:29 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Vr8GX-000KlP-EF; Thu, 12 Dec 2013 17:33:29 +0200 Message-ID: <52A9D724.1040806@FreeBSD.org> Date: Thu, 12 Dec 2013 17:32:52 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "Eugene M. Zheganin" , freebsd-stable@FreeBSD.org Subject: Re: zfs i/o error - all block copies unavailable References: <52A8C5AF.1000800@norma.perm.ru> <52A99894.4080704@FreeBSD.org> <52A9BABF.6060403@norma.perm.ru> In-Reply-To: <52A9BABF.6060403@norma.perm.ru> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2013 15:33:59 -0000 on 12/12/2013 15:31 Eugene M. Zheganin said the following: > => 34 7814037101 ada1 GPT (3.6T) At work we recently had a problem with the 3TB disks on certain systems. Apparently BIOS silently failed to read offsets >= 2TB. Probably it just read from wrong offsets (e.g. modulo 2TB). So, if any files important for booting like zfsloader or kernel or mandatory boot configuration files ended up at the large offsets, then the system just would not boot. As a precise location of the files on disk is not predictable we had to create a smaller partition specifically for the root pool. Not sure if you have the same issue, but this is something to keep in mind. -- Andriy Gapon