Linux EXT2 FS Help

Linux EXT2 FS Help

Post by Kevin Davids » Wed, 05 Mar 1997 04:00:00



   Hello, fellow Linux users.  I have a problem.  And a big one at that.
At my school, we have an e-mail server running Linux something, and the
other day, I unlocked the server room, and found the screen displaying LI
with nothing but the previous BIOS information.  What I am saying, is that
LILO does not work, and I know why.  I used the boot/root disk to start
up, and when I attempted to mount the ext2 FS on hda, I was given the
message that it does not exist.  I know I typed the right command because
I have done it a million itmes before.  Later, I don't remember how, I
found that the superblock was corrupt.  There is only one partition on the
HD, and the partion system, fdisk, does not recognize it.  I have tried
the commend from the "rescue" root disk to recall a superblock copy, but
it does not work.  The command I use is "e2fsck -b 8193 hda" (it is an
EXT2 FS), and I get the command that the superblock is corrupt and it
cannot fix the FS, then it tells me to do what I did to get that message,
and puts be back at the # prompt.  What I am asking is, is there a way to
look at a trashed FS and find where the  copy of the SB is? If not, is
there any way to fix it without re-partioning everything and losing our
customized e-mail system? (that some guy built for us, neglected to give
us the hardware info, software copies, or anything relating to the server
except a key to lock the KB!  His name is Nathan from Second Foundation,
and if you know his, have him get a hold of me, please).  Thank you for
your time,

Humbily yours,
Kevin Davidson

 
 
 

Linux EXT2 FS Help

Post by bgee » Thu, 06 Mar 1997 04:00:00


 >...  The command I use is "e2fsck -b 8193 hda"

First, specify the drive using /dev/hdaN where N is the partition
number.  E.g., /dev/hda1 assuming it's the only partition on the
drive.

Second, copies of the superblock occur at intervals of 8192 blocks
from the first, so I THINK 16385 is the 2nd copy, 24577 is the 3rd,
etc.

I sure wish dumpe2fs printed out all the superblock addresses!

--
<> Robert Geer & Donna Tomky /              *             <>

<>   Salt Lake City, Utah   |   -\<,      * <\      </L   <>
<>          U S A           |   O/ O     __ /__,    />    <>

 
 
 

Linux EXT2 FS Help

Post by Graham Swall » Sat, 08 Mar 1997 04:00:00



> found that the superblock was corrupt.  There is only one partition on the
> HD, and the partion system, fdisk, does not recognize it.  I have tried

     Try running fdisk -l, if fdisk really can't see the drive,
     or the fdisk table of partitions is corrupt, you really are in
     trouble. If it was the only partition on the drive, the obvious values
     may work. If so look for /boot/boot.0300 (300 is hda in hexadecimal)
     and restore it using

        dd if=/boot/boot.0300 of=/dev/hda bs=512 count=1

     That will restore your MBR and the fdisk table within it. You may then
     need to re-run lilo to put the lilo code into the MBR (not the DOS
     MBR code that lilo saved when it first ran).

     If fdisk -l already works, don't do that, instead look at /dev/hda1
     as the others suggest. Then the question is how did this happen?


--
     --------------------------------------------------------------
     Linux Info Pages:  http://sunsite.unc.edu/pub/Linux/docs/Raven
     Home Page, click:  http://www.users.dircon.co.uk/~trix/
     --------------------------------------------------------------