It doesn't. But it will if you use the whole disk for ZFS, but that's not "under the radar". There's simply no partition table at all.I find it confusing that a ZFS drive goes under the radar of gpart.
I had done zpool labelclear -f /dev/da0zpool labelclear
Still, it could show something likeIt doesn't. But it will if you use the whole disk for ZFS, but that's not "under the radar". There's simply no partition table at all.
34 500118125 ada0 GPT (238G)
- zfs - (238G)
yes, 15.0-RELEASE-p1Are you doing this from a FreeBSD system?
Exactly what gpart command are you running, gpart list?
What does "geom disk list" show?
How about just "ls -ltr /dev/da*"
If geom disk list shows da0 and ls -ltr /dev/da* also shows something, does "mount" or "zfs list" show anything related to da0?
Not if you created the zpool on the "whole device". That would have wiped out any existing partition table.Still, it could show s.th. like
34 500118125 ada0 GPT (238G)
- zfs - (238G)
Why would it show partition information if there's no partition table on the disk?Still, it could show something like
I think this confuses some people because a brand new USB drive you get from Walmart "shows up" simply because it has a partition table of some sort because it's been formatted to some kind of Windows thing.Why would it show partition information if there's no partition table on the disk?
That did the trick. Thank you.Not if you created the zpool on the "whole device". That would have wiped out any existing partition table.
So based #7, you should be able to do "gpart create -s GPT /dev/da0" If you do that, it will probably show up under gpart list
# gpart create -s GPT /dev/da0
da0 created
# gpart show
..
=> 40 62357424 da0 GPT (30G)
40 62357424 - free - (30G)
I understand that.Why would it show partition information if there's no partition table on the disk?
But it could show that there is zfs on the disk.
How does one remove ZFS from the drive again? So that gpart shows the device and I can dd an OS image onto it?
Nice little script. The wipe clean at the beginning is the solution to more than one or two problems.
You may want to check what util-linux wipefs does or even call it with `wipefs -a -f $DEV` because I remember dd at the beginning not being enough sometimes. =/
My experience with doing dd to clear stuff is "how much". If one looks at partition table sizes you think "1M should be enough" but it's not. Over the years I've seen recommendations of up to 100MB which I think covers even MS defaults for efi partitioning.You may want to check what util-linux wipefs does or even call it with `wipefs -a -f $DEV` because I remember dd at the beginning not being enough sometimes. =/
But remember that this (and the various other posts of the same sort) will destroy any data currently stored on the device.For an empty disk :
gpart create -s MBR
gpart create -s GPT
A hundred or a few hundred MB at the beginning, and a few MB at the very end.My experience with doing dd to clear stuff is "how much". If one looks at partition table sizes you think "1M should be enough" but it's not. ...
The easiest way to clear (most tedious and often not needed) is dd if=/dev/zero over the whole device