From owner-freebsd-stable@FreeBSD.ORG Sat Apr 6 20:23:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E8AAE95B for ; Sat, 6 Apr 2013 20:23:23 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id 5B302ED3 for ; Sat, 6 Apr 2013 20:23:23 +0000 (UTC) Received: (qmail 24783 invoked from network); 6 Apr 2013 22:16:40 +0200 Received: from smtp.free.de (HELO orwell.free.de) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 6 Apr 2013 22:16:40 +0200 Subject: Re: gptzfsboot: error 4 lba 30 Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Kai Gallasch In-Reply-To: <201304021707.14719.jhb@freebsd.org> Date: Sat, 6 Apr 2013 22:16:39 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0F20F9F9-CBFD-48B6-8A86-82DAA4AB5BEB@free.de> <201304021707.14719.jhb@freebsd.org> To: freebsd-stable X-Mailer: Apple Mail (2.1085) Cc: John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2013 20:23:24 -0000 Am 02.04.2013 um 23:07 schrieb John Baldwin: > On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote: >> Hi. >>=20 >> On one of my fresh installed servers I am seeing the following output = during=20 > boot: >>=20 >> gptzfsboot: error 4 lba 30 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 30 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >> gptzfsboot: error 4 lba 31 >=20 > Humm, do you have disks that the BIOS sees that are small? An error = code of 4 > means 'sector not found' or 'read error'. It would be interesting to = see the > output of 'lsdev -v' from the loader prompt. Since upgrading the server to 9-STABLE (2013-03-30) the gptzfsboot error = message miraculously disappeared. Because I upgraded the zpools on this particular server to a new version = ("feature flags") I cannot boot back to 9.1-REL to find out if the = upgrade was the cause of this - or not. When I bootup the server from a 9.1-REL USB stick, I also cannot = reproduce the error. What did I change since seeing the error message the first time? - I put GPT partitions on da2-da7 and used them for zpools - Upgrading 9.1 REL to 9.1-2013-03-30 - refreshed the zfs bootcode on da0/da1 aferwards If the error shows up again on a similar server soon to be upgraded, = I'll give feedback. Kai.=