Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: weblance on April 19, 2011, 01:03:39 PM

Title: "The superblock could not be read..."
Post by: weblance on April 19, 2011, 01:03:39 PM

Hi

I'm getting an error during boot:

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

What on earth should i do?

/Carl

Title: Re: "The superblock could not be read..."
Post by: Stefano on April 19, 2011, 01:51:53 PM

first of all you should give more details..

Title: Re: "The superblock could not be read..."
Post by: weblance on April 19, 2011, 02:06:49 PM

Which details do you need?

The problem is that i'm not physically at the server location, it's located 400 km from where i am. I probably have to catch a plane tomorrow morning to get to the server :(

It's an IBM server, about 4 yrs old, don't remember the model. It has 4 HDD's running SME 7.5.1 i SME RAID 5. It is a standard SME installation, and the server is only used as a fileserver.

I DON'T HAVE A BACKUP  :-(

Title: Re: "The superblock could not be read..."
Post by: Stefano on April 19, 2011, 02:11:45 PM

Quote from: weblance on April 19, 2011, 02:06:49 PM

Which details do you need?
It's an IBM server, about 4 yrs old, don't remember the model. It has 4 HDD's running SME 7.5.1 i SME RAID 5. It is a standard SME installation, and the server is only used as a fileserver.

hw or sw raid? raid5 with hotspare?

Quote

I DON'T HAVE A BACKUP  :-(

well.. I guess it's time to think about it, isn't it?

Title: Re: "The superblock could not be read..."
Post by: weblance on April 19, 2011, 02:14:31 PM

sw raid5 without hotspare - sme handles this

and you are quite right about the backup !

Title: Re: "The superblock could not be read..."
Post by: weblance on April 19, 2011, 02:25:57 PM

I have a man on site and he tried

e2fsck -b 8193 /dev/mapper/main-root

It resultet in a lot of messages that he had to answer yes to. At last he panict and rebooted the server. No he has a kernel panic...

Is there any possibility to recover the data on the discs?

Title: Re: "The superblock could not be read..."
Post by: Stefano on April 19, 2011, 02:34:35 PM

Quote from: weblance on April 19, 2011, 02:25:57 PM

I have a man on site and he tried

e2fsck -b 8193 /dev/mapper/main-root

It resultet in a lot of messages that he had to answer yes to. At last he panict and rebooted the server. No he has a kernel panic...

...
maybe raid isn't starting properly

Quote

Is there any possibility to recover the data on the discs?

maybe.. but:
- keep your man on site at least at 10 m from the server
- try booting with SME's cd in rescue mode
- come back here and be verbose

Title: Re: "The superblock could not be read..."
Post by: weblance on April 19, 2011, 02:47:19 PM

I'm flying in tomorrow. Going to try booting in rescue mode.

Thanks for the help so far.

/Carl

Title: Re: "The superblock could not be read..."
Post by: weblance on April 20, 2011, 11:12:05 AM

Hi,

i'm at the server now. Trying to boot it up it says:

sde: Spinning up disk..........

And eventually it ends up in a kernel panic.

Title: Re: "The superblock could not be read..."
Post by: Stefano on April 20, 2011, 11:19:19 AM

ok..

is there any external disk (usb) connected?

did you try to boot with SME's cd?

try to identify sde disk, disconnect it and try again

Title: Re: "The superblock could not be read..."
Post by: weblance on April 20, 2011, 11:45:47 AM

There is no external usb disk connected.

I've tried sme rescue and i get the message:

You don't have any Linux partitions. Press return to get a shell. The system will reboot automatically when you exit from the shell.  :-(

Working on identifying sde disk...