Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
  3. Troubleshooting
  4. Multiple error messages might be displayed during the first boot after the restoration of a client with ZFS storage pools
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

Multiple error messages might be displayed during the first boot after the restoration of a client with ZFS storage pools

During the first boot after the restoration of a client with ZFS storage pools, multiple error messages might be displayed. The following is an example:

SUNW-MSG-ID: ZFS-8000-D3, TYPE: Fault, VER: 1, SEVERITY: Major
EVENT-TIME: Mon May 23 13:10:09 CDT 2011
PLATFORM: SUNW,Sun-Fire-V215, CSN: -, HOSTNAME: bmrsol101.vxindia.veritas.com
SOURCE: zfs-diagnosis, REV: 1.0
EVENT-ID: c257eb38-495e-cdb6-9a52-a4d9c2ae38be
DESC: A ZFS device failed.  Refer to http://sun.com/msg/ZFS-8000-D3 for more information.
AUTO-RESPONSE: No automated response will occur.
IMPACT: Fault tolerance of the pool may be compromised.
REC-ACTION: Run 'zpool status -x' and replace the bad device.

For each disk in the computer you may see the error message. However, when you log on and run the zpool status -x command, you see the following message:

all pools are healthy

That is because of the ZFS import operation that is done during the first boot sequence. Bare Metal Restore (BMR) restores storage pools and contents in the BMR restoration environment and later imports to the client environment during first boot. That can cause an error message or a warning message during the first boot operation.

These messages only occur during the first boot operation and you can safely ignore them.

Feedback

Was this page helpful?
Previous

The /boot partition must be on a separate partition for a multiple device-based OS configuration

Next

BMR may not format or clear the ZFS metadata

Feedback

Was this page helpful?