How to restore partitions after renumbering?
I have read the posts and decided to follow it to do it, Change the number of the partition from sda1 to sda2, made by Joao S Veiga. I thought it would be light-risk because renumbering partitions seems doesn't touch my datas but only MBR, though it is warned that it is not a good idea to do it. But now most of my partitions lost (NTFS and ETX4), even restoring MBR to my disk doesn't work. Try to mount one partition mount /dev/sda6 /mnt in the terminal failed and puts an error message: ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.
Do I have chance to restore partitions and my datas?
linux partition restore
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
|
show 1 more comment
I have read the posts and decided to follow it to do it, Change the number of the partition from sda1 to sda2, made by Joao S Veiga. I thought it would be light-risk because renumbering partitions seems doesn't touch my datas but only MBR, though it is warned that it is not a good idea to do it. But now most of my partitions lost (NTFS and ETX4), even restoring MBR to my disk doesn't work. Try to mount one partition mount /dev/sda6 /mnt in the terminal failed and puts an error message: ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.
Do I have chance to restore partitions and my datas?
linux partition restore
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
3
Which "the posts" did you read. I don't know how to solve the problems you might get in Windows after renumbering the partitions. In Linux you have to change all commands or table entries that reference a partition by its number, e.g. replace the6inmount /dev/sda6 /mntto the new partition number after renumbering. If you change all partition numbers back to their original value everything should work as before.
– Bodo
Feb 18 at 12:51
In principle if you know exactly where a partition starts and stops you can just recreate it. Hopefully nothing you have done has corrupted any of your file systems. But you will need to tell us more about what you did (which commands you used) so we can help you undo the damage.
– Philip Couling
Feb 18 at 13:39
@Philip Couling: Restoring MBR is enough for me?fdiskcan delete the partition and recreate it, MBR seems simple, why don't work?
– maggicmuojet
Feb 19 at 5:57
@maggicmuojet the most likely thing is that you didn't re-create them with the same size and position as before. You only have get the position one sector out and you will make the partition unreadable.
– Philip Couling
Feb 19 at 7:53
1
Note that in MBR partitioning scheme, only partitions 1-4 are primary partitions and so their partition information is in the actual MBR block. Partitions with numbers 5 or greater are "logical partitions", meaning that one of the primary partitions must be used as an "extended partition", which can then be further sub-divided into "logical partitions", each of which will have its own partition information block located just before the beginning of that partition. I guess something is wrong with this chaining/encapsulation scheme.
– telcoM
Feb 19 at 8:05
|
show 1 more comment
I have read the posts and decided to follow it to do it, Change the number of the partition from sda1 to sda2, made by Joao S Veiga. I thought it would be light-risk because renumbering partitions seems doesn't touch my datas but only MBR, though it is warned that it is not a good idea to do it. But now most of my partitions lost (NTFS and ETX4), even restoring MBR to my disk doesn't work. Try to mount one partition mount /dev/sda6 /mnt in the terminal failed and puts an error message: ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.
Do I have chance to restore partitions and my datas?
linux partition restore
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
I have read the posts and decided to follow it to do it, Change the number of the partition from sda1 to sda2, made by Joao S Veiga. I thought it would be light-risk because renumbering partitions seems doesn't touch my datas but only MBR, though it is warned that it is not a good idea to do it. But now most of my partitions lost (NTFS and ETX4), even restoring MBR to my disk doesn't work. Try to mount one partition mount /dev/sda6 /mnt in the terminal failed and puts an error message: ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.
Do I have chance to restore partitions and my datas?
linux partition restore
linux partition restore
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
edited Feb 19 at 6:20
maggicmuojet
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
asked Feb 18 at 12:40
maggicmuojetmaggicmuojet
11
11
3
Which "the posts" did you read. I don't know how to solve the problems you might get in Windows after renumbering the partitions. In Linux you have to change all commands or table entries that reference a partition by its number, e.g. replace the6inmount /dev/sda6 /mntto the new partition number after renumbering. If you change all partition numbers back to their original value everything should work as before.
– Bodo
Feb 18 at 12:51
In principle if you know exactly where a partition starts and stops you can just recreate it. Hopefully nothing you have done has corrupted any of your file systems. But you will need to tell us more about what you did (which commands you used) so we can help you undo the damage.
– Philip Couling
Feb 18 at 13:39
@Philip Couling: Restoring MBR is enough for me?fdiskcan delete the partition and recreate it, MBR seems simple, why don't work?
– maggicmuojet
Feb 19 at 5:57
@maggicmuojet the most likely thing is that you didn't re-create them with the same size and position as before. You only have get the position one sector out and you will make the partition unreadable.
– Philip Couling
Feb 19 at 7:53
1
Note that in MBR partitioning scheme, only partitions 1-4 are primary partitions and so their partition information is in the actual MBR block. Partitions with numbers 5 or greater are "logical partitions", meaning that one of the primary partitions must be used as an "extended partition", which can then be further sub-divided into "logical partitions", each of which will have its own partition information block located just before the beginning of that partition. I guess something is wrong with this chaining/encapsulation scheme.
– telcoM
Feb 19 at 8:05
|
show 1 more comment
3
Which "the posts" did you read. I don't know how to solve the problems you might get in Windows after renumbering the partitions. In Linux you have to change all commands or table entries that reference a partition by its number, e.g. replace the6inmount /dev/sda6 /mntto the new partition number after renumbering. If you change all partition numbers back to their original value everything should work as before.
– Bodo
Feb 18 at 12:51
In principle if you know exactly where a partition starts and stops you can just recreate it. Hopefully nothing you have done has corrupted any of your file systems. But you will need to tell us more about what you did (which commands you used) so we can help you undo the damage.
– Philip Couling
Feb 18 at 13:39
@Philip Couling: Restoring MBR is enough for me?fdiskcan delete the partition and recreate it, MBR seems simple, why don't work?
– maggicmuojet
Feb 19 at 5:57
@maggicmuojet the most likely thing is that you didn't re-create them with the same size and position as before. You only have get the position one sector out and you will make the partition unreadable.
– Philip Couling
Feb 19 at 7:53
1
Note that in MBR partitioning scheme, only partitions 1-4 are primary partitions and so their partition information is in the actual MBR block. Partitions with numbers 5 or greater are "logical partitions", meaning that one of the primary partitions must be used as an "extended partition", which can then be further sub-divided into "logical partitions", each of which will have its own partition information block located just before the beginning of that partition. I guess something is wrong with this chaining/encapsulation scheme.
– telcoM
Feb 19 at 8:05
3
3
Which "the posts" did you read. I don't know how to solve the problems you might get in Windows after renumbering the partitions. In Linux you have to change all commands or table entries that reference a partition by its number, e.g. replace the
6 in mount /dev/sda6 /mnt to the new partition number after renumbering. If you change all partition numbers back to their original value everything should work as before.– Bodo
Feb 18 at 12:51
Which "the posts" did you read. I don't know how to solve the problems you might get in Windows after renumbering the partitions. In Linux you have to change all commands or table entries that reference a partition by its number, e.g. replace the
6 in mount /dev/sda6 /mnt to the new partition number after renumbering. If you change all partition numbers back to their original value everything should work as before.– Bodo
Feb 18 at 12:51
In principle if you know exactly where a partition starts and stops you can just recreate it. Hopefully nothing you have done has corrupted any of your file systems. But you will need to tell us more about what you did (which commands you used) so we can help you undo the damage.
– Philip Couling
Feb 18 at 13:39
In principle if you know exactly where a partition starts and stops you can just recreate it. Hopefully nothing you have done has corrupted any of your file systems. But you will need to tell us more about what you did (which commands you used) so we can help you undo the damage.
– Philip Couling
Feb 18 at 13:39
@Philip Couling: Restoring MBR is enough for me?
fdisk can delete the partition and recreate it, MBR seems simple, why don't work?– maggicmuojet
Feb 19 at 5:57
@Philip Couling: Restoring MBR is enough for me?
fdisk can delete the partition and recreate it, MBR seems simple, why don't work?– maggicmuojet
Feb 19 at 5:57
@maggicmuojet the most likely thing is that you didn't re-create them with the same size and position as before. You only have get the position one sector out and you will make the partition unreadable.
– Philip Couling
Feb 19 at 7:53
@maggicmuojet the most likely thing is that you didn't re-create them with the same size and position as before. You only have get the position one sector out and you will make the partition unreadable.
– Philip Couling
Feb 19 at 7:53
1
1
Note that in MBR partitioning scheme, only partitions 1-4 are primary partitions and so their partition information is in the actual MBR block. Partitions with numbers 5 or greater are "logical partitions", meaning that one of the primary partitions must be used as an "extended partition", which can then be further sub-divided into "logical partitions", each of which will have its own partition information block located just before the beginning of that partition. I guess something is wrong with this chaining/encapsulation scheme.
– telcoM
Feb 19 at 8:05
Note that in MBR partitioning scheme, only partitions 1-4 are primary partitions and so their partition information is in the actual MBR block. Partitions with numbers 5 or greater are "logical partitions", meaning that one of the primary partitions must be used as an "extended partition", which can then be further sub-divided into "logical partitions", each of which will have its own partition information block located just before the beginning of that partition. I guess something is wrong with this chaining/encapsulation scheme.
– telcoM
Feb 19 at 8:05
|
show 1 more comment
2 Answers
2
active
oldest
votes
oops
In future you might want to backup the first few MB of your hard drive with dd before doing something drastic. That would at least have given you a way back.
Now that you are here, its not great news. To be able to get back you need to know the exact size and position of every partition. Without this you are in real trouble.
What can you do to recover?
If you just lost sizes
You might not need them. You can assume every partition filled up all space up to the next partition. You should be able to calculate a size from that.
Fortunately most file systems don't mind being given extra space. So for example: if you accidentally forgot your swap partition, the ext4 partition before it wouldn't mind being finding itself on a larger partition (absorbing space from the swap partition).
If you lost everything
Your last chance is to try to detect your partitions using their magic number or other similar feature. Each / every file system should have a "magic number" at a predictable position in it's first sector. If you find the details of each file system you use (NTFS, EXT3, etc...) you might be able to scan every sector on your HD looking for one containing the correct magic number. There's no guarantee this won't find other sectors that happen to contain the same sequence in the right place, so it might come to a matter of trial and error.
- This might mean you have to write your own program to do this.
- There might be data recovery software you can purchase that would do this for you.
- Data recovery specialists might be able to take the drive of your hands and do it for you.
Which option you chose will be based on how confident you are doing the work yourself, how valuable the data is and how much you are willing to spend to get it back.
Also double check
You mentioned MBR. Just double check that your actions to renumber your partitions didn't result in a GPT partition table replacing your MBR table. That could have thrown something off when you recreated your partitions.
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
1
testdisk can be used to scan the contents of a disk, find the standard structures at the beginning of partitions and so reconstruct a corrupted partition table.
– telcoM
Feb 19 at 8:16
add a comment |
I'm the original asker here, I thought I can handle 'fdisk' enough to rebuild my partitions by its start sector and the end, but after that operation, some luks partitions could be open at the time I made the first post in this page, can not be opened by cryptsetup open /dev/sdaX my_luka right now, ouput saying ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.. In fact if I restored my NTFS partition to be a primary partition, its content can be seen, not only setting the position can be. Any chance where should I put my LUKS, or how to repair LUKS?
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
add a comment |
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
});
}
});
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%2f501340%2fhow-to-restore-partitions-after-renumbering%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
oops
In future you might want to backup the first few MB of your hard drive with dd before doing something drastic. That would at least have given you a way back.
Now that you are here, its not great news. To be able to get back you need to know the exact size and position of every partition. Without this you are in real trouble.
What can you do to recover?
If you just lost sizes
You might not need them. You can assume every partition filled up all space up to the next partition. You should be able to calculate a size from that.
Fortunately most file systems don't mind being given extra space. So for example: if you accidentally forgot your swap partition, the ext4 partition before it wouldn't mind being finding itself on a larger partition (absorbing space from the swap partition).
If you lost everything
Your last chance is to try to detect your partitions using their magic number or other similar feature. Each / every file system should have a "magic number" at a predictable position in it's first sector. If you find the details of each file system you use (NTFS, EXT3, etc...) you might be able to scan every sector on your HD looking for one containing the correct magic number. There's no guarantee this won't find other sectors that happen to contain the same sequence in the right place, so it might come to a matter of trial and error.
- This might mean you have to write your own program to do this.
- There might be data recovery software you can purchase that would do this for you.
- Data recovery specialists might be able to take the drive of your hands and do it for you.
Which option you chose will be based on how confident you are doing the work yourself, how valuable the data is and how much you are willing to spend to get it back.
Also double check
You mentioned MBR. Just double check that your actions to renumber your partitions didn't result in a GPT partition table replacing your MBR table. That could have thrown something off when you recreated your partitions.
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
1
testdisk can be used to scan the contents of a disk, find the standard structures at the beginning of partitions and so reconstruct a corrupted partition table.
– telcoM
Feb 19 at 8:16
add a comment |
oops
In future you might want to backup the first few MB of your hard drive with dd before doing something drastic. That would at least have given you a way back.
Now that you are here, its not great news. To be able to get back you need to know the exact size and position of every partition. Without this you are in real trouble.
What can you do to recover?
If you just lost sizes
You might not need them. You can assume every partition filled up all space up to the next partition. You should be able to calculate a size from that.
Fortunately most file systems don't mind being given extra space. So for example: if you accidentally forgot your swap partition, the ext4 partition before it wouldn't mind being finding itself on a larger partition (absorbing space from the swap partition).
If you lost everything
Your last chance is to try to detect your partitions using their magic number or other similar feature. Each / every file system should have a "magic number" at a predictable position in it's first sector. If you find the details of each file system you use (NTFS, EXT3, etc...) you might be able to scan every sector on your HD looking for one containing the correct magic number. There's no guarantee this won't find other sectors that happen to contain the same sequence in the right place, so it might come to a matter of trial and error.
- This might mean you have to write your own program to do this.
- There might be data recovery software you can purchase that would do this for you.
- Data recovery specialists might be able to take the drive of your hands and do it for you.
Which option you chose will be based on how confident you are doing the work yourself, how valuable the data is and how much you are willing to spend to get it back.
Also double check
You mentioned MBR. Just double check that your actions to renumber your partitions didn't result in a GPT partition table replacing your MBR table. That could have thrown something off when you recreated your partitions.
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
1
testdisk can be used to scan the contents of a disk, find the standard structures at the beginning of partitions and so reconstruct a corrupted partition table.
– telcoM
Feb 19 at 8:16
add a comment |
oops
In future you might want to backup the first few MB of your hard drive with dd before doing something drastic. That would at least have given you a way back.
Now that you are here, its not great news. To be able to get back you need to know the exact size and position of every partition. Without this you are in real trouble.
What can you do to recover?
If you just lost sizes
You might not need them. You can assume every partition filled up all space up to the next partition. You should be able to calculate a size from that.
Fortunately most file systems don't mind being given extra space. So for example: if you accidentally forgot your swap partition, the ext4 partition before it wouldn't mind being finding itself on a larger partition (absorbing space from the swap partition).
If you lost everything
Your last chance is to try to detect your partitions using their magic number or other similar feature. Each / every file system should have a "magic number" at a predictable position in it's first sector. If you find the details of each file system you use (NTFS, EXT3, etc...) you might be able to scan every sector on your HD looking for one containing the correct magic number. There's no guarantee this won't find other sectors that happen to contain the same sequence in the right place, so it might come to a matter of trial and error.
- This might mean you have to write your own program to do this.
- There might be data recovery software you can purchase that would do this for you.
- Data recovery specialists might be able to take the drive of your hands and do it for you.
Which option you chose will be based on how confident you are doing the work yourself, how valuable the data is and how much you are willing to spend to get it back.
Also double check
You mentioned MBR. Just double check that your actions to renumber your partitions didn't result in a GPT partition table replacing your MBR table. That could have thrown something off when you recreated your partitions.
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
oops
In future you might want to backup the first few MB of your hard drive with dd before doing something drastic. That would at least have given you a way back.
Now that you are here, its not great news. To be able to get back you need to know the exact size and position of every partition. Without this you are in real trouble.
What can you do to recover?
If you just lost sizes
You might not need them. You can assume every partition filled up all space up to the next partition. You should be able to calculate a size from that.
Fortunately most file systems don't mind being given extra space. So for example: if you accidentally forgot your swap partition, the ext4 partition before it wouldn't mind being finding itself on a larger partition (absorbing space from the swap partition).
If you lost everything
Your last chance is to try to detect your partitions using their magic number or other similar feature. Each / every file system should have a "magic number" at a predictable position in it's first sector. If you find the details of each file system you use (NTFS, EXT3, etc...) you might be able to scan every sector on your HD looking for one containing the correct magic number. There's no guarantee this won't find other sectors that happen to contain the same sequence in the right place, so it might come to a matter of trial and error.
- This might mean you have to write your own program to do this.
- There might be data recovery software you can purchase that would do this for you.
- Data recovery specialists might be able to take the drive of your hands and do it for you.
Which option you chose will be based on how confident you are doing the work yourself, how valuable the data is and how much you are willing to spend to get it back.
Also double check
You mentioned MBR. Just double check that your actions to renumber your partitions didn't result in a GPT partition table replacing your MBR table. That could have thrown something off when you recreated your partitions.
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
answered Feb 18 at 14:07
Philip CoulingPhilip Couling
1,535919
1,535919
1
testdisk can be used to scan the contents of a disk, find the standard structures at the beginning of partitions and so reconstruct a corrupted partition table.
– telcoM
Feb 19 at 8:16
add a comment |
1
testdisk can be used to scan the contents of a disk, find the standard structures at the beginning of partitions and so reconstruct a corrupted partition table.
– telcoM
Feb 19 at 8:16
1
1
testdisk can be used to scan the contents of a disk, find the standard structures at the beginning of partitions and so reconstruct a corrupted partition table.
– telcoM
Feb 19 at 8:16
testdisk can be used to scan the contents of a disk, find the standard structures at the beginning of partitions and so reconstruct a corrupted partition table.
– telcoM
Feb 19 at 8:16
add a comment |
I'm the original asker here, I thought I can handle 'fdisk' enough to rebuild my partitions by its start sector and the end, but after that operation, some luks partitions could be open at the time I made the first post in this page, can not be opened by cryptsetup open /dev/sdaX my_luka right now, ouput saying ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.. In fact if I restored my NTFS partition to be a primary partition, its content can be seen, not only setting the position can be. Any chance where should I put my LUKS, or how to repair LUKS?
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
add a comment |
I'm the original asker here, I thought I can handle 'fdisk' enough to rebuild my partitions by its start sector and the end, but after that operation, some luks partitions could be open at the time I made the first post in this page, can not be opened by cryptsetup open /dev/sdaX my_luka right now, ouput saying ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.. In fact if I restored my NTFS partition to be a primary partition, its content can be seen, not only setting the position can be. Any chance where should I put my LUKS, or how to repair LUKS?
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
add a comment |
I'm the original asker here, I thought I can handle 'fdisk' enough to rebuild my partitions by its start sector and the end, but after that operation, some luks partitions could be open at the time I made the first post in this page, can not be opened by cryptsetup open /dev/sdaX my_luka right now, ouput saying ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.. In fact if I restored my NTFS partition to be a primary partition, its content can be seen, not only setting the position can be. Any chance where should I put my LUKS, or how to repair LUKS?
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
I'm the original asker here, I thought I can handle 'fdisk' enough to rebuild my partitions by its start sector and the end, but after that operation, some luks partitions could be open at the time I made the first post in this page, can not be opened by cryptsetup open /dev/sdaX my_luka right now, ouput saying ...wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.. In fact if I restored my NTFS partition to be a primary partition, its content can be seen, not only setting the position can be. Any chance where should I put my LUKS, or how to repair LUKS?
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
answered Feb 23 at 5:00
MaggicmuojetMaggicmuojet
112
112
add a comment |
add a comment |
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%2f501340%2fhow-to-restore-partitions-after-renumbering%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
3
Which "the posts" did you read. I don't know how to solve the problems you might get in Windows after renumbering the partitions. In Linux you have to change all commands or table entries that reference a partition by its number, e.g. replace the
6inmount /dev/sda6 /mntto the new partition number after renumbering. If you change all partition numbers back to their original value everything should work as before.– Bodo
Feb 18 at 12:51
In principle if you know exactly where a partition starts and stops you can just recreate it. Hopefully nothing you have done has corrupted any of your file systems. But you will need to tell us more about what you did (which commands you used) so we can help you undo the damage.
– Philip Couling
Feb 18 at 13:39
@Philip Couling: Restoring MBR is enough for me?
fdiskcan delete the partition and recreate it, MBR seems simple, why don't work?– maggicmuojet
Feb 19 at 5:57
@maggicmuojet the most likely thing is that you didn't re-create them with the same size and position as before. You only have get the position one sector out and you will make the partition unreadable.
– Philip Couling
Feb 19 at 7:53
1
Note that in MBR partitioning scheme, only partitions 1-4 are primary partitions and so their partition information is in the actual MBR block. Partitions with numbers 5 or greater are "logical partitions", meaning that one of the primary partitions must be used as an "extended partition", which can then be further sub-divided into "logical partitions", each of which will have its own partition information block located just before the beginning of that partition. I guess something is wrong with this chaining/encapsulation scheme.
– telcoM
Feb 19 at 8:05