Find the answer to your Linux question:
Results 1 to 4 of 4
Anyone who can help me with this, I'd be most grateful. We had a power outage in our server room and our servers overheated, thus they shut themselves down. One ...
  1. 06-25-2009 #1
    Lia
    Lia is offline
    Just Joined!
    Join Date
    Nov 2008
    Posts
    11

    Question Superblock error

    Anyone who can help me with this, I'd be most grateful.

    We had a power outage in our server room and our servers overheated, thus they shut themselves down. One of our servers did not boot back up properly. The error is a bad superblock on the / partition. The slash partition is on /dev/sda8. I'm run e2fsck on every device- I gathered my devices by running fdisk -l- and they all come back clean. However, when I reboot, I keep getting bad superblock on the / partition.
    I've fun dumpe2fs on the /dev/sda8 partition to gather the available backup blocks. I then ran e2fsck -b <block#> /dev/sda8 to fix the bad superblock. Some fixes were made and I reboot. No success, still bad superblock.
    My conundrum is why is it reporting a bad superblock when I boot up on the / partition, but when I run e2fsck -p /dev/sda8 is comes back clean?
    I aslo popped in my RHEL install disk and ran the rescue utility but that didn't help the situation either.
    Can anyone suggest what else I can try that may resolve this issue? Does it sound like things are WAY bad and it's not resolvable?
    I'd appreciate any and all advice.
    Thanks,
    Lia.
    Reply With Quote Reply With Quote
  2. 06-25-2009 #2
    Rubberman
    Rubberman is offline
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    How do you know that /dev/sda8 is the partition that contains the root / file system? Usually it is on /dev/sda3 when you do a normal RHEL installation. The installer usually places /boot on /dev/sda1, swap on /dev/sda2, and / on /dev/sda3.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!
    Reply With Quote Reply With Quote
  3. 06-25-2009 #3
    Lia
    Lia is offline
    Just Joined!
    Join Date
    Nov 2008
    Posts
    11
    Because when I run e2fsck -p /dev/sda8 the results are:
    /: clean [followed by number of blocks etc]
    I ran this for all the devices- sda1, sda2 etc- and the results always showed which folder/ partition was mounted on it. Also, all the devices come back as clean when I run e2fsck on them.
    I hope my methodology was correct...
    Reply With Quote Reply With Quote
  4. 06-25-2009 #4
    Rubberman
    Rubberman is offline
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    Probably not. You cannot run fsck on a mounted partition in any case, at least without possibly munging it totally. Boot a recovery disc, then manually run fsck -f on each partition to force checking the file system, even if they seem clean. If you did not use the -f (force) option, then just because they came back clean it does not mean that they are. Depending upon how large your drive and the partitions may be, this can take some time.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules

...