Sfdwhf

Should I be concerned about student access to a test bank?

Recursively updating the MLE as new observations stream in

is this saw blade faulty?

Would this string work as string?

Do people actually use the word "kaputt" in conversation?

Why are there no stars visible in cislunar space?

What favor did Moody owe Dumbledore?

How old is Nick Fury?

How are passwords stolen from companies if they only store hashes?

The English Debate

When did hardware antialiasing start being available?

Homology of the fiber

Asserting that Atheism and Theism are both faith based positions

"Marked down as someone wanting to sell shares." What does that mean?

Exit shell with shortcut (not typing exit) that closes session properly

Error in master's thesis, I do not know what to do

Have the tides ever turned twice on any open problem?

Would mining huge amounts of resources on the Moon change its orbit?

Determine voltage drop over 10G resistors with cheap multimeter

If I cast the Enlarge/Reduce spell on an arrow, what weapon could it count as?

Do I need to convey a moral for each of my blog post?

Help with identifying unique aircraft over NE Pennsylvania

Why is indicated airspeed rather than ground speed used during the takeoff roll?

I got the following comment from a reputed math journal. What does it mean?

Is it possible to “reset” the badblocks?

How do I check the integrity of a storage medium (hard disk or flash drive)?Cannot mount disk at all. Detailed explanation, Need helpHow to reset Ubuntu to act as at the first start?How to best check my hardware (mem and HD) for errors?Reset Linux Ubuntu desktopUbuntu 14.04 factory resetPartition Errors and Remounts Read-Only when Accessing Specific FileHow to reset all settings their original state?I was trying to reset the password >Factory Reset UbuntuIs there a command to factory reset Ubuntu?

4

4

I had a problem with a disk and ran badblocks.

So now when I run:

sudo dumpe2fs -b /dev/sdc1

I get a list of bad badblocks such as:

dumpe2fs 1.41.11 (14-Mar-2010)

192

1592

2416

3112

3552

...

But in fact, I realised that the problem came from the rack and not from the disk. I was using the rack in eSata and got plenty of read errors. Now i switched to USB, it's not as fast, but no errors at all.

So my question is:

How do I reset the badblock list stored in the inode #1 (badblock inode)?
(of course, without reformating!... That's the last thing I'll try if I get no solution)

Because apparently blocks are not at all "bad", they were just reported so because the rack is faulty.

Many thanks in advance and merry Christmas.

---

Edit: I tried to run another badblocks once the disk was connected to USB but no success: previously found bad-blocks remained.
I ran:

sudo badblocks -i /tmp/emptyList -s /dev/sdc1

the file /tmp/emptyList being empty so that badblocks is fed an empty list of known bad blocks. But apparently, it's not THE list of bad blocks, it is the ADDITIONAL list of bad blocks, which would be added to the existing ones declared in the inode #1.
The documentation (man) is not very accurate about that.

ext4 reset

share|improve this question

edited Dec 26 '10 at 11:10

8128

24.9k21101137

asked Dec 25 '10 at 15:46

ZakharZakhar

16917

add a comment | 

4

4

I had a problem with a disk and ran badblocks.

So now when I run:

sudo dumpe2fs -b /dev/sdc1

I get a list of bad badblocks such as:

dumpe2fs 1.41.11 (14-Mar-2010)

192

1592

2416

3112

3552

...

But in fact, I realised that the problem came from the rack and not from the disk. I was using the rack in eSata and got plenty of read errors. Now i switched to USB, it's not as fast, but no errors at all.

So my question is:

How do I reset the badblock list stored in the inode #1 (badblock inode)?
(of course, without reformating!... That's the last thing I'll try if I get no solution)

Because apparently blocks are not at all "bad", they were just reported so because the rack is faulty.

Many thanks in advance and merry Christmas.

---

Edit: I tried to run another badblocks once the disk was connected to USB but no success: previously found bad-blocks remained.
I ran:

sudo badblocks -i /tmp/emptyList -s /dev/sdc1

the file /tmp/emptyList being empty so that badblocks is fed an empty list of known bad blocks. But apparently, it's not THE list of bad blocks, it is the ADDITIONAL list of bad blocks, which would be added to the existing ones declared in the inode #1.
The documentation (man) is not very accurate about that.

ext4 reset

share|improve this question

edited Dec 26 '10 at 11:10

8128

24.9k21101137

asked Dec 25 '10 at 15:46

ZakharZakhar

16917

add a comment | 

I had a problem with a disk and ran badblocks.

So now when I run:

sudo dumpe2fs -b /dev/sdc1

I get a list of bad badblocks such as:

