![]() How can we be sure? Sometimes it is quite obvious that the error is in initrd, as GRUB tells you that it failed to load the file /boot/initrd, in other cases some forensic work is needed as only a vague driver error message is generated. If a kernel panic occurs immediately after a driver installation, this is often caused by an error in the initrd. In the case of a kernel panic, you can be sure about one thing: GRUB has loaded successfully and you are not yet at phase 4 of the boot procedure where the init process takes over. ![]() In some cases it is possible to tell exactly what happens, more often you will see that you can only give a rough indication of what is happening. When a problem occurs, try to pin-point it to any of these seven phases. The root file system is accessed by the kernel.During the system boot procedure, several phases occur, starting in GRUB, the Linux boot loader. Troubleshooting is a near-science by itself on which I could spend many articles, but I'll try to keep it brief. So, if you ever want to get your system running again, you'll need to correct this error. The initrd is a temporary file system created by system for the boot.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |