System hang after output "Reached target Basic System."
Hi
I'w working on a Greenlow platform Server. Now met an issue: System hang after output "Reached target Basic System."
My question is which function of kernel will output this message? I can continue to trace this issue if i can find the function name.
Thanks
[ 0.000000] tsc: Fast TSC calibration failed
ÿ[ 2.279076] i8042: No controller found
[[32m OK [0m] Started Show Plymouth Boot Screen.
[[32m OK [0m] Reached target Paths.
[[32m OK [0m] Reached target Basic System.
Responses
Hi Roger,
Are you able to switch to another terminal by pressing Alt+F2, for example? If so, try running
journalctl --catalog --boot
This should show log messages from the current boot.
The message that you ask about (Reached target Basic System) is output by systemd when the basic system is booted -- this can be followed by starting the GUI and various system services. See the bootup(7) man page for more information about the boot sequence.
"Reached target Basic System" is not a kernel message: it comes from initramfs.
You can get a diagnostic shell by using the rd.break=<breakpoint> boot parameter.
More specifically, it looks like the boot parameter
rd.break=pre-trigger
will give you a diagnostic shell before the "Reached target Basic System" message (= just after message "Started udev Kernel Device Manager."), and the boot parameter
rd.break=initqueue
will result in diagnostic shell just after the "Reached target Basic System" message.
The other virtual consoles are not usable at that point, because the step "Started Login Service" has not been reached yet. That's why Alt+F2 won't work.
The next step after "Reached target Basic System" is apparently loading of the storage controller modules required for finding and activating the root filesystem. If the system hangs at that point, you might try loading the appropriate modules manually and seeing which module causes the system to hang on load. If that module is not an essential one, you might try blacklisting it with boot option
rd.driver.blacklist=<name of the problematic module>
Hi, I had this issue. I solved by changing the scsi controller type (vmware...) I moved out all my disks from the vm ( i had my reasons...). Later on - i added them back. I didn't notice that once i've done it, the scsi controllere created was paravirtual (probably vmware default), instead of my original - LSI Logic Parallel. Once i've changed to the original scsi type - the vm booted up ok. Hope this will help. Zeevik
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
