11/26   on Linux file system (ext2/ext3)... I know that the superblock
        is repeated every X of blocks.  and yes, my linux partition's
        superblock got fucked up... block 8193 is corrupt as well... which
        superblock is next?             --googled and find no answer
        \_ From the mke2fs manpage:
           -S     Write  superblock and group descriptors only.  This
                  is useful if  all  of  the  superblock  and  backup
                  superblocks  are corrupted, and a last-ditch recovĀ­
                  ery method is desired.  It causes mke2fs to  reiniĀ­
                  superblocks  are corrupted, and a last-ditch recovM--
                  ery method is desired.  It causes mke2fs to  reiniM--
                  tialize the superblock and group descriptors, while
                  not touching the inode  table  and  the  block  and
                  inode  bitmaps.   The  e2fsck program should be run
                  immediately after this option is used, and there is
                  no guarantee that any data will be salvageable.
           Never tried this myself, but I try to avoid redhat.  --scotsman
        \_ Depends on the options to mke2fs.  Default options depend on
           your distro.
        \_ Some versions of newfs when given the proper parameters will give
           you the alternate super block list.  I'd give you the exact options
           but I'd rather you checked the man pages for newfs and got it
           exactly right for your distro.  I don't want to be responsible for
           wiping your drive by telling you something that might be wrong on
           your system.
           \_ anything is welcome.  I don't have that many thing important
              on that Linux box, and worse comes worse I will reinstall it.
              Just that I have encountered this very very often, and I would
              like to find a way to fix it... in case that there is something
              important on my linux box in teh future.
              \_ Ok then, try "newfs -N <device>", where <device> is going to
                 be something like /dev/hd0c or whatever the path is to the
                 hard drives on your distro.  Please check the man pages that
                 -N option exists and that it only prints the parameters for
                 the device in question as it does on mine.  You want the
                 character device, not the block device.
           \_ there is no newfs.  only zuul.
           \_ tried newfs prior to my post on motd, newfs doesn't come with
              Redhat.
        \_ I believe it repeats every 8192 blocks, so just add 8192 to 8193,
           try to restore the superblock from there, rinse, repeat.
           \_ tried... "Bad Magic Number in super-block while trying to open
                /dev/hdc3"
           \_ are you assuming the first superblock is at 0? then you need
              to re-check your math. --aaron
        \_ man fsck.ext2 and look at -b option.  tune2fs -l /dev/whatever will
           tell you if you have sparse superblocks --dwc