If you already have a server image that you would like to use on top of UpCloud\u2019s infrastructure, you can create bootable OS storage from it. The process requires that you deploy a new server, upload the image to the cloud host and set up the new disk device. This guide goes through the process step-by-step.<\/p>\n\n\n\n

Test hosting on UpCloud!<\/a><\/div>\n<\/div>\n\n\n\n

Deploying a new host<\/h2>\n\n\n\n
Start off by creating a new cloud server of your choice at your UpCloud Control Panel<\/a>. The instructions in this guide are directed at a Linux system but the process would be largely the same on any server OS.<\/p>\n\n\n\n
Make the required configurations by:<\/p>\n\n\n\n
\n
Selecting the location you wish to import the server<\/li>\n\n\n\n
Choose the configuration, the 1CPU and 1GB General Purpose plan works fine<\/li>\n\n\n\n
Add a second storage disk by clicking the Add a new device<\/em> button and choosing the size, it can be scaled up later<\/a><\/li>\n<\/ul>\n\n\n\n
$\"Deploy$ <\/figure>\n\n\n\n
\n
Pick the OS you are comfortable with for a one-time boot<\/li>\n\n\n\n
Include any SSH keys you wish if available to allow password-free login<\/li>\n\n\n\n
Naming your server and giving it a description.<\/li>\n\n\n\n
Confirm your selections and click the Deploy<\/em> button.<\/li>\n<\/ul>\n\n\n\n
Once your server has finished deploying, you can log in with SSH using any keys selected at deployment or using the root password.<\/p>\n\n\n\n
Update the system to make sure the software is running the latest version.<\/p>\n\n\n\n
# Debian and Ubuntu\nsudo apt-get update && sudo apt-get dist-upgrade -y\n# CentOS\nsudo yum update -y<\/pre>\n\n\n\n
With the new server up to date, check that both of the storage drives are attached and report their size correctly.<\/p>\n\n\n\n
lsblk<\/pre>\n\n\n\n
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT\nvda 253:0 0 25G 0 disk\n\u2514\u2500vda1 253:1 0 25G 0 part \/\nvdb 253:16 0 10G 0 disk<\/pre>\n\n\n\n
Here the vda<\/em> disk with a partition called vda1<\/em> is your primary storage and the vdb<\/em> disk is the second device without partitions. If everything seems in order, continue with uploading your server image to the cloud host.<\/p>\n\n\n\n
Importing the system image<\/h2>\n\n\n\n
When the new host is up and ready, upload your server image, for example using Secure Copy, SFTP or rsync.<\/p>\n\n\n\n
You can find out about some of the different secure file transfer options in the first section for Encrypt communications in the guide for cloud server security<\/a>. Depending on your original system and your network connection it may be useful to compress the disk files for the transfer and then uncompress them again on the target host.<\/p>\n\n\n\n
When you have uploaded the image to the server, you will need to copy the image content to the empty storage device. Use the following command while replacing the server_image<\/span> with the system image file, the target disk is usually located at \/dev\/vdb<\/em>.<\/p>\n\n\n\n
dd if=server_image<\/span> of=\/dev\/vdb bs=16M oflag=direct<\/pre>\n\n\n\nNote that the server image needs to be in RAW format ending with the .img<\/em> file extension. This means images taken, for example, from a VMware environment do not work as is. The VMware images should be converted to the RAW format with a tool such as qemu-img, which is available for installation on most package managers. Check out our guide about how to import VMware images to UpCloud<\/a> to learn more.<\/p>\n\n\n\n
Afterwards, you can shut down the server and remove the old primary disk. Go to your UpCloud Control Panel<\/a> and the Storage tab at your server settings. Once the server is in the stopped state, click the eject<\/i> icon on the primary storage device to remove it. The second disk, where you just transferred the system image, will then be automatically set as the new primary device. In the same menu, you should also choose the disk controller.<\/p>\n\n\n\n
$\"Detaching$ <\/figure>\n\n\n\n
VirtIO controller provides the best performance, but if you have issues starting the server, try IDE as it has better compatibility with different operating systems.<\/p>\n\n\n\n
You can then restart the server again to continue configuring the system.<\/p>\n\n\n\n
Reconfiguring the new host<\/h2>\n\n\n\n
The newly transferred operating system should now boot up to the cloud server. However, depending on your old network setting you may need to log in using the web console to fix any issues before the system will connect normally. Go to your UpCloud Control Panel<\/a> then select the Console<\/em> tab under your server settings and click Open the console connection<\/em>.<\/p>\n\n\n\n
Log in normally with the user credentials for the server image before transferring it to the cloud. Once in, check the network settings with the following command.<\/p>\n\n\n\n
ip addr<\/pre>\n\n\n\n
UpCloud hosts have three network interfaces in the default configuration, public IPv4, private IPv4 and public IPv6 addresses. You might see something similar to the example output below. The first interface eth0<\/em> might work but the other devices are not yet configured.<\/p>\n\n\n\n
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default\n link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n inet 127.0.0.1\/8 scope host lo\n valid_lft forever preferred_lft forever\n inet6 ::1\/128 scope host\n valid_lft forever preferred_lft forever\n2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000\n link\/ether 6e:d7:1b:bf:18:29 brd ff:ff:ff:ff:ff:ff\n inet 83.136.248.62\/22 brd 83.136.251.255 scope global eth0\n valid_lft forever preferred_lft forever\n inet6 fe80::6cd7:1bff:febf:1829\/64 scope link\n valid_lft forever preferred_lft forever\n3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000\n link\/ether 6e:d7:1b:bf:e6:f2 brd ff:ff:ff:ff:ff:ff\n4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000\n link\/ether 6e:d7:1b:bf:61:a8 brd ff:ff:ff:ff:ff:ff<\/pre>\n\n\n\n
Edit your network configuration files to match the network interface names listed in the above output. For example, Ubuntu and other Debian-based systems use the command below to open the configuration file.<\/p>\n\n\n\n
sudo nano \/etc\/network\/interfaces<\/pre>\n\n\n\n
Add the following sections to the file. If the network interfaces were named differently, use those names instead of eth0<\/em>, eth1<\/em>, etc.<\/p>\n\n\n\n
auto lo\niface lo inet loopback\n\nauto eth0\niface eth0 inet dhcp\n\nauto eth1\niface eth1 inet dhcp\n\nauto eth2\niface eth2 inet6 auto<\/pre>\n\n\n\n
On CentOS and other Red Hat variants, the network interfaces are configured in individual files. These files are stored in the \/etc\/sysconfig\/network-scripts\/ directory, check the file names with the command below.<\/p>\n\n\n\n
ls \/etc\/sysconfig\/network-scripts\/ | grep ifcfg-<\/pre>\n\n\n\n
Then open the first interface file for editing, for example, ifcfg-eth0<\/em>.<\/p>\n\n\n\n
sudo vi \/etc\/sysconfig\/network-scripts\/ifcfg-eth0<\/pre>\n\n\n\n
The file should read at least the following settings. In case, ONBOOT<\/em> is set to no<\/em>, change it to yes<\/em> and save the file.<\/p>\n\n\n\n
DEVICE=eth0\nBOOTPROTO=dhcp\nONBOOT=yes<\/pre>\n\n\n\n
You may need to do the same operation to other network interfaces, or simply create new configuration files if your old system only had one or two interfaces.<\/p>\n\n\n\n
Afterwards, reboot the server and try logging in with SSH. If the network is working you can start using the new host as before with the added benefit of the freely scalable system resources and faster than SSD storage disks with MaxIOPS technology.<\/p>\n\n\n\n
Final steps<\/h2>\n\n\n\n
Congratulations, your own server image should now be up and running on a brand new cloud host. In case you have any further problems with the network, you can find additional help with troubleshooting the connectivity in the guide for network issues with the Linux host<\/a>.<\/p>\n\n\n\n
If you run into issues with booting from the new system image, you can always attach the old primary disk again and find the image files safely stored for another try without the need to wait for the image to upload again. Once you are confident that the new system is running properly, you can go to the Storage list in your UpCloud Control Panel<\/a> and delete the unnecessary storage device.<\/p>\n","protected":false},"featured_media":26821,"comment_status":"open","ping_status":"closed","template":"","community-category":[109,110],"class_list":["post-24388","tutorial","type-tutorial","status-publish","has-post-thumbnail","hentry","community-category-upcloud-services","community-category-storage"],"acf":[],"_links":{"self":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial\/24388","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/types\/tutorial"}],"replies":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/comments?post=24388"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media\/26821"}],"wp:attachment":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media?parent=24388"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/community-category?post=24388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}