This volume is hanged with detaching status on old instance i-49d0d020 that hanged in Shutting-down status. Such situation was happend with one of our instance a few weeks ago. There are two solutions:
1. Force detach this volume from old instance (In this case you can lose data) 2. Submit ticket to amazon. Scalr will attach and mount this volume as soon as it become to available state. On Aug 28, 2:41 am, Rod Frey <[email protected]> wrote: > My database master rebooted. I don't know why, it's the same IP it > had before so I don't think it was killed by AWS. > > In any case, the EBS partition that holds my mysql data didn't > reattach. The EBS Volumes page shows it attached, but when I log in > it is not, and the device that scalr.net says it's attached to does > not exist. > > The EBS volume is vol-191ef770 and the EC2 instance is i-49d0d020. > Scalr.net reports the volume attached to /dev/sdf but when I log onto > the instance there is no /dev/sdf, and of course my database was > failing. > > I'm now redirecting all traffic including writes against my slave > since I can't seem to get to the master EBS partition anymore. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
