By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Issue with Force Detaching an AWS Volume

0

Hi everyone,

I'm facing a challenge with an AWS volume that refuses to detach, and I'm hoping someone here might have some insight or suggestions on how to resolve this issue.

Issue: I have a volume in AWS that I've been trying to detach from us-east-1a. Initially, when the standard detachment process didn't work, I attempted to force detach the volume, but it's still stuck and shows no signs of detaching.

What I've Tried:

  1. Detaching the volume through the AWS Management Console.
  2. Force detaching when the standard detachment didn't work.
  3. Checked for any ongoing snapshots or processes that might interfere.

The volume remains in the 'attached' state, with no error messages or updates. Just a spinning animation.

I haven't made any recent changes to the instance or the volume settings that might lead to this. Is there something I'm overlooking, or is there another method to force the detachment of a volume in AWS?

Any advice, insights, or steps that I can take to troubleshoot this issue would be greatly appreciated!

Thanks in advance for your help!

Best, Happy holidays!

Topics
ComputeManagement & Governance
Tags
Amazon EC2AWS Account Management
Language
English
yak
asked 4 months ago185 views
1 Answer
0

Hello.

You may want to try the troubleshooting methods described in the documentation below.
https://repost.aws/knowledge-center/ebs-stuck-attaching

Note: The instance must be in the running state.

If the previous steps to troubleshoot the issue don't resolve the issue or if you must use a device name that isn't working, complete these steps:

  • Reboot the instance.
  • Stop and start the instance to migrate the instance to new underlying hardware.
  • If the issue persists after you start and stop the instance, create a Support case.
profile picture
EXPERT
Riku_Kobayashi
answered 4 months ago
profile pictureAWS
EXPERT
Didier_Durand
reviewed 4 months ago
  • yak
    4 months ago

    Hello,

    Thank you for your response and the helpful link. I'd like to add an important detail: the volume in question is quite old, having been created on Thu May 16, 2013, at 09:02:59 GMT-0300. Despite being marked as "in-use," it's not actually attached to any instance. It appears to be stuck in the "in-use" state without being associated with any specific instance.

    I've tried standard troubleshooting steps as suggested in the AWS documentation. However, the volume's status hasn't changed, and it remains in this erroneous "in-use" state and detaching doesn't work.

    Given its age and the unusual nature of this issue, I'm wondering if there might be some legacy factors at play here. I wanted to see if anyone in the community has faced a similar situation, especially with older volumes, and found a workaround or solution.

    Any further insights or suggestions would be greatly appreciated.

    Thanks again for your help!

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content