Results 1 to 9 of 9
My Virtualbox installed REDHAT Enterprise 5 I don't know why ,open it prompt "Memory for crash kernel (0x0 to 0x0) notwithin permissible rang Red Hat nash version 220.127.116.11 starting exec ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 03-27-2009 #1
Memory for crash kernel !!!??
I don't know why ,open it prompt
"Memory for crash kernel (0x0 to 0x0) notwithin permissible rang
Red Hat nash version 18.104.22.168 starting
exec of init (/sbin/init)failed !!!ermission denied
Kernel panic - not syncing: Attempted to kill init!"
than stop here
Start rescue mode
chroot /mnt/sysimage chroot: cannot run command '/bin/sh': Permission denied rpm -qf /mnt/sysimage/sbin/init file /mnt/sysimage/sbin/init is not owned by any package rpm -qf /mnt/sysimage/boot/vmlinux-* file /mnt/sysimage/boot//vmlinuz-2.6* is not owned by any package
use rpm -ivh /directory/package --root /mnt/sysimage/ --force
- 03-27-2009 #2
welllooks like your fstab has bone down the drain...... oops ..... i mean got corrupted. mount the /etc partitions and recreate it. otherwise post the fdisk -l list and i maye able to help you.
- 03-27-2009 #3Code:
e2label /dev/hda2 e2label: Bad magic number in super-plock while trying to open /dev/hda2 Counld't find valid filesystem superblock
I don't think so!
But thank you very much
- 03-27-2009 #4
also please attach the result of the command blkid
- 03-27-2009 #5
I don't think so !
fstab is alright!
look that image!
- 03-27-2009 #6
I don't know how to say!
I think it's virtualbox problem!
- 03-30-2009 #7
- Join Date
- Aug 2006
- Portsmouth, UK
RHEL / CentOS 5 work just fine under virtualboxRHCE #100-015-395
Please don't PM me with questions as no reply may offend, that's what the forums are for.
- 06-20-2011 #8
- Join Date
- Jun 2011
memory for crash kernel (0X0 to 0 X 0) noth within permissible range,
i formatted my red hat server 64 bit amd type
after successfull installation when i rebooted my server there is error
"memory for crash kernel ( 0 X 0 to 0X0) not within permissible range.
kernel panic -not syncing :vfs:unable to mount root fs on unknown block(0,0)
kernel direct mapping table up to 228000000
so if any have solution then please wrtie to us at
or post here
- 06-20-2011 #9
Hello and Welcome,
Please start a new thread with a detailed description of your problems. This one is too old. *locking*