In case you have SAN RAID storage, and you are running a "zpool create" to create a new zfs volume and you encounter these messages:
This does not always mean that your SAN disk has a problem, no it can be simply the fact that the disks you use already have a zfs header stating the length of the "disk". On some RAID devices, when you reconfigure system disks/disk sets, disks won't be initialized again and - if the new disk group is smaller than it was before - Solaris will try to get the last block of that "disk" - as written in the "wrong" zfs header. This will fail.
Correct it by writing zeroes at the header:
dd if=/dev/zero count=10 of=/dev/dsk/...diskname....
and reboot.
May 26 08:40:22 atlanta scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g0080e52126cdf002 (sd69):
May 26 08:40:22 atlanta SCSI transport failed: reason 'tran_err': giving up
May 26 08:40:23 atlanta scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g0080e52126cdf002 (sd69):
May 26 08:40:23 atlanta SCSI transport failed: reason 'tran_err': giving up
May 26 08:40:24 atlanta scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g0080e52126cdf002 (sd69):
May 26 08:40:24 atlanta SCSI transport failed: reason 'tran_err': giving up
May 26 08:40:24 atlanta scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g0080e52126cdf002 (sd69):
May 26 08:40:24 atlanta SCSI transport failed: reason 'tran_err': giving upThis does not always mean that your SAN disk has a problem, no it can be simply the fact that the disks you use already have a zfs header stating the length of the "disk". On some RAID devices, when you reconfigure system disks/disk sets, disks won't be initialized again and - if the new disk group is smaller than it was before - Solaris will try to get the last block of that "disk" - as written in the "wrong" zfs header. This will fail.
Correct it by writing zeroes at the header:
dd if=/dev/zero count=10 of=/dev/dsk/...diskname....
and reboot.
Leave a comment