- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Tru64 v4.0f boot problem
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО07-28-2005 09:05 AM
тАО07-28-2005 09:05 AM
Tru64 v4.0f boot problem
INIT: command is respawning too rapidly. Check for possible errors.
id: cons "/usr/sbin/getty" console console vt100.
I know this is from the inittab file and I've tried to boot in single user mode and mount the file sets to see what is in the inittab, but I am only able to perform the /sbin/bcheckrc and /sbin/update, but cannot get the/sbin/swapon -a cmd to work... it says the device doesn't exist...
We did have some hardware problems and a terminal was attached for RMC commands.... maybe something there was reset?
Any suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 09:33 AM
тАО07-28-2005 09:33 AM
Re: Tru64 v4.0f boot problem
>>> show dev
Verify that you can see all disks and devices connected.
If you changed an adapter, maybe the disk naming changed, and a new device was generated because the device naming in 4.0F depends of the SCSI ID and LUN numbering.
You should check that all dk* devices are detected as they where before the problem, or correct the entries in /etc/fstab and the links on /etc/fdmns to reflect the changes.
If you don't know the output from show device before the hardware problem, that will be a problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 09:50 PM
тАО07-28-2005 09:50 PM
Re: Tru64 v4.0f boot problem
I usually got that error when it could not mount /usr. Could you please state os version and patch kit version? Please also tell us whether you use lsm.
Check in fstab or sysconfigtab what swap device is accessed with swapon -a
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 09:51 PM
тАО07-28-2005 09:51 PM
Re: Tru64 v4.0f boot problem
forget the os question.
Can you post fstab?
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2005 07:57 AM
тАО07-29-2005 07:57 AM
Re: Tru64 v4.0f boot problem
That solved the problem... I would imagine that there were discrepancies in the system tables and what hardware was actually in the machine. During the process of determining what our hardware problem actually was, the system was rebooted with various cards removed, etc. After further discussions with hardware guys, we determined that rebuilding the kernel was the solution.