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
On this page

Initialization Overview

Updated on 2025-01-02 GMT+08:00

After you attach a new data disk to a server, you must initialize the disk including creating partitions, creating file systems, and mounting the partitions before you can use the disk.

Scenario

  • System disk

    When a server is created, a system disk is automatically initialized with master boot record (MBR).

  • New data disk
    • If a data disk is created together with a server, EVS automatically attaches it to the server. You only need to initialize it to make it available for use.
    • If a data disk is created explicitly, you need to first attach it to a server and then initialize it.

    For detailed operation instructions, see Table 1.

  • Existing data disk
    An existing data disk is a disk created from a snapshot, a backup, or an image, or a disk detached from another server.
    • You can choose not to initialize the disk and use the disk existing partitions.
    • You can also re-initialize the data disk.

      Re-partitioning a disk will erase all the existing data on the disk, so you are advised to use snapshots to back up the disk data first.

      • In Linux, unmount the partitions, delete them (by running fdisk Disk name, entering d and the partition number, and entering w), and then re-initialize the disk.
      • In Windows, delete the partitions (using the volume deletion tool) and then re-initialize the disk.

      For detailed initialization operations, see Table 1.

      NOTE:

      Initializing a disk does not delete the snapshots created for the disk, so you can still use snapshots to roll back data to the source disk after the disk is initialized.

Operation Instructions

Table 1 Disk initialization instructions

Disk Capacity

Partition Style

Partition Type

Operating System

Reference

Capacity ≤ 2 TiB

GPT/MBR

  • GPT partitions are not classified, and there is no limit on the number of GPT partitions.
  • MBR partitions can be:
    • Four primary partitions
    • Three primary partitions and one extended partition

      The number of logical partitions allowed in the extended partition is not limited, so theoretically you can create as many logical partitions as you want.

    If you need five or more partitions, use the "primary partitions + one extended partition" model and then create logical partitions in the extended partition.

Linux

Initializing a Linux Data Disk (Less Than or Equal to 2 TiB)

Windows

Initializing a Windows Data Disk

Capacity > 2 TiB

GPT

GPT partitions are not classified, and there is no limit on the number of GPT partitions.

Linux

Initializing a Linux Data Disk (Greater Than 2 TiB)

Windows

Initializing a Windows Data Disk

NOTICE:
  • The maximum disk size that MBR supports is 2 TiB, and that GPT supports is 18 EiB. If your disk is greater than 2 TiB or you may expand it to over 2 TiB later, use GPT when initializing disks.
  • If you change the partition style of a disk, data on the disk will be erased. Select an appropriate partition style when initializing disks.
  • In Linux, you can use either fdisk or parted to create MBR partitions, and use only parted to create GPT partitions.

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