Date: Mon, 13 Jun 2022 01:10:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262617] ZFS pool on USB drive does not mount correctly on startup Message-ID: <bug-262617-227-bE820TDjQo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262617-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262617-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262617 --- Comment #7 from donaldcallen@gmail.com --- (In reply to donaldcallen from comment #5) I tried something other than FreeBSD on the machine I have written about he= re and that experiment did not work out. So I have re-installed FreeBSD. In do= ing so, I revisited the problem caused by creating a pool on the whole backup device, rather than using a partition. This works, but produces error messa= ges about the primary gpt partition table being corrupt, as I mentioned in an earlier comment here. I did some googling on this, and I think my speculati= on in the comment to which I'm replying is correct. Others have seen this issue and one person said that zpool create was not wiping the secondary gpt tabl= e, confusing the system at mount time, exactly as I guessed. His recommendation was to use gpart destroy before creating the pool, which wipes both gpt tab= les. I think this is a bug in zfs create. If it's going to create a pool, it nee= ds to do so in a way that doesn't cause problems when the pool is mounted. That includes wiping the secondary gpt table. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262617-227-bE820TDjQo>