To set this we enter the root command, grub> root (hd0,1)įilesystem type is ext2fs, partition type 0x83 The root will be on the same hard disk and partition that we found the Grub file /boot/grub/stage1 on. Now that we know the hard disk partition that the kernel files are located, we can set the root location. We remember from above, that the Grub files are located on (hd0,1), but I will show the find command again for consistency. It has nothing to do with the user “root”. Note: The word “root” is used here to represent a starting point.
Then we need to set “root” to its proper disk device, tell Grub which kernel to use and then which initrd to use Again, SLES puts the kernel files in the /boot/ directory as with most distros. If you still get the Grub prompt, we can load the kernel manually.įirst we need to find out where the kernel files are located.
#WHERE IS THE KERNEL IN MAC DISK IMAGE WINDOWS#
Re-installing Grub to the MBR does not affect your data, unless this was a Windows Server to begin with. # this device map was generated by anacondaĭon’t worry.
If any of the lines is incorrect,įix it and re-run the script `grub-install'. This is the contents of the device map /boot/grub/device.map.Ĭheck if this is correct or not. You can use the /sbin/grub-install command to re-install it to the MBR. Note: I have found SLES servers (various versions) that will have the nf in /etc/, so if the above command doesn’t work, you can “find” the nf file just like before.īoot up the kernel and ensure that Grub is still part of your MBR. Now that we know that on hard disk 0, partition 1 (the second partition), the Grub files reside and we can issue the “configfile” command and start the menu. But, we need to know what disk device and partition. On SLES, by default, Grub files reside in /boot/grub/ directory. We know the server is not dead, Grub cannot find its files for some reason. grub>īut, seeing this prompt has it’s upside. Now, aside from a drastic failure in hardware, seeing the prompt below causes one to scratch one’s head in confusion and perhaps state a few unmentionable explicatives. Grub then loads the kernel into memory and passes control to that kernel. There are other options that can be configured, but we’ll stick with the SLES defaults here. Once Grub has loaded, it normally presents a graphical interface where you can select which kernel to load. These files are located on a SLES server in the /boot/grub/ directory. Stage 2 will then load the default configuration file and any other modules needed.
#WHERE IS THE KERNEL IN MAC DISK IMAGE DRIVERS#
Stage 1.5 can contain any drivers needed and it then loads Stage 2. Grub Stage 1.5 is located in the first 30 kilobytes of hard disk immediately following the MBR and before the first partition. Stage 1 can load Stage 2 directly, but it’s normally set up to load Stage 1.5. Stage 1 resides in the MBR and because it is very small code, it basically loads the next Stage from a defined location on the disk within the first 1024 cylinders. When the server is powered on, the server’s BIOS finds the primary bootable device and loads the initial bootstrap program from the master boot record (MBR), then transfers control to Grub Stage 1. This article will show you how, when presented with this situation, to manually load your kernel and find out what went awry.įirst thing is to briefly explain how Grub loads itself and the kernel.
0 kommentar(er)
