Sometimes your system may display an error with the message root uuid of the gentoo kernel. There can be several reasons for this problem.
Show outside topic :: Show next topic
Author
message
guyuming Dachshund’s Little Helper < p> Registration date: November 19, 2020 Messages: 146
Published: Thursday, December 03, 2020 1:43 PM Message: Could not find real block in device UUID=94db66e3-blabl
Background: On the other hand, creating a new topic or keeping an old topic is of course encouraged. https://forums.gentoo.org/viewtopic-t-1124482-highlight-.html https://forums.gentoo.org/viewtopic-t-1124446-highlight-.html
After following the steps in https://wiki.gentoo.org/wiki/Kernel/Rebuild and typing reload, my friends and I see the following (I entered it manually, so you should look a little different on the screen):
[4.094674] Run /init as init process >> 4 genkernel.1.2 (blabalba) Linux kernel 5.4.72-gentoo-x86_64 >> enable udev… >> Determine root device (try UUID=94db66e3-blablabla) … !! Block device UUID=94db66e3-blablabla is not a logical device rootoistva… !! Unable to find root block device only via UUID=94db66e3-blablabla !! Enter a value or: !! – In the meantime press Enter !! – Sort the shell by “shell”. !! – send nature “q”… Disable Device (UUID=94db66e3-blablabla)
Is your computer running slow? Is it plagued with frustrating errors and problems? Then you need ASR Pro � the ultimate software for repairing and optimizing your Windows PC. With ASR Pro, you can fix any Windows issue with just a few clicks � including the dreaded Blue Screen of Death. Plus, the software will detect and resolve files and applications that are crashing frequently, so you can get back to work as quickly as possible. Don't let your computer hold you back � download ASR Pro today!
And after checking the kernel/recovery history above, I realized that my wife and I missed the next step:
Don’t forget to copy the newly released kernel image to the /boot folder. Rise/start if needed. root #mount /boot
I just used the “ls /boot” command to check if there were any factors and the folder didn’t do anything, I thought “make install” could do everything for me.
So, what actions should I take? Press Enter or shell or q?
Profitability that can grow
NeddySagoon Administrator
Joined: 05 July 2003 Messages: 49947 Location: 56N 3W
Published: Thursday, 03 December 2020 18:12 Post subject:
guyum,
Let’s quickly run through this initial procedure to broaden your knowledge and then make some educated guesses to see what you need.
The next time you turn on the system, the RAM will be empty. The firmware loads something to run the CPU from the hard drive. The details differ between Bios and UEFI, but we don’t have to worry about that. We must assume that we are using the grub formatter bootloader. The firmware makes its own patch, loads grub and passes control to this method. Grub shows you the compilation and you make your choice.
Basically grab the kernel and possibly one or more initrd files which are then passed on to manage the kernel binary. Grab is ready. Now it’s just the kernel plus the optional initrd files that keep your system running. The kernel unpacks again, initializes the inline code, and mounts the initrd as an eternal root filesystem. There is also aA certain degree of parallelism when starting the kernel.
When an initrd is mounted as root, the kernel executes the init script found in /init. It takes everything to get the best mounted real root filesystem. The last thing it does is finally switch to the real main file system and tell the kernel to provide /sbin/init.
It really is a house with cards. Remember that the boot process solves a problem that is equivalent to booting an operating system into a full-fledged computer that doesn’t know how to boot its own operating system. Undoubtedly, there are many cyclic dependencies that can be broken.
Code:
Determining the UUID of the root device=
Message (Tests are important. Since you are a UUID, your company’s use should also have an initrd that generates a userspace mount command. The kernel does understand UUIDs. Around the same place, a completely new message
Code:
Unable to find root software in .
Looks like on the it’s very strange with a worthless list. It’s just
Code:
Unable to understand root device.
If you see this, your family kernel and initrd cannot read any monolithic devices. It’s definitely a kernel configuration issue.
It is very easy for you to properly reinstall the kernel and initrd in the wrong place. There are already various places on your system that show up as a free download. The kernel can see both, but the bootloader may only be able to access one.
First comes /boot. This is a directory under the root partition. In all respects it behaves like any other list. You can put things down if you want to find them. Then comes a kind of boot, boot partition. These are the shoes used by the Loadout Machine. If you are updating the currently used bootloader files, the disk partition simply needs to be mounted on /boot in the root partition. If this is not done, the files get stuck in the directory.Replace /boot of the original polluting partition.
You may also need to update this grub.cfg file.
The last trap for the unwary is that grub usually doesn’t make new kernel the default boot option. You can call to find it on the menu.
< p> Registration date: November 19, 2020
