"Now with ZFS if you don't specify a slice, you're essentially asking
ZFS to use and autolabel the entire disk which will put an EFI style
label on since the older sun style VTOC labels have an upper limit of
1TB per disk (EFI should work up to 2^64 LBAs.) The older sun VTOC
labels typically use slice 2 as a backup to show the entire disk and
will store the label in the first 512B, whereas the EFI labels will
use 34 sectors at the start of the disk to store the label, and will
also reserve a portion at the tail end of the disk for a backup label.

With the older sun style VTOC labels, if you ever overwrite the first
the first 512B on cylinder 0 of the disk (eg: dd if=/dev/zero of=/dev/
rdsk/c1t1d0s2 where s2 is the typical backup label starting at
cylinder 0) you'll overwrite the label, whereas with the EFI label
you have to overwrite both protected sections of the disk."

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

You enable/query smart status on the drive.
Do not specify the slice
prtvtoc /dev/dsk/c1t6d0

Do not label or try until you confirm that it is not used anywhere. At this point it is not reflected as mounted.
You may want to explore whether you want to clone it using dd though it is a 146GB in size.

a corrupt label is not about ZFS, it might be UFS as well : The disks c1t6d0 and c1t7d0 have never been labeled before using format => so it's not used. that's it. wanna learn something more ? read on.

a starter how can I tell it's not used
look for the disk in ZFS/zpool
zpool status will show details of all zpools created.
where
zpool status -v rpool
will only show the disks in the rpool.
so
zpool status |grep c1t6d0
or leave the pipe grep out to see all devices
BUT
It might be used by UFS in some kind of mirror...
how to identify ...
metastat -c |grep c1t6d0
or leave the pipe grep out to see all meta devices
BUT it might be used directly in /etc/vfstab
grep C1t6d0 /etc/vfstab
as mentionned before, I'm pretty sure it's not the case.

now we are going to change something to your system !!

use :
format c1t6d0
select:
volname
give it a name, max 8 character, enclosed with " (double quote) , confirm, ...
Exit at the end should do it.
In the action it will label the disk and it will be more than enough in most cases, you shouldn't have the error anymore.

Featured Post

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

SSH (Secure Shell) - Tips and Tricks
As you all know SSH(Secure Shell) is a network protocol, which we use to access/transfer files securely between two networked devices. SSH was actually designed as a replacement for insecure protocols that sen…

It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.

Learn how to navigate the file tree with the shell.
Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…