- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- linux OS issue
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
тАО06-25-2010 03:09 AM
тАО06-25-2010 03:09 AM
linux OS issue
After giving fsck with bootable CD the system is showing the output as below in multiuser mode.
WARNING:
This is a private computer system and should only be accessed by authorised
users. If you do not have prior authorisation to access this system you must
disconnect immediately or face criminal prosecution for attempting to gain
confidential information through unauthorised access.
(none) login:
If we give the password then it is just erasing the entered login name without showing even any error message
If we enter in Single user mode it is showing the error as "SELinux:Disabled at runtime"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2010 03:14 AM
тАО06-25-2010 03:14 AM
Re: linux OS issue
As for the system not showing a login or shell in Single User mode: it looks like the getty lines are gone for the single usermode inittab entries....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2010 03:47 AM
тАО06-25-2010 03:47 AM
Re: linux OS issue
After hardboot done , then it is showing the same error message both in single and multi user modes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2010 12:10 PM
тАО06-25-2010 12:10 PM
Re: linux OS issue
If the kernel has been compiled with the SELinux feature enabled (like most distributions' standard kernels are), this message is displayed at boot time if SELinux has been switched off.
In single user mode, there may be no syslogd/klogd running, so the kernel messages will be displayed directly on the system console. They may in some cases hide/overwrite the single-user login prompt. Try pressing Enter once or twice when booting into single user mode to re-display the prompt.
It might be that the problem affects the early phases of the boot-up sequence, and makes even the normal entry to the single user mode impossible. In that case, you might try booting the system using the rescue mode of the Linux installation CD/DVD.
As Elmar said, your system seems to have lost at least some configuration files. I hope you have some good back-ups available, or at least know/have documented the correct configuration for this system.
Without knowing the name and version of your Linux distribution, it's going to be very difficult to give exact instructions for recovery. Could you please identify your Linux distribution?
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2010 09:24 PM
тАО06-25-2010 09:24 PM
Re: linux OS issue
Linux vps211 2.6.9-78.ELsmp #1 SMP Wed Jul 9 15:46:26 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
Is there any other solution other than restoration of OS, since there is no back up available for the system.Avilable backup is Old, it is of Aug 2009. Can i restore root ,boot partitions ? Is there any problem with that? Is any configuration will loose if i do this process
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2010 11:47 PM
тАО06-25-2010 11:47 PM
Re: linux OS issue
Restoring the boot partition is probably not necessary: if it had failed, your boot wouldn't go nearly as far as it does now.
Restoring the entire root filesystem might be overkill if you're only lost some small files. By the symptoms, you've lost at least some files from /etc/sysconfig. If that's all, it should be easy enough to fix.
You might want to restore the /etc directory from your old backup to some temporary location (e.g. /tmp/etc), or to a removable media, like a USB memory stick. Then start comparing the files you currently have in your /etc/sysconfig to the old files in the backup.
I think one of the files you've lost is /etc/sysconfig/network: it is used to configure the hostname of your system. This would explain why your login prompt is now "(none) login:".
You might also want to look into /lost+found: if the fsck finds salvageable files from a corrupted directory, it will store them to /lost+found with an auto-generated name. Each file you find in /lost+found has gone missing from its proper location. Some files may have been completely lost, so you cannot rely on finding all the missing files in lost+found.
If you see a large number of files in lost+found, you'll know your root filesystem was pretty severely damaged. In that case, you might consider more drastic recovery options, like restoring the entire root filesystem from the old backup, or even salvaging whatever important data you can find, then reinstalling the system.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2010 04:49 AM
тАО06-26-2010 04:49 AM