Topic: My e-smith 5.5 are chrashed - HELP.....

[Sonny]

Hi

My e-smith has crashed.... unfortuenly i wassent the person who discovered it, and the one that did just tryed to restart it, so i don't know what error there was written on the screen, when they did!

But when i tryes to restart, i get thees messages :

It starts as normal, and some  [   OK    ] aperes
The last one is : Initializing USB controler (usb-ohci)
And then the line where i get the error :
Checking root filesystem
/ contains a file system with errors, check forced.
/:
Inode 337913 has imagic flag set.

/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
      (i.e., without -a or -p options)
                                                                   [    FAILED    ]

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup):
(Repair filesystem) 1 #

---- end ---

But when i tryes to run fsck i just get this message

No device specified to be checked......

I am NOT specialy driven in linux, so i dont know what the comand "fsck" will do... and what comands i have to give to get it checked...

PLEASE help!

SIncerly
Sonny

[Dan Brown]

You need to specify the partition, which is probably /dev/hda6.  So, do

fsck /dev/hda6

[Sonny]

okay, i am now got a bit further...

I have typed the command
fsck /dev/hda
And get this messag :
fsck 1.26 (3-feb-2002)
e2fsck 1.26 (3-feb-2002)
Couldn't find ext2 superblock, trying backup blocks......
fsck.ext2: bad magic number in super-block while trying to open /dev/hda

the super block could not be read or dos not describe a correct ext2 filesystem.if the device is vallid and it really contains an ext2 filesystem (and not swap or ufs or somthing else), then the superblock is corrupt, and you might trye running e2fsck with an alternate superblock:
     e2fsck -b 8193

And i have then tryed to run : e2fsck -b 8193 /dev/hda
And get this messag :
e2fsck : Bad magic number in super-block while trying to open /dev/hda

the super block could not be read or dos not describe a correct ext2 filesystem.if the device is vallid and it really contains an ext2 filesystem (and not swap or ufs or somthing else), then the superblock is corrupt, and you might trye running e2fsck with an alternate superblock:
     e2fsck -b 8193


What shoud i do ????

Sonny

[Dan Brown]

Like I said before, you need to specify the PARTITION.

[Sonny]

and while i have written the last messag, there was an other post... i am in progres of dooing this, and got LOTS of Inode xxxxxx errors, Thees is in progres of being fixed....

Whye / When is this error occured..... ??
I can inform that the fokes inside of the network was in progres of uploading a new game site to the server (with maps etc.) it contains 530 MB of data
And then the server crashed in the middel of this operation....

[Chris]

try just typing

fsck /

and then answer yes to everything that comes up

[Ray Mitchell]

This excerpt from Abe Lovless's How to book may be useful
Regards
Ray

Recovery from power interruption with file check errors on reboot.

Occasionally every system will lose power.  You want to be sure to have your E-Smith / SME Server running through a UPS.  Linux, like all Operating Systems, frowns on in-correct shutdown procedures.  A power interruption, or just killing the power, may cause a file check error to occur during the boot process.

If this occurs, there are a few utilities that you can use to repair your disk and get the system booted correctly.  You will need to login as root, and execute the following commands.  In all cases, do not actually type the quotes, the last character is a number, and there is a space between “fsck” and “/dev/..”.

The following instructions vary depending on the harddrives inside your individual computer and their configuration.  Choose the configuration that matches your system.  “Test All Drives” should work if your system isn’t listed here.

1 Drive (IDE):
Type: "fsck /dev/hda1" and ENTER  
Type: "fsck /dev/hda6" and ENTER
Reboot: “shutdown –r now”

1 Drive (SCSI):
Incomplete.

2 Drives RAID1 Mirror (IDE):
Incomplete.

2 Drives RAID1 Mirror (SCSI):
Type: "fsck /dev/md0" and ENTER  
Type: "fsck /dev/md1" and ENTER
Reboot: “shutdown –r now”

Test All Drives:
(If you are un-sure what you have, this may be best.  However, documentation suggests that you should be careful doing this.  See the following article:
http://e-smith.org/bboard/read.php?v=t&f=1&i=13728&t=13720)

Type: “fsck –A” and ENTER
Reboot: “shutdown –r now”