- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Re: Deployment problem 4.1.0 new cluster, Step 8 o...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2022 08:51 AM - last edited on 05-31-2022 06:06 PM by support_s
05-31-2022 08:51 AM - last edited on 05-31-2022 06:06 PM by support_s
Hi
We have problem to deploy a new cluster 4.1.0, it's stopp/error on step 8
Step 8 of 43: ERR_HVI.COPY.VC.FAILED: Unable to copy the Virtual Controller to the datastore. - Conversion failed
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2022 09:51 AM
05-31-2022 09:51 AM
Query: Deployment problem 4.1.0 new cluster, Step 8 of 43: https://hpe.to/6603zpukZ.FAILED
System recommended content:
1. HPE OmniStack 4.1.1U1 for vSphere Deployment Guide
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2022 10:53 AM
05-31-2022 10:53 AM
SolutionHello @YungChiang
One thing that usually causes a deployment to fail at step 8 is not having a clean RAID set before starting the deployment. I don't have details of your nodes but if they are Proliants you need to make sure to delete both the front and back RAID sets and only recreate the rear RAID set again before starting the deployment (RAID 1).
Also, make sure the tiny image .img file is always mounted during the process of deployment (if you are doing it via network attaching the image) or the USB drive always connected to the host.
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2022 06:03 PM
05-31-2022 06:03 PM
Re: Deployment problem 4.1.0 new cluster, Step 8 of 43: ERR_HVI.COPY.VC.FAILED
Hi
Deployment passed, thank you for reminding.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2022 09:16 PM
05-31-2022 09:16 PM
Re: Deployment problem 4.1.0 new cluster, Step 8 of 43: ERR_HVI.COPY.VC.FAILED
Hello @YungChiang,
Awesome! Glad to know the problem has been resolved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2022 09:16 PM
05-31-2022 09:16 PM
Re: Deployment problem 4.1.0 new cluster, Step 8 of 43: ERR_HVI.COPY.VC.FAILED
Hello @YungChiang,
Awesome! Glad to know the problem has been resolved.