Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/compute/docs/disks/attach-disks below:

Attach a non-boot disk to a VM | Compute Engine Documentation

Stay organized with collections Save and categorize content based on your preferences.

This page explains how to attach an existing non-boot disk to one or more virtual machine (VM) instances.

To create or change a VM's boot disk, see Create a boot disk and Detach and reattach a boot disk, respectively.

To create a new disk, see Create a new Persistent Disk volume and Create a new Hyperdisk volume.

To get the permissions that you need to attach a disk to a VM, ask your administrator to grant you the following IAM roles on the project:

• Compute Instance Admin (v1) (roles/compute.instanceAdmin.v1)
• To connect to a VM instance that can run as a service account: Service Account User (v1) (roles/iam.serviceAccountUser role)

For more information about granting roles, see Manage access to projects, folders, and organizations.

These predefined roles contain the permissions required to attach a disk to a VM. To see the exact permissions that are required, expand the Required permissions section:

The following permissions are required to attach a disk to a VM:

• To attach a disk to a VM:
  • compute.instances.attachDisk on the VM
  • compute.instances.attachDisk on the VM
  • compute.disks.use on the disk that you want to attach to the VM
• To format and mount the attached volume: compute.instances.setMetadata on the VM

You might also be able to get these permissions with custom roles or other predefined roles.

When you attach a disk to a VM, you indicate how the VM can access the data on the disk by specifying the disk attachment mode. You can choose read-only or read-write mode.

The default mode is read-write.

You can share the same disk between VMs so that each VM can simultaneously access the disk by attaching the disk to each VM. You can attach a disk to multiple VMs if the disk's type and the VM's machine type support it.

To attach a disk to multiple VMs, follow the procedure in Attach a non-boot disk to your VM for each VM.

You must use the same disk attachment mode for all VMs that you attach the disk to. For example, you can't attach a disk to one VM in read-write mode and attach it at the same time to another VM in read-only mode.

For information about attaching a disk to multiple VMs, including the supported disk types, see Share a disk between VMs.

To attach a Hyperdisk volume to multiple VMs, make sure the disk's access mode is set to an appropriate value for your use case. For instructions on setting the access mode, see set the disk's access mode.

When you attach a Hyperdisk volume to a VM, you must choose a disk attachment mode that doesn't conflict with the disk's access mode. For example, you can't use read-only attachment mode with a disk that's in single-writer or multi-writer mode.

When attaching a disk to a VM, be aware of the following limitations:

• You can attach up to 127 secondary, non-boot, zonal disks to a VM.

• You can't attach a disk to a VM if doing so will exceed the Hyperdisk size and attachment limits.

• The following disk types don't support read-only mode:

  • Hyperdisk Balanced
  • Hyperdisk Balanced High Availability
  • Hyperdisk Throughput
  • Hyperdisk Extreme

• When you attach a disk to multiple VMs, you must use the same disk attachment mode for all the VMs.

• When you attach a disk to multiple VMs, additional restrictions apply. See the restrictions for sharing a disk between VMs in read-only mode and multi-writer mode.

• Disks attached to multiple VMs don't support auto-delete, that is, they can't be automatically deleted when the VM is deleted.

You can attach a non-boot zonal disk to a VM by using the Google Cloud console, the Google Cloud CLI, or REST.

When attaching a disk to a VM, keep the following points in mind:

• Use a custom device name: Google recommends that you specify a custom device name when attaching a disk to a VM. The name you specify is used to generate a symlink for the disk in the guest OS, which makes it easier to identify and manage disks on the VM.

  Caution: If you add a custom device name to a disk after you attach the disk to a VM, Compute Engine temporarily detaches the disk from the VM, which might disrupt your workloads.

• Attaching a disk to multiple VMs: To attach a disk to multiple VMs, repeat the procedure in this section for each VM. You must use the same disk attachment mode for all VMs that you attach the disk to.

To attach a Regional Persistent Disk or Hyperdisk Balanced High Availability volume to your VM, see instead Attach a regional disk to your VM.

