Linux 6.5 boot freezes during startup !
My Linux RHEL freezes at initializing (loading). The usual bar that appears at the bottom of the screen during loading shows up and increases until about almost ready to load the desktop, but instead , the bar freezes and stay there.
The last think I was doing was playing with adding new repositories and downloading files. I don't know much else. I Don't know anyting about troubleshooting.
Any help here?
Responses
First thing to do is press 'esc' during the boot sequence (when the progress bar appears), this will reveal which part of the boot process is being executed. Watch the services start, and hopefully you will see one that hangs/pauses.
If it is an nvidia card, and you got a new kernel, download (if you haven't already), and run the nvidia setup at init 3 (not init 5)
root@yoursystem # NVIDIA.someversion.run --accept-license
(run chmod 755 against the file first).
You may have to (afterwards) run 'nvidia-xconfig' or something like that (I'm rebuilding my current system right now and typing this from memory).
Jose, did you try booting to your other kernel??? See the comments near the end of this discussion (James Radtke). Then you can see if that works and make it work with your current kernel if you got a new kernel.
What rhel version are you running? There are bugs for certmonger at certian previous points with RHEL (saw this with Google results)
Hi Jose,
Sorry to hear your system is giving you trouble.
-
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).
-
Check additional basic system recovery options through this Red Hat Rescue Mode guidance...
-
Take a bit and look at the overall boot process at this Red Hat documentation
-
Try logging into single user using the grub menu, check the log files for errors/issues.
-- Examine your /etc/fstab and see if all your local partitions/mounts have mounted
-- While in single user mode, no remote mounts will mount. -
While in single user mode, check to see if you received a new kernel or other updates
- Do you use a system with an NVIDIA card or some other display driver that needs updating after a kernel?
- Is your system hanging on a remote mount?
- Did you make any changes to your /etc/fstab very recently?
- Do you have another like system that is behaving well and is not experiencing these issues?
If you are able to get to the grub menu, go to single user and log in.
Then cd to /var/log/ - and check the latest log files written to (probably messages file, maybe the yum.log file)
[root@yoursystem ~]# cd /var/log
[root@yoursystem log]# ls -ltr
[root@yoursystem log]# less messages
Look in the messages file (while in "less messages" hit SHIFT G together to go to the bottom of the log. 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
Also, do a dmsg and scroll through the results to see if there's anything that looks like it failed.
[root@yoursystem log]# dmesg
---check your output for anything obviously wrong---
- Below, check to see if you got a recent kernel update:
1) The time/date stamp of your /boot/grub/grub.conf to see when the last time it was updated (that is when the most likely time you received a kernel update)
2) The time/date stamp of /boot/vmlinuz-[latest-version] and /boot/initramfs-[latest-version]
[root@yoursystem log]# ls -l /boot/grub/grub.conf
-rw-------. 1 root root 1800 ??? ?? ??:?? /boot/grub/grub.conf
[root@yoursystem log]# ls -l /boot/
[root@yoursystem log]# ls -ltr /boot/ | egrep 'vmlinuz|initramfs'
The question marks above will be different - make note of the date of grub.conf, vmlinuz and initramfs files and determine if you the time/date stamps correspond with the issues you faced.
- Check your /var/log/yum.log file and see if you have any recent updates
[root@yoursystem log]# cat /var/log/yum.log
---check your output---
- Check your mounts (local while in single-user mode) to see if everything mounted as expected:
- Also check your /etc/fstab against the df -PhT output from below
[root@yoursystem log]# df -PhT | column -t
[root@yoursystem log]# grep -v ^\# /etc/fstab
-
Check your partitions with 'fdisk -l' 'pvdisplay' 'vgdisplay' and 'lvdisplay' and compare to your df -PhT output and output from your /etc/fstab.
-
Come back here and post if you need more help - someone should probably reply.
Hopefully others will join in and provide anything I may have missed above,
Kind Regards,
Remmele
You likely downloaded/installed a new kernel. I would first boot to one of the previous kernels to see if they still work. Press any key after the BIOS finishes.
If the old kernel does boot, I would remove the other kernels and reboot. The install the kernels again.
The tip from Pixel/Remmele is priceless - you can hit -esc- once the "progress bar" appears (or shortly thereafter). The point where things go south will help quite a bit in helping us figure this out.
(I and the others are) Glad to help,
By the way, rhel is quite stable. the tips folks gave above - you might have been back in business quickly. 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. Although the BSD folks (bless their hearts) might say theirs is the most stable etc...
THIS PARAGRAPH EDITED That aside, my Linux systems have far more stability in my environment than the windows systems and the Solaris systems. EDITED: the last statement was too heavy handed. Solaris Unix is actually very stable, and while my preference is Linux, Solaris is quite stable. 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. 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.
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. I wish you luck.
I mean the above plainly and with a full absence of negativity, but wanted to reply to your last comment.
Kind regards, Remmele
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
