[SGVLUG] File system corruption

[Rich Pinder]

Hi all,


Fortunately I've not had to create such a subject line often concerning 
my Linux machines.
But I do have one that seems to be giving me troubles.

I had a 60gb drive that two partitions created.  it's on an older RH 
distro, with a 2.4 kernal.

/dev/sdh1                     59.8    50.7     6.1        90%     
/mnt/h1    
/dev/sdh2                      9.1     0.0     8.6         1%     /mnt/h2

After some flakey SAMBA behavior and a couple reboots, the file systems 
would not mount.

I ran   fsck on both of the systems - notice the first (the  h1 ) with 
all the data seemed to return as 'clean'.  I ran on the  h2, got the 
warning about mounted... ran and got the  'cleaned' message below.

After remounting (and later, rebooting), note below the final directory 
listing on the drive - instead of seeing a ton of .tif images, I'm 
seeing those  'OS Boot' type files  !!

If anyone can steer me in the proper direction, I'd appreciate it.
I would like to recover the data on the drive, if possible

Thanks
Rich Pinder
USC School of Medicine


> [root at asdfzxcv sbin]# ./fsck -t ext2 /dev/sdh1
> fsck 1.32 (09-Nov-2002)
> e2fsck 1.32 (09-Nov-2002)
> /boot: clean, 40/26104 files, 18352/104391 blocks
> [root at asdfzxcv sbin]# ./fsck -t ext2 /dev/sdh2
> fsck 1.32 (09-Nov-2002)
> e2fsck 1.32 (09-Nov-2002)
> /dev/sdh2 is mounted.  
>
> WARNING!!!  Running e2fsck on a mounted filesystem may cause
> SEVERE filesystem damage.
>
> Do you really want to continue (y/n)? yes
>
> /: recovering journal
>
> Clearing orphaned inode 213208 (uid=500, gid=0, mode=0140600, size=0)
> Clearing orphaned inode 213207 (uid=500, gid=0, mode=0140600, size=0)
> Clearing orphaned inode 213206 (uid=500, gid=0, mode=0140600, size=0)
> /: clean, 136539/4341760 files, 775290/8673091 blocks


>
>
>      File System:       Size (GB)  GB Used  GB Free    % Used   Mount 
> Point
> Filesystem                     0.0     0.0     0.0       Use%     
> Mounted    
> /dev/sdh2                     33.3     2.5    29.2         8%     
> /          
> none                           0.3     0.0     0.3         0%     
> /dev/shm   
> /dev/sda1                     59.8    23.5    33.3        42%     
> /mnt/a1    
> /dev/sda2                      9.1     0.0     8.6         1%     
> /mnt/a2    
> /dev/sdb1                     59.8    23.5    33.3        42%     
> /mnt/b1    
> /dev/sdb2                      9.1     0.0     8.6         1%     
> /mnt/b2    
> /dev/sdc1                     59.8    18.2    38.6        33%     
> /mnt/c1    
> /dev/sdc2                      9.1     0.0     8.6         1%     
> /mnt/c2    
> /dev/sdd1                     59.8    50.7     6.1        90%     
> /mnt/d1    
> /dev/sdd2                      9.1     0.0     8.6         1%     
> /mnt/d2    
> /dev/sde1                     59.8    44.0    12.8        78%     
> /mnt/e1    
> /dev/sde2                      9.1     0.0     8.6         1%     
> /mnt/e2    
> /dev/sdf1                     59.8     0.0    56.8         1%     
> /mnt/f1    
> /dev/sdf2                      9.1     0.0     8.6         1%     
> /mnt/f2    
> /dev/sdg1                     59.8    15.0    41.8        27%     
> /mnt/g1    
> /dev/sdg2                      9.1     0.0     8.6         1%     
> /mnt/g2    
> /dev/sdh1                      0.1     0.0     0.1        16%     
> /mnt/h1    
>
> [root at asdfzxcv rpinder]# cd /mnt/h1
> [root at asdfzxcv h1]# ls
> config-2.4.21-15.EL      initrd-2.4.21-15.ELsmp.img  
> message.ja                  vmlinux-2.4.21-15.EL
> config-2.4.21-15.ELsmp   kernel.h                    
> System.map                  vmlinux-2.4.21-15.ELsmp
> grub                     lost+found                  
> System.map-2.4.21-15.EL     vmlinuz-2.4.21-15.EL
> initrd-2.4.21-15.EL.img  message                     
> System.map-2.4.21-15.ELsmp  vmlinuz-2.4.21-15.ELsmp
> [root at asdfzxcv h1]#