Our server froze during the night , when we came in and restarted it , it came up with a kernel panic . We have see this before and run a fsck command in rescue mode and it sorts out the problem .
When we run
fsck -p /dev/sda2
we get the following
fsck: Waring : couldn't open /etc/fstab: no such file or directory
fsck.ext2: Bad magic number in superblock while trying to open /dev/sda2
The superblock could not be read or does not describe a correct ext2 file system. If the device is valid and ...........
The server is running a mirror raid from the bios.
I can boot from both disks and get the exact same error message
( I have not typed to whole screen as it is in a photo )
to make the problem worse the computer is of site in a remote location !
any advice that can help to get he the PC up and running again
Regards
Justin
When we run
fsck -p /dev/sda2
we get the following
fsck: Waring : couldn't open /etc/fstab: no such file or directory
fsck.ext2: Bad magic number in superblock while trying to open /dev/sda2
The superblock could not be read or does not describe a correct ext2 file system. If the device is valid and ...........
The server is running a mirror raid from the bios.
I can boot from both disks and get the exact same error message
( I have not typed to whole screen as it is in a photo )
to make the problem worse the computer is of site in a remote location !
any advice that can help to get he the PC up and running again
Regards
Justin
In Hardware
Share this post:
Responses (11)
-
Accepted Answer
Noted the typo, !
We have two disks and are using only one , they are part of a hardware raid , the other is untouched !
Regards
Have you ever used the command
mke2fs -S /dev/xxx in our case xxx = sdb2
followed by
e2fsck /dev/xxx in our case xxx =x sdb2
We have run this and are answing yes to all the "do you want to fix "
There seem to be quite a few of them.
Will let you know if it works or not !
cowboy style i know
Regards
Justin -
Accepted Answer
I don't know what advice to give here. I just knew about this fixing route which I may have used before, but I can't remember. Conventional wisdom says you should not work on your live disk. The first thing you should do is make a bitwise clone of the disk to a new disk using something like the command dd, then you try all your repairs on the clone.
After that, all I can suggest is trying different superblocks.
FWIW your last command in the second screen shot is missing the last digit (0 or 8) - 265400 (or 8) -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Ok, We have got a list of superblock backups by typing in the following comand
mke2fs -n /dev/sdb2
and we get a list
When we run the command
e2fsck -b 32768 /dev/sdb2
it comes up with the same error message.
e2fsck : Bad magic number .........
is it reasonable to try all number blocks or am i doing something wrong with the command ?
We are in rescue mode with clearos 5.2
e2fsck version 1.39 (29-May-2006) -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Dear Nick, Many thanks for your prompt reply !
Let me clarify. When I say we “normally “run the fsck command it is on other servers and this happens when it has been uncleanly shut down. But only once in a blue moon. This particular server has never given any problems before. However it is in rural Zambia! Where the power utility service is erratic, especially during the rainy season!
I will update this post once I have had a chance to run the commands.
Many thanks
Justin Richards -
Accepted Answer
Have a look at this link, among others. Although it is for ext4 it should be the same for ext2. Or else try a program such as TestDisk.
I'd be quite concerned if this is regular and I'd suspect a hardware issue. Do you have SMART disk's. If so have a look at smartmontools, available in clearos-core. Also could you have a m/b problem?
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »