The CRC for the main partition and back up partition table are invalid
I've been having problems with my HDD since I tried dual booting ubuntu 14.04 with windows 8.1. When I was installing from the ubuntu installer I was receiving "input/output error during write on /dev/sda".
I can't do anything in gdisk, it seems that both the main and the back up GPT header are corrupt. It seems that the back up header is unable to save whenever I do anything and try to write to the disk. At this point, I've already lost all my data, I don't have any of my windows partitions, and I just want to start fresh and be able to reinstall either windows or linux. Any help is greatly appreciated
When I try using fdisk:
$ sudo fdisk /dev/sda
I get "The backup GPT table is corrupt, but the primary appears OK, so that will be used."
I tried to use
g create a new empty GPT partition table
and
w write table to disk and exit
I get "failed to write disklabel: Input/output error"
v verify the partition table
I get
No errors detected.
Header version: 1.0
Using 0 out of 128 partitions.
A total of 1953525101 free sectors is available in 1 segment.
using gdisk:
$ sudo gdisk /dev/sda
I receive
Warning! Error 5 reading partition table for CRC check!
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
when I enter v to verify my disk i get
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Identified 1 problems!
I have tried loading back up and main gpt tables but no matter what I do, when I enter w to write table to disk and exit I receive this error:
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
partitioning hard-drive uefi gpt fdisk
add a comment |
I've been having problems with my HDD since I tried dual booting ubuntu 14.04 with windows 8.1. When I was installing from the ubuntu installer I was receiving "input/output error during write on /dev/sda".
I can't do anything in gdisk, it seems that both the main and the back up GPT header are corrupt. It seems that the back up header is unable to save whenever I do anything and try to write to the disk. At this point, I've already lost all my data, I don't have any of my windows partitions, and I just want to start fresh and be able to reinstall either windows or linux. Any help is greatly appreciated
When I try using fdisk:
$ sudo fdisk /dev/sda
I get "The backup GPT table is corrupt, but the primary appears OK, so that will be used."
I tried to use
g create a new empty GPT partition table
and
w write table to disk and exit
I get "failed to write disklabel: Input/output error"
v verify the partition table
I get
No errors detected.
Header version: 1.0
Using 0 out of 128 partitions.
A total of 1953525101 free sectors is available in 1 segment.
using gdisk:
$ sudo gdisk /dev/sda
I receive
Warning! Error 5 reading partition table for CRC check!
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
when I enter v to verify my disk i get
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Identified 1 problems!
I have tried loading back up and main gpt tables but no matter what I do, when I enter w to write table to disk and exit I receive this error:
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
partitioning hard-drive uefi gpt fdisk
More detailed errors about the "IO error" can be found after by runningdmesg
, but most likely, your drive is failing.
– psusi
Jun 7 '15 at 23:31
add a comment |
I've been having problems with my HDD since I tried dual booting ubuntu 14.04 with windows 8.1. When I was installing from the ubuntu installer I was receiving "input/output error during write on /dev/sda".
I can't do anything in gdisk, it seems that both the main and the back up GPT header are corrupt. It seems that the back up header is unable to save whenever I do anything and try to write to the disk. At this point, I've already lost all my data, I don't have any of my windows partitions, and I just want to start fresh and be able to reinstall either windows or linux. Any help is greatly appreciated
When I try using fdisk:
$ sudo fdisk /dev/sda
I get "The backup GPT table is corrupt, but the primary appears OK, so that will be used."
I tried to use
g create a new empty GPT partition table
and
w write table to disk and exit
I get "failed to write disklabel: Input/output error"
v verify the partition table
I get
No errors detected.
Header version: 1.0
Using 0 out of 128 partitions.
A total of 1953525101 free sectors is available in 1 segment.
using gdisk:
$ sudo gdisk /dev/sda
I receive
Warning! Error 5 reading partition table for CRC check!
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
when I enter v to verify my disk i get
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Identified 1 problems!
I have tried loading back up and main gpt tables but no matter what I do, when I enter w to write table to disk and exit I receive this error:
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
partitioning hard-drive uefi gpt fdisk
I've been having problems with my HDD since I tried dual booting ubuntu 14.04 with windows 8.1. When I was installing from the ubuntu installer I was receiving "input/output error during write on /dev/sda".
I can't do anything in gdisk, it seems that both the main and the back up GPT header are corrupt. It seems that the back up header is unable to save whenever I do anything and try to write to the disk. At this point, I've already lost all my data, I don't have any of my windows partitions, and I just want to start fresh and be able to reinstall either windows or linux. Any help is greatly appreciated
When I try using fdisk:
$ sudo fdisk /dev/sda
I get "The backup GPT table is corrupt, but the primary appears OK, so that will be used."
I tried to use
g create a new empty GPT partition table
and
w write table to disk and exit
I get "failed to write disklabel: Input/output error"
v verify the partition table
I get
No errors detected.
Header version: 1.0
Using 0 out of 128 partitions.
A total of 1953525101 free sectors is available in 1 segment.
using gdisk:
$ sudo gdisk /dev/sda
I receive
Warning! Error 5 reading partition table for CRC check!
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
when I enter v to verify my disk i get
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Identified 1 problems!
I have tried loading back up and main gpt tables but no matter what I do, when I enter w to write table to disk and exit I receive this error:
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
partitioning hard-drive uefi gpt fdisk
partitioning hard-drive uefi gpt fdisk
asked Jun 7 '15 at 17:43
JacobJacob
111
111
More detailed errors about the "IO error" can be found after by runningdmesg
, but most likely, your drive is failing.
– psusi
Jun 7 '15 at 23:31
add a comment |
More detailed errors about the "IO error" can be found after by runningdmesg
, but most likely, your drive is failing.
– psusi
Jun 7 '15 at 23:31
More detailed errors about the "IO error" can be found after by running
dmesg
, but most likely, your drive is failing.– psusi
Jun 7 '15 at 23:31
More detailed errors about the "IO error" can be found after by running
dmesg
, but most likely, your drive is failing.– psusi
Jun 7 '15 at 23:31
add a comment |
1 Answer
1
active
oldest
votes
It sounds like you're encountering I/O errors. Such problems are usually caused by failing hardware. If you're lucky, this might be something simple and cheap to fix like a loose or defective cable. It could also be a failing hard disk, though. I recommend you run a SMART test on your hard disk. If you need help interpreting the results, post back with details. (Edit your question to include a screen shot or paste text-mode output to a pastebin site and post the URL to your document here.)
I/O errors can also be caused by buggy drivers. This is pretty rare, though. If your problems occur only in one OS, that might be the explanation.
Yet another possibility is that the Host Protected Area (HPA) may be set. This can sometimes cause problems, especially if you mix older and newer Linux kernels, since some older kernels ignore the HPA, causing a mis-match in perceived disk size and where GPT backup data structures reside. I don't think this hypothesis explains your symptoms all that well, but it's worth mentioning. You can type sudo hdparm -N /dev/sda
to see if HPA is enabled on /dev/sda
.
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
});
}
});
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%2f633465%2fthe-crc-for-the-main-partition-and-back-up-partition-table-are-invalid%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It sounds like you're encountering I/O errors. Such problems are usually caused by failing hardware. If you're lucky, this might be something simple and cheap to fix like a loose or defective cable. It could also be a failing hard disk, though. I recommend you run a SMART test on your hard disk. If you need help interpreting the results, post back with details. (Edit your question to include a screen shot or paste text-mode output to a pastebin site and post the URL to your document here.)
I/O errors can also be caused by buggy drivers. This is pretty rare, though. If your problems occur only in one OS, that might be the explanation.
Yet another possibility is that the Host Protected Area (HPA) may be set. This can sometimes cause problems, especially if you mix older and newer Linux kernels, since some older kernels ignore the HPA, causing a mis-match in perceived disk size and where GPT backup data structures reside. I don't think this hypothesis explains your symptoms all that well, but it's worth mentioning. You can type sudo hdparm -N /dev/sda
to see if HPA is enabled on /dev/sda
.
add a comment |
It sounds like you're encountering I/O errors. Such problems are usually caused by failing hardware. If you're lucky, this might be something simple and cheap to fix like a loose or defective cable. It could also be a failing hard disk, though. I recommend you run a SMART test on your hard disk. If you need help interpreting the results, post back with details. (Edit your question to include a screen shot or paste text-mode output to a pastebin site and post the URL to your document here.)
I/O errors can also be caused by buggy drivers. This is pretty rare, though. If your problems occur only in one OS, that might be the explanation.
Yet another possibility is that the Host Protected Area (HPA) may be set. This can sometimes cause problems, especially if you mix older and newer Linux kernels, since some older kernels ignore the HPA, causing a mis-match in perceived disk size and where GPT backup data structures reside. I don't think this hypothesis explains your symptoms all that well, but it's worth mentioning. You can type sudo hdparm -N /dev/sda
to see if HPA is enabled on /dev/sda
.
add a comment |
It sounds like you're encountering I/O errors. Such problems are usually caused by failing hardware. If you're lucky, this might be something simple and cheap to fix like a loose or defective cable. It could also be a failing hard disk, though. I recommend you run a SMART test on your hard disk. If you need help interpreting the results, post back with details. (Edit your question to include a screen shot or paste text-mode output to a pastebin site and post the URL to your document here.)
I/O errors can also be caused by buggy drivers. This is pretty rare, though. If your problems occur only in one OS, that might be the explanation.
Yet another possibility is that the Host Protected Area (HPA) may be set. This can sometimes cause problems, especially if you mix older and newer Linux kernels, since some older kernels ignore the HPA, causing a mis-match in perceived disk size and where GPT backup data structures reside. I don't think this hypothesis explains your symptoms all that well, but it's worth mentioning. You can type sudo hdparm -N /dev/sda
to see if HPA is enabled on /dev/sda
.
It sounds like you're encountering I/O errors. Such problems are usually caused by failing hardware. If you're lucky, this might be something simple and cheap to fix like a loose or defective cable. It could also be a failing hard disk, though. I recommend you run a SMART test on your hard disk. If you need help interpreting the results, post back with details. (Edit your question to include a screen shot or paste text-mode output to a pastebin site and post the URL to your document here.)
I/O errors can also be caused by buggy drivers. This is pretty rare, though. If your problems occur only in one OS, that might be the explanation.
Yet another possibility is that the Host Protected Area (HPA) may be set. This can sometimes cause problems, especially if you mix older and newer Linux kernels, since some older kernels ignore the HPA, causing a mis-match in perceived disk size and where GPT backup data structures reside. I don't think this hypothesis explains your symptoms all that well, but it's worth mentioning. You can type sudo hdparm -N /dev/sda
to see if HPA is enabled on /dev/sda
.
edited Apr 13 '17 at 12:24
Community♦
1
1
answered Jun 7 '15 at 22:44
Rod SmithRod Smith
35.7k43970
35.7k43970
add a comment |
add a comment |
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%2f633465%2fthe-crc-for-the-main-partition-and-back-up-partition-table-are-invalid%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
More detailed errors about the "IO error" can be found after by running
dmesg
, but most likely, your drive is failing.– psusi
Jun 7 '15 at 23:31