Elastic Compute Service
Elastic Compute Service
Elastic Compute Service
Document
Elastic Compute Service
What's New
Announcement
OpenAPI related
Pricing and quotas are related
About products and plugins
Feature discontinuation
Overview
Billing
Billable items
Billing methods
Billing methods change
Getting Started
User Guide
Instances
Instance types
X86 Computing
Elastic Bare Metal Server
Heterogeneous Computing
Select instance billing method
Spot instance
Elastic Scheduled Instance
Offsetting Resources
Reserved Instances
Buying ECS instances
Logging in to an instance
Logging in to a Linux instance
Managing instance status
Modifying instance types
Using instance user data and metadata
Instance metadata
Images
Public images
veLinux images
Custom images
Importing custom images
Creating custom images
Image detection
End of life (EOL) of image
Elastic Block Storage
Basic volume operations
Partitioning and formatting a volume
Extending a volume
EBS Agent
Snapshots
Basic snapshot operations
Auto snapshot policies
DataInsights
Network
Network interface and IP address
IP Address
IPv4 address
Security group
Security
Passwords and key pairs
Deployment and scaling
Monitoring
Monitoring metrics
Event monitoring
Local volume event O&M
Method 1: Solve the local volume failure by replacing the faulty volume
O&M
Cloud assistant
Managing agents
Process choreography
Common operation and maintenance tasks
Batch operations on instances
Batch operations on EBS Volumes
Batch operations on images
Temporary upgrade of bandwidth
Managing application updates
orchestration plan
Patch management
Managing patch plans
Managing patch baselines
IAM
Tags and projects
Best Practices
AI applications
OpenClaw (formerly Moltbot)
Quickly deploying OpenClaw via application templates
Quickly deploying OpenClaw via marketplace images
Manually deploying OpenClaw
Self-service website creation
Building environments
Building a Web environment (Windows)
Building applications
Building FTP site
Deploying databases
Building game servers
Building websites
Building a WordPress blog
Building multiple websites
Manage software sources for Linux instances
AIGC practices
Performance test
Network performance test
Instance configuration
Setting up AD Domain Services on Windows OS
Windows Multi - User Login
Changing screen resolution
Instance data
Uploading or downloading files
Data restoration
ECS instance local time synchronization
Volume
Monitoring
Security
Images
Kernel fine-tuning
O&M
Troubleshooting
Remote log in issue
Linux operating system issue
Windows operating system issue
SSH log in issue
Operating system issue
veLinux operating system issue
Linux operating system issue
Windows operating system issue
Instance status issue
Instance unable to start issue
High instance load issue
GPU instances issue
Network connection issue
Network configuration issue
Storage classes issue
EBS Volume issue
Local Disk issue
Logs and monitoring issue
Third - party software issue
API Reference
Regions and availability zones
Instances
Images
HPC clusters
Key pairs
Tags
Volumes
Reserved storage capacity
Snapshot
Auto snapshot policy
Monitoring
Deployment sets
Launch templates
Cloud assistant
Patch management
SDK reference
CLI Reference
FAQ
Dedicated Host DDH
What's New
Billing
User Guide
Manage Dedicated Host
Manage Dedicated Host Cluster
Manage ECS instances
Monitoring and O&M
API reference
proprietary host
- Documentation
Elastic Compute ServiceElastic Compute ServiceTroubleshootingStorage classes issueEBS Volume issueTroubleshooting unrecognition of volumes mounted to DPU instances with Ubuntu 16.04 and 18.04
Copy page
Download PDFEBS Volume issue
Troubleshooting unrecognition of volumes mounted to DPU instances with Ubuntu 16.04 and 18.04
Copy pageDownload PDFTroubleshooting unrecognition of volumes mounted to DPU instances with Ubuntu 16.04 and 18.04
Issue description
After you mount a volume on a DPU ECS instance running Ubuntu 16.04 or 18.04 (for example, General-purpose g3i/g3a, Compute-optimized c3i/c3a, and Memory-optimized r3i/r3a), the instance can not recognize the newly mounted volume.
Causes
This may be because the /etc/udev/rules.d/72-virtio.rules file and its configuration are missing from your operating system. As a result, the DPU-architecture instance fails to recognize the newly mounted volume.
Solutions
You need to create the /etc/udev/rules.d/72-virtio.rules file and configure it on the operating system.
- Execute the following command to confirm whether the /etc/udev/rules.d/72-virtio.rules file exists.
- find /etc/udev/rules.d/ -name "72-virtio.rules"
- If the output is displayed as follows, the /etc/udev/rules.d/72-virtio.rules file is missing from your operating system. Follow the subsequent steps to resolve the issue. Otherwise, we recommend that you submit a ticket to obtain technical support.
-
- Create the /etc/udev/rules.d/72-virtio.rules file.
- Execute the following command to create the /etc/udev/rules.d/72-virtio.rules file.
- touch /etc/udev/rules.d/72-virtio.rules
- Execute the following commands to modify the Virtio driver configurations.
- cat <<EOF > /etc/udev/rules.d/72-virtio.rulesACTION=="add" \, ATTRS{device}=="0x1042" \, ATTRS{vendor}=="0x1af4" \, SUBSYSTEM=="virtio" \, RUN+="/etc/initramfs-tools/scripts/init-premount/rebind.sh"ACTION=="add" \, ATTRS{device}=="0x1041" \, ATTRS{vendor}=="0x1af4" \, SUBSYSTEM=="virtio" \, RUN+="/etc/initramfs-tools/scripts/init-premount/rebind.sh"ACTION=="add" \, ATTRS{device}=="0x1001" \, ATTRS{vendor}=="0x1af4" \, SUBSYSTEM=="virtio" \, RUN+="/etc/initramfs-tools/scripts/init-premount/rebind.sh"ACTION=="add" \, ATTRS{device}=="0x1000" \, ATTRS{vendor}=="0x1af4" \, SUBSYSTEM=="virtio" \, RUN+="/etc/initramfs-tools/scripts/init-premount/rebind.sh"EOF
- Execute the lsblk command in the instance to verify whether the newly mounted volume is recognized as expected.
- If the following output is displayed, the newly mounted volume is recognized as expected.
-
Last updated: 2026.04.13 16:50:03
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
