Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Dano on February 23, 2002, 07:55:58 AM

Title: help w/ fsck?!?!?!
Post by: Dano on February 23, 2002, 07:55:58 AM
When starting my SME server, I get

**An error occured 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)

I type the password and get

(Repair filesystem) 1#

It does nothing after that, if i try control d it puts me back in the same place.

it says run fsck manually but i have no clue what is going on or how to do that.

what do i do?

any suggestions would be appreciated.
Title: Re: help w/ fsck?!?!?!
Post by: Bobby on February 23, 2002, 08:12:10 AM
Try this for IDE drives:
fsck /dev/hdx
of this for SCSI drives:
fsck /dev/sdx
or this for RAID:
fsck /dev/mdx

(x = the drive)

If this does not work then my memory is bad, as it has been a while since I had to do this.

/B
Title: Re: help w/ fsck?!?!?!
Post by: Kees Blokland on February 23, 2002, 12:14:33 PM
Maybe this helps too..

If you have a suspect disk, you might also want to try efsck
I recently had a 50G drive going funny, after applying the following spell
(took al night) it's totally happy again!

e2fsck -cvpy /dev/hdaX

typing 'e2fsck' at the prompt will show you the options available.

Before you do this, be very sure to read the man pages.
and on large disks this takes a LONG time!

see man:efsck at : http://nodevice.com/sections/ManIndex/man0299.html

have fun,

kees
Title: Re: help w/ fsck?!?!?!
Post by: Dano on February 24, 2002, 05:14:46 AM
once I e2fsck

what do I do to make the system run again?

How do I know the filesytem is repaired? How do I know its reparing?

I just need to get my e-smith back in action . . .!!!

HELP!

e-smith novice thanks you
Title: Re: help w/ fsck?!?!?!
Post by: Kees Blokland on February 24, 2002, 12:08:36 PM
Just reboot.

If it fixed the problem, you simply reboot and all is well.

If the problems were so bad it could not repair them, (unlikely) then you have a real challenge, and I would suggest you find someone locally who has a lot of unix knowledge.
He/she might be able to rescue some of you data.
If you are not sure, be carefull, it's easy to loose everything.

good luck.