Latest
Open
RNA-Seq
ChIP-Seq
SNP
Assembly
Forum
Planet
All »
Home
Log In
Question: CloudLaunch can't attach an instance to my volume after I increased the disk size
0
gravatar for marp.p
11 months ago by
marp.p • 20
marp.p • 20 wrote:

Hi,

I'm working with a local Galaxy (v. 17.05) in EC2, managed by CloudLaunch. I increased the size of the disk (by clicking "Grow" in the CloudMan console) and the process seemed to go well, so once finished, I terminated the instance from CloudMan. However, when I tried to lunch a new instance I had this error:

EC2ResponseError: 400 Bad Request InvalidVolume.NotFound

From the AWS console i saw that the instance I tried to launch wasn't attach to the volume, so I tried to manually attach the volume to the instance, but it didn't work. Do someone have any idea of what I could do for retrieving my data?

I'm not sure this is the right forum for this post; of course if it's not, I can delete it.

Thanks!
cloudlaunch cloud aws cloudman galaxy • 440 views
ADD COMMENT • link •
modified 10 months ago by Jennifer Hillman Jackson ♦ 25k • written 11 months ago by marp.p • 20
3
gravatar for Enis Afgan
11 months ago by
Enis Afgan • 690
United States
Enis Afgan • 690 wrote:

Sounds like you did this but just to make sure: when recreating the cluster, you clicked that 'Fetch saved clusters' button and selected the cluster name you're trying to relaunch?

The ID of the volume is stored in a file called persistent_data.yaml in a bucket on S3; the bucket name will be called cm-<string of numbers and letters>. So I'd suggest inspecting that file to make sure the new volume ID is listed there, under a filesystem tagged as galaxyData, galaxyTools. If not, update that file and try launching again.

If that does not work, there are more log files on the instance that we may need to look into: https://galaxyproject.org/cloudman/faq/#command-line-access and https://galaxyproject.org/cloudman/troubleshooting/#log-files
ADD COMMENT • link written 11 months ago by Enis Afgan • 690
0
gravatar for marp.p
10 months ago by
marp.p • 20
marp.p • 20 wrote:

I'm sorry for the late answer, it was exactly my problem. I could fix the issue, so thank you so much!
ADD COMMENT • link written 10 months ago by marp.p • 20
Please log in to add an answer.

Similar posts • Search »

Content
Help
Access
Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 169 users visited in the last hour