All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Briggs <pbriggs@ll.mit.edu>
To: linux-audit@redhat.com
Subject: Re: Boot Failure
Date: Tue, 26 Jul 2011 09:24:26 -0400	[thread overview]
Message-ID: <4E2EC00A.1030303@ll.mit.edu> (raw)
In-Reply-To: <9180F6B27399C541B10663E21C8BDE9201D0F56C@0461-its-exmb09.us.saic.com>


[-- Attachment #1.1: Type: text/plain, Size: 980 bytes --]

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
>

[-- Attachment #1.2: Type: text/html, Size: 3719 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2011-07-26 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 12:58 Boot Failure Rye, Gene R.
2011-07-26 13:24 ` Peter Briggs [this message]
2011-07-26 13:55   ` Steve Grubb
  -- strict thread matches above, loose matches on Subject: below --
2004-03-30 21:56 Boot failure Rune Torgersen
2004-03-30 20:50 Rune Torgersen
2004-03-30 21:43 ` Wolfgang Denk
2001-08-04 19:26 Boot Failure LeRoy Cressy
2001-08-05  1:54 ` Keith Owens
2001-08-06  1:18   ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E2EC00A.1030303@ll.mit.edu \
    --to=pbriggs@ll.mit.edu \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.