while I am trying to boot the system the following error message is coming
"****an error occurred during the file system check
*****dropping u to a shell; the system will reboot
when u leave the shell
warning SELinux is active
disabling security enforcement for system recovery
RUN setenforce 1 to renable
Give root passwd for maintainance
or type ctl +D to reboot"

so what to do for coming out from this..

You have a hard drive that has an error (probably you forgot to shutdown to many times and now have some bad sectors). It has to disable SELinux prior to running fsck. So to get past this point you need to enter your root password and run fsck.

If you dont know what fsck is, google it, or try 'man fsck' at the CLI.

As for re-enabling SELinux, as far as im aware it should do it next time you reboot, but if not try running system-config-securitylevel (GUI), or the above command (CLI).

hi guys,
i am getting this problem while I am trying to boot the system:

"****an error occurred during the file system check
*****dropping u to a shell; the system will reboot
when u leave the shell
warning SELinux is active
disabling security enforcement for system recovery
RUN setenforce 1 to renable
Give root passwd for maintainance
or type ctl +D to reboot"

i suppossed i have a hard drive that has an error, so i tried a
fsck -A <device>
but it does not recognize the device .. it does not exist.

i also try fsck -p, but it says that maybe the superblock is corrupted :-(

do i need the rescue CD ?

what to do ?

is there any where a document to try reparing my HD ?

thanks in advance

hector

If you want to reap you entire Hard Disk there is a command available in linux that is "dd"
You can make a image copy of any file or folder. You just need to run the command
dd bs=1024 if="input file" of="output file"
here this command copies by reading each bit of the input file to the output file. The bs specifies the bit rate.
Try this out and first read the manual for dd
you will get the manual for dd with "man dd"




For more check this link: http://www.macosxhints.com/article.p...50302225659382

I'm not sure but most repair software only mark bad sectors and transfer other data near to it to another safer place. The problem here also is that most new HDs when they start to have bad sectors rapidly earn more bad sectors until they get totally useless. Older ones get destroyed slower since they have larger magnetic area for each data they save.

Edit:
sorry you don't have a hardware problem do you? only bad superblocks..

First of all you should run 'fdisk -l' as root to check if the system can sense the HDD at all (it will list available devices). No use to run 'fsck' until that.

The problem you describe can also happen if you changed or replaced disks in your PC, and due to different master/slave positions your mount configuration in /etc/fstab is not valid anymore - at least not for customized lines. Adjusting these mountpoints solves the problem in such cases.

If fdisk doesn't see the disk even after that step, then the damage is severe. Otherwise you can then use 'fsck' or some utility to test the disk.


Hope this helps,
Regards,
SIMP

Linux Archive

hi guys,
thanks for your help ... i really dont know what happened but after a long/long nigt trying to recognize the disk, after many mesages like "device unknown" or "superblock ... corrupted ...", after many system restarts, i shutdown the pc and went to sleep.

Next day my hd was recognized at booting time :-) and the information looks fine ... i hate this, but i dont have idea about what the problem was :-(

physical connections ?

cheers,

hector

most of the time it's a power supply problem if not connections.

edit: what i mean is in the whole system unit or just on the hd itself..hmm..hope it's just the PSU.

This doesn't happen very often, but I had a few similar issues.
In my case it had (most likely) to do with overheating, but you never get to know for sure.

Bye,
SIMP

it happened again :-(
last time i work i didnt turn off my pc, and after 24 hour i found it with a "no signal" message in the screen; not answer anymore, so i reset it and had the same problem, same messages, no recognized device (the hard disk). I just turnoff my pc and went to watch TV for 30 minutes, ... and guess what ??? ... after 30 minutes it has boot normally :-) ... i agree with SIMP, the problem is OVERHEATING.

so, what to do ?
what to change ?
ventilator ??

cheers,

hector

ok so it's overheating ..

now about the ventilation, why not just add another fan and not change?

edit:
hmmmm... but still about lowpower and overheating it can be like this:

overheat->circuitry, capacitors, resistors, etc. makes stronger resistance->low power->unreadable disk

Computers normally are equipped with the required amount of fan power.

The problem most often is that the PC-box is put in some narrow place or is surrounded by all kind of stuff that does not allow for proper air circulation.

If the problem would be the fan alone, than the PC would crash after an hour. With the case as described above it really takes longer. Exchanging the fan would only extend the time it takes to become overheated.

Hope this helps,
Regards,
SIMP

I find that I often have to make and remake the PATA connectors on my older - about 3 years old - Athlon2400 machine. It seems that here in Aotearoa/NZ, where the RH (humidity) is generally 60%+, the connectors can easily "grow" bad connections.

Sometines at bootup the pc won't show one of the hdds or I will hear lots of unusual noises coming from one of them while running - so I then know that it's time to make/remake the PATA connections. And usually/uptonow everything works OK after doing this.

My tuppence worth :-)

Paul W

Hi to all,

Today morning I booted my linux box after a long time may be after 1 month. I got a problem over here. In booting time I got a message box with "The greeter application appears to be crashing. Attempting to use a different one". While clicking to ok. Nothing happened. The message came again. I don't know how to fix this bug. Is there any problem with the Hard Disk. The hard disk, installed with linux is 5 years old. Now what to be done?