How to move a Ubuntu 14 machine from DigitalOcean to physical hardware?
How would I go about moving a Ubuntu 14 box from Digital Ocean to physical hardware?
14.04
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
|
show 1 more comment
How would I go about moving a Ubuntu 14 box from Digital Ocean to physical hardware?
14.04
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Maybe this is helpful? digitalocean.com/community/tutorials/…
– wjandrea
Jan 23 at 16:25
It may be a good time to upgrade since 14.04 will not be supported for much longer.
– kasperd
Jan 23 at 16:26
Please don't and start fresh with a new installation. Copy the apt cache over if you want to install the same software if you never deleted the cache. Oh and your problem also is related on how digital ocean provides features for this: if they let you make a virtual container you might only need to create one. Otherwise I would useddto create a diskdump if you have the diskspace for it,.
– Rinzwind
Jan 23 at 16:36
I have created a dd image and have it on a local disk, however I've been unable to boot from it.
– Serge
Jan 23 at 17:14
You probably won't have all the drivers necessary to run on real hardware if you bluntly copy the DO installation (that runs on a VM...). Do alspcion your DO server, and see all these devices than run only in VMs:SCSI storage controller: Red Hat, Inc Virtio SCSI,Ethernet controller: Red Hat, Inc Virtio network device, etc... Backup your config and reinstall a fresh system (with a 18.xx release).
– xenoid
Jan 23 at 17:25
|
show 1 more comment
How would I go about moving a Ubuntu 14 box from Digital Ocean to physical hardware?
14.04
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
How would I go about moving a Ubuntu 14 box from Digital Ocean to physical hardware?
14.04
14.04
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 23 at 16:21
SergeSerge
61
61
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Serge is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Maybe this is helpful? digitalocean.com/community/tutorials/…
– wjandrea
Jan 23 at 16:25
It may be a good time to upgrade since 14.04 will not be supported for much longer.
– kasperd
Jan 23 at 16:26
Please don't and start fresh with a new installation. Copy the apt cache over if you want to install the same software if you never deleted the cache. Oh and your problem also is related on how digital ocean provides features for this: if they let you make a virtual container you might only need to create one. Otherwise I would useddto create a diskdump if you have the diskspace for it,.
– Rinzwind
Jan 23 at 16:36
I have created a dd image and have it on a local disk, however I've been unable to boot from it.
– Serge
Jan 23 at 17:14
You probably won't have all the drivers necessary to run on real hardware if you bluntly copy the DO installation (that runs on a VM...). Do alspcion your DO server, and see all these devices than run only in VMs:SCSI storage controller: Red Hat, Inc Virtio SCSI,Ethernet controller: Red Hat, Inc Virtio network device, etc... Backup your config and reinstall a fresh system (with a 18.xx release).
– xenoid
Jan 23 at 17:25
|
show 1 more comment
1
Maybe this is helpful? digitalocean.com/community/tutorials/…
– wjandrea
Jan 23 at 16:25
It may be a good time to upgrade since 14.04 will not be supported for much longer.
– kasperd
Jan 23 at 16:26
Please don't and start fresh with a new installation. Copy the apt cache over if you want to install the same software if you never deleted the cache. Oh and your problem also is related on how digital ocean provides features for this: if they let you make a virtual container you might only need to create one. Otherwise I would useddto create a diskdump if you have the diskspace for it,.
– Rinzwind
Jan 23 at 16:36
I have created a dd image and have it on a local disk, however I've been unable to boot from it.
– Serge
Jan 23 at 17:14
You probably won't have all the drivers necessary to run on real hardware if you bluntly copy the DO installation (that runs on a VM...). Do alspcion your DO server, and see all these devices than run only in VMs:SCSI storage controller: Red Hat, Inc Virtio SCSI,Ethernet controller: Red Hat, Inc Virtio network device, etc... Backup your config and reinstall a fresh system (with a 18.xx release).
– xenoid
Jan 23 at 17:25
1
1
Maybe this is helpful? digitalocean.com/community/tutorials/…
– wjandrea
Jan 23 at 16:25
Maybe this is helpful? digitalocean.com/community/tutorials/…
– wjandrea
Jan 23 at 16:25
It may be a good time to upgrade since 14.04 will not be supported for much longer.
– kasperd
Jan 23 at 16:26
It may be a good time to upgrade since 14.04 will not be supported for much longer.
– kasperd
Jan 23 at 16:26
Please don't and start fresh with a new installation. Copy the apt cache over if you want to install the same software if you never deleted the cache. Oh and your problem also is related on how digital ocean provides features for this: if they let you make a virtual container you might only need to create one. Otherwise I would use
dd to create a diskdump if you have the diskspace for it,.– Rinzwind
Jan 23 at 16:36
Please don't and start fresh with a new installation. Copy the apt cache over if you want to install the same software if you never deleted the cache. Oh and your problem also is related on how digital ocean provides features for this: if they let you make a virtual container you might only need to create one. Otherwise I would use
dd to create a diskdump if you have the diskspace for it,.– Rinzwind
Jan 23 at 16:36
I have created a dd image and have it on a local disk, however I've been unable to boot from it.
– Serge
Jan 23 at 17:14
I have created a dd image and have it on a local disk, however I've been unable to boot from it.
– Serge
Jan 23 at 17:14
You probably won't have all the drivers necessary to run on real hardware if you bluntly copy the DO installation (that runs on a VM...). Do a
lspci on your DO server, and see all these devices than run only in VMs: SCSI storage controller: Red Hat, Inc Virtio SCSI, Ethernet controller: Red Hat, Inc Virtio network device, etc... Backup your config and reinstall a fresh system (with a 18.xx release).– xenoid
Jan 23 at 17:25
You probably won't have all the drivers necessary to run on real hardware if you bluntly copy the DO installation (that runs on a VM...). Do a
lspci on your DO server, and see all these devices than run only in VMs: SCSI storage controller: Red Hat, Inc Virtio SCSI, Ethernet controller: Red Hat, Inc Virtio network device, etc... Backup your config and reinstall a fresh system (with a 18.xx release).– xenoid
Jan 23 at 17:25
|
show 1 more comment
2 Answers
2
active
oldest
votes
One solution is to create an ISO image from your current Ubuntu 14 box and then mount the ISO image onto a USB drive, using the USB drive to boot from next time for installation.
See this similar question/answer for more information.
add a comment |
You need to download an image of the disk that exists on your VPS provider. The problem here is that the most common setup for a VPS is a server with a single "hard drive" attached to it, and you can't reliably make a disk image of a system while it's running without specialized tools or processes. Also, where would the disk image go since trying to take a snapshot of the disk while it's being imaged creates a problem.
If your VPS provider lets you download a disk image/snapshot/backup directly, great, you can just do that. However, most don't provide that functionality directly and instead you have to do it yourself. To do that you need to either create a new volume/disk and attach it to the server or launch a new VPS and attach the disk you're trying to image to that server. In either case, you need a system running Linux that has two disks attached, one the disk you're trying to image and the other a (larger) disk of where to store the image.
Next get the name of the disk you're imaging, in this example we'll call it /dev/sdb. You don't have to actually mount the disk you're trying to image, but instead do something like this:
dd if=/dev/sdb of=/where/to/write.img status=progress
The status=progress is so that you can monitor the progress. If you're doing this over SSH you might want to run this all as a setsid command (setsid dd ...) so that it doesn't get killed if you disconnect.
Once you have that .img file you can reverse the process by plugging a disk into a machine running Linux locally, in this example I'll call the disk we plugged in /dev/sdc
dd if=write.img of=/dev/sdc status=progress
If you're feeling snazzy you can try to do all of this without an intermediate storage disk on your VPS by booting into a Live CD and copying the files over an SSH tunnel by running this command on your VPS while booted into the Live CD:
dd if=/dev/sdb | ssh -C user@ip_of_home_pc dd of=disk.img
This takes advantage of the fact that SSH actually hooks up standard input/output streams and passes the output of the dd imaging process over a compressed (-C) SSH connection.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Serge is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112278%2fhow-to-move-a-ubuntu-14-machine-from-digitalocean-to-physical-hardware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
One solution is to create an ISO image from your current Ubuntu 14 box and then mount the ISO image onto a USB drive, using the USB drive to boot from next time for installation.
See this similar question/answer for more information.
add a comment |
One solution is to create an ISO image from your current Ubuntu 14 box and then mount the ISO image onto a USB drive, using the USB drive to boot from next time for installation.
See this similar question/answer for more information.
add a comment |
One solution is to create an ISO image from your current Ubuntu 14 box and then mount the ISO image onto a USB drive, using the USB drive to boot from next time for installation.
See this similar question/answer for more information.
One solution is to create an ISO image from your current Ubuntu 14 box and then mount the ISO image onto a USB drive, using the USB drive to boot from next time for installation.
See this similar question/answer for more information.
answered Jan 23 at 17:13
PSAPSA
713
713
add a comment |
add a comment |
You need to download an image of the disk that exists on your VPS provider. The problem here is that the most common setup for a VPS is a server with a single "hard drive" attached to it, and you can't reliably make a disk image of a system while it's running without specialized tools or processes. Also, where would the disk image go since trying to take a snapshot of the disk while it's being imaged creates a problem.
If your VPS provider lets you download a disk image/snapshot/backup directly, great, you can just do that. However, most don't provide that functionality directly and instead you have to do it yourself. To do that you need to either create a new volume/disk and attach it to the server or launch a new VPS and attach the disk you're trying to image to that server. In either case, you need a system running Linux that has two disks attached, one the disk you're trying to image and the other a (larger) disk of where to store the image.
Next get the name of the disk you're imaging, in this example we'll call it /dev/sdb. You don't have to actually mount the disk you're trying to image, but instead do something like this:
dd if=/dev/sdb of=/where/to/write.img status=progress
The status=progress is so that you can monitor the progress. If you're doing this over SSH you might want to run this all as a setsid command (setsid dd ...) so that it doesn't get killed if you disconnect.
Once you have that .img file you can reverse the process by plugging a disk into a machine running Linux locally, in this example I'll call the disk we plugged in /dev/sdc
dd if=write.img of=/dev/sdc status=progress
If you're feeling snazzy you can try to do all of this without an intermediate storage disk on your VPS by booting into a Live CD and copying the files over an SSH tunnel by running this command on your VPS while booted into the Live CD:
dd if=/dev/sdb | ssh -C user@ip_of_home_pc dd of=disk.img
This takes advantage of the fact that SSH actually hooks up standard input/output streams and passes the output of the dd imaging process over a compressed (-C) SSH connection.
add a comment |
You need to download an image of the disk that exists on your VPS provider. The problem here is that the most common setup for a VPS is a server with a single "hard drive" attached to it, and you can't reliably make a disk image of a system while it's running without specialized tools or processes. Also, where would the disk image go since trying to take a snapshot of the disk while it's being imaged creates a problem.
If your VPS provider lets you download a disk image/snapshot/backup directly, great, you can just do that. However, most don't provide that functionality directly and instead you have to do it yourself. To do that you need to either create a new volume/disk and attach it to the server or launch a new VPS and attach the disk you're trying to image to that server. In either case, you need a system running Linux that has two disks attached, one the disk you're trying to image and the other a (larger) disk of where to store the image.
Next get the name of the disk you're imaging, in this example we'll call it /dev/sdb. You don't have to actually mount the disk you're trying to image, but instead do something like this:
dd if=/dev/sdb of=/where/to/write.img status=progress
The status=progress is so that you can monitor the progress. If you're doing this over SSH you might want to run this all as a setsid command (setsid dd ...) so that it doesn't get killed if you disconnect.
Once you have that .img file you can reverse the process by plugging a disk into a machine running Linux locally, in this example I'll call the disk we plugged in /dev/sdc
dd if=write.img of=/dev/sdc status=progress
If you're feeling snazzy you can try to do all of this without an intermediate storage disk on your VPS by booting into a Live CD and copying the files over an SSH tunnel by running this command on your VPS while booted into the Live CD:
dd if=/dev/sdb | ssh -C user@ip_of_home_pc dd of=disk.img
This takes advantage of the fact that SSH actually hooks up standard input/output streams and passes the output of the dd imaging process over a compressed (-C) SSH connection.
add a comment |
You need to download an image of the disk that exists on your VPS provider. The problem here is that the most common setup for a VPS is a server with a single "hard drive" attached to it, and you can't reliably make a disk image of a system while it's running without specialized tools or processes. Also, where would the disk image go since trying to take a snapshot of the disk while it's being imaged creates a problem.
If your VPS provider lets you download a disk image/snapshot/backup directly, great, you can just do that. However, most don't provide that functionality directly and instead you have to do it yourself. To do that you need to either create a new volume/disk and attach it to the server or launch a new VPS and attach the disk you're trying to image to that server. In either case, you need a system running Linux that has two disks attached, one the disk you're trying to image and the other a (larger) disk of where to store the image.
Next get the name of the disk you're imaging, in this example we'll call it /dev/sdb. You don't have to actually mount the disk you're trying to image, but instead do something like this:
dd if=/dev/sdb of=/where/to/write.img status=progress
The status=progress is so that you can monitor the progress. If you're doing this over SSH you might want to run this all as a setsid command (setsid dd ...) so that it doesn't get killed if you disconnect.
Once you have that .img file you can reverse the process by plugging a disk into a machine running Linux locally, in this example I'll call the disk we plugged in /dev/sdc
dd if=write.img of=/dev/sdc status=progress
If you're feeling snazzy you can try to do all of this without an intermediate storage disk on your VPS by booting into a Live CD and copying the files over an SSH tunnel by running this command on your VPS while booted into the Live CD:
dd if=/dev/sdb | ssh -C user@ip_of_home_pc dd of=disk.img
This takes advantage of the fact that SSH actually hooks up standard input/output streams and passes the output of the dd imaging process over a compressed (-C) SSH connection.
You need to download an image of the disk that exists on your VPS provider. The problem here is that the most common setup for a VPS is a server with a single "hard drive" attached to it, and you can't reliably make a disk image of a system while it's running without specialized tools or processes. Also, where would the disk image go since trying to take a snapshot of the disk while it's being imaged creates a problem.
If your VPS provider lets you download a disk image/snapshot/backup directly, great, you can just do that. However, most don't provide that functionality directly and instead you have to do it yourself. To do that you need to either create a new volume/disk and attach it to the server or launch a new VPS and attach the disk you're trying to image to that server. In either case, you need a system running Linux that has two disks attached, one the disk you're trying to image and the other a (larger) disk of where to store the image.
Next get the name of the disk you're imaging, in this example we'll call it /dev/sdb. You don't have to actually mount the disk you're trying to image, but instead do something like this:
dd if=/dev/sdb of=/where/to/write.img status=progress
The status=progress is so that you can monitor the progress. If you're doing this over SSH you might want to run this all as a setsid command (setsid dd ...) so that it doesn't get killed if you disconnect.
Once you have that .img file you can reverse the process by plugging a disk into a machine running Linux locally, in this example I'll call the disk we plugged in /dev/sdc
dd if=write.img of=/dev/sdc status=progress
If you're feeling snazzy you can try to do all of this without an intermediate storage disk on your VPS by booting into a Live CD and copying the files over an SSH tunnel by running this command on your VPS while booted into the Live CD:
dd if=/dev/sdb | ssh -C user@ip_of_home_pc dd of=disk.img
This takes advantage of the fact that SSH actually hooks up standard input/output streams and passes the output of the dd imaging process over a compressed (-C) SSH connection.
answered yesterday
Kristopher IvesKristopher Ives
2,16611118
2,16611118
add a comment |
add a comment |
Serge is a new contributor. Be nice, and check out our Code of Conduct.
Serge is a new contributor. Be nice, and check out our Code of Conduct.
Serge is a new contributor. Be nice, and check out our Code of Conduct.
Serge is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112278%2fhow-to-move-a-ubuntu-14-machine-from-digitalocean-to-physical-hardware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Maybe this is helpful? digitalocean.com/community/tutorials/…
– wjandrea
Jan 23 at 16:25
It may be a good time to upgrade since 14.04 will not be supported for much longer.
– kasperd
Jan 23 at 16:26
Please don't and start fresh with a new installation. Copy the apt cache over if you want to install the same software if you never deleted the cache. Oh and your problem also is related on how digital ocean provides features for this: if they let you make a virtual container you might only need to create one. Otherwise I would use
ddto create a diskdump if you have the diskspace for it,.– Rinzwind
Jan 23 at 16:36
I have created a dd image and have it on a local disk, however I've been unable to boot from it.
– Serge
Jan 23 at 17:14
You probably won't have all the drivers necessary to run on real hardware if you bluntly copy the DO installation (that runs on a VM...). Do a
lspcion your DO server, and see all these devices than run only in VMs:SCSI storage controller: Red Hat, Inc Virtio SCSI,Ethernet controller: Red Hat, Inc Virtio network device, etc... Backup your config and reinstall a fresh system (with a 18.xx release).– xenoid
Jan 23 at 17:25