Hard drive works intermittently but stalls on a specific sectorHow can I read my hard drive’s SMART status...
If a set is open, does that imply that it has no boundary points?
Six real numbers so that product of any five is the sixth one
The need of reserving one's ability in job interviews
How to lift/raise/repair a segment of concrete slab?
I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?
Pure Functions: Does "No Side Effects" Imply "Always Same Output, Given Same Input"?
In the comics did Thanos "kill" just sentient beings or all creatures with the snap?
Is there any relevance to Thor getting his hair cut other than comedic value?
What happened to QGIS 2.x
Is there a full canon version of Tyrion's jackass/honeycomb joke?
How can I be pwned if I'm not registered on the compromised site?
What is better: yes / no radio, or simple checkbox?
Non-Italian European mafias in USA?
What am I? I am in theaters and computer programs
Skis versus snow shoes - when to choose which for travelling the backcountry?
How do you say "powers of ten"?
Traversing Africa: A Cryptic Journey
How can atoms be electrically neutral when there is a difference in the positions of the charges?
Practical reasons to have both a large police force and bounty hunting network?
Real life puzzle: Unknown alphabet or shorthand
Plagiarism of code by other PhD student
Second-rate spelling
What should one use the left pedal for on an upright?
Dystopian novel where telepathic humans live under a dome
Hard drive works intermittently but stalls on a specific sector
How can I read my hard drive’s SMART status in Windows 7?How can I get a specific large file off of a broken SSD?Spilled Beer onto Controller Board of 2.5" PATA Hard DriveSeagate hard drive, logic board fried. Desperately need replacementCould other hardware be responsible for bad sectors on my hard drive?Hard drive failure - Can I recover data?Seagate Barracuda 7200.11 Failing AgainSATA HDD suddenly stops being detected by any computerOpening up and diagnosing a faulty 2.5'' hard driveAnything I can do about erratic hard disk drive speedsNew Hard Drive Speed IssuesHard drive data recovery - spins but not recognized in BIOS - PCB + ROM Swap did nothing
I replaced a hard drive for a client, but they have a lot of family photos on the old one, so I'm trying my best to recover them. The drive powers up, but often doesn't appear in HDClone. Sometimes, however, it does appear and I'm able to follow through to the duplication process. Each and every time, the process stalls at sector 13,847,762 and the drive begins making a series of clicking noises.
The drive is a Seagate Barracuda 7200.7 160GB ST3160021A.
Does anyone have any suggestions? Does this sound like something a replacement circuit board might fix or is it probably a mechanical issue?
hard-drive hard-drive-failure
add a comment |
I replaced a hard drive for a client, but they have a lot of family photos on the old one, so I'm trying my best to recover them. The drive powers up, but often doesn't appear in HDClone. Sometimes, however, it does appear and I'm able to follow through to the duplication process. Each and every time, the process stalls at sector 13,847,762 and the drive begins making a series of clicking noises.
The drive is a Seagate Barracuda 7200.7 160GB ST3160021A.
Does anyone have any suggestions? Does this sound like something a replacement circuit board might fix or is it probably a mechanical issue?
hard-drive hard-drive-failure
2
It's fairly likely that there's a defect at that location, and the drive gets caught in a loop trying to recover from it. It could be the defect is on a timing track rather than the data track. You need a utility that can read and write individual sectors, to see if you can get beyond it. If so, then writing that sector might allow a copy to proceed.
– Daniel R Hicks
Jan 16 '12 at 1:03
@Mark Johnson: I was using HDClone on Windows, but PhotoRec on Linux stalls on the same sector. I'll use any OS I have to.
– David Brown
Jan 16 '12 at 2:39
Have you tried DD in linux yet?
– Scott Chamberlain
Jan 16 '12 at 22:03
add a comment |
I replaced a hard drive for a client, but they have a lot of family photos on the old one, so I'm trying my best to recover them. The drive powers up, but often doesn't appear in HDClone. Sometimes, however, it does appear and I'm able to follow through to the duplication process. Each and every time, the process stalls at sector 13,847,762 and the drive begins making a series of clicking noises.
The drive is a Seagate Barracuda 7200.7 160GB ST3160021A.
Does anyone have any suggestions? Does this sound like something a replacement circuit board might fix or is it probably a mechanical issue?
hard-drive hard-drive-failure
I replaced a hard drive for a client, but they have a lot of family photos on the old one, so I'm trying my best to recover them. The drive powers up, but often doesn't appear in HDClone. Sometimes, however, it does appear and I'm able to follow through to the duplication process. Each and every time, the process stalls at sector 13,847,762 and the drive begins making a series of clicking noises.
The drive is a Seagate Barracuda 7200.7 160GB ST3160021A.
Does anyone have any suggestions? Does this sound like something a replacement circuit board might fix or is it probably a mechanical issue?
hard-drive hard-drive-failure
hard-drive hard-drive-failure
edited Apr 15 '16 at 20:19
fixer1234
18.9k144982
18.9k144982
asked Jan 16 '12 at 0:56
David BrownDavid Brown
1,02311020
1,02311020
2
It's fairly likely that there's a defect at that location, and the drive gets caught in a loop trying to recover from it. It could be the defect is on a timing track rather than the data track. You need a utility that can read and write individual sectors, to see if you can get beyond it. If so, then writing that sector might allow a copy to proceed.
– Daniel R Hicks
Jan 16 '12 at 1:03
@Mark Johnson: I was using HDClone on Windows, but PhotoRec on Linux stalls on the same sector. I'll use any OS I have to.
– David Brown
Jan 16 '12 at 2:39
Have you tried DD in linux yet?
– Scott Chamberlain
Jan 16 '12 at 22:03
add a comment |
2
It's fairly likely that there's a defect at that location, and the drive gets caught in a loop trying to recover from it. It could be the defect is on a timing track rather than the data track. You need a utility that can read and write individual sectors, to see if you can get beyond it. If so, then writing that sector might allow a copy to proceed.
– Daniel R Hicks
Jan 16 '12 at 1:03
@Mark Johnson: I was using HDClone on Windows, but PhotoRec on Linux stalls on the same sector. I'll use any OS I have to.
– David Brown
Jan 16 '12 at 2:39
Have you tried DD in linux yet?
– Scott Chamberlain
Jan 16 '12 at 22:03
2
2
It's fairly likely that there's a defect at that location, and the drive gets caught in a loop trying to recover from it. It could be the defect is on a timing track rather than the data track. You need a utility that can read and write individual sectors, to see if you can get beyond it. If so, then writing that sector might allow a copy to proceed.
– Daniel R Hicks
Jan 16 '12 at 1:03
It's fairly likely that there's a defect at that location, and the drive gets caught in a loop trying to recover from it. It could be the defect is on a timing track rather than the data track. You need a utility that can read and write individual sectors, to see if you can get beyond it. If so, then writing that sector might allow a copy to proceed.
– Daniel R Hicks
Jan 16 '12 at 1:03
@Mark Johnson: I was using HDClone on Windows, but PhotoRec on Linux stalls on the same sector. I'll use any OS I have to.
– David Brown
Jan 16 '12 at 2:39
@Mark Johnson: I was using HDClone on Windows, but PhotoRec on Linux stalls on the same sector. I'll use any OS I have to.
– David Brown
Jan 16 '12 at 2:39
Have you tried DD in linux yet?
– Scott Chamberlain
Jan 16 '12 at 22:03
Have you tried DD in linux yet?
– Scott Chamberlain
Jan 16 '12 at 22:03
add a comment |
3 Answers
3
active
oldest
votes
Most likely there are one or more bad blocks on the hard-drive. What you are hearing is the read-write head resetting its position as the drive controller attempts to pull a useable signal off the media. Each block includes error-correcting code which both detects corrupt data and, if a strong enough signal can be obtained, reconstructs the data.
Backup everything you can, cool down the drive by turning up the fans or cooling the environment, and keep trying to read the file. Often you can get the block read after many tries, at which point the firmware will re-write the data into a spare block and mark the bad one as off limits. This will need to be repeated for each bad block, so its helpful to isolate exactly which files are causing problems and work on them individually.
I wrote an article explaining this recover procedure in detail:
Hard Drive Recovery
Small note - not each "block", but each sector, as the filesystem deals with either blocks or clusters (Windows) that are composed of the smallest unit on the hdd level - sectors.
– XXL
Jan 20 '12 at 8:31
add a comment |
For a commercial software that may help you out I recommend SpinRite. It's a little expensive ($89.00) but it does the job well. If you can not get any free utilities to get it to work I would try it as a last resort. It will read the sector as much as it can then mark the sector bad. When it tries the "read as much as it can" its not just doing a normal read, it actually reading the raw data off of the head and doing probability statistics to figure out what is supposed to be there. Be prepared to wait a while, it will continue to try until it has exhausted all possible ways to read the disk, I have heard people have let it run for months as it cranks away at a bad sector (and get the data back).
A lot of people knock SpinRite for recovering the data in place instead of copying the data to another drive, but you must understand that SplinRite is not for restoring data like other data recovery tools. It is a tool to allow other tools like HD Clone and DD to work.
Followup to other question in original post:
Does this sound like something a replacement circuit board might fix
or is it probably a mechanical issue?
No the issue is on the drive platter itself, replacing the circuit board will not fix it. If it was the circuit board the drive would not read at all, not go to a specific sector and stop.
add a comment |
Get another hard drive same size or large.
where sda is the source
sdb is the destination
ddrescue -d -f -r3 /dev/sda /dev/sdb /media/PNY_usb/rescue.logfile
Additionally if you have nothing better to do but wait, or no other method works.
dd if=/dev/sda of=/dev/sdb bs=512 count=13847761
dd if=/dev/sda of=/dev/sdb bs=512 skip=13847763
Depending on the number of bad sectors you may have to modify the range dozens of times using skip and count together.
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%2f378805%2fhard-drive-works-intermittently-but-stalls-on-a-specific-sector%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Most likely there are one or more bad blocks on the hard-drive. What you are hearing is the read-write head resetting its position as the drive controller attempts to pull a useable signal off the media. Each block includes error-correcting code which both detects corrupt data and, if a strong enough signal can be obtained, reconstructs the data.
Backup everything you can, cool down the drive by turning up the fans or cooling the environment, and keep trying to read the file. Often you can get the block read after many tries, at which point the firmware will re-write the data into a spare block and mark the bad one as off limits. This will need to be repeated for each bad block, so its helpful to isolate exactly which files are causing problems and work on them individually.
I wrote an article explaining this recover procedure in detail:
Hard Drive Recovery
Small note - not each "block", but each sector, as the filesystem deals with either blocks or clusters (Windows) that are composed of the smallest unit on the hdd level - sectors.
– XXL
Jan 20 '12 at 8:31
add a comment |
Most likely there are one or more bad blocks on the hard-drive. What you are hearing is the read-write head resetting its position as the drive controller attempts to pull a useable signal off the media. Each block includes error-correcting code which both detects corrupt data and, if a strong enough signal can be obtained, reconstructs the data.
Backup everything you can, cool down the drive by turning up the fans or cooling the environment, and keep trying to read the file. Often you can get the block read after many tries, at which point the firmware will re-write the data into a spare block and mark the bad one as off limits. This will need to be repeated for each bad block, so its helpful to isolate exactly which files are causing problems and work on them individually.
I wrote an article explaining this recover procedure in detail:
Hard Drive Recovery
Small note - not each "block", but each sector, as the filesystem deals with either blocks or clusters (Windows) that are composed of the smallest unit on the hdd level - sectors.
– XXL
Jan 20 '12 at 8:31
add a comment |
Most likely there are one or more bad blocks on the hard-drive. What you are hearing is the read-write head resetting its position as the drive controller attempts to pull a useable signal off the media. Each block includes error-correcting code which both detects corrupt data and, if a strong enough signal can be obtained, reconstructs the data.
Backup everything you can, cool down the drive by turning up the fans or cooling the environment, and keep trying to read the file. Often you can get the block read after many tries, at which point the firmware will re-write the data into a spare block and mark the bad one as off limits. This will need to be repeated for each bad block, so its helpful to isolate exactly which files are causing problems and work on them individually.
I wrote an article explaining this recover procedure in detail:
Hard Drive Recovery
Most likely there are one or more bad blocks on the hard-drive. What you are hearing is the read-write head resetting its position as the drive controller attempts to pull a useable signal off the media. Each block includes error-correcting code which both detects corrupt data and, if a strong enough signal can be obtained, reconstructs the data.
Backup everything you can, cool down the drive by turning up the fans or cooling the environment, and keep trying to read the file. Often you can get the block read after many tries, at which point the firmware will re-write the data into a spare block and mark the bad one as off limits. This will need to be repeated for each bad block, so its helpful to isolate exactly which files are causing problems and work on them individually.
I wrote an article explaining this recover procedure in detail:
Hard Drive Recovery
answered Jan 16 '12 at 21:44
Seth NobleSeth Noble
94647
94647
Small note - not each "block", but each sector, as the filesystem deals with either blocks or clusters (Windows) that are composed of the smallest unit on the hdd level - sectors.
– XXL
Jan 20 '12 at 8:31
add a comment |
Small note - not each "block", but each sector, as the filesystem deals with either blocks or clusters (Windows) that are composed of the smallest unit on the hdd level - sectors.
– XXL
Jan 20 '12 at 8:31
Small note - not each "block", but each sector, as the filesystem deals with either blocks or clusters (Windows) that are composed of the smallest unit on the hdd level - sectors.
– XXL
Jan 20 '12 at 8:31
Small note - not each "block", but each sector, as the filesystem deals with either blocks or clusters (Windows) that are composed of the smallest unit on the hdd level - sectors.
– XXL
Jan 20 '12 at 8:31
add a comment |
For a commercial software that may help you out I recommend SpinRite. It's a little expensive ($89.00) but it does the job well. If you can not get any free utilities to get it to work I would try it as a last resort. It will read the sector as much as it can then mark the sector bad. When it tries the "read as much as it can" its not just doing a normal read, it actually reading the raw data off of the head and doing probability statistics to figure out what is supposed to be there. Be prepared to wait a while, it will continue to try until it has exhausted all possible ways to read the disk, I have heard people have let it run for months as it cranks away at a bad sector (and get the data back).
A lot of people knock SpinRite for recovering the data in place instead of copying the data to another drive, but you must understand that SplinRite is not for restoring data like other data recovery tools. It is a tool to allow other tools like HD Clone and DD to work.
Followup to other question in original post:
Does this sound like something a replacement circuit board might fix
or is it probably a mechanical issue?
No the issue is on the drive platter itself, replacing the circuit board will not fix it. If it was the circuit board the drive would not read at all, not go to a specific sector and stop.
add a comment |
For a commercial software that may help you out I recommend SpinRite. It's a little expensive ($89.00) but it does the job well. If you can not get any free utilities to get it to work I would try it as a last resort. It will read the sector as much as it can then mark the sector bad. When it tries the "read as much as it can" its not just doing a normal read, it actually reading the raw data off of the head and doing probability statistics to figure out what is supposed to be there. Be prepared to wait a while, it will continue to try until it has exhausted all possible ways to read the disk, I have heard people have let it run for months as it cranks away at a bad sector (and get the data back).
A lot of people knock SpinRite for recovering the data in place instead of copying the data to another drive, but you must understand that SplinRite is not for restoring data like other data recovery tools. It is a tool to allow other tools like HD Clone and DD to work.
Followup to other question in original post:
Does this sound like something a replacement circuit board might fix
or is it probably a mechanical issue?
No the issue is on the drive platter itself, replacing the circuit board will not fix it. If it was the circuit board the drive would not read at all, not go to a specific sector and stop.
add a comment |
For a commercial software that may help you out I recommend SpinRite. It's a little expensive ($89.00) but it does the job well. If you can not get any free utilities to get it to work I would try it as a last resort. It will read the sector as much as it can then mark the sector bad. When it tries the "read as much as it can" its not just doing a normal read, it actually reading the raw data off of the head and doing probability statistics to figure out what is supposed to be there. Be prepared to wait a while, it will continue to try until it has exhausted all possible ways to read the disk, I have heard people have let it run for months as it cranks away at a bad sector (and get the data back).
A lot of people knock SpinRite for recovering the data in place instead of copying the data to another drive, but you must understand that SplinRite is not for restoring data like other data recovery tools. It is a tool to allow other tools like HD Clone and DD to work.
Followup to other question in original post:
Does this sound like something a replacement circuit board might fix
or is it probably a mechanical issue?
No the issue is on the drive platter itself, replacing the circuit board will not fix it. If it was the circuit board the drive would not read at all, not go to a specific sector and stop.
For a commercial software that may help you out I recommend SpinRite. It's a little expensive ($89.00) but it does the job well. If you can not get any free utilities to get it to work I would try it as a last resort. It will read the sector as much as it can then mark the sector bad. When it tries the "read as much as it can" its not just doing a normal read, it actually reading the raw data off of the head and doing probability statistics to figure out what is supposed to be there. Be prepared to wait a while, it will continue to try until it has exhausted all possible ways to read the disk, I have heard people have let it run for months as it cranks away at a bad sector (and get the data back).
A lot of people knock SpinRite for recovering the data in place instead of copying the data to another drive, but you must understand that SplinRite is not for restoring data like other data recovery tools. It is a tool to allow other tools like HD Clone and DD to work.
Followup to other question in original post:
Does this sound like something a replacement circuit board might fix
or is it probably a mechanical issue?
No the issue is on the drive platter itself, replacing the circuit board will not fix it. If it was the circuit board the drive would not read at all, not go to a specific sector and stop.
edited Jan 16 '12 at 22:05
answered Jan 16 '12 at 21:59
Scott ChamberlainScott Chamberlain
28k583101
28k583101
add a comment |
add a comment |
Get another hard drive same size or large.
where sda is the source
sdb is the destination
ddrescue -d -f -r3 /dev/sda /dev/sdb /media/PNY_usb/rescue.logfile
Additionally if you have nothing better to do but wait, or no other method works.
dd if=/dev/sda of=/dev/sdb bs=512 count=13847761
dd if=/dev/sda of=/dev/sdb bs=512 skip=13847763
Depending on the number of bad sectors you may have to modify the range dozens of times using skip and count together.
add a comment |
Get another hard drive same size or large.
where sda is the source
sdb is the destination
ddrescue -d -f -r3 /dev/sda /dev/sdb /media/PNY_usb/rescue.logfile
Additionally if you have nothing better to do but wait, or no other method works.
dd if=/dev/sda of=/dev/sdb bs=512 count=13847761
dd if=/dev/sda of=/dev/sdb bs=512 skip=13847763
Depending on the number of bad sectors you may have to modify the range dozens of times using skip and count together.
add a comment |
Get another hard drive same size or large.
where sda is the source
sdb is the destination
ddrescue -d -f -r3 /dev/sda /dev/sdb /media/PNY_usb/rescue.logfile
Additionally if you have nothing better to do but wait, or no other method works.
dd if=/dev/sda of=/dev/sdb bs=512 count=13847761
dd if=/dev/sda of=/dev/sdb bs=512 skip=13847763
Depending on the number of bad sectors you may have to modify the range dozens of times using skip and count together.
Get another hard drive same size or large.
where sda is the source
sdb is the destination
ddrescue -d -f -r3 /dev/sda /dev/sdb /media/PNY_usb/rescue.logfile
Additionally if you have nothing better to do but wait, or no other method works.
dd if=/dev/sda of=/dev/sdb bs=512 count=13847761
dd if=/dev/sda of=/dev/sdb bs=512 skip=13847763
Depending on the number of bad sectors you may have to modify the range dozens of times using skip and count together.
answered 17 hours ago
cybernardcybernard
10.4k31628
10.4k31628
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%2f378805%2fhard-drive-works-intermittently-but-stalls-on-a-specific-sector%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
2
It's fairly likely that there's a defect at that location, and the drive gets caught in a loop trying to recover from it. It could be the defect is on a timing track rather than the data track. You need a utility that can read and write individual sectors, to see if you can get beyond it. If so, then writing that sector might allow a copy to proceed.
– Daniel R Hicks
Jan 16 '12 at 1:03
@Mark Johnson: I was using HDClone on Windows, but PhotoRec on Linux stalls on the same sector. I'll use any OS I have to.
– David Brown
Jan 16 '12 at 2:39
Have you tried DD in linux yet?
– Scott Chamberlain
Jan 16 '12 at 22:03