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 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.
I am still able to move the files that were already existing though, which I am assuming, means that only few sectors went bad.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix
as well
partitioning mount hard-drive backup rsync
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 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.
I am still able to move the files that were already existing though, which I am assuming, means that only few sectors went bad.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix
as well
partitioning mount hard-drive backup rsync
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 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.
I am still able to move the files that were already existing though, which I am assuming, means that only few sectors went bad.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix
as well
partitioning mount hard-drive backup rsync
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 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.
I am still able to move the files that were already existing though, which I am assuming, means that only few sectors went bad.
Can you please tell me if there is any way I could fix this? I am not able to do ntfs-fix
as well
partitioning mount hard-drive backup rsync
partitioning mount hard-drive backup rsync
edited Aug 7 '17 at 0:23
deeplearning
asked Aug 6 '17 at 22:15
deeplearningdeeplearning
113
113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Input/output error
is bad news in general. It means that the drive is faulty and is unable to read and/or write data from/to the spinning plates.
If this is a new drive I and is still under warranty I suggest you return it and get a new one.
You may try command dmesg
immediately after you get that I/O error and you will see a lot of kernel mumbo-jumbo about how it is unable to use the device. Not very helpful to the regular user but I am sure some kernel developer is in a position to understand it.
Thanks for your reply. I am still able to move the unbroken files though, which I am assuming, means that only few sectors went bad. Is there any way I could fix them?
– deeplearning
Aug 7 '17 at 0:22
If your drive is formatted ntfs you might be better off attaching it to a Windows PC and let it do a full scan. There is a utilitybadbclocks
which integrates nicely with Ext2/3/4 filesystems but I don't think it would be much of a help for you. Regardless, I wouldn't trust that drive.
– sмurf
Aug 7 '17 at 1:15
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%2f943691%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
Input/output error
is bad news in general. It means that the drive is faulty and is unable to read and/or write data from/to the spinning plates.
If this is a new drive I and is still under warranty I suggest you return it and get a new one.
You may try command dmesg
immediately after you get that I/O error and you will see a lot of kernel mumbo-jumbo about how it is unable to use the device. Not very helpful to the regular user but I am sure some kernel developer is in a position to understand it.
Thanks for your reply. I am still able to move the unbroken files though, which I am assuming, means that only few sectors went bad. Is there any way I could fix them?
– deeplearning
Aug 7 '17 at 0:22
If your drive is formatted ntfs you might be better off attaching it to a Windows PC and let it do a full scan. There is a utilitybadbclocks
which integrates nicely with Ext2/3/4 filesystems but I don't think it would be much of a help for you. Regardless, I wouldn't trust that drive.
– sмurf
Aug 7 '17 at 1:15
add a comment |
Input/output error
is bad news in general. It means that the drive is faulty and is unable to read and/or write data from/to the spinning plates.
If this is a new drive I and is still under warranty I suggest you return it and get a new one.
You may try command dmesg
immediately after you get that I/O error and you will see a lot of kernel mumbo-jumbo about how it is unable to use the device. Not very helpful to the regular user but I am sure some kernel developer is in a position to understand it.
Thanks for your reply. I am still able to move the unbroken files though, which I am assuming, means that only few sectors went bad. Is there any way I could fix them?
– deeplearning
Aug 7 '17 at 0:22
If your drive is formatted ntfs you might be better off attaching it to a Windows PC and let it do a full scan. There is a utilitybadbclocks
which integrates nicely with Ext2/3/4 filesystems but I don't think it would be much of a help for you. Regardless, I wouldn't trust that drive.
– sмurf
Aug 7 '17 at 1:15
add a comment |
Input/output error
is bad news in general. It means that the drive is faulty and is unable to read and/or write data from/to the spinning plates.
If this is a new drive I and is still under warranty I suggest you return it and get a new one.
You may try command dmesg
immediately after you get that I/O error and you will see a lot of kernel mumbo-jumbo about how it is unable to use the device. Not very helpful to the regular user but I am sure some kernel developer is in a position to understand it.
Input/output error
is bad news in general. It means that the drive is faulty and is unable to read and/or write data from/to the spinning plates.
If this is a new drive I and is still under warranty I suggest you return it and get a new one.
You may try command dmesg
immediately after you get that I/O error and you will see a lot of kernel mumbo-jumbo about how it is unable to use the device. Not very helpful to the regular user but I am sure some kernel developer is in a position to understand it.
answered Aug 7 '17 at 0:16
sмurfsмurf
4,11911628
4,11911628
Thanks for your reply. I am still able to move the unbroken files though, which I am assuming, means that only few sectors went bad. Is there any way I could fix them?
– deeplearning
Aug 7 '17 at 0:22
If your drive is formatted ntfs you might be better off attaching it to a Windows PC and let it do a full scan. There is a utilitybadbclocks
which integrates nicely with Ext2/3/4 filesystems but I don't think it would be much of a help for you. Regardless, I wouldn't trust that drive.
– sмurf
Aug 7 '17 at 1:15
add a comment |
Thanks for your reply. I am still able to move the unbroken files though, which I am assuming, means that only few sectors went bad. Is there any way I could fix them?
– deeplearning
Aug 7 '17 at 0:22
If your drive is formatted ntfs you might be better off attaching it to a Windows PC and let it do a full scan. There is a utilitybadbclocks
which integrates nicely with Ext2/3/4 filesystems but I don't think it would be much of a help for you. Regardless, I wouldn't trust that drive.
– sмurf
Aug 7 '17 at 1:15
Thanks for your reply. I am still able to move the unbroken files though, which I am assuming, means that only few sectors went bad. Is there any way I could fix them?
– deeplearning
Aug 7 '17 at 0:22
Thanks for your reply. I am still able to move the unbroken files though, which I am assuming, means that only few sectors went bad. Is there any way I could fix them?
– deeplearning
Aug 7 '17 at 0:22
If your drive is formatted ntfs you might be better off attaching it to a Windows PC and let it do a full scan. There is a utility
badbclocks
which integrates nicely with Ext2/3/4 filesystems but I don't think it would be much of a help for you. Regardless, I wouldn't trust that drive.– sмurf
Aug 7 '17 at 1:15
If your drive is formatted ntfs you might be better off attaching it to a Windows PC and let it do a full scan. There is a utility
badbclocks
which integrates nicely with Ext2/3/4 filesystems but I don't think it would be much of a help for you. Regardless, I wouldn't trust that drive.– sмurf
Aug 7 '17 at 1:15
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%2f943691%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