ok....that's what I did. I had some mess with an instance stuck after synchronization....so I did some manual terminations and launching of instances...during which I also lost the current assigned elastic ip and got a new one....
Not sure what was going on but I guess it's all because of that...it was not during normal action. On Mon, Jun 29, 2009 at 6:23 PM, Nickolas Toursky <[email protected]> wrote: > > Hi Arie, > > For now, just terminate the instance launched and the EBS volume will > be attached to a newly launched instance. > We are investigating the cause of this problem. > > Nick > > On Mon, Jun 29, 2009 at 6:09 PM, Arie Fishler<[email protected]> wrote: > > Hi, > > > > I have an EBS volume not mounted to an instance it was supposed to. The > EBS > > is currently marked as available. > > > > although it says...never assign manually...is it possible to do it now? > If > > so what should be used for the checkbox "Always attach volume vol- to > this > > instance upon startup" > > > > vol is vol-7a20c413 and it was supposed to go to an instance in farm 1173 > > > > If not....what is the best action now to make it mount? > > > > Thanks, > > Arie > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
