Red Hat 6.2 Installation - "received signal 11" error

Red Hat 6.2 Installation - "received signal 11" error

Post by fmSTAF » Sun, 31 Dec 1899 09:00:00



on installing red hat 6.2, everything worked fine.
it was partitioned within an extended DOS partition.

then one day i deleted the logical DOS partitions within
the extended DOS partition (containing Linux).  although
i technically didn't touch the linux partitions, i can no longer
access linux.  kernel panic, can't open root ... something like that

so, i figured that i would simply reinstall red hat 6.2 on the system
this time, reorganizing the partitions so that it's no longer within
an extended DOS partition.  result: i can't neither update, nor install
linux on my machine!

each time i attempt to use fdisk or disk druid to reset my partitions,
the install exits saying, "exiting install abnormally...received signal
11..."
and then proceeds to close everything down, eject the CD, and tell
me that my system is ready for reboot.

can anyone tell me what signal 11 is?  how to deal with it?
how to simply erase all linux partitions and start anew?

thanks
-robert m.

 
 
 

Red Hat 6.2 Installation - "received signal 11" error

Post by Gregory Crutche » Sun, 31 Dec 1899 09:00:00



> on installing red hat 6.2, everything worked fine.
> it was partitioned within an extended DOS partition.

> then one day i deleted the logical DOS partitions within
> the extended DOS partition (containing Linux).  although
> i technically didn't touch the linux partitions, i can no longer
> access linux.  kernel panic, can't open root ... something like that

> so, i figured that i would simply reinstall red hat 6.2 on the system
> this time, reorganizing the partitions so that it's no longer within
> an extended DOS partition.  result: i can't neither update, nor install
> linux on my machine!

> each time i attempt to use fdisk or disk druid to reset my partitions,
> the install exits saying, "exiting install abnormally...received signal
> 11..."
> and then proceeds to close everything down, eject the CD, and tell
> me that my system is ready for reboot.

> can anyone tell me what signal 11 is?  how to deal with it?
> how to simply erase all linux partitions and start anew?

> thanks
> -robert m.

Below is from the Redhat knowledgebase. Hope it helps.

Good Luck!!

                                                  Product Description
                                                                 Red Hat
Linux 6.0/Intel
 Summary
                Multiple failures while loading packages
                                                  Problem Code

 Problem Description

                 Install fails repeatedly while loading packages. Failure
occures at
                 different points i.e. Package 8 of ~273 (server), 40 of
~273, 137 of ~273

                 Also the messges are not consistant from one failure to
the next.

                 An example follows:
                 <6> Adding 72256 swap space (priority 1)
                 <5> ll_rw_block: device 03:05 only 1024-char blockes
implemented (12032)
                 <1> Unable to handle kernel NULL pointer dereference at
virt addr 000000
                 <1> Current -> tss.cr3 = 07fdd000, %cr3 = 07fdd000
                 <1> *pde = 000000000
                 <4> Oops: 0000
                 <4> CPU: 0
                 <4> EIP: 0010:[]
                 <4> Eflags: 00010203
                 ...
                 VFS: Cannot open root device 08:21
                 Kernel panic: VFS: Unable to mount rootfs on 08:21

                 Objective: Configure as Internet Web Server
                 Symptoms of other failures:

                 ...
                 <2> EXT2-fs error (device ide0(3,5)):
ext2_check_blocks_bitmap: Wrong free blocks count in super block, stored =

                 3997817, counted = 3997825
                 <1> Unable to handle kernel paging request at virt addr
eef88d89
                 <1> Current -> tss.cr3 = 07f10000, %cr3 = 07f10000
                 <1> *pde = 0000000000
                 <4> Oops: 0000
                 ...
                 install exited abnormally -- received signal 11
                 ...

 Resolution Description

                 This problem can sometimes be caused by large amopunts of
memory on the
                 machine. The following boot parameter passed at boot time
circumvents the
                 problem:

                 boot: linux mem=64M