Detach Volumes

Disconnect persistent storage volumes from instances while preserving all volume data. Detached volumes can be re-attached to the same or different instances.

Detachment Requirements

Before detaching a volume, ensure these conditions are met:

Volume Status

Must Be "Attached"

Currently connected to an instance

Not in "Available" status

Not in "Creating" status

Not in a transitional state (Attaching/Detaching)

Shows "Attached" badge on volume card

Volume Type

Must Be Non-Bootable

Cannot be OS/bootable volume

Volume details show "Bootable: No"

Was not created from OS image

Detach button is enabled (not grayed out)

OS/Bootable Volume Restriction:

Created from OS image (CANADA-1 only)

Bootable flag set to true

Permanent attachment — cannot be detached or moved to a different instance

Detach button disabled with tooltip

Instance Status

Must Be "SHUTOFF"

Instance is powered off

Not running (ACTIVE)

Not creating, hibernated, or suspended

Not terminated

Shut down instance before detachment

How to Shut Down:

Go to instances page

Click shutdown/stop button

Wait for SHUTOFF status

Return to volumes page

Additional Requirements:

Volume and instance must be in the same tier (Advanced or Legacy)

Volume and instance must be in the same region

Instance currency must match your current currency preference

Maximum 10 volumes can be detached in a single API request

No duplicate volume IDs in a single request

Detaching a Volume

Verify & Prepare

Check Volume Type:

Navigate to barrack.ai/volumes

Use region dropdown to filter volumes

Locate the attached volume

Verify volume details show "Bootable: No"

If "Bootable: Yes", volume cannot be detached

Verify Instance Status:

Check instance status displayed on volume card

Status must show SHUTOFF

If not SHUTOFF, shut down the instance:

Go to barrack.ai/instances

Click shutdown/stop button on instance card

Wait for status to change to SHUTOFF

Return to volumes page

Confirm Before Proceeding:

Volume is non-bootable (can be detached)

Instance is in SHUTOFF state

Detach button is enabled on volume card

Detach Volume

Click the Detach button on the volume card

Confirmation Modal Appears:

Shows volume name

Displays warning about potential application disruption

Shows instance status validation

If Instance Not SHUTOFF:

Error message displays:

"VM must be in SHUTOFF state for volume detachment (current state: {status})"

If Instance Is SHUTOFF:

Click the Detach button in the modal to confirm

Processing:

Request sent to backend

Volume disconnected from instance

Typically completes in 5-10 seconds

Success notification appears

Verify Detachment

Volume Card Updates:

Status changes from "Attached" to "Available"

Instance name and ID are removed

Detach button changes to Attach button

Delete button becomes enabled

Volume Details Updates:

"Attached to" field is cleared

Status shows "Available"

Data Preservation:

All data on volume is preserved

No data loss occurs during detachment

Filesystem and files remain unchanged

Volume can be re-attached with data intact

Post-Detachment Status

After successful detachment, these changes occur:

Volume Changes

Status Updates:

Status badge changes from "Attached" to "Available"

Instance information removed from volume card

"Attached to" field cleared in volume details

Button Changes:

Detach button is hidden

Attach button appears

Delete button becomes enabled

Clone/Resize buttons remain available (advanced tier only)

Data Preservation:

All data on volume is preserved

No data loss during detachment

Volume can be re-attached to same or different instance

Data immediately accessible after re-attachment

Instance Impact

Instance State:

Instance remains in SHUTOFF state

Instance can be started without detached volume

Boot process unaffected (unless it was an OS volume)

Application Impact:

Applications configured to use the detached volume will:

Fail to start if volume mount is missing

Show errors when accessing volume mount point

Require reconfiguration to use different storage

Need volume re-attachment to function normally

Configuration Updates Needed:

If starting instance without the volume:

Remove volume mount from /etc/fstab

Update application configurations

Remove volume-dependent services

Verify applications still function correctly

Billing Impact

No Change in Billing:

Volume billing continues at the same rate

Detachment does not affect billing charges

Credits deducted hourly based on volume size and type

Same rate whether attached or available

Troubleshooting

OS/Bootable volumes cannot be detached

Instance must be SHUTOFF to detach volumes

Volume is not attached to this VM

Volume detachment or attachment already in progress

Instance not available in current currency context

VM and volumes must be from the same tier

VM and volumes must be in the same region

Detach button is disabled

Detachment fails after confirmation

Instance status showing wrong state

Common Errors

For authentication, credits, profile, and session errors, see Common Volume Errors.

Instance State Reference

Understanding instance states is critical for successful volume detachment:

SHUTOFF (Required)

ACTIVE (Invalid)

CREATING (Invalid)

HIBERNATED (Invalid)

TERMINATED (Invalid)

Description: Instance is powered off and not consuming compute resources

Volume Operations:

✅ Detach volumes allowed (non-OS volumes only)

✅ Attach volumes allowed

How to Achieve:

Navigate to instances page

Click shutdown/stop button on instance card

Wait for status to change to SHUTOFF

Verification: Instance card shows "SHUTOFF" status badge

Next Steps

After detaching volumes:

Verify Detachment

Confirm successful detachment:

Volume status shows "Available"

Instance information removed from volume card

Attach button is displayed

Decide Next Action

Choose based on your needs:

Attach volume to a different instance

Delete volume if no longer needed

Keep volume available for future use

Clone or resize volume (advanced tier only)

Update Instance Configuration

If starting instance without the volume:

Remove volume mount from /etc/fstab

Update application configurations

Remove volume-dependent services

Verify applications still function correctly

Support

Email Support

Detachment Issues Help

Contact for:

Detachment errors

Instance state problems

OS/bootable volume questions

Include: volume ID and name, instance ID and name, error messages, request ID, screenshots

Delete Volumes

Volume Deletion Guide

Learn how to:

Delete detached volumes

Verify volume requirements

Understand billing impact

Troubleshoot deletion errors

Detachment Requirements#

Detaching a Volume#

Post-Detachment Status#

Volume Changes#

Instance Impact#

Billing Impact#

Troubleshooting#

Common Errors#

Instance State Reference#

Next Steps#

Support#