![]() ![]() You can imagine that list of programs, including the X server, as another stack inside the User Stack. More than likely X server, a window manager and some programs. Somewhere inside the User Stack, you have programs running. We want to find a way to avoid a reboot or at least provide the cleanest reboot possible to avoid corruption.įor the purpose of this article, Linux can be seen as a set of 2 stacks: The Kernel Stack and The User Stack. At this point, we are not looking to save any unsaved work. One can attempt a few tricks with Linux in such a case. Then comes the awful feeling as you push and hold “Power”. I mean the above plainly and with a full absence of negativity, but wanted to reply to your last comment.Linux is known to be very stable, but even the most stable system can encounter situations that cause it to become unresponsive. If you can find an OS that doesn't have some discussion group or need for troubleshooting or a support plan - make sure to pick that one. ![]() If you want something that never freezes or requires tuning, you will find that will be a tough call in the long run because any OS can be betrayed by it's lack of care/feeding, proper instantiation or ill-administration, or even 3rd party software not properly instantiated. END EDIT Operating systems that freeze etc may be the result of numerous things such as memory leaks (databases, and more), a simple kernel patch for oracle, a full file system, or not going back to a previous kernel on rare occasion. Solaris Unix is actually very stable, and while my preference is Linux, Solaris is quite stable. EDITED: the last statement was too heavy handed. ![]() That aside, my Linux systems have far more stability in my environment than the windows systems and the Solaris systems. Although the BSD folks (bless their hearts) might say theirs is the most stable etc. I've been an administrator with time in the trenches across most major operating systems and RHEL Linux is far more predictable and stable than all the others I've dealt with over decades. the tips folks gave above - you might have been back in business quickly. Hopefully others will join in and provide anything I may have missed above,īy the way, rhel is quite stable. Also check your /etc/fstab against the df -PhT output from log]# df -PhT | column log]# grep -v ^\# /etc/fstabĬheck your partitions with 'fdisk -l' 'pvdisplay' 'vgdisplay' and 'lvdisplay' and compare to your df -PhT output and output from your /etc/fstab.Ĭome back here and post if you need more help - someone should probably reply.Check your mounts (local while in single-user mode) to see if everything mounted as expected:.Check your /var/log/yum.log file and see if you have any recent log]# cat /var/log/yum.log.The question marks above will be different - make note of the date of nf, vmlinuz and initramfs files and determine if you the time/date stamps correspond with the issues you faced. 1 root root 1800 ?:? log]# ls -l log]# ls -ltr /boot/ | egrep 'vmlinuz|initramfs' Below, check to see if you got a recent kernel update:ġ) The time/date stamp of your /boot/grub/nf to see when the last time it was updated (that is when the most likely time you received a kernel update)Ģ) The time/date stamp of /boot/vmlinuz- and log]# ls -l /boot/grub/nf.check your output for anything obviously wrong. ![]() You'll have to scroll up to get past the typical boot messages, but dig for a while and see if there's any obvious errorrsĪlso, do a dmsg and scroll through the results to see if there's anything that looks like it failed. Look in the messages file (while in "less messages" hit SHIFT G together to go to the bottom of the log. Then cd to /var/log/ - and check the latest log files written to (probably messages file, maybe the yum.log file) ~]# cd log]# ls log]# less messages If you are able to get to the grub menu, go to single user and log in. Do you have another like system that is behaving well and is not experiencing these issues?.Did you make any changes to your /etc/fstab very recently?.Is your system hanging on a remote mount?.Do you use a system with an NVIDIA card or some other display driver that needs updating after a kernel?.While in single user mode, check to see if you received a new kernel or other updates While in single user mode, no remote mounts will mount. Examine your /etc/fstab and see if all your local partitions/mounts have mounted Try logging into single user using the grub menu, check the log files for errors/issues. Take a bit and look at the overall boot process at this Red Hat documentation Try the tip above first from PixelDrift, be ready with pen/paper or a smart phone to take a photo of errors during boot (if an option).Ĭheck additional basic system recovery options through this Red Hat Rescue Mode guidance. Sorry to hear your system is giving you trouble. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |