From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Briggs Subject: Re: Boot Failure Date: Tue, 26 Jul 2011 09:24:26 -0400 Message-ID: <4E2EC00A.1030303@ll.mit.edu> References: <9180F6B27399C541B10663E21C8BDE9201D0F56C@0461-its-exmb09.us.saic.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1716063262443418532==" Return-path: Received: from mx1.redhat.com (ext-mx11.extmail.prod.ext.phx2.redhat.com [10.5.110.16]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p6QDOTkx015653 for ; Tue, 26 Jul 2011 09:24:29 -0400 Received: from mx2.ll.mit.edu (MX2.LL.MIT.EDU [129.55.12.46]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p6QDOSj3020058 for ; Tue, 26 Jul 2011 09:24:28 -0400 Received: from LLE2K7-HUB02.mitll.ad.local (LLE2K7-HUB02.mitll.ad.local) by mx2.ll.mit.edu (unknown) with ESMTP id p6QDOQ4H023355 for ; Tue, 26 Jul 2011 09:24:27 -0400 In-Reply-To: <9180F6B27399C541B10663E21C8BDE9201D0F56C@0461-its-exmb09.us.saic.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com --===============1716063262443418532== Content-Type: multipart/alternative; boundary="------------050901000800040003040500" --------------050901000800040003040500 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit I believe that after you boot from the live cd, you can remount the boot partition with something like mount -o rw,remount such as mount -o rw,remount /dev/sda1 if the boot /boot were on /dev/sda1 and you can just type mount to find out where /boot is currently mounted Good Luck PS - The "memory for crash kernel ..." thing is, I think, normal On 7/26/11 8:58 AM, Rye, Gene R. wrote: > > After loading RHEL5 onto a system and then configuring the security in > accordance with the NSA Guide, I cannot boot the system. I am getting > the error : > > Memory for crash kernel (0x0 to 0x0) not within permissible range > > Kernel panic - not syncing: VFS: Unable to mount root fs > on unknown-block (0,0) > > I believe there may be a problem with the /boot/grub/grub.conf file. > I can boot the system with a Fedora livecd but am denied access to > modify the file. Any words of help? > > Thanks > > Gene Rye > --------------050901000800040003040500 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit I believe that after you boot from the live cd, you can remount the boot partition with something like

mount -o rw,remount <device for boot partition>

such as

mount -o rw,remount /dev/sda1

if the boot /boot were on /dev/sda1

and you can just type

mount

to find out where /boot is currently mounted

Good Luck

PS -
The "memory for crash kernel ..." thing is, I think, normal

On 7/26/11 8:58 AM, Rye, Gene R. wrote:

After loading RHEL5 onto a system and then configuring the security in accordance with the NSA Guide, I cannot boot the system. I am getting the error :

Memory for crash kernel (0x0 to 0x0) not within permissible range

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)

I believe there may be a problem with the /boot/grub/grub.conf file. I can boot the system with a Fedora livecd but am denied access to modify the file. Any words of help?

Thanks

Gene Rye

--------------050901000800040003040500-- --===============1716063262443418532== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1716063262443418532==--