Hello. I have problem with installing windows on my droplet.
I run the command (via SSH to the server, not via the webwindow, cant write the | in the webwindow)
wget -O- http://mirror.whatuptime.com/xxxxx/betas/2016.STD.x64.EVAL.US-English.gz | gunzip | dd of=/dev/vda
it starts and downloads a bunch of files.
it looks something like this:
2018-03-10 21:48:37 (288 KB/s) - written to stdout [4742419180/4742419180]
31457280+0 records in
31457280+0 records out
16106127360 bytes (16 GB, 15 GiB) copied, 1199.13 s, 13.4 MB/s
[* Rescue *] win2016-1vcpu-2gb-lon1-01:/opt/digitalocean#
I never get the bash-4-2# message, but i have a promt (like above)
Is it done now ? should I turn off the droplet and contact digital ocean to dismantle the iso? or has something gone wrong?
thank you in advance!/Zac
Hello. I have problem with installing windows on my droplet.
I run the command (via SSH to the server, not via the webwindow, cant write the | in the webwindow)
wget -O- http://mirror.whatuptime.com/xxxxx/betas/2016.STD.x64.EVAL.US-English.gz | gunzip | dd of=/dev/vda
it starts and downloads a bunch of files.
it looks something like this:2018-03-10 21:48:37 (288 KB/s) - written to stdout [4742419180/4742419180]
31457280+0 records in
31457280+0 records out
16106127360 bytes (16 GB, 15 GiB) copied, 1199.13 s, 13.4 MB/s
[* Rescue *] win2016-1vcpu-2gb-lon1-01:/opt/digitalocean#I never get the bash-4-2# message, but i have a promt (like above)
Is it done now ? should I turn off the droplet and contact digital ocean to dismantle the iso? or has something gone wrong?
thank you in advance!/Zac
Are you following our installation guide for DigitalOcean?
oh, sorry 🙂 yes,
This guide.
https://www.whatuptime.com/installing-microsoft-windows-onto-digitalocean-droplet/
This is the FULL log (runned via SSH against digital ocean droplet with recovery enabled)
--------------------------------------------------------------------
DigitalOcean Recovery Environment 17.04.1 (Zesty Zona)
This image has been mounted by the DigitalOcean Support Team.
When you have completed your work in the recovery environment
update your support ticket to request that your droplet be booted
to it's disk.
This rescue environment is based on Ubuntu 17.04.
--------------------------------------------------------------------
Last login: Sat Mar 10 20:49:24 2018 from 79.136.31.173
The DigitalOcean Rescue Console may be accessed remotely
when using a terminal session manager. To enter the rescue
menu, run one of the following programs:
* screen
* tmux
* byobu
root@win2016-1vcpu-2gb-lon1-01:~# screen
--2018-03-10 21:28:45-- http://mirror.whatuptime.com/xxxx/betas/2016.STD.x64.EVAL.US-English.gz
Resolving mirror.whatuptime.com (mirror.whatuptime.com)... 198.50.139.60
Connecting to mirror.whatuptime.com (mirror.whatuptime.com)|198.50.139.60|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4742419180 (4.4G) [application/octet-stream]
Saving to: 'STDOUT'
- 97%[==========================================================================> ] 4.32G 276KB/s in 14m 13s
2018-03-10 21:42:58 (5.19 MB/s) - Connection closed at byte 4643475085. Retrying.
--2018-03-10 21:42:59-- (try: 2) http://mirror.whatuptime.com/xxx/betas/2016.STD.x64.EVAL.US-English.gz
Connecting to mirror.whatuptime.com (mirror.whatuptime.com)|198.50.139.60|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 4742419180 (4.4G), 98944095 (94M) remaining [application/octet-stream]
Saving to: 'STDOUT'
- 100%[+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=>] 4.42G 13.7KB/s in 5m 36s
2018-03-10 21:48:37 (288 KB/s) - written to stdout [4742419180/4742419180]
31457280+0 records in
31457280+0 records out
16106127360 bytes (16 GB, 15 GiB) copied, 1199.13 s, 13.4 MB/s
[* Rescue *] win2016-1vcpu-2gb-lon1-01:/opt/digitalocean#
You should be all set to request the rescue disk be removed and reboot your Droplet.
Even thou i did not get the bash-4-2# message?
Oh, it worked out fine! thank you
Oh, it worked out fine! thank you
Excellent to hear!
We will be updating our guide shortly to reflect the changes to the DigitalOcean recovery system and to ensure our guide is clear.