[Bug 218026] GEOM / gpart: secondary table(s) are consistently corrupted

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218026

--- Comment #1 from Chris Hutchinson <portmaster at bsdforge.com> ---
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

-- 
You are receiving this mail because:
You are the assignee for the bug.