[mdlug] Recovering damaged EXT2

[Michael ORourke]

Dave,

If you were using the external USB drive in a pseudo RAID-1 configuration, 
then all you data would be on the other drive (internal), and there would be 
no need to recover anything.  And I suspect that the new USB drive would 
have some sort of warranty, so if you can't get it working again, then just 
send it back for a replacement.  Or am I missing something?

-Mike

----- Original Message ----- 
From: "David McMillan" <skyefire at skyefire.org>
To: "MDLUG's Main discussion list" <mdlug at mdlug.org>
Sent: Tuesday, September 15, 2009 9:39 PM
Subject: [mdlug] Recovering damaged EXT2


>
> So, one of the two big USB drives I've been using as a poor man's
> RAID-1 (using periodic rsync) died, and I bought a replacement and
> immediately began a fresh rsync to copy the remaining drive to the new
> one.  No big deal... except that, thanks to a dangling cord and careless
> footwork (my own), the remaining drive of the original pair fell off the
> table and hit the floor.  It *seems* okay -- no weird noises, parted
> recognizes its filesystem (ext2) and size, but....
> Now, when I try to mount it, I get a "bad superblock" error.  If I try
> to run fsck or e2fsck, I get "the superblock is corrupt" and a
> suggestion to run e2fsck with the "e2fsck -b 8192 <device".  But if I
> try that, I get a "device busy" error message, even though the partition
> is not mounted and no other process is accessing that drive.
>
> So... am I screwed?  Or are there tools that might allow me to recover
> what was on this drive?
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug


--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.100/2373 - Release Date: 09/15/09 
13:37:00