HDD produces corrupted files, could it be the enclosure?
up vote
-1
down vote
favorite
I've purchased a new HDD and installed it in old enclosure to make it an external drive for my media center.
After not being able to see any movie from this disk, because there were pixelations and strange colors during movie playback, and spending enough time in troubleshooting decoding options, I did a test playing back the movie on my laptop before copying it over to the external HDD. And it played back fine. While the same movie being copied to the external HDD and then back to the laptop did not.
So, I did a simple experiment with plain text files, and found out that files are getting corrupted in sizes over 100MB.
Here is an example showing the md5sum hash of a plain txt file when copied to the disk (Ovelix2) and then read back:
osmc@gimli:~$ cp 1GB /media/Ovelix2/
osmc@gimli:~$ cp /media/Ovelix2/1GB 1GB_FromOvelix
osmc@gimli:~$ md5sum 1GB*
c0744c4f34c41beda77c690f4d0ef018 1GB
7e9ed91cee56f406f5a3646c3b413e61 1GB_FromOvelix
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
265523f1120f1a0ce0e82e5308312018 /media/Ovelix2/1GB
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
8f0bbe29cfa531c165deb9efec91ca5a /media/Ovelix2/1GB
osmc@gimli:~$
Everytime I read the file from the disk I get a different one.
I even saw the corruptions in the txt file, by using diff.
smartctl tool and badblocks did not reveal any problem on the disk.
Question is could the enclosure electronics (SATA to USB), e.g. some buffers, be the cause of the corruption? Or should I return the disk and get a replacement?
I don't have spare disk or enclosure, to test combinations.
hard-drive external-hard-drive file-corruption
asked Nov 27 at 21:24
athanassis
1022
add a comment |
up vote
-1
down vote
favorite
I've purchased a new HDD and installed it in old enclosure to make it an external drive for my media center.
After not being able to see any movie from this disk, because there were pixelations and strange colors during movie playback, and spending enough time in troubleshooting decoding options, I did a test playing back the movie on my laptop before copying it over to the external HDD. And it played back fine. While the same movie being copied to the external HDD and then back to the laptop did not.
So, I did a simple experiment with plain text files, and found out that files are getting corrupted in sizes over 100MB.
Here is an example showing the md5sum hash of a plain txt file when copied to the disk (Ovelix2) and then read back:
osmc@gimli:~$ cp 1GB /media/Ovelix2/
osmc@gimli:~$ cp /media/Ovelix2/1GB 1GB_FromOvelix
osmc@gimli:~$ md5sum 1GB*
c0744c4f34c41beda77c690f4d0ef018 1GB
7e9ed91cee56f406f5a3646c3b413e61 1GB_FromOvelix
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
265523f1120f1a0ce0e82e5308312018 /media/Ovelix2/1GB
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
8f0bbe29cfa531c165deb9efec91ca5a /media/Ovelix2/1GB
osmc@gimli:~$
Everytime I read the file from the disk I get a different one.
I even saw the corruptions in the txt file, by using diff.
smartctl tool and badblocks did not reveal any problem on the disk.
Question is could the enclosure electronics (SATA to USB), e.g. some buffers, be the cause of the corruption? Or should I return the disk and get a replacement?
I don't have spare disk or enclosure, to test combinations.
hard-drive external-hard-drive file-corruption
asked Nov 27 at 21:24
athanassis
1022
Just seeing different hashes may not mean all that much (the difference may not be anything that actually affects the file). However, if you compare the files with diff and see corruption, that's a different story. Can you elaborate on the nature of the corruption you saw? Also, are you saying that the behavior isn't consistent from time to time (you copy the same file twice and get different results each time)?
– fixer1234
Nov 29 at 4:22
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I've purchased a new HDD and installed it in old enclosure to make it an external drive for my media center.
After not being able to see any movie from this disk, because there were pixelations and strange colors during movie playback, and spending enough time in troubleshooting decoding options, I did a test playing back the movie on my laptop before copying it over to the external HDD. And it played back fine. While the same movie being copied to the external HDD and then back to the laptop did not.
So, I did a simple experiment with plain text files, and found out that files are getting corrupted in sizes over 100MB.
Here is an example showing the md5sum hash of a plain txt file when copied to the disk (Ovelix2) and then read back:
osmc@gimli:~$ cp 1GB /media/Ovelix2/
osmc@gimli:~$ cp /media/Ovelix2/1GB 1GB_FromOvelix
osmc@gimli:~$ md5sum 1GB*
c0744c4f34c41beda77c690f4d0ef018 1GB
7e9ed91cee56f406f5a3646c3b413e61 1GB_FromOvelix
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
265523f1120f1a0ce0e82e5308312018 /media/Ovelix2/1GB
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
8f0bbe29cfa531c165deb9efec91ca5a /media/Ovelix2/1GB
osmc@gimli:~$
Everytime I read the file from the disk I get a different one.
I even saw the corruptions in the txt file, by using diff.
smartctl tool and badblocks did not reveal any problem on the disk.
Question is could the enclosure electronics (SATA to USB), e.g. some buffers, be the cause of the corruption? Or should I return the disk and get a replacement?
I don't have spare disk or enclosure, to test combinations.
hard-drive external-hard-drive file-corruption
asked Nov 27 at 21:24
athanassis
1022
I've purchased a new HDD and installed it in old enclosure to make it an external drive for my media center.
After not being able to see any movie from this disk, because there were pixelations and strange colors during movie playback, and spending enough time in troubleshooting decoding options, I did a test playing back the movie on my laptop before copying it over to the external HDD. And it played back fine. While the same movie being copied to the external HDD and then back to the laptop did not.
So, I did a simple experiment with plain text files, and found out that files are getting corrupted in sizes over 100MB.
Here is an example showing the md5sum hash of a plain txt file when copied to the disk (Ovelix2) and then read back:
osmc@gimli:~$ cp 1GB /media/Ovelix2/
osmc@gimli:~$ cp /media/Ovelix2/1GB 1GB_FromOvelix
osmc@gimli:~$ md5sum 1GB*
c0744c4f34c41beda77c690f4d0ef018 1GB
7e9ed91cee56f406f5a3646c3b413e61 1GB_FromOvelix
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
265523f1120f1a0ce0e82e5308312018 /media/Ovelix2/1GB
osmc@gimli:~$ md5sum /media/Ovelix2/1GB
8f0bbe29cfa531c165deb9efec91ca5a /media/Ovelix2/1GB
osmc@gimli:~$
Everytime I read the file from the disk I get a different one.
I even saw the corruptions in the txt file, by using diff.
smartctl tool and badblocks did not reveal any problem on the disk.
Question is could the enclosure electronics (SATA to USB), e.g. some buffers, be the cause of the corruption? Or should I return the disk and get a replacement?
I don't have spare disk or enclosure, to test combinations.
hard-drive external-hard-drive file-corruption
hard-drive external-hard-drive file-corruption
asked Nov 27 at 21:24
athanassis
1022
asked Nov 27 at 21:24
athanassis
1022
asked Nov 27 at 21:24
athanassis
1022
asked Nov 27 at 21:24
athanassis
1022
asked Nov 27 at 21:24
athanassis
1022
1022
Just seeing different hashes may not mean all that much (the difference may not be anything that actually affects the file). However, if you compare the files with diff and see corruption, that's a different story. Can you elaborate on the nature of the corruption you saw? Also, are you saying that the behavior isn't consistent from time to time (you copy the same file twice and get different results each time)?
– fixer1234
Nov 29 at 4:22
add a comment |
Just seeing different hashes may not mean all that much (the difference may not be anything that actually affects the file). However, if you compare the files with diff and see corruption, that's a different story. Can you elaborate on the nature of the corruption you saw? Also, are you saying that the behavior isn't consistent from time to time (you copy the same file twice and get different results each time)?
– fixer1234
Nov 29 at 4:22
Just seeing different hashes may not mean all that much (the difference may not be anything that actually affects the file). However, if you compare the files with diff and see corruption, that's a different story. Can you elaborate on the nature of the corruption you saw? Also, are you saying that the behavior isn't consistent from time to time (you copy the same file twice and get different results each time)?
– fixer1234
Nov 29 at 4:22
Just seeing different hashes may not mean all that much (the difference may not be anything that actually affects the file). However, if you compare the files with diff and see corruption, that's a different story. Can you elaborate on the nature of the corruption you saw? Also, are you saying that the behavior isn't consistent from time to time (you copy the same file twice and get different results each time)?
– fixer1234
Nov 29 at 4:22
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Could the enclosure electronics be the cause of the corruption?
With any electronic device, there's always a possibility of it malfunctioning. So you can't rule that out. I've run into strange issues, myself, where the enclosure USB interface caused problems, even when it was apparently working properly.
In my case, it didn't involve any form of file modification or corruption; mine have all been in the nature of compatibility issues between either the drive and the enclosure, or the enclosure vs. other enclosures connected concurrently. Everything worked properly in most conditions, but failed in strange ways in certain situations.
One involved the drive working fine when used for storage, but causing unusual symptoms when using it as a system drive for certain Linux distros but not others. Another involved plugging in one drive after having booted on another external drive (but no issue if the sequence was reversed). These strange behaviors involved three or four different enclosures, and it was traced to the enclosure electronics; the drives, themselves, had no issues at all if inserted in a different enclosure.
My symptoms were totally different from yours, but it's evidence that the enclosure's interface can misbehave, even when appearing to be operational.
Should I return the disk and get a replacement?
Your testing indicates that the drive doesn't appear to have a problem. Before returning it, I would get another enclosure of a different brand, or test the drive with a USB adapter. Either one is inexpensive, and will give you the tools to diagnose the problem.
answered Nov 29 at 4:05
fixer1234
17.5k144281
add a comment |
up vote
-1
down vote
Yes. The power supply for the external chassis could generate interference adequate to disrupt file transfers, for one thing.
answered Nov 27 at 21:46
K7AAY
3,26021437
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Could the enclosure electronics be the cause of the corruption?
With any electronic device, there's always a possibility of it malfunctioning. So you can't rule that out. I've run into strange issues, myself, where the enclosure USB interface caused problems, even when it was apparently working properly.
In my case, it didn't involve any form of file modification or corruption; mine have all been in the nature of compatibility issues between either the drive and the enclosure, or the enclosure vs. other enclosures connected concurrently. Everything worked properly in most conditions, but failed in strange ways in certain situations.
One involved the drive working fine when used for storage, but causing unusual symptoms when using it as a system drive for certain Linux distros but not others. Another involved plugging in one drive after having booted on another external drive (but no issue if the sequence was reversed). These strange behaviors involved three or four different enclosures, and it was traced to the enclosure electronics; the drives, themselves, had no issues at all if inserted in a different enclosure.
My symptoms were totally different from yours, but it's evidence that the enclosure's interface can misbehave, even when appearing to be operational.
Should I return the disk and get a replacement?
Your testing indicates that the drive doesn't appear to have a problem. Before returning it, I would get another enclosure of a different brand, or test the drive with a USB adapter. Either one is inexpensive, and will give you the tools to diagnose the problem.
answered Nov 29 at 4:05
fixer1234
17.5k144281
add a comment |
up vote
0
down vote
Could the enclosure electronics be the cause of the corruption?
With any electronic device, there's always a possibility of it malfunctioning. So you can't rule that out. I've run into strange issues, myself, where the enclosure USB interface caused problems, even when it was apparently working properly.
In my case, it didn't involve any form of file modification or corruption; mine have all been in the nature of compatibility issues between either the drive and the enclosure, or the enclosure vs. other enclosures connected concurrently. Everything worked properly in most conditions, but failed in strange ways in certain situations.
One involved the drive working fine when used for storage, but causing unusual symptoms when using it as a system drive for certain Linux distros but not others. Another involved plugging in one drive after having booted on another external drive (but no issue if the sequence was reversed). These strange behaviors involved three or four different enclosures, and it was traced to the enclosure electronics; the drives, themselves, had no issues at all if inserted in a different enclosure.
My symptoms were totally different from yours, but it's evidence that the enclosure's interface can misbehave, even when appearing to be operational.
Should I return the disk and get a replacement?
Your testing indicates that the drive doesn't appear to have a problem. Before returning it, I would get another enclosure of a different brand, or test the drive with a USB adapter. Either one is inexpensive, and will give you the tools to diagnose the problem.
answered Nov 29 at 4:05
fixer1234
17.5k144281
add a comment |
up vote
0
down vote
up vote
0
down vote
Could the enclosure electronics be the cause of the corruption?
With any electronic device, there's always a possibility of it malfunctioning. So you can't rule that out. I've run into strange issues, myself, where the enclosure USB interface caused problems, even when it was apparently working properly.
In my case, it didn't involve any form of file modification or corruption; mine have all been in the nature of compatibility issues between either the drive and the enclosure, or the enclosure vs. other enclosures connected concurrently. Everything worked properly in most conditions, but failed in strange ways in certain situations.
One involved the drive working fine when used for storage, but causing unusual symptoms when using it as a system drive for certain Linux distros but not others. Another involved plugging in one drive after having booted on another external drive (but no issue if the sequence was reversed). These strange behaviors involved three or four different enclosures, and it was traced to the enclosure electronics; the drives, themselves, had no issues at all if inserted in a different enclosure.
My symptoms were totally different from yours, but it's evidence that the enclosure's interface can misbehave, even when appearing to be operational.
Should I return the disk and get a replacement?
Your testing indicates that the drive doesn't appear to have a problem. Before returning it, I would get another enclosure of a different brand, or test the drive with a USB adapter. Either one is inexpensive, and will give you the tools to diagnose the problem.
answered Nov 29 at 4:05
fixer1234
17.5k144281
Could the enclosure electronics be the cause of the corruption?
With any electronic device, there's always a possibility of it malfunctioning. So you can't rule that out. I've run into strange issues, myself, where the enclosure USB interface caused problems, even when it was apparently working properly.
In my case, it didn't involve any form of file modification or corruption; mine have all been in the nature of compatibility issues between either the drive and the enclosure, or the enclosure vs. other enclosures connected concurrently. Everything worked properly in most conditions, but failed in strange ways in certain situations.
One involved the drive working fine when used for storage, but causing unusual symptoms when using it as a system drive for certain Linux distros but not others. Another involved plugging in one drive after having booted on another external drive (but no issue if the sequence was reversed). These strange behaviors involved three or four different enclosures, and it was traced to the enclosure electronics; the drives, themselves, had no issues at all if inserted in a different enclosure.
My symptoms were totally different from yours, but it's evidence that the enclosure's interface can misbehave, even when appearing to be operational.
Should I return the disk and get a replacement?
Your testing indicates that the drive doesn't appear to have a problem. Before returning it, I would get another enclosure of a different brand, or test the drive with a USB adapter. Either one is inexpensive, and will give you the tools to diagnose the problem.
answered Nov 29 at 4:05
fixer1234
17.5k144281
edited Nov 29 at 4:23
answered Nov 29 at 4:05
fixer1234
17.5k144281
answered Nov 29 at 4:05
fixer1234
17.5k144281
answered Nov 29 at 4:05
fixer1234
17.5k144281
17.5k144281
add a comment |
add a comment |
up vote
-1
down vote
Yes. The power supply for the external chassis could generate interference adequate to disrupt file transfers, for one thing.
answered Nov 27 at 21:46
K7AAY
3,26021437
add a comment |
up vote
-1
down vote
Yes. The power supply for the external chassis could generate interference adequate to disrupt file transfers, for one thing.
answered Nov 27 at 21:46
K7AAY
3,26021437
add a comment |
up vote
-1
down vote
up vote
-1
down vote
Yes. The power supply for the external chassis could generate interference adequate to disrupt file transfers, for one thing.
answered Nov 27 at 21:46
K7AAY
3,26021437
Yes. The power supply for the external chassis could generate interference adequate to disrupt file transfers, for one thing.
answered Nov 27 at 21:46
K7AAY
3,26021437
answered Nov 27 at 21:46
K7AAY
3,26021437
answered Nov 27 at 21:46
K7AAY
3,26021437
answered Nov 27 at 21:46
K7AAY
3,26021437
3,26021437
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1378892%2fhdd-produces-corrupted-files-could-it-be-the-enclosure%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
Just seeing different hashes may not mean all that much (the difference may not be anything that actually affects the file). However, if you compare the files with diff and see corruption, that's a different story. Can you elaborate on the nature of the corruption you saw? Also, are you saying that the behavior isn't consistent from time to time (you copy the same file twice and get different results each time)?
– fixer1234
Nov 29 at 4:22