[clue] Oops, I did it again...

chris fedde chris at fedde.us
Mon Jul 25 15:38:00 MDT 2011


I'm not sure how a tool that zeros duplicates like that will help you
fix sdb.  If you got the ctl-c in fast enough you just mucked the
inode list.

On Mon, Jul 25, 2011 at 3:34 PM, David L. Willson <DLWillson at thegeek.nu> wrote:
> sda and sdb will get dd'd into files on the great big new drive, as soon as I have time. For now, they've been pulled out of the system and are waiting patiently.
>
> What I need is a script that goes something like:
>
> Read a block from sda, read a block from sdb.
> If they're the same, overwrite the block from sdb with zeroes.
> If they're different, quit.
> Read the next block from sda and sdb. Repeat.
>
> Since nobody's produced such a thing, I suppose I'll have to write it...
>
> David L. Willson
> Trainer, Engineer, Enthusiast
> RHCE MCT MCSE Network+ A+ Linux+ LPIC-1 NovellCLA UbuntuCP
> tel://720.333.LANS
> Freedom is better when you earn it. Learn Linux.
>
> ----- Original Message -----
>> I suspect that you  don't have any other backup of the sdb drive?
>> yeah. I've been there.  Sucks to be you right now. :-(
>>
>> At this point the most important thing is to preserve the state of
>> what you have.  I hate to say it but you might want to dd what's left
>> of /dev/sdb to some static storage like a usb drive.
>> Step 2 is to try to fsck with some alternate superblock.  With luck
>> you'll get a file system back from that.  After that its pretty much
>> catch as catch can as to what will work.
>> If you know how much got over written you can write back that amount
>> from a newfs'd drive and retry the fsck.
>>
>> On Mon, Jul 25, 2011 at 3:00 PM, David L. Willson
>> <DLWillson at thegeek.nu> wrote:
>> > Damn it, dd! Stop doing what I say! Or at least warn me... Ugh...
>> >
>> > I ~meant~: $ dd if=/dev/sda of=/dev/sdc
>> > but I said: $ dd if=/dev/sda of=/dev/sdb
>> >
>> > /dev/sdb ~had~ important stuph on it.
>> >
>> > Now, it has an in-determinate amount of garbage copied verbatim
>> > from
>> > /dev/sda, as much as it could copy before I read what I'd written,
>> > shrieked,
>> > and filled the keyboard buffer with <CTRL>+c's followed by some
>> > important
>> > stuph I might never see again.
>> >
>> > Sigh...
>> >
>> > I think step 0 of my "get some back" plan is to zero out the bit of
>> > /dev/sdb
>> > that matches /dev/sda, in order to get rid of the bogus information
>> > at the
>> > beginning of the disk. Anyone have a script handy?
>> >
>> > Links for when I get to steps 1-99?
>> >
>> > David L. Willson
>> > Trainer, Engineer, Enthusiast
>> > RHCE MCT MCSE Network+ A+ Linux+ LPIC-1 NovellCLA UbuntuCP
>> > tel://720.333.LANS
>> > Freedom is better when you earn it. Learn Linux.
>> >
>> >
>> > _______________________________________________
>> > clue mailing list: clue at cluedenver.org
>> > For information, account preferences, or to unsubscribe see:
>> > http://cluedenver.org/mailman/listinfo/clue
>> >
>> _______________________________________________
>> clue mailing list: clue at cluedenver.org
>> For information, account preferences, or to unsubscribe see:
>> http://cluedenver.org/mailman/listinfo/clue
>>
> _______________________________________________
> clue mailing list: clue at cluedenver.org
> For information, account preferences, or to unsubscribe see:
> http://cluedenver.org/mailman/listinfo/clue
>


More information about the clue mailing list