<div dir="ltr">fsck does not offer to take any action. Even if I pass flags to it that should have it try to fix things, it just goes"Bad superblock! Oh noes!" and exits.<div><br></div><div>I have not compared the superblocks to one another. Might tell me if I'm looking at the wrong blocks for backups I suppose.</div>
<div><br></div><div>Still weird to me that everything seems to be working fine, if the superblock is actually bad...</div><div><br></div><div>QH</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 14, 2014 at 11:09 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">Quentin Hartman wrote:<br>
><br>
> Tried running against a ton of different potential superblock backup<br>
> locations, no dice. The only difference is that when I run against a backup<br>
> superblock it reports:<br>
><br>
> 1.41.10-2198: ***** FILE SYSTEM WAS MODIFIED *****<br>
><br>
> In addition to the warning about the bad superblock. (1.41.10-2198 is the<br>
> drive label)<br>
<br>
</div>Does fsck offer to do anything about the errors?<br>
<br>
Did you extract some superblocks and try comparing them?<br>
<br>
Dave<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</blockquote></div><br></div>