# Unattached Block Volume (Non-Boot)

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/unattached-block-volume-non-boot

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Unattached Block Volume (Non-Boot)

## Explanation

Block volumes that are not attached to any instance continue to incur charges. These often accumulate after instance deletion or reconfiguration. Unlike boot volumes, unattached data volumes may be harder to track if not labeled or tagged clearly.

## Relevant Billing Model

Charged per GB provisioned, regardless of attachment or usage state.

## Detection

- Lifecycle state is "AVAILABLE"

- No attached instance (attached-instance-id is null or missing)

## Remediation

- Delete unattached boot volumes that are no longer needed

- Establish lifecycle policies or instance termination settings that automatically delete boot volumes unless explicitly retained

- Periodically audit the Block Volumes service for orphaned resources

## Relevant Documentation

[Managing Block Volumes](https://docs.oracle.com/en-us/iaas/Content/Block/Tasks/managingvolumes.htm)

[Submit Feedback](https://hub.pointfive.co/inefficiencies/unattached-block-volume-non-boot)

## At a glance

Reference

CER-0208

Cloud provider

OCI

Service

OCI Block Volume

Category

[Storage](https://www.pointfive.co/efficiency-hub/service-category/storage)

Inefficiency type

Orphaned Storage Resource

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.