- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Problem booting RHEL 4 box - virtual media hel...
Operating System - Linux
1752288
Members
3533
Online
108786
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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-23-2009 02:17 AM
тАО02-23-2009 02:17 AM
Hi Guys,
I have a RHEL box which gives the following error once the VGs have been activated:
/sbin/init: error while loading shared libraries: /lib64/tls/libc.so.6: file too short
Kernel panic - not syncing: Attempted to kill init!
I'm assuming there is some sort of corruption on the disk.
The problem I have is this.. I am unable to PXE boot the box and I can only use the virtual media option for mounting a CD. I've been able to mount a RHEL iso but the problem comes when it asks where the install image will come from. If I select 'local CD' it tries to open /dev/cdrom and I assume is unable to map the virtual CD.
Can anyone advise a way I might be able to get a shell and potentially look at fixing?
Thanks in advance.
Tony
I have a RHEL box which gives the following error once the VGs have been activated:
/sbin/init: error while loading shared libraries: /lib64/tls/libc.so.6: file too short
Kernel panic - not syncing: Attempted to kill init!
I'm assuming there is some sort of corruption on the disk.
The problem I have is this.. I am unable to PXE boot the box and I can only use the virtual media option for mounting a CD. I've been able to mount a RHEL iso but the problem comes when it asks where the install image will come from. If I select 'local CD' it tries to open /dev/cdrom and I assume is unable to map the virtual CD.
Can anyone advise a way I might be able to get a shell and potentially look at fixing?
Thanks in advance.
Tony
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 08:04 AM
тАО02-23-2009 08:04 AM
Re: Problem booting RHEL 4 box - virtual media help?
Shalom Tony,
The recommended solution in this case is to boot the system off of CD media as you have tried.
Disk corruption may be the cause, but you are attempting to look at the system in hte acceptable fashion.
You should however try linux rescue instead of an install image. This is the path to diagnosis, though you will probably be reinstalling the system.
As for a media source for that, I suggest NFS.
linux askmethod
Its simple, its fast and usually not filtered.
sEP
The recommended solution in this case is to boot the system off of CD media as you have tried.
Disk corruption may be the cause, but you are attempting to look at the system in hte acceptable fashion.
You should however try linux rescue instead of an install image. This is the path to diagnosis, though you will probably be reinstalling the system.
As for a media source for that, I suggest NFS.
linux askmethod
Its simple, its fast and usually not filtered.
sEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 05:14 PM
тАО02-23-2009 05:14 PM
Solution
Gday,
We have built machines via virtual media - these days however using NFS and Kickstart is better than the virtual disk shuffle but its possible.
Insert CD1 iso (this is preferable than using desktop drive as virtual media - as we sometimes got some problems with systems locking up on it). When linux prompt appears press return and follow as one would normally - the only aspect is the shuffling of ISO images as the install asks for different CDs.
Note: Some virtual media environments - Proliant G2s dont have virtual CDROM drives only floppies, G3/G4s may only do CD and not DVD sized images so this may be an issue in that it reads up to 700mb then dies?.
PXE boot requires setting up PXEboot server from what I have seen - I just use RHEL1 disk to linux prompt and then type
linux ks=nfs:kickstartserver:/path/to/rhel
System will then ask for appropriate ethernet adapter and if you dont have dhcp will ask for ip address. As for NFS copy mount isos -o loop and copy out contents to directory and establish NFS mount point which the (all) servers can use.
as SEP mentioned RHEL disk #1 allows for rescue mode which may give some clues.
Also from a desktop boot the RHEL1 cd and disk media checks to ensure the CDs are ok.
You can also get some VG problems with incorrect sized partitions or incorrect kickstart configs - although this is more so from building your own kickstart scripts and setting up your own storage environment.
Robert.
We have built machines via virtual media - these days however using NFS and Kickstart is better than the virtual disk shuffle but its possible.
Insert CD1 iso (this is preferable than using desktop drive as virtual media - as we sometimes got some problems with systems locking up on it). When linux prompt appears press return and follow as one would normally - the only aspect is the shuffling of ISO images as the install asks for different CDs.
Note: Some virtual media environments - Proliant G2s dont have virtual CDROM drives only floppies, G3/G4s may only do CD and not DVD sized images so this may be an issue in that it reads up to 700mb then dies?.
PXE boot requires setting up PXEboot server from what I have seen - I just use RHEL1 disk to linux prompt and then type
linux ks=nfs:kickstartserver:/path/to/rhel
System will then ask for appropriate ethernet adapter and if you dont have dhcp will ask for ip address. As for NFS copy mount isos -o loop and copy out contents to directory and establish NFS mount point which the (all) servers can use.
as SEP mentioned RHEL disk #1 allows for rescue mode which may give some clues.
Also from a desktop boot the RHEL1 cd and disk media checks to ensure the CDs are ok.
You can also get some VG problems with incorrect sized partitions or incorrect kickstart configs - although this is more so from building your own kickstart scripts and setting up your own storage environment.
Robert.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2009 06:42 AM
тАО02-27-2009 06:42 AM
Re: Problem booting RHEL 4 box - virtual media help?
Thanks both of you.
Unfortunately I had to re-patch this box temporarily to get this done but will refer to this thread in future!
Thanks,
Tony
Unfortunately I had to re-patch this box temporarily to get this done but will refer to this thread in future!
Thanks,
Tony
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