1. Go to the VM instances page.

   Go to the VM instances page

2. Click the name of the VM where you want to add a disk.

3. On the details page, click Edit.

4. In the Storage section, under Additional disks, click + Attach existing disk.

5. In the Disk list, select the disk you want to attach. If the disk isn't listed, make sure it's in the same location as the VM. This means the same zone for a zonal disk and the same region for a regional disk.

6. For Disk attachment mode, select Read-only to only allow the VM to read from the disk. To allow the VM read-write access, select Read/write.

7. Under Deletion rule, specify whether to delete the disk when the VM is deleted. To keep the disk when the VM is deleted, select Keep disk. To delete the disk when the VM is deleted, select Delete disk. If you're attaching the disk to multiple VMs, you must select Keep disk.

8. Optional: Under the heading Device name, select the option Use a custom device name. The name you enter is used to generate a symlink for the disk, which makes disk identification easier.

9. To apply the changes to the disk, click Done.

10. Click Save to apply your changes and attach the disk to the VM.

To attach a disk to a VM, use the gcloud compute instances attach-disk command. Use the mode flag to specify the disk attachment mode.

gcloud compute instances attach-disk VM_NAME \
    --disk DISK_NAME --device-name=DEVICE_NAME
    --mode DISK_ATTACHMENT_MODE

Replace the following:

• VM_NAME: the name of the VM where you are adding the new zonal persistent disk
• DISK_NAME: the name of the new disk that you are attaching to the VM.
• DEVICE_NAME: Optional: a name that the guest OS uses to identify the disk.
• DISK_ATTACHMENT_MODE: Optional: how to attach the disk to the VM. For read-only mode, set to ro. For read-write mode, set to rw, or omit this flag because rw is the default.

To attach the disk to a VM, use the google_compute_instance resource.

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.

To attach a disk to a VM, construct a POST request to the compute.instances.attachDisk method, and include the URL to the disk that you want to attach.

To specify the disk attachment mode, use the mode parameter.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances/VM_NAME/attachDisk

{
   "source": "/compute/v1/projects/PROJECT_ID/zones/ZONE/disks/DISK_NAME",
   "deviceName": DEVICE_NAME,
   "mode" : "DISK_ATTACHMENT_MODE"
}

Replace the following:

• PROJECT_ID: your project ID
• ZONE: the zone where the VM and disk are located
• VM_NAME: the name of the VM that you want to attach the disk to
• DISK_NAME: the name of the disk to attach
• DEVICE_NAME: Optional: a name that the guest OS uses to create a symlink, which helps identify the disk.
• DISK_ATTACHMENT_MODE: Optional: how the disk should be attached to the VM. For read-only mode, use READ_ONLY. For read-write mode, set to READ_WRITE, or omit because READ_WRITE is the default.

After you attach a disk to a VM, connect to the VM and enable the VM's operating system (OS) to use the disk:

• If you attached a blank disk, format and mount the disk
• If you attached a non-empty disk, mount the disk

Learn how to format and mount your new disks on Linux or Windows VMs.

• Prevent data loss by regularly backing up your disks with snapshots
• Use regional persistent disks for synchronous replication between two zones.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-02 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-02 UTC."],[[["This guide outlines the process of attaching an existing non-boot disk to one or multiple virtual machine (VM) instances, providing instructions for using the Google Cloud console, gcloud CLI, Terraform, and REST."],["When attaching a disk, you can specify the disk attachment mode as either read-only or read-write, and you must use the same mode for all VMs if the disk is shared among multiple instances."],["To successfully attach a disk to a VM, you need specific IAM permissions, including `compute.instances.attachDisk` on the VM and `compute.disks.use` on the disk."],["You can share a disk among multiple VMs, provided that the disk type and the VM's machine type support it, and that you select the correct access mode for Hyperdisks."],["There are limitations to be aware of when attaching disks, such as a maximum of 127 secondary disks per VM, and certain disk types do not support read-only mode."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4