Re: URGENT AND MAJOR RH 7.2 Problems - PLEASE HELP

Eric Koldeweij <[email protected]>
Newsgroups gmane.linux.redhat.release.enigma
Message-ID <[email protected]>
This sounds like a hardware problem, more specific the hard drive. I 
suggest putting in a new HD  and see if it helps.
I'm not sure though, you give little information to work with. It could 
also be faulty memory... bad mem always gives totally unpredictable results.
Assuming it's a more or less regular Intel 386 or Athlon machine, the 
weirdness of the errors (as in they're errors not caught by the 
handlers) points to faulty hardware, probably the HD or memory.

Eric.

[email protected] wrote:

>This is for a server I need to be up by Wednesday, so I'd appreciate any
>help whatsoever.
>
>I have a big 'ol problem with the RH 7.2 install. I'm installing in text
>mode, as X doesn't work with this gfx card. Here goes: 
>
>
><0>Kernel panic: Attempted to kill init! 
>Unable to handle kernel NULL pointer dereference at virtual address
>00000000 
>printing eip: 
>00000000 
>*pde = 00000000 
>Oops: 0000 
>CPU: 0 
>EIP: 0010:[<00000000>] 
>EFLAGS: 00010282 
>
>(stack trace is here) 
>
>Process IJKLMNOPQRSTUVWXYZ (pid 1, stackpage=cffe0000) 
>Code: Bad EIP Value. 
><0>Kernel Panic: Attempted to kill init! 
>
>
>And then the install stops, I have to reboot to get it to try again. I get
>the same error every time, and I even tried switching install media. 
>
>Just for kicks, I tried installing RH 8, and here's what I got: 
>
>
>(regular initilaztion output) 
>invalid compressed format (err=2)<6> freeing initrd memory: 2648k freed 
>EXT2-fs: unable to read superblock 
>cramfs: wrong magic 
>FAT: unable to read bootsector 
>isofs_read_super: bread failed, dev=09:02, iso_blknum=16, block=32 
>Kernel panic: VFS: unable to mount root fs on 09:02 
>
>And the install stops. Same error every time. 
>
>Any ideas? Please email me or call me. 
>  
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.