First off if this happened to someone before... I feel so sorry for you.

when i booted i got,
error in /ect/devfsd.conf

/ect/rc.d/rc.sysnit : line 253 /dev/tty0:fic/dir }or something like that. it was for the keymap{

fsch.exds/dev/hda1
The supermount could not be read or it doesn't describe a correct ext2 filesystem. If device is valid and it contains ext2 filesystem(and not swap or system or somely device), then the superbloxk is corrrupted, and you might try running e2fsch with an allernative system file
e2fsck -b 8193 <device>

no such file/discribtion while truing to open /dev/hda1faleed to check system files

fsch.ext3 doesnt exist

ill give some background while my brother was logging out it froze and he turned it off.

that is all i know

It's meant to be fsck not fsch. I don't know if that helps you. Does your computer actually make it to either the command prompt or X?

We'd definitely need some background to solve this.

Is the computer in question running Mandrake 9.2 as indicated by your user info, or is it your brother's machine, which is running another distribution? If so, which one? Was this a new install? An install that had previously been running fine? If a previous install that had been running, did you upgrade anything (the kernel, for example)? If Mandrake, did you try to update to 10.0 packages in some way? Did you install any new hardware, or move any hardware around (meaning, could any internal cables have been loosened, such as IDE cables)? If you added a new piece of hardware, what is the size/wattage of your power supply unit? What are the specs of the PC as a whole (mobo, CPU, video card)?

What type of drive or drives are these (ATA, serial ATA)? What is the setup of the drive or drives (is it one drive partitioned into several sections or several drives, and what is their order of connection to the motherboard)? How old are they? Could the drive(s) it/themselves be failing? Can you test them in another PC? Are the drives in a RAID configuration? Are they connected to a RAID controller on the motherboard without being in a RAID configuration? Are the drives connected to a controller card (which might be failing)? What other drives do you have in the system (CD-ROM, DVD-ROM, etc)? Can you disconnect one of them temporarily and see if the problem persists (my PC recently wouldn't even POST because my CD-RW drive went belly up). Is this a dual-boot machine? If so, does Windows boot? If not, have you tried booting from the Mandrake 9.2 CD 1 and doing a rescue boot of the system (meaning, you can try to boot your installed system from CD 1, which is also a Rescue CD)? Do you have any Live CD distros around (Knoppix, Mepis, Mandrake Move)? If so, have you tried booting from that and mounting your installed partitions to see if they can be read?

Basically, the error message indicates that the drive or drives is or are borked, but what we need to determine is whether this is true or not.

Drives can appear borked because they are (of course), or because something else (either hardware or software) is borked, and preventing the drives from being read properly, even though the drives are actually fine.

Sorry for your trouble, though... this is really ugly. Hang in there.

Q:Is the computer in question running Mandrake 9.2 as indicated by your user info, or is it your brother's machine, which is running another distribution? If so, which one?
A:it is on the family machine, running mdk 9.2 (i dont ask about mine... i just reformat it)

Q:Was this a new install?
A:Old install

An install that had previously been running fine?
A: yes it was running fine
Q: If a previous install that had been running, did you upgrade anything (the kernel, for example)? If Mandrake, did you try to update to 10.0 packages in some way?
A: i tried installing k3b for 10.0, because the 9.2 didn't work

Q: Did you install any new hardware, or move any hardware around (meaning, could any internal cables have been loosened, such as IDE cables)? If you added a new piece of hardware, what is the size/wattage of your power supply unit? What are the specs of the PC as a whole (mobo, CPU, video card)?
A: only thing that happened prior to this is the Ethernet cable was removed... but i did that a few times before with out any problems

Q:What type of drive or drives are these (ATA, serial ATA)? What is the setup of the drive or drives (is it one drive partitioned into several sections or several drives, and what is their order of connection to the motherboard)? How old are they?

A: 1 ide CD rw drive(3 yr), 1 DVD +- r/rw with CD rw support(<1yr), and one ide hard drive the hard drive is running windows 2k C, E drive, mdk 9.2 (root home swap) (<1yr)
hd slot 1
DVD slot 3
CD rw slot 4

Q: Could the drive(s) it/themselves be failing? Can you test them in another PC?
i am not sure... and i cant test them

Q:Are the drives in a RAID configuration? Are they connected to a RAID controller on the motherboard without being in a RAID configuration?
A: i don't think i raided them

Q:Are the drives connected to a controller card (which might be failing)?
A:no they are all ide

Q: Can you disconnect one of them temporarily and see if the problem persists (my PC recently wouldn't even POST because my CD-RW drive went belly up).

A:i don't think the problem would be with an optical drive

Q: Is this a dual-boot machine? If so, does Windows boot?
A: I am in windows on the same HD... and i am hating every second of it

Q: If not, have you tried booting from the Mandrake 9.2 CD 1 and doing a rescue boot of the system (meaning, you can try to boot your installed system from CD 1, which is also a Rescue CD)? Do you have any Live CD distros around (Knoppix, Mepis, Mandrake Move)? If so, have you tried booting from that and mounting your installed partitions to see if they can be read?
A: I wouldnt know what to do in the rescue mode...
bootable distro no... but i could try one...


... the linux /home is there... but i cleaned it up in failsafe with a lot of bad inode and i could view the / directory in the repair mode in the boot function... but i don't now what to do with it...

-----------------------------------------------------------------------------------------------
adz
It's meant to be fsck not fsch. I don't know if that helps you. Does your computer actually make it to either the command prompt or X?

sorry about the typo i writ with a green sharpie( in script) and it kinda blurred...
i could you the command prompt... kinda... repair during boot... but not x (which i hope when ever i boot this box.

I assume that means your boot process actaully makes it as far as the command prompt. If that is the case, could you type (as root) shutdown -Fr now? This will run fsck on boot.

... i could type it... but it did not do anything... and nothing ran

It doesn't look like this is recoverable. If the cp command works I recommend you back up as much stuff as you can. Then format and reinstall. Then hope it's not a hardware problem.

that sounds like what my fall back is...
anyway what does that cp command do...
i have a second hard drive that i can use to burn stuff off this one i am having a problem with it is just not convenient for me to get it...
and i am prying that it is not a hardware problem...
and read my signeture

The cp command copies files from <source> to <destination>.

Try cp --help or man cp for more details.

I hope it's not a hardware problem too, but I don't feel too hopeful about it, sorry to say .

... it is an on going hardware battle... too bad i had the box for 5 years...
but i built a new one... but now i am working on the ram so hopefully this type of problem will soon stop for me
and i only use windows 2k as a fall back, looking for help with a linux problem when linux is not booting