Redhat Linux 7 boot issue-Kernel Panic and steps to troubleshoot-Part2

hello and welcome guys today is another topic about Linux boot issues today what I'm going to show you when you face kernel panic related when you reboot your Linux system so possible region I would say when you get kernel panic error is the men you have to check your kernel your kernel is probably not installed properly or the unit Rd image related to your kernel is not created properly or for some nation you have installed some rich recent modules or in Windows world we call them as drivers and you have not regenerate your unit RDMs then you could also get kernel painting errors okay so and I have faced this kind of error kinetic error in the scenario of recent patching so whenever people pets the system and they reboot the system they usually face this issue so why you have issues when you pass your system and you reboot because the main region is like like it said you probably have not installed your in it rd image so what is the reason behind your init RDMs is not created properly it can be because of your slash boot partition the slash boot partition you have to ensure that there is enough space to create a new unit Rd in image so in case if you do not have unit ID image if you do not have space in slash boot partition then you're in it Rd image we're not going to create properly and due to that you may not you may not notice and you reboot the system and you'll have end up with that colonel painting issues so before reboot or after applying the page you just need to ensure that /boot has enough space and your net ID image is installed properly and also you have to ensure yours less temp and less USA so this two file system has enough space to apply your patches so if you are ensuring that you would not probably face the issue of creating in a tardy image okay so let me just reboot it so here you can see there are color information in many problems the first one is about the kernel and the version it has mentioned and the other you can see there is something about rescue I will tell you what is that so let me just boot the system normally and when I try to boot it I see an error saying that in Atari image not found okay so and again if I press Enter you can able to see here there is an error there is an a big error you can see an Evo here you can see kernel panic not sinking so this is the kernel painting error so now how you're going to troubleshoot it so first thing what you have to do is you just have to reboot your system again and for your information I'm running rhel7 point three so once you reboot it you just have to go to this rescue prompt here and in original 6 or the earlier version we'd not have this option and we had to boot our system with any Linux version and we need to go to rescue mod and there we need to troubleshoot but in addition seven we already have this built in in your quest so you just need to in go with this rescue image and you have to boot your system so let me just select I just selected that and I'm just trying to board my system now and if I just press escape I can see my system is trying to put up it will going to take hardly five or ten seconds okay so my system is up let me just login right so let me just open a terminal here and increase the font size so now if I just do a UNM minus a or are I can see the same kind of information and other information about the kernel and when it has built so how the system came up if I just go to slash bud and do an ll here I can able to see there is an init Rd image this is for my k-dub kdump image and there is one more here you can see in it Rama face rescue image so I have boarded my system with this in it Rd image so it isn't that it is nothing but a temporary init RDMs if when you have issue something similar like kernel panic then you would be able to boot your system it is saying a rescue so it is similar like whatever the action you you would have done in earlier distribution in rescue mode you would be able to do the same thing here so this is the unit Rd with this it has booted and the kernel so now you would be able to do any action as you do in rescue mode so now the problem is why my system end up with the kernel panic and it was unable to boot because of the inlet rd image so in it Rd image is there for Kadim and for SQ but for my kernel it is not there if I do Unum minus R this is my kernel version so with this kernel if I see here related in it re image I do not have it so what I have to do is I have to create create a new unit ID image so for that there are two command if you are familiar with MK in a tardy command you can also use that we used to use this command in earlier distribution in our HT l 6 or 5 and if it is do one help here you'd be able to see an example how you're going to create an innie dirty image so here you can see in a dirty image you have to specify your current kernel version and also your conversion here and the last extension here is with dot I am G that means image so you can use this command and also there is one more command call record so you can also use this record command which is a new and it has a better functionality with compared to in MK net ID so you can also use Draycott command to create your unit ID image so for now what I'm going to do is I'm going to use record command and specifying the file under slash boot and I'm going to specify the same thing because this is the image I need for my kernel so let me just remove here and - f is for pre-loaded modules you can see here - F Lawson and let me just specify the kernel version here that's it now if I just run this command it should create a new unit order image since this file is a little bigger it will going to take a minute probably or thirty second it is taking a little time than expected anyways so it is done so now I got a prompt here and if I just clear the screen and do an ll again I would be able to see a new image is created so this is the new image created so now if I just reboot the system I should not be having that kernel panic error and my system should boots of normal okay so my system is back and if I just login with fruit and I would be able to see my desktop here so this is how guys need to troubleshoot kernel painting error and you have to ensure when you pass your system you have those Pyrrhic acid-like /boot USR and slash stem those three file system has enough space otherwise the most likely you will end up with this unit early issues so I believe you liked the video and this video is informative for you if you feel this video is informative then please subscribe my channel and also hit like thank you so much for watching my video have a good day [Music] I go whatever I say I remember yo if you remember me

Channel: Tune To Linux

Views: 49,568

Keywords: redhat linux boot, redhat linux 6 boot issue, redhat linux 7 boot issue, redhat linux kernel panic issue, redhat linux superblock currupt, redhat linux superblock issue, redhat linux boot process, redhat linux7 booting, linux boot issues, redhat linux 7 kernel panic issue, redhat linux kernel panic troubleshoot steps, redhat linux 7 kernel panic, redhat linux 6 kernel panic, redhat linux kernel panic, troubleshoot kernel panic in rhel7, kernel panic, linux rescue

Id: WDZV4QWduNo

Length: 13min 42sec (822 seconds)

Published: Mon Mar 05 2018