- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Kernel panic
ProLiant Servers (ML,DL,SL)
1756459
Members
3539
Online
108847
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2004 09:20 PM
02-22-2004 09:20 PM
Kernel panic
I have installed Redhat7.3 on HP Netserver lp2000r and it was working fine.Suddenly today morning ,it gave number of "connection are exceeded " .I was able to ping but unable to do the telnet.Restarted the system ,now it is no coming giving an error
"kernel panic" No init found .Try passing init = option to kernl.
I have two images 1.linux and 2. linux-up.It used to up with linux-up.Tried with rescue mode also ,and when I tried to run chroot /mnt/sysimage ,it gave a message ,unable to execute /bin/sh.As this system is little bit critical please do me help to bring this system up.
The lilo.conf entry is as follows.
prompt
timeout=50
default=linux
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32
image=/boot/vmlinuz-2.4.7-10smp
label=linux
initrd=/boot/initrd-2.4.7-10smp.img
read-only
root=/dev/sda3
image=/boot/vmlinuz-2.4.7-10
label=linux-up
initrd=/boot/initrd-2.4.7-10.img
read-only
root=/dev/sda3
The fstab entry is as follows.
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sda2 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0
0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
Thanks in advance,
Regards,
Raghu.
"kernel panic" No init found .Try passing init = option to kernl.
I have two images 1.linux and 2. linux-up.It used to up with linux-up.Tried with rescue mode also ,and when I tried to run chroot /mnt/sysimage ,it gave a message ,unable to execute /bin/sh.As this system is little bit critical please do me help to bring this system up.
The lilo.conf entry is as follows.
prompt
timeout=50
default=linux
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32
image=/boot/vmlinuz-2.4.7-10smp
label=linux
initrd=/boot/initrd-2.4.7-10smp.img
read-only
root=/dev/sda3
image=/boot/vmlinuz-2.4.7-10
label=linux-up
initrd=/boot/initrd-2.4.7-10.img
read-only
root=/dev/sda3
The fstab entry is as follows.
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sda2 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0
0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
Thanks in advance,
Regards,
Raghu.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2004 09:34 AM
02-24-2004 09:34 AM
Re: Kernel panic
Well these are always fun. When I have seen this it usually means a file in the /boot is clobbered. If you can get it to boot from a floppy and have a shell, you may be able to do a mkinitrd to recreate the ramdisk it wants to load. Otherwise I would do an "upgrade" of the Redhat 7.3 and then re-patch the kernel and other stuff...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP