Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Attaching a Shared Disk

Updated on 2024-10-10 GMT+08:00

Scenarios

Separately purchased shared EVS disks are data disks. In the disk list, the function of such a disk is displayed as Data disk, and the status is displayed as Available. In this case, you need to attach the shared data disk to servers for use.

Prerequisites

  • The shared disk status is In-use or Available.
  • The account is not in arrears.

Notes and Constraints

NOTICE:

If you simply attach a shared disk to multiple servers, files cannot be shared among them. Because there are no mutually agreed data read/write rules among servers, read and write operations from them may interfere with each other, or unpredictable errors may occur. To share files between servers, set up a shared file system or a clustered management system first.

  • A shared disk can be attached to a maximum of 16 servers. These servers and the shared disk must be in the same AZ within a region.
  • A shared, In-use disk can be attached to other servers only when the maximum number of servers that the disk can be attached to has not been reached.
  • All the servers attached with a shared disk must run either Windows or Linux.

    For example, if you attach a shared disk to multiple Windows servers and then detach it from these servers, the shared disk cannot be attached to Linux servers later. This is because Windows and Linux support different file systems and cannot identify the original file system on the disk. Improper operations may damage the original file system.

  • A shared disk can only be used as a data disk. It cannot be used as a system disk.
  • Cloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.
  • A shared disk can be attached only when the servers' statuses are Running or Stopped.
  • A frozen disk cannot be attached.
  • A detached, yearly/monthly system disk purchased together with a server can be re-attached and used as a data disk for any server. If you want to use it again as a system disk, you must attach it to the original server.
  • A detached, pay-per-use system disk purchased together with a server can be re-attached and used as a data disk for any server. If you want to use it again as a system disk, you must attach it to a server that uses the same image as the original server.

Attaching the Disk on the EVS Console

  1. Log in to the management console.
  2. Click in the upper left corner and choose Storage > Elastic Volume Service.

    The Elastic Volume Service page is displayed.

  3. Locate the target disk in the list and click Attach.

    Shared disks support batch attachment, so you can attach a shared disk to multiple servers. The left area in the Attach Disk dialog box shows the server list. After you select the target servers, the selected servers will be displayed in the right area.

  4. Select the target servers you want to attach the shared disk. Ensure that the disk and servers are in the same AZ. After you select the servers, Data disk is automatically entered as the disk function for each server.

    One device name can be used for one disk only. If a device name has been used, it will no longer be displayed in the drop-down list and cannot be selected.

    Figure 1 Attach Disk

  5. Click OK.

    A dialog box is displayed, showing "The attaching process is NOT completed yet. You must initialize the disk before using it."

  6. Click OK to return to the disk list page.

    The status of the disk is Attaching, indicating that the disk is being attached to the servers. When the disk status changes to In-use, the disk is successfully attached.

Attaching the Disk on the ECS Console

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Choose Compute > Elastic Cloud Server.
  4. In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID for search.
  5. Click the name of the target ECS.

    The page providing details about the ECS is displayed.

  6. Click the Disks tab. Then, click Attach Disk.

    The Attach Disk page is displayed.

  7. Select the target disk and specify it as the system disk or a data disk.
    • For Xen ECSs, you can specify a specific device name, such as /dev/sdb.
    • For KVM ECSs, you can specify the disk as the system disk or a data disk but cannot specify a specific device name.
    NOTE:
  8. Click OK.

    After the disk is attached, you can view the information about it on the Disks tab.

Follow-Up Operations

If you are attaching a new disk, you must then log in to the server and initialize the disk before it can be used. To learn how to initialize disks, see Initialization Overview.

Helpful Links

If your disk cannot be attached to a server, see Why Can't I Attach My Disk to a Server?

If the attached data disk is not showing up, see Why Can't I View the Attached Data Disk on the Server?

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback