GParted error while expanding file system “Error fsyncing/closing /dev/sdb1: Input/output error”
My expansion Hard disk is having error and some data is lost/corrupted.
I was using GParted to expand a partition. I got this error "Error fsyncing/closing /dev/sdb1: Input/output error".
I have uploaded the Gparted error log at following link:
http://pastebin.com/qMy0VE6a
I tried both Gparted & testdisk to recover data or partition but failed.
Please help to recover my data.
data-recovery gparted
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
|
show 4 more comments
My expansion Hard disk is having error and some data is lost/corrupted.
I was using GParted to expand a partition. I got this error "Error fsyncing/closing /dev/sdb1: Input/output error".
I have uploaded the Gparted error log at following link:
http://pastebin.com/qMy0VE6a
I tried both Gparted & testdisk to recover data or partition but failed.
Please help to recover my data.
data-recovery gparted
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
please usepastebinfor log instead.
– Aizuddin Zali
Oct 13 '15 at 12:51
Tried pastebin earlier but the log file is larger than 512kb. I don't have pro account.
– Amandeep Singh
Oct 13 '15 at 13:04
you can try to snip the logs and just share the relevant one.
– Aizuddin Zali
Oct 13 '15 at 13:13
thanks for guidance. uploaded the significant parts of logs to pastebin.
– Amandeep Singh
Oct 13 '15 at 13:33
looks like the filesystem was corrupted. doe2fsck.
– Aizuddin Zali
Oct 14 '15 at 4:03
|
show 4 more comments
My expansion Hard disk is having error and some data is lost/corrupted.
I was using GParted to expand a partition. I got this error "Error fsyncing/closing /dev/sdb1: Input/output error".
I have uploaded the Gparted error log at following link:
http://pastebin.com/qMy0VE6a
I tried both Gparted & testdisk to recover data or partition but failed.
Please help to recover my data.
data-recovery gparted
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
My expansion Hard disk is having error and some data is lost/corrupted.
I was using GParted to expand a partition. I got this error "Error fsyncing/closing /dev/sdb1: Input/output error".
I have uploaded the Gparted error log at following link:
http://pastebin.com/qMy0VE6a
I tried both Gparted & testdisk to recover data or partition but failed.
Please help to recover my data.
data-recovery gparted
data-recovery gparted
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
edited Oct 13 '15 at 13:33
Amandeep Singh
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
asked Oct 13 '15 at 12:42
Amandeep SinghAmandeep Singh
1981411
1981411
please usepastebinfor log instead.
– Aizuddin Zali
Oct 13 '15 at 12:51
Tried pastebin earlier but the log file is larger than 512kb. I don't have pro account.
– Amandeep Singh
Oct 13 '15 at 13:04
you can try to snip the logs and just share the relevant one.
– Aizuddin Zali
Oct 13 '15 at 13:13
thanks for guidance. uploaded the significant parts of logs to pastebin.
– Amandeep Singh
Oct 13 '15 at 13:33
looks like the filesystem was corrupted. doe2fsck.
– Aizuddin Zali
Oct 14 '15 at 4:03
|
show 4 more comments
please usepastebinfor log instead.
– Aizuddin Zali
Oct 13 '15 at 12:51
Tried pastebin earlier but the log file is larger than 512kb. I don't have pro account.
– Amandeep Singh
Oct 13 '15 at 13:04
you can try to snip the logs and just share the relevant one.
– Aizuddin Zali
Oct 13 '15 at 13:13
thanks for guidance. uploaded the significant parts of logs to pastebin.
– Amandeep Singh
Oct 13 '15 at 13:33
looks like the filesystem was corrupted. doe2fsck.
– Aizuddin Zali
Oct 14 '15 at 4:03
please use
pastebin for log instead.– Aizuddin Zali
Oct 13 '15 at 12:51
please use
pastebin for log instead.– Aizuddin Zali
Oct 13 '15 at 12:51
Tried pastebin earlier but the log file is larger than 512kb. I don't have pro account.
– Amandeep Singh
Oct 13 '15 at 13:04
Tried pastebin earlier but the log file is larger than 512kb. I don't have pro account.
– Amandeep Singh
Oct 13 '15 at 13:04
you can try to snip the logs and just share the relevant one.
– Aizuddin Zali
Oct 13 '15 at 13:13
you can try to snip the logs and just share the relevant one.
– Aizuddin Zali
Oct 13 '15 at 13:13
thanks for guidance. uploaded the significant parts of logs to pastebin.
– Amandeep Singh
Oct 13 '15 at 13:33
thanks for guidance. uploaded the significant parts of logs to pastebin.
– Amandeep Singh
Oct 13 '15 at 13:33
looks like the filesystem was corrupted. do
e2fsck.– Aizuddin Zali
Oct 14 '15 at 4:03
looks like the filesystem was corrupted. do
e2fsck.– Aizuddin Zali
Oct 14 '15 at 4:03
|
show 4 more comments
2 Answers
2
active
oldest
votes
A message such as "Error fsyncing/closing /dev/sdb1: Input/output error" often indicates a hardware problem. This can be as simple as a loose cable, or as serious as a failing drive.
When the error occurs, you can check the output of the dmesg command for any additional details.
Also some hard drives include smart monitoring. You might try using gsmartcontrol to see if there are any indications of poor health for the drive.
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
add a comment |
I got this error on a fairly new and good working drive. It took me ages to realize I had a hard drive password set on the drive on a newer machine and I was using the drive on an older desktop that didn't support the same HD encryption.
Solution? Put it back in the newer machine, remove the HD password in the BIOS and everything works great.
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
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%2f684993%2fgparted-error-while-expanding-file-system-error-fsyncing-closing-dev-sdb1-inp%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
A message such as "Error fsyncing/closing /dev/sdb1: Input/output error" often indicates a hardware problem. This can be as simple as a loose cable, or as serious as a failing drive.
When the error occurs, you can check the output of the dmesg command for any additional details.
Also some hard drives include smart monitoring. You might try using gsmartcontrol to see if there are any indications of poor health for the drive.
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
add a comment |
A message such as "Error fsyncing/closing /dev/sdb1: Input/output error" often indicates a hardware problem. This can be as simple as a loose cable, or as serious as a failing drive.
When the error occurs, you can check the output of the dmesg command for any additional details.
Also some hard drives include smart monitoring. You might try using gsmartcontrol to see if there are any indications of poor health for the drive.
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
add a comment |
A message such as "Error fsyncing/closing /dev/sdb1: Input/output error" often indicates a hardware problem. This can be as simple as a loose cable, or as serious as a failing drive.
When the error occurs, you can check the output of the dmesg command for any additional details.
Also some hard drives include smart monitoring. You might try using gsmartcontrol to see if there are any indications of poor health for the drive.
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
A message such as "Error fsyncing/closing /dev/sdb1: Input/output error" often indicates a hardware problem. This can be as simple as a loose cable, or as serious as a failing drive.
When the error occurs, you can check the output of the dmesg command for any additional details.
Also some hard drives include smart monitoring. You might try using gsmartcontrol to see if there are any indications of poor health for the drive.
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
answered Oct 20 '15 at 16:47
Curtis GedakCurtis Gedak
88654
88654
add a comment |
add a comment |
I got this error on a fairly new and good working drive. It took me ages to realize I had a hard drive password set on the drive on a newer machine and I was using the drive on an older desktop that didn't support the same HD encryption.
Solution? Put it back in the newer machine, remove the HD password in the BIOS and everything works great.
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
add a comment |
I got this error on a fairly new and good working drive. It took me ages to realize I had a hard drive password set on the drive on a newer machine and I was using the drive on an older desktop that didn't support the same HD encryption.
Solution? Put it back in the newer machine, remove the HD password in the BIOS and everything works great.
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
add a comment |
I got this error on a fairly new and good working drive. It took me ages to realize I had a hard drive password set on the drive on a newer machine and I was using the drive on an older desktop that didn't support the same HD encryption.
Solution? Put it back in the newer machine, remove the HD password in the BIOS and everything works great.
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
I got this error on a fairly new and good working drive. It took me ages to realize I had a hard drive password set on the drive on a newer machine and I was using the drive on an older desktop that didn't support the same HD encryption.
Solution? Put it back in the newer machine, remove the HD password in the BIOS and everything works great.
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
answered Jan 26 '17 at 4:46
Ryan ShillingtonRyan Shillington
1114
1114
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%2f684993%2fgparted-error-while-expanding-file-system-error-fsyncing-closing-dev-sdb1-inp%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
please use
pastebinfor log instead.– Aizuddin Zali
Oct 13 '15 at 12:51
Tried pastebin earlier but the log file is larger than 512kb. I don't have pro account.
– Amandeep Singh
Oct 13 '15 at 13:04
you can try to snip the logs and just share the relevant one.
– Aizuddin Zali
Oct 13 '15 at 13:13
thanks for guidance. uploaded the significant parts of logs to pastebin.
– Amandeep Singh
Oct 13 '15 at 13:33
looks like the filesystem was corrupted. do
e2fsck.– Aizuddin Zali
Oct 14 '15 at 4:03