-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Chris:

        I had to go through the painful process of recovering lost files on an
ext FS (twice!) and it really is a PITA. Eventually I discovered that my 
problems
were card-specific  to having a kernel built for dual-processors. Nevertheless,
if it werent for the fact that the data was really, really, important to me
(digital photos, personal coding libraries, etc..) I wouldnt have bothered.
Allow for spending bunches of time in inode hell:(

        I used  ext2utils (works for ext3),  tried to restore
a copy of the superblock,  then had to go through every inode, ID'ing dirs from 
files, until the system
locked up on un-recoverable ones; I had to re-boot the system numerous times
because it locks up ( Input/output error)
, but i did get about 70% of the FS's contents.



I had a corrupt ext2 filesystem w/an error message
corrup superblock - linux A block group is missing an inode table"

Below are the proggy's I used:

[EMAIL PROTECTED]:pwd
/usr/local/ext2Utils
[EMAIL PROTECTED]:ls
bin                       e2fsprogs-1.35         ext2read           README.rion
BlockId.results           e2resizeblk-0.98       fixdisktable-0.3   
RuinedPartitions
CatProcPartitions.result  e2retrieve             fskc-2.1.pdf       
runningNotes.txt
disc-recovery-utils.lsm   e2salvage-0.0.8a       GPART_hda.results  
SDB2_super.txt
Dumpe2fs_HDA1.results     e2salvage-0.0.8a-dupe  Hdparam.results    SleuthKit
Dumpe2fs_HDE6.results     e2undel-0.82           lde                
TuneFs.results
DumpE2fs.result           Ext2Ed                 lde-2.6.0          
util-linux-2.9i
DumpHDB5.results          EXT2ED_Userguide.txt   Lspci.results      vche-1.7.2
e2fsimage-0.2.0           ext2.html              Mke2fsOPT.result
e2fsprogs-1.34            ext2kit                Mke2fs.result

[EMAIL PROTECTED]:ls bin/
badblocks  dumpe2fs      e2retrieve    icat   istat     
parse_directory_inode.pl  tune2fs
blkid      e2extract.pl  fixdisktable  ifind  lde-i386  stat_inodes.pl          
debugfs    e2image       gpart         ils        stat_inodes.pl.bak


 I  determined where the copies of the superblock are kept: 
 I eventually had to create a list of
all inodes in the FS, allowing for system lock-up when it encountered a bad
block. then  I ran stat_inodes.pl to get a dump of them, then i ran a script i
created to ID the inodes and determine their proper names.

If you find you need to go to these lengths then i'll be happy to get back with 
the particulars 
of what exactly i did before blowing away the FS. (the drive was good and still 
runs today)


Rion

                                     3010 Rte 109
                                     Waterville, VT 05492
                                     email: rion_at_dluz.com
                                     web: http://dluz.com/Rion/
                                     Phone: 802.644.2255

                 L I N U X       .~.
                  Choice         /V\
                 of a  GNU      /( )\
                Generation      ^^-^^
                                POSIX
                                RULES

"Unix guru wanted.  
Must dream in sed and awk.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEiZ1294WPEVwn1ncRAmbJAJ966QMfbYYndYa2LaArOqutFlLx2gCfd7XF
fkkhQhJwKeA1ZkvhBvrJBms=
=6vio
-----END PGP SIGNATURE-----

Reply via email to