In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-08 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/01 Report--
RHEL guide the troubleshooting process, I believe that many inexperienced people do not know what to do, so this paper summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.
In the solution of RHEL boot fault, the fault is solved step by step, mainly from the application scenario.
Application scenarios:
All the files in the / boot directory were deleted by the administrator, and the / etc/fstab file was renamed and the system was unable to boot. After entering the system in repair mode, it was found that all the partitions could not be mounted and accessed normally.
Very important services and data require rapid repair of the system without damaging any data.
RHEL Boot troubleshooting process:
1. Enable PXE boot function from BIOS, and select boot from network.
2. After booting from the network, enter repair mode: linux
Rescue
3. Use NFS image to enter, and enter the system shell after you enter all the way.
NFS server:192.168.0.254
Directory:/var/ftp/pub
4. Due to the renaming of the / etc/fstab file, the system cannot read the file normally, so the partition cannot be mounted and all data cannot be read, so the / etc/fstab file needs to be restored first.
5. Create a directory on the root partition, such as mkdir test, and mount the root partition to this directory
Mount / dev/hda3 test (/ dev/hda3 varies from system to system)
6. Use the df command to check that the system should have been mounted to the test directory. If you enter this directory, you can see the / test/etc directory and change the fstab file back.
7. Press exit to restart the system, and the system will automatically mount the file system when it reads the / etc/fstab file.
8. Enter cd in the directory where the kernel resides.
/ mnt/source/Server
9. Reinstall the kernel (rpm-ivh kernel-2.6.18-53.el5.i686.rpm-- root=/mnt/sysimage-- force)
10. Switch to the system root partition chroot
/ mnt/sysimage
11. Install GRUB
Grub-install / dev/hda
/ dev/hda varies from system to system)
12. Regenerate initrd-2.6.18-53.el5.img
① rm/boot/initrd-2.6.18.el5.img
② cd / lib/modules
③ mkinitrd / boot/initrd-2.6.18-53.el5.img
2.6.18-53.el5
13. Edit / boot/grub/grub.conf file
Default=0
Timeout=10
Title Redhat Enterprise 5
Root (hd0,0)
Kernel / vmlinuz-2.6.18-53.el5 ro root=LABEL=/
Initrd / initrd-2.6.18.el5.img
14. Restart the system by pressing exit twice to boot from the hard disk with RHEL to test whether it can be started normally.
After reading the above, have you mastered the solution to the RHEL boot failure? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.