5l‚ gĀ˙˙˙˙˙˙˙˙˙& ˙˙˙;1˙˙˙˙˙˙NWfĨ˙˙˙y#˙˙˙˙˙˙Š) Ÿ/˙˙˙˙˙˙´T Į|˙˙˙˙˙˙ßįō2˙˙˙8˙˙˙˙˙˙> -c˙˙˙˙˙˙@‹Xö˙˙˙˙˙˙kA|G˙˙˙‘M˙˙˙˙˙˙Ļ´šä˙˙˙˙˙˙Ņ^䐝˙˙˙˙˙˙õ– ' œ˙˙˙˙˙˙˙˙˙2FJÁ˙˙˙]ķ˙˙˙˙˙˙nų#ƒ˙˙˙˙"˜$˙˙˙˙˙˙ĢF!%ڝ˙˙˙˙˙˙Ö{ $&į ˙˙˙˙˙˙ü‡ .Š ˙˙˙)$Ų ˙˙˙˙˙˙< (,OC ˙˙˙˙˙˙`I +-uO ˙˙˙˙˙˙Šq *1Ž ˙˙˙0ĩĖ ˙˙˙˙˙˙ČI /3ŲO ˙˙˙˙˙˙îU 24w ˙˙˙˙˙˙ P.÷ ˙˙˙7AĻ˙˙˙˙˙˙RŦ69g˛˙˙˙:|á˙˙˙˙˙˙p8>§å˙˙˙=ēŠ"˙˙˙˙˙˙ː"<@ā™"˙˙˙˙˙˙õž"?Aä"˙˙˙˙˙˙ B#;I3@,˙˙˙DDF,˙˙˙˙˙˙YO,CGnt,˙˙˙˙˙˙”,FH™ę,˙˙˙˙˙˙ŦÚ7ELŊā7˙˙˙KŌé7˙˙˙˙˙˙į8JNú*8˙˙˙˙˙˙x8MO%V=˙˙˙˙˙˙6\=B^Ke=˙˙˙R`Š=˙˙˙˙˙˙sĒ=QU‹7>˙˙˙˙˙˙ž°CTV¯ļC˙˙˙˙˙˙ÄŧCSZŲčC˙˙˙Yė2D˙˙˙˙˙˙ĄDX\%N˙˙˙˙˙˙(+N[]=4N˙˙˙˙˙˙RYNWeeyN˙˙˙`}ØN˙˙˙˙˙˙ W_cĄW˙˙˙˙˙˙ļWbdËEW˙˙˙˙˙˙ŪWahöķW˙˙˙g Vb˙˙˙˙˙˙\bfj/eb˙˙˙˙˙˙DŠbikWŦb˙˙˙˙˙˙oībZFS-8000-K4.typeZFS-8000-K4.severityZFS-8000-K4.responseZFS-8000-K4.impactZFS-8000-K4.descriptionZFS-8000-K4.actionZFS-8000-JQ.typeZFS-8000-JQ.severityZFS-8000-JQ.responseZFS-8000-JQ.impactZFS-8000-JQ.descriptionZFS-8000-JQ.actionZFS-8000-HC.typeZFS-8000-HC.severityZFS-8000-HC.responseZFS-8000-HC.impactZFS-8000-HC.descriptionZFS-8000-HC.actionZFS-8000-GH.typeZFS-8000-GH.severityZFS-8000-GH.responseZFS-8000-GH.impactZFS-8000-GH.descriptionZFS-8000-GH.actionZFS-8000-FD.typeZFS-8000-FD.severityZFS-8000-FD.responseZFS-8000-FD.impactZFS-8000-FD.descriptionZFS-8000-FD.actionZFS-8000-EY.typeZFS-8000-EY.severityZFS-8000-EY.responseZFS-8000-EY.impactZFS-8000-EY.descriptionZFS-8000-EY.actionZFS-8000-D3.typeZFS-8000-D3.severityZFS-8000-D3.responseZFS-8000-D3.impactZFS-8000-D3.descriptionZFS-8000-D3.actionZFS-8000-CS.typeZFS-8000-CS.severityZFS-8000-CS.responseZFS-8000-CS.impactZFS-8000-CS.descriptionZFS-8000-CS.actionZFS-8000-A5.typeZFS-8000-A5.severityZFS-8000-A5.responseZFS-8000-A5.impactZFS-8000-A5.descriptionZFS-8000-A5.actionZFS-8000-9P.typeZFS-8000-9P.severityZFS-8000-9P.responseZFS-8000-9P.impactZFS-8000-9P.descriptionZFS-8000-9P.actionZFS-8000-8A.typeZFS-8000-8A.severityZFS-8000-8A.responseZFS-8000-8A.impactZFS-8000-8A.descriptionZFS-8000-8A.actionZFS-8000-72.typeZFS-8000-72.severityZFS-8000-72.responseZFS-8000-72.impactZFS-8000-72.descriptionZFS-8000-72.actionZFS-8000-6X.typeZFS-8000-6X.severityZFS-8000-6X.responseZFS-8000-6X.impactZFS-8000-6X.descriptionZFS-8000-6X.actionZFS-8000-5E.typeZFS-8000-5E.severityZFS-8000-5E.responseZFS-8000-5E.impactZFS-8000-5E.descriptionZFS-8000-5E.actionZFS-8000-4J.typeZFS-8000-4J.severityZFS-8000-4J.responseZFS-8000-4J.impactZFS-8000-4J.descriptionZFS-8000-4J.actionZFS-8000-3C.typeZFS-8000-3C.severityZFS-8000-3C.responseZFS-8000-3C.impactZFS-8000-3C.descriptionZFS-8000-3C.actionZFS-8000-2Q.typeZFS-8000-2Q.severityZFS-8000-2Q.responseZFS-8000-2Q.impactZFS-8000-2Q.descriptionZFS-8000-2Q.actionZFS-8000-14.typeZFS-8000-14.severityZFS-8000-14.responseZFS-8000-14.impactZFS-8000-14.descriptionZFS-8000-14.actionErrorMajorNo automated response will be taken.The intent log(s) cannot be replayed.A ZFS intent log device could not be read. Refer to %s for more information.Either restore the affected device(s) and run 'zpool online', or ignore the intent log records by running 'zpool clear'.ErrorMajorNo automated response will be taken.Read and write I/Os cannot be serviced.The ZFS pool has experienced currently unrecoverable I/O failures. Refer to %s for more information.Make sure the affected devices are connected, then run 'zpool clear'.ErrorMajorNo automated response will be taken.Read and write I/Os cannot be serviced.The ZFS pool has experienced currently unrecoverable I/O failures. Refer to %s for more information.Make sure the affected devices are connected, then run 'zpool clear'.FaultMajorThe device has been marked as degraded. An attempt will be made to activate a hot spare if available.Fault tolerance of the pool may be compromised.The number of checksum errors associated with a ZFS device exceeded acceptable levels. Refer to %s for more information.Run 'zpool status -x' and replace the bad device.FaultMajorThe device has been offlined and marked as faulted. An attempt will be made to activate a hot spare if available. Fault tolerance of the pool may be compromised.The number of I/O errors associated with a ZFS device exceeded acceptable levels. Refer to %s for more information.Run 'zpool status -x' and replace the bad device.ErrorMajorNo automated response will be taken.ZFS filesystems are not availableThe ZFS pool was last accessed by another system Refer to %s for more information. The pool has been written to from another host, and was not cleanly exported from the other system. Actively importing a pool on multiple systems will corrupt the pool and leave it in an unrecoverable state. To determine which system last accessed the pool, run the 'zpool import' command: # zpool import pool: test id: 14702934086626715962 state: ONLINE status: The pool was last accessed by another system. action: The pool can be imported using its name or numeric identifier and the '-f' flag. see: http://illumos.org/msg/ZFS-8000-EY config: test ONLINE c0t0d0 ONLINE # zpool import test cannot import 'test': pool may be in use from other system, it was last accessed by 'tank' (hostid: 0x1435718c) on Fri Mar 9 15:42:47 2007 use '-f' to import anyway If you are certain that the pool is not being actively accessed by another system, then you can use the '-f' option to 'zpool import' to forcibly import the pool. FaultMajorNo automated response will occur.Fault tolerance of the pool may be compromised.A ZFS device failed. Refer to %s for more information.Run 'zpool status -x' and replace the bad device.FaultMajorNo automated response will occur.The pool data is unavailableA ZFS pool failed to open. Refer to %s for more information.Run 'zpool status -x' and attach any missing devices, follow any provided recovery instructions or restore from backup.ErrorMajorNo automated response will occur.The pool is unavailable.The on-disk version is not compatible with the running system. Refer to %s for more information. If this error is seen during 'zpool import', see the section below. Otherwise, run 'zpool status -x' to determine which pool is faulted: # zpool status -x pool: test state: FAULTED status: The ZFS version for the pool is incompatible with the software running on this system. action: Destroy and re-create the pool. scrub: none requested config: NAME STATE READ WRITE CKSUM test FAULTED 0 0 0 incompatible version mirror ONLINE 0 0 0 c0t0d0 ONLINE 0 0 0 c0t0d1 ONLINE 0 0 0 errors: No known errors The pool cannot be used on this system. Either move the storage to the system where the pool was originally created, upgrade the current system software to a more recent version, or destroy the pool and re-create it from backup. If this error is seen during import, the pool cannot be imported on the current system. The disks must be attached to the system which originally created the pool, and imported there. The list of currently supported versions can be displayed using 'zpool upgrade -v'. ErrorMinorZFS has attempted to repair the affected data.The system is unaffected, though errors may indicate future failure. Future errors may cause ZFS to automatically fault the device.A device has experienced uncorrectable errors in a replicated configuration. Refer to %s for more information. Run 'zpool status -x' to determine which pool has experienced errors: # zpool status pool: test state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool online' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror ONLINE 0 0 0 c0t0d0 ONLINE 0 0 2 c0t0d1 ONLINE 0 0 0 errors: No known data errors Find the device with a non-zero error count for READ, WRITE, or CKSUM. This indicates that the device has experienced a read I/O error, write I/O error, or checksum validation error. Because the device is part of a mirror or RAID-Z device, ZFS was able to recover from the error and subsequently repair the damaged data. If these errors persist over a period of time, ZFS may determine the device is faulty and mark it as such. However, these error counts may or may not indicate that the device is unusable. It depends on how the errors were caused, which the administrator can determine in advance of any ZFS diagnosis. For example, the following cases will all produce errors that do not indicate potential device failure: A network attached device lost connectivity but has now recovered A device suffered from a bit flip, an expected event over long periods of time An administrator accidentally wrote over a portion of the disk using another program In these cases, the presence of errors does not indicate that the device is likely to fail in the future, and therefore does not need to be replaced. If this is the case, then the device errors should be cleared using 'zpool clear': # zpool clear test c0t0d0 On the other hand, errors may very well indicate that the device has failed or is about to fail. If there are continual I/O errors to a device that is otherwise attached and functioning on the system, it most likely needs to be replaced. The administrator should check the system log for any driver messages that may indicate hardware failure. If it is determined that the device needs to be replaced, then the 'zpool replace' command should be used: # zpool replace test c0t0d0 c0t0d2 This will attach the new device to the pool and begin resilvering data to it. Once the resilvering process is complete, the old device will automatically be removed from the pool, at which point it can safely be removed from the system. If the device needs to be replaced in-place (because there are no available spare devices), the original device can be removed and replaced with a new device, at which point a different form of 'zpool replace' can be used: # zpool replace test c0t0d0 This assumes that the original device at 'c0t0d0' has been replaced with a new device under the same path, and will be replaced appropriately. You can monitor the progress of the resilvering operation by using the 'zpool status -x' command: # zpool status -x pool: test state: DEGRADED status: One or more devices is currently being replaced. The pool may not be providing the necessary level of replication. action: Wait for the resilvering operation to complete scrub: resilver in progress, 0.14% done, 0h0m to go config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 mirror ONLINE 0 0 0 replacing ONLINE 0 0 0 c0t0d0 ONLINE 0 0 3 c0t0d2 ONLINE 0 0 0 58.5K resilvered c0t0d1 ONLINE 0 0 0 errors: No known data errors ErrorCriticalNo automated response will be taken.The file or directory is unavailable.A file or directory could not be read due to corrupt data. Refer to %s for more information. Run 'zpool status -x' to determine which pool is damaged: # zpool status -x pool: test state: ONLINE status: One or more devices has experienced an error and no valid replicas are available. Some filesystem data is corrupt, and applications may have been affected. action: Destroy the pool and restore from backup. see: http://illumos.org/msg/ZFS-8000-8A scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 2 c0t0d0 ONLINE 0 0 2 c0t0d1 ONLINE 0 0 0 errors: 1 data errors, use '-v' for a list Unfortunately, the data cannot be repaired, and the only choice to repair the data is to restore the pool from backup. Applications attempting to access the corrupted data will get an error (EIO), and data may be permanently lost. On recent versions of Solaris, the list of affected files can be retrieved by using the '-v' option to 'zpool status': # zpool status -xv pool: test state: ONLINE status: One or more devices has experienced an error and no valid replicas are available. Some filesystem data is corrupt, and applications may have been affected. action: Destroy the pool and restore from backup. see: http://illumos.org/msg/ZFS-8000-8A scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 2 c0t0d0 ONLINE 0 0 2 c0t0d1 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: /export/example/foo Damaged files may or may not be able to be removed depending on the type of corruption. If the corruption is within the plain data, the file should be removable. If the corruption is in the file metadata, then the file cannot be removed, though it can be moved to an alternate location. In either case, the data should be restored from a backup source. It is also possible for the corruption to be within pool-wide metadata, resulting in entire datasets being unavailable. If this is the case, the only option is to destroy the pool and re-create the datasets from backup. ErrorCriticalNo automated response will be taken.The pool is no longer availableThe metadata required to open the pool is corrupt. Refer to %s for more information. Even though all the devices are available, the on-disk data has been corrupted such that the pool cannot be opened. If a recovery action is presented, the pool can be returned to a usable state. Otherwise, all data within the pool is lost, and the pool must be destroyed and restored from an appropriate backup source. ZFS includes built-in metadata replication to prevent this from happening even for unreplicated pools, but running in a replicated configuration will decrease the chances of this happening in the future. If this error is encountered during 'zpool import', see the section below. Otherwise, run 'zpool status -x' to determine which pool is faulted and if a recovery option is available: # zpool status -x pool: test id: 13783646421373024673 state: FAULTED status: The pool metadata is corrupted and cannot be opened. action: Recovery is possible, but will result in some data loss. Returning the pool to its state as of Mon Sep 28 10:24:39 2009 should correct the problem. Approximately 59 seconds of data will have to be discarded, irreversibly. Recovery can be attempted by executing 'zpool clear -F test'. A scrub of the pool is strongly recommended following a successful recovery. see: http://illumos.org/msg/ZFS-8000-72 config: NAME STATE READ WRITE CKSUM test FAULTED 0 0 2 corrupted data c0t0d0 ONLINE 0 0 2 c0t0d1 ONLINE 0 0 2 If recovery is unavailable, the recommended action will be: action: Destroy the pool and restore from backup. If this error is encountered during 'zpool import', and if no recovery option is mentioned, the pool is unrecoverable and cannot be imported. The pool must be restored from an appropriate backup source. If a recovery option is available, the output from 'zpool import' will look something like the following: # zpool import share cannot import 'share': I/O error Recovery is possible, but will result in some data loss. Returning the pool to its state as of Sun Sep 27 12:31:07 2009 should correct the problem. Approximately 53 seconds of data will have to be discarded, irreversibly. Recovery can be attempted by executing 'zpool import -F share'. A scrub of the pool is strongly recommended following a successful recovery. Recovery actions are requested with the -F option to either 'zpool clear' or 'zpool import'. Recovery will result in some data loss, because it reverts the pool to an earlier state. A dry-run recovery check can be performed by adding the -n option, affirming if recovery is possible without actually reverting the pool to its earlier state. ErrorCriticalNo automated response will be taken.The pool cannot be importedOne or more top level devices are missing. Refer to %s for more information. Run 'zpool import' to list which pool cannot be imported: # zpool import pool: test id: 13783646421373024673 state: FAULTED status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: http://illumos.org/msg/ZFS-8000-6X config: test FAULTED missing device c0t0d0 ONLINE Additional devices are known to be part of this pool, though their exact configuration cannot be determined. ZFS attempts to store enough configuration data on the devices such that the configuration is recoverable from any subset of devices. In some cases, particularly when an entire toplevel virtual device is not attached to the system, ZFS will be unable to determine the complete configuration. It will always detect that these devices are missing, even if it cannot identify all of the devices. The pool cannot be imported until the unknown missing device is attached to the system. If the device has been made available in an alternate location, use the '-d' option to 'zpool import' to search for devices in a different directory. If the missing device is unavailable, then the pool cannot be imported. ErrorCriticalNo automated response will be taken.The pool is no longer availableA device could not be opened due to a missing or invalid device label and no replicas are available. Refer to %s for more information. For an active pool If this error was encountered while running 'zpool import', please see the section below. Otherwise, run 'zpool status -x' to determine which pool has experienced a failure: # zpool status -x pool: test state: FAULTED status: One or more devices could not be used because the the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://illumos.org/msg/ZFS-8000-5E scrub: none requested config: NAME STATE READ WRITE CKSUM test FAULTED 0 0 0 insufficient replicas c0t0d0 FAULTED 0 0 0 corrupted data c0t0d1 ONLINE 0 0 0 errors: No known data errors The device listed as FAULTED with 'corrupted data' cannot be opened due to a corrupt label. ZFS will be unable to use the pool, and all data within the pool is irrevocably lost. The pool must be destroyed and recreated from an appropriate backup source. Using replicated configurations will prevent this from happening in the future. For an exported pool If this error is encountered during 'zpool import', the action is the same. The pool cannot be imported - all data is lost and must be restored from an appropriate backup source. ErrorMajorA hot spare will be activated if available.The pool is no longer providing the configured level of replication.A device could not be opened due to a missing or invalid device label. Refer to %s for more information. For an active pool If this error was encountered while running 'zpool import', please see the section below. Otherwise, run 'zpool status -x' to determine which pool has experienced a failure: # zpool status -x pool: test state: DEGRADED status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-4J scrub: none requested config: NAME STATE READ WRITE CKSUM test DEGRADED 0 0 0 mirror DEGRADED 0 0 0 c0t0d0 ONLINE 0 0 0 c0t0d1 FAULTED 0 0 0 corrupted data errors: No known data errors If the device has been temporarily detached from the system, attach the device to the system and run 'zpool status' again. The pool should automatically detect the newly attached device and resume functioning. If the device is no longer available, it can be replaced using 'zpool replace': # zpool replace test c0t0d1 c0t0d2 If the device has been replaced by another disk in the same physical slot, then the device can be replaced using a single argument to the 'zpool replace' command: # zpool replace test c0t0d1 ZFS will begin migrating data to the new device as soon as the replace is issued. Once the resilvering completes, the original device (if different from the replacement) will be removed, and the pool will be restored to the ONLINE state. For an exported pool If this error is encountered while running 'zpool import', the pool can be still be imported despite the failure: # zpool import pool: test id: 5187963178597328409 state: DEGRADED status: One or more devices contains corrupted data. The fault tolerance of the pool may be compromised if imported. action: The pool can be imported using its name or numeric identifier. see: http://illumos.org/msg/ZFS-8000-4J config: test DEGRADED mirror DEGRADED c0t0d0 ONLINE c0t0d1 FAULTED corrupted data To import the pool, run 'zpool import': # zpool import test Once the pool has been imported, the damaged device can be replaced according to the above procedure. ErrorCriticalNo automated response will be taken.The pool is no longer availableA device could not be opened and no replicas are available. Refer to %s for more information. For an active pool If this error was encountered while running 'zpool import', please see the section below. Otherwise, run 'zpool status -x' to determine which pool has experienced a failure: # zpool status -x pool: test state: FAULTED status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. see: http://illumos.org/msg/ZFS-8000-3C scrub: none requested config: NAME STATE READ WRITE CKSUM test FAULTED 0 0 0 insufficient replicas c0t0d0 ONLINE 0 0 0 c0t0d1 FAULTED 0 0 0 cannot open errors: No known data errors If the device has been temporarily detached from the system, attach the device to the system and run 'zpool status' again. The pool should automatically detect the newly attached device and resume functioning. You may have to mount the filesystems in the pool explicitly using 'zfs mount -a'. If the device is no longer available and cannot be reattached to the system, then the pool must be destroyed and re-created from a backup source. For an exported pool If this error is encountered during a 'zpool import', it means that one of the devices is not attached to the system: # zpool import pool: test id: 10121266328238932306 state: FAULTED status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: http://illumos.org/msg/ZFS-8000-3C config: test FAULTED insufficient replicas c0t0d0 ONLINE c0t0d1 FAULTED cannot open The pool cannot be imported until the missing device is attached to the system. If the device has been made available in an alternate location, use the '-d' option to 'zpool import' to search for devices in a different directory. If the missing device is unavailable, then the pool cannot be imported. ErrorMajorA hot spare will be activated if available.The pool is no longer providing the configured level of replication.A device in a replicated configuration could not be opened. Refer to %s for more information. For an active pool If this error was encountered while running 'zpool import', please see the section below. Otherwise, run 'zpool status -x' to determine which pool has experienced a failure: # zpool status -x pool: test state: DEGRADED status: One or more devices could not be opened. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Attach the missing device and online it using 'zpool online'. see: http://illumos.org/msg/ZFS-8000-2Q scrub: none requested config: NAME STATE READ WRITE CKSUM test DEGRADED 0 0 0 mirror DEGRADED 0 0 0 c0t0d0 ONLINE 0 0 0 c0t0d1 FAULTED 0 0 0 cannot open errors: No known data errors Determine which device failed to open by looking for a FAULTED device with an additional 'cannot open' message. If this device has been inadvertently removed from the system, attach the device and bring it online with 'zpool online': # zpool online test c0t0d1 If the device is no longer available, the device can be replaced using the 'zpool replace' command: # zpool replace test c0t0d1 c0t0d2 If the device has been replaced by another disk in the same physical slot, then the device can be replaced using a single argument to the 'zpool replace' command: # zpool replace test c0t0d1 Existing data will be resilvered to the new device. Once the resilvering completes, the device will be removed from the pool. For an exported pool If this error is encountered during a 'zpool import', it means that one of the devices is not attached to the system: # zpool import pool: test id: 10121266328238932306 state: DEGRADED status: One or more devices are missing from the system. action: The pool can be imported despite missing or damaged devices. The fault tolerance of the pool may be compromised if imported. see: http://illumos.org/msg/ZFS-8000-2Q config: test DEGRADED mirror DEGRADED c0t0d0 ONLINE c0t0d1 FAULTED cannot open Unlike when the pool is active on the system, the device cannot be replaced while the pool is exported. If the device can be attached to the system, attach the device and run 'zpool import' again. Alternatively, the pool can be imported as-is, though it will be placed in the DEGRADED state due to a missing device. The device will be marked as UNAVAIL. Once the pool has been imported, the missing device can be replaced as described above. ErrorCriticalNo automated response will be taken.ZFS filesystems are not availableThe ZFS cache file is corrupted Refer to %s for more information. ZFS keeps a list of active pools on the filesystem to avoid having to scan all devices when the system is booted. If this file is corrupted, then normally active pools will not be automatically opened. The pools can be recovered using the 'zpool import' command: # zpool import pool: test id: 12743384782310107047 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: test ONLINE c0t0d0 ONLINE This will automatically scan /dev/dsk for any devices part of a pool. If devices have been made available in an alternate location, use the '-d' option to 'zpool import' to search for devices in a different directory. Once you have determined which pools are available for import, you can import the pool explicitly by specifying the name or numeric identifier: # zpool import test Alternately, you can import all available pools by specifying the '-a' option. Once a pool has been imported, the ZFS cache will be repaired so that the pool will appear normally in the future.