Stay organized with collectionsSave and categorize content based on your preferences.
AutopilotStandard
This page describes storage-related errors you might experience when using
Backup for GKE, things to consider when performing the action, and steps on
how to troubleshoot the issue.
Error 100010105: Failed to backup PersistentVolumeClaim - Disk referenced by PersistentVolume does not exist
Error100010105occurs when an attempt to back up aPersistentVolumeClaimfails because it references a disk that doesn't exist, resulting in an error
message statingFailed to backup PersistentVolumeClaim - Disk referenced by PersistentVolume does not exist.
In Google Kubernetes Engine,PersistentVolumeClaimsrequest storage fromPersistentVolumes. APersistentVolume, in turn, represents a piece of
storage, often an underlying Compute Engine Persistent Disk. An error can occur
when aPersistentVolumeClaimis bound to aPersistentVolumeand thePersistentVolume's configuration specifies a
Compute Engine Persistent Disk. However, the actual disk with the name and
location specified in thePersistentVolumeconfiguration cannot be found in
your Google Cloud project. Thus, Backup for GKE cannot proceed with backing up
a non-existent disk, and a failure occurs.
To resolve this error, use the following instructions:
Identify the problematicPersistentVolumeClaimandPersistentVolume.
The names of both the problematicPersistentVolumeClaimand its associatedPersistentVolumeare listed in thestate reasonfield of your failed
Backup for GKE operation. We recommend documenting both thePersistentVolumeClaimname, its namespace, and the name of thePersistentVolume.
Inspect thePersistentVolume. To describe thePersistentVolume, use thePersistentVolumename you identified from the state reason field in the
following command:
kubectldescribepvPERSISTENTVOLUME_NAME
ReplacePERSISTENTVOLUME_NAMEwith the name of your
PersistentVolume.
In the output, examine thesourcesection, specifically undercsi. This
section describes theVolumeHandlethat thePersistentVolumeis trying to
reference. For example:
Source:
Type: GCEPersistentDisk (a Persistent Disk resource in Google Compute Engine)
PDName: my-non-existent-disk
FSType: ext4
Partition: 0
ReadOnly: false
In this example, the PD name is my-non-existent-disk.
Source:
Type: CSI (a Container Storage Interface (CSI) volume)
Driver: pd.csi.storage.gke.io
VolumeHandle: projects/PROJECT_ID/zones/ZONE/disks/DISK_NAME...
In this example, theVolumeHandlecontains the full path to the disk,
including its name and location. For example,projects/my-gcp-project/zones/us-central1-a/disks/my-disk-name.
Use theVolumeHandleobtained from thePersistentVolumedescription to
identify the disk name and zone.
Verify that the disk exists in your Google Cloud project by using one of the
following methods:
Zonal disk
If you're using a zonal disk, use Google Cloud CLI to run thegcloud compute disks describecommand:
DISK_NAME: the name of the disk you obtained
from thePersistentVolumedescription.
REGION_NAME: the region of the disk you obtained from
thePersistentVolumedescription.
PROJECT_ID: your Google Cloud project ID.
If you get aResource not foundorThe resourceDISK_NAMEwas not founderror message,
the disk doesn't exist. Use one of the following methods
to resolve the issue depending on the scenario that best fits your needs:
If the disk was accidentally deleted or misnamed and you want to keep the
data orPersistentVolumeClaim, or thePersistentVolumewas configured
with an incorrect disk name, use one of the following methods to resolve
the issue:
Restore the disk: if you have a backup of the disk, restore it with
the exact same name and location that thePersistentVolumereferences.
Create a new disk: if restoring the disk isn't an option, create a
new disk with the same name and location that's in thePersistentVolumeconfiguration.
If thePersistentVolumeClaimorPersistentVolume, their data, or the
application are no longer needed, we recommend removing the unneeded entity:
Delete thePersistentVolumeClaim: delete thePersistentVolumeClaimby using thekubectlcommand-line tool to run
thekubectl delete pvccommand:
kubectldeletepvcPVC_NAME-nNAMESPACE
Replace the following:
PVC_NAME: the name of thePersistentVolumeClaimyou want to delete.
NAMESPACE: the namespace of thePersistentVolumeClaimyou want to delete.
ThePersistentVolumeis still present after you delete thePersistentVolumeClaim:
if thePersistentVolume'sPersistentVolumeReclaimPolicyis set toDelete, thePersistentVolumeis automatically deleted when thePersistentVolumeClaimis deleted. If thepersistentVolumeReclaimPolicyis set toRetain, you need to manually delete thePersistentVolumeafter thePersistentVolumeClaimis deleted. To delete thePersistentVolume, use thekubectlcommand-line tool to run thekubectl delete pvcommand:
kubectldeletepvPV_NAME
ReplacePV_NAMEwith the name of thePersistentVolumeyou want to delete.
If the operation continues to fail, contact Cloud Customer Care for further
assistance.
[[["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-09-04 UTC."],[],[],null,["# Troubleshoot storage errors in Backup for GKE\n\nAutopilot Standard\n\n*** ** * ** ***\n\nThis page describes storage-related errors you might experience when using\nBackup for GKE, things to consider when performing the action, and steps on\nhow to troubleshoot the issue.\n\nError 100010105: Failed to backup PersistentVolumeClaim - Disk referenced by PersistentVolume does not exist\n------------------------------------------------------------------------------------------------------------\n\nError `100010105` occurs when an attempt to back up a `PersistentVolumeClaim`\nfails because it references a disk that doesn't exist, resulting in an error\nmessage stating `Failed to backup PersistentVolumeClaim - Disk referenced by PersistentVolume does not exist`.\n\nIn Google Kubernetes Engine, `PersistentVolumeClaims` request storage from\n`PersistentVolumes`. A `PersistentVolume`, in turn, represents a piece of\nstorage, often an underlying Compute Engine Persistent Disk. An error can occur\nwhen a `PersistentVolumeClaim` is bound to a\n`PersistentVolume` and the `PersistentVolume`'s configuration specifies a\nCompute Engine Persistent Disk. However, the actual disk with the name and\nlocation specified in the `PersistentVolume` configuration cannot be found in\nyour Google Cloud project. Thus, Backup for GKE cannot proceed with backing up\na non-existent disk, and a failure occurs.\n\nTo resolve this error, use the following instructions:\n\n1. Identify the problematic `PersistentVolumeClaim` and `PersistentVolume`.\n The names of both the problematic `PersistentVolumeClaim` and its associated\n `PersistentVolume` are listed in the `state reason` field of your failed\n Backup for GKE operation. We recommend documenting both the\n `PersistentVolumeClaim` name, its namespace, and the name of the\n `PersistentVolume`.\n\n2. Inspect the `PersistentVolume`. To describe the `PersistentVolume`, use the\n `PersistentVolume` name you identified from the state reason field in the\n following command:\n\n kubectl describe pv \u003cvar translate=\"no\"\u003ePERSISTENTVOLUME_NAME\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003ePERSISTENTVOLUME_NAME\u003c/var\u003e with the name of your\n PersistentVolume.\n3. In the output, examine the `source` section, specifically under `csi`. This\n section describes the `VolumeHandle` that the `PersistentVolume` is trying to\n reference. For example:\n\n Source:\n Type: GCEPersistentDisk (a Persistent Disk resource in Google Compute Engine)\n PDName: my-non-existent-disk\n FSType: ext4\n Partition: 0\n ReadOnly: false\n In this example, the PD name is my-non-existent-disk.\n\n Source:\n Type: CSI (a Container Storage Interface (CSI) volume)\n Driver: pd.csi.storage.gke.io\n VolumeHandle: projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/zones/\u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e/disks/\u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e\n ...\n\n In this example, the `VolumeHandle` contains the full path to the disk,\n including its name and location. For example,\n `projects/my-gcp-project/zones/us-central1-a/disks/my-disk-name`.\n4. Use the `VolumeHandle` obtained from the `PersistentVolume` description to\n identify the disk name and zone.\n\n5. Verify that the disk exists in your Google Cloud project by using one of the\n following methods:\n\n ### Zonal disk\n\n If you're using a zonal disk, use Google Cloud CLI to run the\n `gcloud compute disks describe` command: \n\n gcloud compute disks describe \u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e \\\n --zone=\u003cvar translate=\"no\"\u003eZONE_NAME\u003c/var\u003e \\\n --project=\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e: the name of the disk you obtained\n from the `PersistentVolume` description.\n\n - \u003cvar translate=\"no\"\u003eZONE_NAME\u003c/var\u003e: the zone of the disk you obtained from\n the `PersistentVolume` description.\n\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your Google Cloud project ID.\n\n ### Regional disk\n\n If you're using a regional disk, use Google Cloud CLI to run the\n `gcloud compute disks describe` command: \n\n gcloud compute disks describe \u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003eREGION_NAME\u003c/var\u003e \\\n --project=\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e: the name of the disk you obtained\n from the `PersistentVolume` description.\n\n - \u003cvar translate=\"no\"\u003eREGION_NAME\u003c/var\u003e: the region of the disk you obtained from\n the `PersistentVolume` description.\n\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your Google Cloud project ID.\n\n If you get a `Resource not found` or\n `The resource `\u003cvar translate=\"no\"\u003eDISK_NAME\u003c/var\u003e` was not found` error message,\n the disk doesn't exist. Use one of the following methods\n to resolve the issue depending on the scenario that best fits your needs:\n - If the disk was accidentally deleted or misnamed and you want to keep the\n data or `PersistentVolumeClaim`, or the `PersistentVolume` was configured\n with an incorrect disk name, use one of the following methods to resolve\n the issue:\n\n - **Restore the disk** : if you have a backup of the disk, restore it with\n the exact same name and location that the `PersistentVolume` references.\n\n - **Create a new disk** : if restoring the disk isn't an option, create a\n new disk with the same name and location that's in the `PersistentVolume`\n configuration.\n\n - If the `PersistentVolumeClaim` or `PersistentVolume`, their data, or the\n application are no longer needed, we recommend removing the unneeded entity:\n\n - **Delete the `PersistentVolumeClaim`** : delete the `PersistentVolumeClaim` by using the `kubectl` command-line tool to run the `kubectl delete pvc` command:\n\n kubectl delete pvc \u003cvar translate=\"no\"\u003ePVC_NAME\u003c/var\u003e -n \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePVC_NAME\u003c/var\u003e: the name of the\n `PersistentVolumeClaim` you want to delete.\n\n - \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e: the namespace of the\n `PersistentVolumeClaim` you want to delete.\n\n - **The `PersistentVolume` is still present after you delete the `PersistentVolumeClaim`** :\n if the `PersistentVolume`'s `PersistentVolumeReclaimPolicy` is set to\n `Delete`, the `PersistentVolume` is automatically deleted when the\n `PersistentVolumeClaim` is deleted. If the `persistentVolumeReclaimPolicy`\n is set to `Retain`, you need to manually delete the `PersistentVolume`\n after the `PersistentVolumeClaim` is deleted. To delete the\n `PersistentVolume`, use the `kubectl` command-line tool to run the\n `kubectl delete pv` command:\n\n kubectl delete pv \u003cvar translate=\"no\"\u003ePV_NAME\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003ePV_NAME\u003c/var\u003e with the name of the\n `PersistentVolume` you want to delete.\n\n| **Important:** If the `reclaimPolicy` is set to `Retain` and the underlying disk exists, deleting the `PersistentVolume` doesn't delete the disk. You must manually delete the disk from Google Cloud if it's truly no longer needed.\n\nIf the operation continues to fail, contact Cloud Customer Care for further\nassistance.\n\n- [Read the Backup for GKE error codes overview page](/kubernetes-engine/docs/add-on/backup-for-gke/troubleshoot/backup-error-codes)."]]
