WINDOZE Using dd to transfer shrunk partitions on a 2TB HDD to a 500GB SSD
Situation:
A source HDA (2TB mechanical HDD) has 5 partitions on it (presumably in GPT) that used to occupy the entire capacity of the 2TB HDA.
The operation system resident on the source drive is Windows 10.
Since the majority of the 'data' partition was unused storage space, and occupied 1.5TB of the drive capacity, it was shrunk, using gparted, to about 350GB, and the 'Push Button Recovery' partition (above it on the source HDA) was moved downward to be contiguous with the data partition.
The resultant state of the source HDA is 5 partitions occupying less than 400GB on a 2TB HDA, with the excess storage space on the drive being unallocated space.
Proposed target device is a Samsung 500GB SDD, which is currently in an unallocated state (no partitions defined and no boot structures written to the drive).
Hypothesis:
I can use dd (bs=1M, no count parameter specified) to write directly from the source device to the target device, since the aggregate partition sizes on the source device amount to less than the capacity of the target device; and have only an anomalous condition in what will be the unallocated space that results on the target device, post transfer.
Addressing this anomalous unallocated region of the target device by relocating the 'Push Button Recovery' partition to the upper end of the drive space, and growing the data partition to fill the remainder of the unallocated space on the target device, using gparted should work and leave me with a bootable device.
Question:
I don't tinker with windows systems unless I get backed into a corner by somebody else (like a family member), so I do not have a great deal of intuition in dealing with such situations; so, can anybody see why this would produce a non-bootable target SSD before I waste the time doing this?
hard-disk dd ssd
edited 1 min ago
Jasen
2,160713
asked 1 hour ago
AllanGHAllanGH
61
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Situation:
A source HDA (2TB mechanical HDD) has 5 partitions on it (presumably in GPT) that used to occupy the entire capacity of the 2TB HDA.
The operation system resident on the source drive is Windows 10.
Since the majority of the 'data' partition was unused storage space, and occupied 1.5TB of the drive capacity, it was shrunk, using gparted, to about 350GB, and the 'Push Button Recovery' partition (above it on the source HDA) was moved downward to be contiguous with the data partition.
The resultant state of the source HDA is 5 partitions occupying less than 400GB on a 2TB HDA, with the excess storage space on the drive being unallocated space.
Proposed target device is a Samsung 500GB SDD, which is currently in an unallocated state (no partitions defined and no boot structures written to the drive).
Hypothesis:
I can use dd (bs=1M, no count parameter specified) to write directly from the source device to the target device, since the aggregate partition sizes on the source device amount to less than the capacity of the target device; and have only an anomalous condition in what will be the unallocated space that results on the target device, post transfer.
Addressing this anomalous unallocated region of the target device by relocating the 'Push Button Recovery' partition to the upper end of the drive space, and growing the data partition to fill the remainder of the unallocated space on the target device, using gparted should work and leave me with a bootable device.
Question:
I don't tinker with windows systems unless I get backed into a corner by somebody else (like a family member), so I do not have a great deal of intuition in dealing with such situations; so, can anybody see why this would produce a non-bootable target SSD before I waste the time doing this?
hard-disk dd ssd
edited 1 min ago
Jasen
2,160713
asked 1 hour ago
AllanGHAllanGH
61
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Do both drives have the same block size? You can check withfdiskIf not then you may take a performance hit when usingddbecause the partitions (and filesystems) would be out of alignment with the block size of the SSD
– Emmanuel Rosa
20 mins ago
On the 2TB HDA, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 4096B / 4096B / 4096B. On the 500GB SSD, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 512B / 512B / 512B. I would conclude that, given your inquiry, my best move would be to dd with a bs=512, rather than the 1M?
– AllanGH
6 mins ago
what you suggest makes sense, but windows questions might be better asked on "superuser"
– Jasen
2 mins ago
add a comment |
Situation:
A source HDA (2TB mechanical HDD) has 5 partitions on it (presumably in GPT) that used to occupy the entire capacity of the 2TB HDA.
The operation system resident on the source drive is Windows 10.
Since the majority of the 'data' partition was unused storage space, and occupied 1.5TB of the drive capacity, it was shrunk, using gparted, to about 350GB, and the 'Push Button Recovery' partition (above it on the source HDA) was moved downward to be contiguous with the data partition.
The resultant state of the source HDA is 5 partitions occupying less than 400GB on a 2TB HDA, with the excess storage space on the drive being unallocated space.
Proposed target device is a Samsung 500GB SDD, which is currently in an unallocated state (no partitions defined and no boot structures written to the drive).
Hypothesis:
I can use dd (bs=1M, no count parameter specified) to write directly from the source device to the target device, since the aggregate partition sizes on the source device amount to less than the capacity of the target device; and have only an anomalous condition in what will be the unallocated space that results on the target device, post transfer.
Addressing this anomalous unallocated region of the target device by relocating the 'Push Button Recovery' partition to the upper end of the drive space, and growing the data partition to fill the remainder of the unallocated space on the target device, using gparted should work and leave me with a bootable device.
Question:
I don't tinker with windows systems unless I get backed into a corner by somebody else (like a family member), so I do not have a great deal of intuition in dealing with such situations; so, can anybody see why this would produce a non-bootable target SSD before I waste the time doing this?
hard-disk dd ssd
edited 1 min ago
Jasen
2,160713
asked 1 hour ago
AllanGHAllanGH
61
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Situation:
A source HDA (2TB mechanical HDD) has 5 partitions on it (presumably in GPT) that used to occupy the entire capacity of the 2TB HDA.
The operation system resident on the source drive is Windows 10.
Since the majority of the 'data' partition was unused storage space, and occupied 1.5TB of the drive capacity, it was shrunk, using gparted, to about 350GB, and the 'Push Button Recovery' partition (above it on the source HDA) was moved downward to be contiguous with the data partition.
The resultant state of the source HDA is 5 partitions occupying less than 400GB on a 2TB HDA, with the excess storage space on the drive being unallocated space.
Proposed target device is a Samsung 500GB SDD, which is currently in an unallocated state (no partitions defined and no boot structures written to the drive).
Hypothesis:
I can use dd (bs=1M, no count parameter specified) to write directly from the source device to the target device, since the aggregate partition sizes on the source device amount to less than the capacity of the target device; and have only an anomalous condition in what will be the unallocated space that results on the target device, post transfer.
Addressing this anomalous unallocated region of the target device by relocating the 'Push Button Recovery' partition to the upper end of the drive space, and growing the data partition to fill the remainder of the unallocated space on the target device, using gparted should work and leave me with a bootable device.
Question:
I don't tinker with windows systems unless I get backed into a corner by somebody else (like a family member), so I do not have a great deal of intuition in dealing with such situations; so, can anybody see why this would produce a non-bootable target SSD before I waste the time doing this?
hard-disk dd ssd
hard-disk dd ssd
edited 1 min ago
Jasen
2,160713
asked 1 hour ago
AllanGHAllanGH
61
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 min ago
Jasen
2,160713
asked 1 hour ago
AllanGHAllanGH
61
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 min ago
Jasen
2,160713
edited 1 min ago
Jasen
2,160713
edited 1 min ago
Jasen
2,160713
2,160713
asked 1 hour ago
AllanGHAllanGH
61
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
AllanGHAllanGH
61
asked 1 hour ago
AllanGHAllanGH
61
61
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
AllanGH is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Do both drives have the same block size? You can check withfdiskIf not then you may take a performance hit when usingddbecause the partitions (and filesystems) would be out of alignment with the block size of the SSD
– Emmanuel Rosa
20 mins ago
On the 2TB HDA, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 4096B / 4096B / 4096B. On the 500GB SSD, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 512B / 512B / 512B. I would conclude that, given your inquiry, my best move would be to dd with a bs=512, rather than the 1M?
– AllanGH
6 mins ago
what you suggest makes sense, but windows questions might be better asked on "superuser"
– Jasen
2 mins ago
add a comment |
Do both drives have the same block size? You can check withfdiskIf not then you may take a performance hit when usingddbecause the partitions (and filesystems) would be out of alignment with the block size of the SSD
– Emmanuel Rosa
20 mins ago
On the 2TB HDA, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 4096B / 4096B / 4096B. On the 500GB SSD, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 512B / 512B / 512B. I would conclude that, given your inquiry, my best move would be to dd with a bs=512, rather than the 1M?
– AllanGH
6 mins ago
what you suggest makes sense, but windows questions might be better asked on "superuser"
– Jasen
2 mins ago
Do both drives have the same block size? You can check with
fdisk If not then you may take a performance hit when using dd because the partitions (and filesystems) would be out of alignment with the block size of the SSD– Emmanuel Rosa
20 mins ago
Do both drives have the same block size? You can check with
fdisk If not then you may take a performance hit when using dd because the partitions (and filesystems) would be out of alignment with the block size of the SSD– Emmanuel Rosa
20 mins ago
On the 2TB HDA, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 4096B / 4096B / 4096B. On the 500GB SSD, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 512B / 512B / 512B. I would conclude that, given your inquiry, my best move would be to dd with a bs=512, rather than the 1M?
– AllanGH
6 mins ago
On the 2TB HDA, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 4096B / 4096B / 4096B. On the 500GB SSD, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 512B / 512B / 512B. I would conclude that, given your inquiry, my best move would be to dd with a bs=512, rather than the 1M?
– AllanGH
6 mins ago
what you suggest makes sense, but windows questions might be better asked on "superuser"
– Jasen
2 mins ago
what you suggest makes sense, but windows questions might be better asked on "superuser"
– Jasen
2 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
AllanGH 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%2funix.stackexchange.com%2fquestions%2f504032%2fwindoze-using-dd-to-transfer-shrunk-partitions-on-a-2tb-hdd-to-a-500gb-ssd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
AllanGH is a new contributor. Be nice, and check out our Code of Conduct.
AllanGH is a new contributor. Be nice, and check out our Code of Conduct.
AllanGH is a new contributor. Be nice, and check out our Code of Conduct.
AllanGH is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f504032%2fwindoze-using-dd-to-transfer-shrunk-partitions-on-a-2tb-hdd-to-a-500gb-ssd%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
Do both drives have the same block size? You can check with
fdiskIf not then you may take a performance hit when usingddbecause the partitions (and filesystems) would be out of alignment with the block size of the SSD– Emmanuel Rosa
20 mins ago
On the 2TB HDA, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 4096B / 4096B / 4096B. On the 500GB SSD, Sector_logical / Sector_physical / IO_minimum / IO_optimal come back as: 512B / 512B / 512B / 512B. I would conclude that, given your inquiry, my best move would be to dd with a bs=512, rather than the 1M?
– AllanGH
6 mins ago
what you suggest makes sense, but windows questions might be better asked on "superuser"
– Jasen
2 mins ago