Gilad Berman
2017-05-25 18:52:22 UTC
Do you have consoles on demand set to yes in the site table (or specific to the node)?
If yes, remove âhardâ from your console settings, nodeset again and try.
If this is a similar case, it is because when you set the flow control to hardware, the OS waits for the serial console to be connected (which is flow control..)
[http://lenovocentral.lenovo.com/marketing/branding/email_signature/images/gradient.gif]
Gilad Berman
HPC Architect
Lenovo EMEA
[Phone]+972-52-2554262
[Email]***@lenovo.com<mailto:***@lenovo.com>
Lenovo.com <http://www.lenovo.com/>
Twitter<http://twitter.com/lenovo> | Facebook<http://www.facebook.com/lenovo> | Instagram<https://instagram.com/lenovo> | Blogs<http://blog.lenovo.com/> | Forums<http://forums.lenovo.com/>
[DCG-Hardware]
From: Damir Krstic [mailto:***@gmail.com]
Sent: Thursday, May 25, 2017 9:44 PM
To: xCAT Users Mailing list <xcat-***@lists.sourceforge.net>
Subject: [xcat-user] problems booting redhat 7.3 on NextScale 360M5
We are installing RH7.3 on NextScale nodes and after the install, node reboots. The problem is node seems to get "stuck" until I rcons into it and then it continues booting. So far, I can't pinpoint exact spot where it gets stuck, but it just sits there until I remote console (rcons) into it and then it continues booting. Here is where the last one got stuck until I did remote console:
[***@mgt ~]# rcons qnode5118
[Enter `^Ec?' for help]
Info: SOL payload already de-activated
[SOL Session operational. Use ~? for help]
??6?+
?+#6cK??6?[?+s?
[ 131.345026] systemd[1]: Created slice Root Slice.
[ 131.350307] systemd[1]: Starting Root Slice.
[ OK ] Listening on Journal Socket.
[ 131.360103] systemd[1]: Listening on Journal Socket.
[ 131.365676] systemd[1]: Starting Journal Socket.
[ OK ] Listening on udev Control Socket.
[ 131.377102] systemd[1]: Listening on udev Control Socket.
[ 131.383152] systemd[1]: Starting udev Control Socket.
[ OK ] Listening on udev Kernel Socket.
[ 131.395101] systemd[1]: Listening on udev Kernel Socket.
[ 131.401055] systemd[1]: Starting udev Kernel Socket.
[ OK ] Reached target Sockets.
[ 131.411102] systemd[1]: Reached target Sockets.
[ 131.416180] systemd[1]: Starting Sockets.
[ OK ] Created slice System Slice.
[ 131.426105] systemd[1]: Created slice System Slice.
[ 131.431578] systemd[1]: Starting System Slice.
[ 131.437357] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 131.448652] systemd[1]: Starting Journal Service...
Any help is appreciated.
Thanks,
Damir
If yes, remove âhardâ from your console settings, nodeset again and try.
If this is a similar case, it is because when you set the flow control to hardware, the OS waits for the serial console to be connected (which is flow control..)
[http://lenovocentral.lenovo.com/marketing/branding/email_signature/images/gradient.gif]
Gilad Berman
HPC Architect
Lenovo EMEA
[Phone]+972-52-2554262
[Email]***@lenovo.com<mailto:***@lenovo.com>
Lenovo.com <http://www.lenovo.com/>
Twitter<http://twitter.com/lenovo> | Facebook<http://www.facebook.com/lenovo> | Instagram<https://instagram.com/lenovo> | Blogs<http://blog.lenovo.com/> | Forums<http://forums.lenovo.com/>
[DCG-Hardware]
From: Damir Krstic [mailto:***@gmail.com]
Sent: Thursday, May 25, 2017 9:44 PM
To: xCAT Users Mailing list <xcat-***@lists.sourceforge.net>
Subject: [xcat-user] problems booting redhat 7.3 on NextScale 360M5
We are installing RH7.3 on NextScale nodes and after the install, node reboots. The problem is node seems to get "stuck" until I rcons into it and then it continues booting. So far, I can't pinpoint exact spot where it gets stuck, but it just sits there until I remote console (rcons) into it and then it continues booting. Here is where the last one got stuck until I did remote console:
[***@mgt ~]# rcons qnode5118
[Enter `^Ec?' for help]
Info: SOL payload already de-activated
[SOL Session operational. Use ~? for help]
??6?+
?+#6cK??6?[?+s?
[ 131.345026] systemd[1]: Created slice Root Slice.
[ 131.350307] systemd[1]: Starting Root Slice.
[ OK ] Listening on Journal Socket.
[ 131.360103] systemd[1]: Listening on Journal Socket.
[ 131.365676] systemd[1]: Starting Journal Socket.
[ OK ] Listening on udev Control Socket.
[ 131.377102] systemd[1]: Listening on udev Control Socket.
[ 131.383152] systemd[1]: Starting udev Control Socket.
[ OK ] Listening on udev Kernel Socket.
[ 131.395101] systemd[1]: Listening on udev Kernel Socket.
[ 131.401055] systemd[1]: Starting udev Kernel Socket.
[ OK ] Reached target Sockets.
[ 131.411102] systemd[1]: Reached target Sockets.
[ 131.416180] systemd[1]: Starting Sockets.
[ OK ] Created slice System Slice.
[ 131.426105] systemd[1]: Created slice System Slice.
[ 131.431578] systemd[1]: Starting System Slice.
[ 131.437357] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 131.448652] systemd[1]: Starting Journal Service...
Any help is appreciated.
Thanks,
Damir