From owner-freebsd-current@FreeBSD.ORG Thu Apr 16 15:14:55 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 959F010656D5; Thu, 16 Apr 2009 15:14:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9232A8FC1D; Thu, 16 Apr 2009 15:14:54 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA23407; Thu, 16 Apr 2009 18:14:52 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <49E74B6B.50100@icyb.net.ua> Date: Thu, 16 Apr 2009 18:14:51 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: Diego Depaoli References: <83e5fb980904061402q73940f8at4ec4b8f821354320@mail.gmail.com> <200904150838.25099.jhb@freebsd.org> <83e5fb980904151627k726294deoe8feba8c0b7d5167@mail.gmail.com> <200904151943.51066.jkim@FreeBSD.org> <83e5fb980904151722p17d4210dqeca1c137683eebb0@mail.gmail.com> In-Reply-To: <83e5fb980904151722p17d4210dqeca1c137683eebb0@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Jung-uk Kim Subject: disklablel/gpart [Was: AMD 780G chipset major issues 3/3 (btx)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2009 15:14:56 -0000 on 16/04/2009 03:22 Diego Depaoli said the following: > On Thu, Apr 16, 2009 at 1:43 AM, Jung-uk Kim wrote: >>> After reboot I get BTX halted. >>> Perhaps bsdlabel -B works only upon a slice with 0X80 flag set? >>> Otherwise I don't know... >> It only works when there is no error. ;-) It seems you have to fix the >> label first. > Starting from this... > can be done without loosing data? You can try to do it with gpart, maybe it will like slices of your disks better :) http://lists.freebsd.org/pipermail/freebsd-geom/2009-April/003440.html E.g.: gpart bootcode -b /boot/boot ad10s1 Be warned that gpart says back something like "partition has boot code" and it's not terribly clear what is actually meant here: "it (already) has boot code, so I am not doing anything" or "I did my job and it (now) has boot code". It is the latter :-) P.S. I have a disk that was labeled from the very start with gpart - both gpart and disklabel treat it nice; another disk was lebeled with disklabel in pre-gpart environment and then moved to a gpart environment - gpart works good with this disk, but disklabel barks the same kind of messages. I guess that this happens because gpart hasn't reset to zero offset field of the special partition c when it adopted disklabel-authored label. -- Andriy Gapon