From owner-freebsd-stable@freebsd.org Tue Aug 21 18:43:17 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29277107C229 for ; Tue, 21 Aug 2018 18:43:17 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCF4591DCE for ; Tue, 21 Aug 2018 18:43:16 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from hammy.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 5B7855646E; Tue, 21 Aug 2018 13:43:10 -0500 (CDT) Subject: Re: gpart strangeness To: Mike Tancsa , FreeBSD-STABLE Mailing List References: <4e5b6d81-7fc5-c538-2bd2-8cd5dd040a1d@sentex.net> <6be4ee74-c09d-b88f-e4ed-cadb1537e478@grosbein.net> <7886da80-d2e3-1562-07df-cb955d888e1b@sentex.net> <62183e11-77ad-9b6d-ed57-357764e988d8@sentex.net> From: Eric van Gyzen Message-ID: <2cfb1ceb-7f42-9c00-bbdc-1fbf8036edd1@vangyzen.net> Date: Tue, 21 Aug 2018 13:43:09 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <62183e11-77ad-9b6d-ed57-357764e988d8@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2018 18:43:17 -0000 On 8/21/18 1:30 PM, Mike Tancsa wrote: > There are 3 of these disks I found. Unfortunately, they all seem a > little different from the revision stamps on the board. They are all > from PCEngines who generally seem to source quality products. This is in > an APU3 I have an APU2.  My disk is exactly like your 'good' disk, except for the serial number, obviously.  I don't have any trouble. Maybe you can update the firmware on your bad disk.  I have no idea how. Eric