Sometimes, HDD is shown *faulted" in "zpool status",but the fact is not. I would recommend getting this relevant disk removed from the pool, and reseated in its slot before seeing if it can be added back into the slot again.
1. Identify faulted logical drives using the following NMC command -
nmc$ show volume {VOLNAME} status
2a. If you have vendor provided slot mapping, identify the slot number, by executing
nmc$ show lun slotmap | grep c8t50000393E8CABBF0d0
2b. Alternatively, if you do not have slot mapping pre-configured, you could still identify the faulted drive using the following command: nmc$ show lun c8t50000393E8CABBF0d0 blink
2c. Use /usr/lib/fm/fmd/fmtopo -V > /tmp/fmtopo.outgrep -B12 c8t50000393E8CABBF0d0 /tmp/fmtopo.out | grep -A1 SLOT
label string SLOT 55 46
FRU fmri hc://:product-id=DataON-DNS-1660:server-id=:chassis-id=500093d000401000:serial=32R0A04GFM13:part=TOSHIBA-MK2001TRKB:revision=0105/ses-enclosure=4/bay=56/disk=0
The BAY # is the SLOT # on the DNS 1660
2d. Use dd to identify the location of the drive within the JBODAs root:
-- while true
______do
____________ dd if=/dev/rdsk/c8t50000393E8CABBF0d0s0 of=/dev/null bs=8192 count=100000
____________ sleep 5
______done
2e. If you are still unable to locate the disk, you will need to locate it by a process of elimination by blinking the remaining disks and seeing which one remains
3. Once physical location of the faulted drive is identified, remove it from the pool
nmc$ setup volume {VOLNAME} remove-lun {lun}
4. from bash see if the disk can be unconfigured
# cfgadm -al
# cfgadm -c unconfigure c1::dsk/c1t2d0 (change c1 and dsk to reflect your device)
5. Physically remove failed-disk from JBOD.
6. nmc$ lunsync -r
7. Insert new drive into the JBOD
8. nmc$ lunsync -r
Add the disk back into the pool again