From owner-freebsd-bugs@freebsd.org Fri Mar 31 16:35:56 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99299D27CBA for ; Fri, 31 Mar 2017 16:35:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 62556BBF for ; Fri, 31 Mar 2017 16:35:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2VGZuCI074044 for ; Fri, 31 Mar 2017 16:35:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 218026] GEOM / gpart: secondary table(s) are consistently corrupted Date: Fri, 31 Mar 2017 16:35:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: portmaster@bsdforge.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 16:35:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218026 --- Comment #1 from Chris Hutchinson --- OK. I use the USB3 flash stick I mentioned above, for dumps, and other important backups. Today, in an attempt to experiment with the 12-CURRENT install I have a fresh dump on the stick for. I plugged in a USB2 external drive, and bounced the box, with the intention of performing a restore(8) to the external drive. I forgot that I had an install of ghostbsd on that external drive, and given that I usually have a USB DVD plugged into that port, it booted to ghostbsd. So I simply bounced the box, and changed the boot order in the BIOS, and booted single-user to my 12-CURRENT. performed the following (to the external [usb] drive): gpart destroy -F da0 gpart create -s GPT da0 gpart add -t freebsd-boot -l usbboot -b 40 -s 512k da0 gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 gpart add -t freebsd-ufs -l usbroot -s 8G da0 gpart add -t freebsd-swap -l usbswap -s 3G da0 gpart add -t freebsd-ufs -l usbvar -s 55G da0 gpart add -t freebsd-ufs -l usbusr da0 followed by a newfs -U /dev/gpt/usbroot newfs -U /dev/gpt/usbvar newfs -U /dev/gpt/usbusr then individually mounting those to /mnt followed by a restore(8) to each. Bounce the box, change boot order in BIOS, and new usb external drive is not listed. Booting into single-user from main drive reveals secondary table is corrupt! Same is true on the usb stick I keep the dumps on. Before performing any of the above. I am forced to perform gpart recover on the usb stick && an fsck. Both return good status. What to do? I can now see this is not limited to USB3, as the external drive is on a USB2 port. This is a real problem! Thanks for anything that might fix this! --Chris FreeBSD 12.0-CURRENT #0 r314700 --=20 You are receiving this mail because: You are the assignee for the bug.=