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. First boot after BMR restore fails on UNIX platforms
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

First boot after BMR restore fails on UNIX platforms

After BMR restore, first boot may fail at Grub if root disk that is originally mirrored across two disks is changed to concatenate layout. In the system setup, root disk was mirrored across 2 disks say c3t0d0 and c4t0d0. In BIOS settings, c3t0d0 is the first disk in boot sequence. During DDR configuration, root disk is changed from mirror to concatenate and mapped on c4t0d0. In BIOS, this disk is the second disk in boot sequence. So, after BMR restore, when system boots for the first time, as c3t0d0 is the first disk in boot sequence AND as "grub signature is still present on this disk as it was mirrored earlier", system tries to boot from the grub on c3t0d0 and then fails to boot as it does not get root file system and other bootable files which are now on c4t0d0.

After BMR restore, during system boot, change the BIOS settings and choose the correct disk for system to boot.

Feedback

Was this page helpful?
Previous

How to recover client when BMR configuration is deleted accidentally

Next

Client network based boot issue

Feedback

Was this page helpful?