Error when getting information for file - Input/output error
I ran rsync sudo rsync -aE --progress /mnt/seagate/dataset/RD 8* /mnt/backUp/backUp/dataset/ and pressed ctrl-c by mistake. There was a SIG-INT error whic makes sense.
But now, I am not able to access the hard disk mounted on /mnt/backUp.
Whenver I try to access my drive, it says:
This location could not be displayed. Sorry, could not display all the contents of “dataset”: Error when getting information for file '/mnt/backUp/backUp/dataset/RD 838Jun05': Input/output error
output of sudo ll is attached in the image below.
output of sudo ll
I tried running :
sudo smartctl -i /dev/sde2 whose output is
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.2.0-42-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: Seagate
Product: BUP BK
Revision: 0108
User Capacity: 4,000,787,029,504 bytes [4.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
Lowest aligned LBA: 0
Logical block provisioning type unreported, LBPME=0, LBPRZ=0
Logical Unit id: 0x3e41375436453851
Serial number: NA7T6E8Q
Device type: disk
Local Time is: Sun Aug 6 16:55:06 2017 EDT
SMART support is: Unavailable - device lacks SMART capability.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix as well
linux hard-drive backup rsync sudo
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
add a comment |
I ran rsync sudo rsync -aE --progress /mnt/seagate/dataset/RD 8* /mnt/backUp/backUp/dataset/ and pressed ctrl-c by mistake. There was a SIG-INT error whic makes sense.
But now, I am not able to access the hard disk mounted on /mnt/backUp.
Whenver I try to access my drive, it says:
This location could not be displayed. Sorry, could not display all the contents of “dataset”: Error when getting information for file '/mnt/backUp/backUp/dataset/RD 838Jun05': Input/output error
output of sudo ll is attached in the image below.
output of sudo ll
I tried running :
sudo smartctl -i /dev/sde2 whose output is
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.2.0-42-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: Seagate
Product: BUP BK
Revision: 0108
User Capacity: 4,000,787,029,504 bytes [4.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
Lowest aligned LBA: 0
Logical block provisioning type unreported, LBPME=0, LBPRZ=0
Logical Unit id: 0x3e41375436453851
Serial number: NA7T6E8Q
Device type: disk
Local Time is: Sun Aug 6 16:55:06 2017 EDT
SMART support is: Unavailable - device lacks SMART capability.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix as well
linux hard-drive backup rsync sudo
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
I doubt it is a problem with the hard drive. See if you have any process in "device sleep"Sz(I think is the indicator, when you runps). Try remounting the drive, and, perhaps, reporting the bug to whoever supplied the driver / perhaps even to the Linux Kernel people (but check if this isn't a known issue first).
– wvxvw
Aug 7 '17 at 8:05
@wvxvw I tried remounting the drive, even on different computers and it gives me the same error.
– deeplearning
Aug 7 '17 at 10:27
Can you try runningfsckon it? Maybe the filesystem got damaged somehow. hm...
– wvxvw
Aug 7 '17 at 18:32
add a comment |
I ran rsync sudo rsync -aE --progress /mnt/seagate/dataset/RD 8* /mnt/backUp/backUp/dataset/ and pressed ctrl-c by mistake. There was a SIG-INT error whic makes sense.
But now, I am not able to access the hard disk mounted on /mnt/backUp.
Whenver I try to access my drive, it says:
This location could not be displayed. Sorry, could not display all the contents of “dataset”: Error when getting information for file '/mnt/backUp/backUp/dataset/RD 838Jun05': Input/output error
output of sudo ll is attached in the image below.
output of sudo ll
I tried running :
sudo smartctl -i /dev/sde2 whose output is
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.2.0-42-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: Seagate
Product: BUP BK
Revision: 0108
User Capacity: 4,000,787,029,504 bytes [4.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
Lowest aligned LBA: 0
Logical block provisioning type unreported, LBPME=0, LBPRZ=0
Logical Unit id: 0x3e41375436453851
Serial number: NA7T6E8Q
Device type: disk
Local Time is: Sun Aug 6 16:55:06 2017 EDT
SMART support is: Unavailable - device lacks SMART capability.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix as well
linux hard-drive backup rsync sudo
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
I ran rsync sudo rsync -aE --progress /mnt/seagate/dataset/RD 8* /mnt/backUp/backUp/dataset/ and pressed ctrl-c by mistake. There was a SIG-INT error whic makes sense.
But now, I am not able to access the hard disk mounted on /mnt/backUp.
Whenver I try to access my drive, it says:
This location could not be displayed. Sorry, could not display all the contents of “dataset”: Error when getting information for file '/mnt/backUp/backUp/dataset/RD 838Jun05': Input/output error
output of sudo ll is attached in the image below.
output of sudo ll
I tried running :
sudo smartctl -i /dev/sde2 whose output is
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.2.0-42-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: Seagate
Product: BUP BK
Revision: 0108
User Capacity: 4,000,787,029,504 bytes [4.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
Lowest aligned LBA: 0
Logical block provisioning type unreported, LBPME=0, LBPRZ=0
Logical Unit id: 0x3e41375436453851
Serial number: NA7T6E8Q
Device type: disk
Local Time is: Sun Aug 6 16:55:06 2017 EDT
SMART support is: Unavailable - device lacks SMART capability.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix as well
linux hard-drive backup rsync sudo
linux hard-drive backup rsync sudo
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
asked Aug 6 '17 at 21:04
deeplearningdeeplearning
114
114
I doubt it is a problem with the hard drive. See if you have any process in "device sleep"Sz(I think is the indicator, when you runps). Try remounting the drive, and, perhaps, reporting the bug to whoever supplied the driver / perhaps even to the Linux Kernel people (but check if this isn't a known issue first).
– wvxvw
Aug 7 '17 at 8:05
@wvxvw I tried remounting the drive, even on different computers and it gives me the same error.
– deeplearning
Aug 7 '17 at 10:27
Can you try runningfsckon it? Maybe the filesystem got damaged somehow. hm...
– wvxvw
Aug 7 '17 at 18:32
add a comment |
I doubt it is a problem with the hard drive. See if you have any process in "device sleep"Sz(I think is the indicator, when you runps). Try remounting the drive, and, perhaps, reporting the bug to whoever supplied the driver / perhaps even to the Linux Kernel people (but check if this isn't a known issue first).
– wvxvw
Aug 7 '17 at 8:05
@wvxvw I tried remounting the drive, even on different computers and it gives me the same error.
– deeplearning
Aug 7 '17 at 10:27
Can you try runningfsckon it? Maybe the filesystem got damaged somehow. hm...
– wvxvw
Aug 7 '17 at 18:32
I doubt it is a problem with the hard drive. See if you have any process in "device sleep"
Sz (I think is the indicator, when you run ps). Try remounting the drive, and, perhaps, reporting the bug to whoever supplied the driver / perhaps even to the Linux Kernel people (but check if this isn't a known issue first).– wvxvw
Aug 7 '17 at 8:05
I doubt it is a problem with the hard drive. See if you have any process in "device sleep"
Sz (I think is the indicator, when you run ps). Try remounting the drive, and, perhaps, reporting the bug to whoever supplied the driver / perhaps even to the Linux Kernel people (but check if this isn't a known issue first).– wvxvw
Aug 7 '17 at 8:05
@wvxvw I tried remounting the drive, even on different computers and it gives me the same error.
– deeplearning
Aug 7 '17 at 10:27
@wvxvw I tried remounting the drive, even on different computers and it gives me the same error.
– deeplearning
Aug 7 '17 at 10:27
Can you try running
fsck on it? Maybe the filesystem got damaged somehow. hm...– wvxvw
Aug 7 '17 at 18:32
Can you try running
fsck on it? Maybe the filesystem got damaged somehow. hm...– wvxvw
Aug 7 '17 at 18:32
add a comment |
1 Answer
1
active
oldest
votes
I was able to recover my old data by scanning and repairing my disk using Windows OS. You have to right click on your device detected in "My Computer", go to Properties-->Tools and click Scan. It will eventually report errors if any and you can repair them. I was able to remount it in Linux later without an issue.
As quoted from howtogeek" Chkdsk can also optionally scan every sector on a disk volume looking for bad sectors. Bad sectors come in two forms: soft bad sectors, that can occur when data is written badly, and hard bad sectors that can occur because of physical damage to the disk. Chkdsk attempts to fix these problems by repairing soft bad sectors, and marking hard bad sectors so they won’t be used again.
"
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1238298%2ferror-when-getting-information-for-file-input-output-error%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
I was able to recover my old data by scanning and repairing my disk using Windows OS. You have to right click on your device detected in "My Computer", go to Properties-->Tools and click Scan. It will eventually report errors if any and you can repair them. I was able to remount it in Linux later without an issue.
As quoted from howtogeek" Chkdsk can also optionally scan every sector on a disk volume looking for bad sectors. Bad sectors come in two forms: soft bad sectors, that can occur when data is written badly, and hard bad sectors that can occur because of physical damage to the disk. Chkdsk attempts to fix these problems by repairing soft bad sectors, and marking hard bad sectors so they won’t be used again.
"
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
add a comment |
I was able to recover my old data by scanning and repairing my disk using Windows OS. You have to right click on your device detected in "My Computer", go to Properties-->Tools and click Scan. It will eventually report errors if any and you can repair them. I was able to remount it in Linux later without an issue.
As quoted from howtogeek" Chkdsk can also optionally scan every sector on a disk volume looking for bad sectors. Bad sectors come in two forms: soft bad sectors, that can occur when data is written badly, and hard bad sectors that can occur because of physical damage to the disk. Chkdsk attempts to fix these problems by repairing soft bad sectors, and marking hard bad sectors so they won’t be used again.
"
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
add a comment |
I was able to recover my old data by scanning and repairing my disk using Windows OS. You have to right click on your device detected in "My Computer", go to Properties-->Tools and click Scan. It will eventually report errors if any and you can repair them. I was able to remount it in Linux later without an issue.
As quoted from howtogeek" Chkdsk can also optionally scan every sector on a disk volume looking for bad sectors. Bad sectors come in two forms: soft bad sectors, that can occur when data is written badly, and hard bad sectors that can occur because of physical damage to the disk. Chkdsk attempts to fix these problems by repairing soft bad sectors, and marking hard bad sectors so they won’t be used again.
"
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
I was able to recover my old data by scanning and repairing my disk using Windows OS. You have to right click on your device detected in "My Computer", go to Properties-->Tools and click Scan. It will eventually report errors if any and you can repair them. I was able to remount it in Linux later without an issue.
As quoted from howtogeek" Chkdsk can also optionally scan every sector on a disk volume looking for bad sectors. Bad sectors come in two forms: soft bad sectors, that can occur when data is written badly, and hard bad sectors that can occur because of physical damage to the disk. Chkdsk attempts to fix these problems by repairing soft bad sectors, and marking hard bad sectors so they won’t be used again.
"
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
answered Aug 8 '17 at 23:13
deeplearningdeeplearning
114
114
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1238298%2ferror-when-getting-information-for-file-input-output-error%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
I doubt it is a problem with the hard drive. See if you have any process in "device sleep"
Sz(I think is the indicator, when you runps). Try remounting the drive, and, perhaps, reporting the bug to whoever supplied the driver / perhaps even to the Linux Kernel people (but check if this isn't a known issue first).– wvxvw
Aug 7 '17 at 8:05
@wvxvw I tried remounting the drive, even on different computers and it gives me the same error.
– deeplearning
Aug 7 '17 at 10:27
Can you try running
fsckon it? Maybe the filesystem got damaged somehow. hm...– wvxvw
Aug 7 '17 at 18:32