{"action":"created","issue":{"url":"https://api.github.com/repos/gh2o/digitalocean-debian-to-arch/issues/7","labels_url":"https://api.github.com/repos/gh2o/digitalocean-debian-to-arch/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/gh2o/digitalocean-debian-to-arch/issues/7/comments","events_url":"https://api.github.com/repos/gh2o/digitalocean-debian-to-arch/issues/7/events","html_url":"https://github.com/gh2o/digitalocean-debian-to-arch/issues/7","id":53307496,"number":7,"title":"Incompatible with snapshots?","user":{"login":"jeaye","id":1057635,"avatar_url":"https://avatars.githubusercontent.com/u/1057635?v=3","gravatar_id":"","url":"https://api.github.com/users/jeaye","html_url":"https://github.com/jeaye","followers_url":"https://api.github.com/users/jeaye/followers","following_url":"https://api.github.com/users/jeaye/following{/other_user}","gists_url":"https://api.github.com/users/jeaye/gists{/gist_id}","starred_url":"https://api.github.com/users/jeaye/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeaye/subscriptions","organizations_url":"https://api.github.com/users/jeaye/orgs","repos_url":"https://api.github.com/users/jeaye/repos","events_url":"https://api.github.com/users/jeaye/events{/privacy}","received_events_url":"https://api.github.com/users/jeaye/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-01-03T15:59:49Z","updated_at":"2015-01-06T08:38:18Z","closed_at":"2015-01-06T08:38:18Z","body":"I initially setup my system with this approach about 20 days ago and it's been working wonderfully. After creating some snapshots, I've found that I'm unable to boot a new droplet. That is, I can flawlessly take down my initial droplet and spin it back up, but I'm unable to spin up any new droplets using a snapshot of this system.\r\n\r\nI've spent a couple of days going over this with the DigitalOcean support team and they've found nothing wrong on their end so I'm lead to believe it's some bad state from this transmutation. Since my evidence for this is inconclusive, I'd really appreciate it if anyone else would try the same thing. Snap shot your \"Arch\" system and try to spin up a droplet based on the snapshot; if it boots and you can log into it, you get further than me.\r\n\r\nOtherwise, having written this system, perhaps you have some more troubleshooting suggestions. I've run fsck on the droplet (from a recovery kernel) with no reported errors and nothing in lost+found."},"comment":{"url":"https://api.github.com/repos/gh2o/digitalocean-debian-to-arch/issues/comments/68839327","html_url":"https://github.com/gh2o/digitalocean-debian-to-arch/issues/7#issuecomment-68839327","issue_url":"https://api.github.com/repos/gh2o/digitalocean-debian-to-arch/issues/7","id":68839327,"user":{"login":"gh2o","id":371529,"avatar_url":"https://avatars.githubusercontent.com/u/371529?v=3","gravatar_id":"","url":"https://api.github.com/users/gh2o","html_url":"https://github.com/gh2o","followers_url":"https://api.github.com/users/gh2o/followers","following_url":"https://api.github.com/users/gh2o/following{/other_user}","gists_url":"https://api.github.com/users/gh2o/gists{/gist_id}","starred_url":"https://api.github.com/users/gh2o/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gh2o/subscriptions","organizations_url":"https://api.github.com/users/gh2o/orgs","repos_url":"https://api.github.com/users/gh2o/repos","events_url":"https://api.github.com/users/gh2o/events{/privacy}","received_events_url":"https://api.github.com/users/gh2o/received_events","type":"User","site_admin":false},"created_at":"2015-01-06T08:38:18Z","updated_at":"2015-01-06T08:38:18Z","body":"Never mind, that was just an oddity with my droplet. Apparently if `/root/.ssh/authorized_keys` is a symlink, droplet restore will fail because they can't write the public keys specified at droplet creation. I fixed that and all is good."}}