Goodday.

Current user of Redhat 9.

I did a unclean shut down and GOD!!!!
I wouldnt boot up.

At first i just says that the system encountered a unclean shutdown and
forced into an intergrity check.
it shows
%=========10.8

And just hang for a very long time.

So a restart again, it hang again. I restarted a few time and it came to stage

with all black screen and wordings i dun understand below

CALIBRATING DELAY LOOP....1998.84 BogoMIPS
----------------[cut here]-------------------------------
CPU: 0
EIP: 0060:[<c013e1c8>] Not Tainted
EFlags:00010206

EIP is at __free_pages_ok [kernel] 0x38 (2.4.20-8)
eax: 00000000 ebx:c100dff8 ecx:c100dff8 edx:00000000
esi:000003ff edi:0000000 ebp:00440000 esp:c034df1c
dx:0068 es:0068 ss:0068
Process swapper (pid:0, stackpage=C034d0000)
Stack: c030.........................

Call trace : [c0110068>] dump_fpu[kernel] 0x48 (0xc034df98))
[<c0105000>] stext[kernel]] 0x0 (0xc034dfe0))

Code:0f 0b,..........................

<0>Kernel panic:attempt to kill the idle task!
In idle task - not syncing


PLEASE HELP ME!!!!!!!!!!

Boot into rescue mode using the first RHL9 installation CD (boot: linux rescue), but don’t search for or mount the RHL9 installation. If you get a screen telling you to run “chroot /mnt/sysimage”, then reboot and start over.

From rescue mode, check the filesystem integrity on each linux partition using fsck (e.g., “fsck -fvt ext2 /dev/hda1" or “fsck -fvt ext3 /dev/hda1"). If you are not sure about which partitions to look at, then run “fdisk -l”, which will give you a listing of all partitions. You should be able to run “man fsck” and “man fdisk” from rescue mode for more info on the commands.

If you are using an ext2 filesystem, then recovery may take a long time, meaning hours.

OK!
I ran "linux rescue"
they ask for my "language" , and next they ask for "location" blah, blah .....
than they says i press return to some SHELL thing? I dun really understand?

And what happen is the following
sh-2.05b#
I guess it is here, that you want me to run the fsck command .

sh-2.05b# fdisk -l

Disk /dev/hda 40.0GB , 40020664320 bytes
240 heads, 63 sector/tracks, 5169 cylinders
Units = cylinder of 15120*512 = 7741440 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2709 2048008+ 7 HPFS/NTFS
/dev/hda2 2710 5169 18597600 f Win95 Ext'd(LBA)
/dev/hda5 2710 2723 18597600 83 Linux
/dev/hda6 2710 2723 18597600 83 Linux
/dev/hda7 2710 2723 18597600 83 Linux
/dev/hda8 2710 2723 18597600 83 Linux
/dev/hda9 2710 2723 10939288+ 83 Linux
/dev/hda10 2710 2723 521608+ 83 Linux
/dev/hda11 2710 2723 234328+ 83 Linux
/dev/hda12 5123 5169 128488+ 83 Linux

Disk /dev/hdb 80.0gb 80000000000000bytes
240 heads. 63 Sector/Track . 10337 cylinders
Units =cylinders of 15120*512 = 7741440 bytes

Device Boot Start End Blocks Id System
/dev/hdb2 1 10337 78147688+ c Win95 FAT32(LBA)

Than i ran
sh2.05b# fsck -fvt ext3/dev/hda1
fsck 1.32 (09-NOV-2002)
WARNING: couldnt open /etc/fstab:No such file or Directory

And
sh2.05b# fsck -fvt ext2/dev/hda1
fsck 1.32 (09-NOV-2002)
WARNING: couldnt open /etc/fstab:No such file or Directory

sh-2.05b#man fdisk
sh: man: commanf not found

sh-2.05b#man fsck
sh: man: commanf not found

Rescue Mode gives you a command prompt with access to a few commands without mounting your linux installation. Think of it as a Barely-Alive CD linux vs a Live-CD linux like Knoppix. If you have a Knoppix disk, you can use it instead of RHL9 rescue mode to do the repairs.

RHL9 Rescue Mode is somewhat explained in the RHL9 Customization Guide: http://www.redhat.com/docs/manuals/l...mode-boot.html

You need to use the correct partitions with fsck like this:

fsck -fvt ext3 /dev/hda5
fsck -fvt ext3 /dev/hda6
fsck -fvt ext3 /dev/hda7
fsck -fvt ext3 /dev/hda8
fsck -fvt ext3 /dev/hda9
fsck -fvt ext3 /dev/hda10
fsck -fvt ext3 /dev/hda11
fsck -fvt ext3 /dev/hda12

The options (-fvt ext3) are “force”, “verbose” and “ext3 filesystem”.

OK Buddy!

-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda5
-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda6
-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda7
-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda8
-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda9
-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda11
-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda12

And i get similar results below. I rem it was hda7 that ask me to fix certain items
And i press "Y" all the way. I believe it is hda7 that is corrupted.

fsck 1.32 (09-Nov-2002)
WARNING:couln't open /etc/fstab:No such file or directory
e2fsck 1.32 (09-Nov-2002)
Pass 1 : Checking inodes, blocks and Sizes
Pass 2: Checking directory structure
Pass 3: Cecking directory connectivity
Pass 4: Checking refernce counts
Pass 5: Checking group summary infomation

1242 inodes used (2%)
135 non-contiguous inodes (10.9%)
# of inodes with ind/dind/tind blocks:241/15/0
47586blocks used 20%
0 bad blocks
0 large files

933 regular files
289 directories
0 character device files
0 block device files
1 fifo
0 links
9 symbolic links (9 fast symbolic links)
1 socket

Strange thing is for hda2 and hda10.
I gor different results

-/bin/sh-2.05b#fsck -fvt ext3 /dev/hda10

fsck 1.32 (09-Nov-2002)
WARNING:couln't open /etc/fstab:No such file or directory
e2fsck 1.32 (09-Nov-2002)
Couldnt find ext 2 superblock, trying backup blocks..
fsck.ext3:Bad magic number in super-block while trying to open /dev/hda10

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contain a n ext2 filesystem( and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with the alternate superblock:
e2fck -b 8193 <device>

I reboot my PC and it is finallyt working!!!!!!!!

I am sincerely greatful.

I would like to say a "BIG THANK YOU"!!!!!!

It’s good to hear that everything worked out.