dosfsck seems to hang after bad cluster message
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I used the following terminal command to fix bad sector on /dev/sda5 partition I have which is FAT32
sudo dosfsck -w -r -l -a -v -t /dev/sda5
after running for a long time it displayed the following:
Cluster 3109747 is unreadable.
Cluster 3109748 is unreadable.
Cluster 3109749 is unreadable.
Cluster 3109750 is unreadable.
Cluster 3109751 is unreadable.
Cluster 3109752 is unreadable.
Cluster 3109753 is unreadable.
Cluster 3109754 is unreadable.
Cluster 3109755 is unreadable.
Cluster 3109756 is unreadable.
Cluster 3109758 is unreadable.
Cluster 3109759 is unreadable.
Cluster 3109760 is unreadable.
and there is a white blinking cursor at the end but it seems to be hangs because the white cusros keeps blinking without any other output.
what to do?
partitioning badblocks
edited 14 hours ago
pomsky
33.2k11104135
asked 15 hours ago
markmark
1
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I used the following terminal command to fix bad sector on /dev/sda5 partition I have which is FAT32
sudo dosfsck -w -r -l -a -v -t /dev/sda5
after running for a long time it displayed the following:
Cluster 3109747 is unreadable.
Cluster 3109748 is unreadable.
Cluster 3109749 is unreadable.
Cluster 3109750 is unreadable.
Cluster 3109751 is unreadable.
Cluster 3109752 is unreadable.
Cluster 3109753 is unreadable.
Cluster 3109754 is unreadable.
Cluster 3109755 is unreadable.
Cluster 3109756 is unreadable.
Cluster 3109758 is unreadable.
Cluster 3109759 is unreadable.
Cluster 3109760 is unreadable.
and there is a white blinking cursor at the end but it seems to be hangs because the white cusros keeps blinking without any other output.
what to do?
partitioning badblocks
edited 14 hours ago
pomsky
33.2k11104135
asked 15 hours ago
markmark
1
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I used the following terminal command to fix bad sector on /dev/sda5 partition I have which is FAT32
sudo dosfsck -w -r -l -a -v -t /dev/sda5
after running for a long time it displayed the following:
Cluster 3109747 is unreadable.
Cluster 3109748 is unreadable.
Cluster 3109749 is unreadable.
Cluster 3109750 is unreadable.
Cluster 3109751 is unreadable.
Cluster 3109752 is unreadable.
Cluster 3109753 is unreadable.
Cluster 3109754 is unreadable.
Cluster 3109755 is unreadable.
Cluster 3109756 is unreadable.
Cluster 3109758 is unreadable.
Cluster 3109759 is unreadable.
Cluster 3109760 is unreadable.
and there is a white blinking cursor at the end but it seems to be hangs because the white cusros keeps blinking without any other output.
what to do?
partitioning badblocks
edited 14 hours ago
pomsky
33.2k11104135
asked 15 hours ago
markmark
1
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I used the following terminal command to fix bad sector on /dev/sda5 partition I have which is FAT32
sudo dosfsck -w -r -l -a -v -t /dev/sda5
after running for a long time it displayed the following:
Cluster 3109747 is unreadable.
Cluster 3109748 is unreadable.
Cluster 3109749 is unreadable.
Cluster 3109750 is unreadable.
Cluster 3109751 is unreadable.
Cluster 3109752 is unreadable.
Cluster 3109753 is unreadable.
Cluster 3109754 is unreadable.
Cluster 3109755 is unreadable.
Cluster 3109756 is unreadable.
Cluster 3109758 is unreadable.
Cluster 3109759 is unreadable.
Cluster 3109760 is unreadable.
and there is a white blinking cursor at the end but it seems to be hangs because the white cusros keeps blinking without any other output.
what to do?
partitioning badblocks
partitioning badblocks
edited 14 hours ago
pomsky
33.2k11104135
asked 15 hours ago
markmark
1
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 14 hours ago
pomsky
33.2k11104135
asked 15 hours ago
markmark
1
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 14 hours ago
pomsky
33.2k11104135
edited 14 hours ago
pomsky
33.2k11104135
edited 14 hours ago
pomsky
33.2k11104135
33.2k11104135
asked 15 hours ago
markmark
1
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 15 hours ago
markmark
1
asked 15 hours ago
markmark
1
1
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
what to do?
Generally I would expect a hardware problem when a filesystem check locks up.
The only advice I can give is to try to repair it using Windows. Dos tools will be almost 100% compatible but there is never a guarantee. You might just have ran into a bug.
Besides that: open a 2nd terminal and see if any of the logs in /var/log/ is being written. If so there might be a notice there that explains there is a problem. If so add that to the question.
The other option is to throw it into the bin.
answered 14 hours ago
RinzwindRinzwind
210k28404537
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
});
}
});
mark is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1131422%2fdosfsck-seems-to-hang-after-bad-cluster-message%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
what to do?
Generally I would expect a hardware problem when a filesystem check locks up.
The only advice I can give is to try to repair it using Windows. Dos tools will be almost 100% compatible but there is never a guarantee. You might just have ran into a bug.
Besides that: open a 2nd terminal and see if any of the logs in /var/log/ is being written. If so there might be a notice there that explains there is a problem. If so add that to the question.
The other option is to throw it into the bin.
answered 14 hours ago
RinzwindRinzwind
210k28404537
add a comment |
what to do?
Generally I would expect a hardware problem when a filesystem check locks up.
The only advice I can give is to try to repair it using Windows. Dos tools will be almost 100% compatible but there is never a guarantee. You might just have ran into a bug.
Besides that: open a 2nd terminal and see if any of the logs in /var/log/ is being written. If so there might be a notice there that explains there is a problem. If so add that to the question.
The other option is to throw it into the bin.
answered 14 hours ago
RinzwindRinzwind
210k28404537
add a comment |
what to do?
Generally I would expect a hardware problem when a filesystem check locks up.
The only advice I can give is to try to repair it using Windows. Dos tools will be almost 100% compatible but there is never a guarantee. You might just have ran into a bug.
Besides that: open a 2nd terminal and see if any of the logs in /var/log/ is being written. If so there might be a notice there that explains there is a problem. If so add that to the question.
The other option is to throw it into the bin.
answered 14 hours ago
RinzwindRinzwind
210k28404537
what to do?
Generally I would expect a hardware problem when a filesystem check locks up.
The only advice I can give is to try to repair it using Windows. Dos tools will be almost 100% compatible but there is never a guarantee. You might just have ran into a bug.
Besides that: open a 2nd terminal and see if any of the logs in /var/log/ is being written. If so there might be a notice there that explains there is a problem. If so add that to the question.
The other option is to throw it into the bin.
answered 14 hours ago
RinzwindRinzwind
210k28404537
answered 14 hours ago
RinzwindRinzwind
210k28404537
answered 14 hours ago
RinzwindRinzwind
210k28404537
answered 14 hours ago
RinzwindRinzwind
210k28404537
210k28404537
add a comment |
add a comment |
mark is a new contributor. Be nice, and check out our Code of Conduct.
mark is a new contributor. Be nice, and check out our Code of Conduct.
mark is a new contributor. Be nice, and check out our Code of Conduct.
mark is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1131422%2fdosfsck-seems-to-hang-after-bad-cluster-message%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