dumpe2fs 1.41.11 (14-Mar-2010)

192

1592

2416

3112

3552

...

But in fact, I realised that the problem came from the rack and not from the disk. I was using the rack in eSata and got plenty of read errors. Now i switched to USB, it's not as fast, but no errors at all.

So my question is:

How do I reset the badblock list stored in the inode #1 (badblock inode)?
(of course, without reformating!... That's the last thing I'll try if I get no solution)

Because apparently blocks are not at all "bad", they were just reported so because the rack is faulty.

Many thanks in advance and merry Christmas.

---

Edit: I tried to run another badblocks once the disk was connected to USB but no success: previously found bad-blocks remained.
I ran:

sudo badblocks -i /tmp/emptyList -s /dev/sdc1

the file /tmp/emptyList being empty so that badblocks is fed an empty list of known bad blocks. But apparently, it's not THE list of bad blocks, it is the ADDITIONAL list of bad blocks, which would be added to the existing ones declared in the inode #1.
The documentation (man) is not very accurate about that.

ext4 reset

share|improve this question

edited Dec 26 '10 at 11:10

8128

24.9k21101137

asked Dec 25 '10 at 15:46

ZakharZakhar

16917

sudo dumpe2fs -b /dev/sdc1

dumpe2fs 1.41.11 (14-Mar-2010)

192

1592

2416

3112

3552

...

sudo badblocks -i /tmp/emptyList -s /dev/sdc1

share|improve this question

edited Dec 26 '10 at 11:10

8128

24.9k21101137

asked Dec 25 '10 at 15:46

ZakharZakhar

16917

share|improve this question

edited Dec 26 '10 at 11:10

8128

24.9k21101137

asked Dec 25 '10 at 15:46

ZakharZakhar

16917

edited Dec 26 '10 at 11:10

8128

24.9k21101137

edited Dec 26 '10 at 11:10

8128

24.9k21101137

asked Dec 25 '10 at 15:46

ZakharZakhar

16917

asked Dec 25 '10 at 15:46

ZakharZakhar

16917

1 Answer
1

active

oldest

votes

4

ATTENTION: this is a risky operation, don't do it if you don't fully master what are the risks!

I just did:

sudo debugfs -w /dev/sdc1

clri <1>

quit

This clears the inode number 1 (the one containing bad blocks list) on your filesystem.

Then you have to run an e2fsck again to reset various things, and your are done!

share|improve this answer

edited 6 mins ago

Pablo Bianchi

2,97021535

answered Dec 26 '10 at 10:43

ZakharZakhar

16917

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
});


}
});

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f18826%2fis-it-possible-to-reset-the-badblocks%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

4

ATTENTION: this is a risky operation, don't do it if you don't fully master what are the risks!

I just did:

sudo debugfs -w /dev/sdc1

clri <1>

quit

This clears the inode number 1 (the one containing bad blocks list) on your filesystem.

Then you have to run an e2fsck again to reset various things, and your are done!

share|improve this answer

edited 6 mins ago

Pablo Bianchi

2,97021535

answered Dec 26 '10 at 10:43

ZakharZakhar

16917

add a comment | 

4

ATTENTION: this is a risky operation, don't do it if you don't fully master what are the risks!

I just did:

sudo debugfs -w /dev/sdc1

clri <1>

quit

This clears the inode number 1 (the one containing bad blocks list) on your filesystem.

Then you have to run an e2fsck again to reset various things, and your are done!

share|improve this answer

edited 6 mins ago

Pablo Bianchi

2,97021535

answered Dec 26 '10 at 10:43

ZakharZakhar

16917

add a comment | 

ATTENTION: this is a risky operation, don't do it if you don't fully master what are the risks!

I just did:

sudo debugfs -w /dev/sdc1

clri <1>

quit

This clears the inode number 1 (the one containing bad blocks list) on your filesystem.

Then you have to run an e2fsck again to reset various things, and your are done!

share|improve this answer

edited 6 mins ago

Pablo Bianchi

2,97021535

answered Dec 26 '10 at 10:43

ZakharZakhar

16917

sudo debugfs -w /dev/sdc1

clri <1>

quit

share|improve this answer

edited 6 mins ago

Pablo Bianchi

2,97021535

answered Dec 26 '10 at 10:43

ZakharZakhar

16917

edited 6 mins ago

Pablo Bianchi

2,97021535

edited 6 mins ago

Pablo Bianchi

2,97021535

answered Dec 26 '10 at 10:43

ZakharZakhar

16917

answered Dec 26 '10 at 10:43

ZakharZakhar

16917