My droplet is inaccessible for 28 hours now and yes I have opened several support tickets. My original support ticket was because the droplet was showing signs of data loss, and it is not anywhere
near using a high percentage of ram or disk space. At least at that point, I could get to my droplet, it just was getting very slow about changes updating. Then support did something without asking me first, and just emailed me afterward. They attached the recovery iso to my droplet. I guess that is a reasonable thing to do IF you ask your client first and IF you plan to detach the iso afterward, as that is something the client has no access to do.
I did the fsck and listed info about the kernel per the instructions that support sent me in their one and only email to me. Those commands executed fine and showed no problems with file system or kernel.
I immediately afterward unmounted the iso and updated my suport ticket to ask them to detach it.
28 hours later. I have not heard from them. I cannot access the droplet by ssh, and from the console
I just get the menu displayed by the recovery iso, so it obviously has not been detached. Yes I have rebooted every possible way, through the command line and through the DO website.
My question: It would have been much quicker for me to drive to NY (I don’t live far), find the server
my droplet is on and just hit the button to eject the DVD tray of the recovery disk.. but I guess everything is virtual, there is no physical tray to eject, right? Is there any command I can use from within the recovery disk (as in it is mounted) to force it to detach?