An existing LPAR hangs with an LED code of 0553 after a scheduled reboot. An administrator boots the LPAR into a maintenance mode to investigate the cause of the issue. All filesystems fsck cleanly. There is plenty of space in / and /tmp. And /etc/inittab appears to be intact and valid. Based on the following output, why is one of these symbolic links likely to be the cause of the LED code?

Question

Accepted Answer

D. bash can interpret the AIX startup scripts differently to the default shell AIX startup scripts in /etc/inittab and related init paths are written using ksh or bsh syntax. If a symbolic link causes bash to be invoked as the script interpreter, subtle differences in shell behavior - such as handling of certain builtins, variable expansion, or condition tests - can cause init scripts to fail silently or fatally, producing the 0553 hang.

Answer

A. /bin should be linked to/sbin /bin on AIX is conventionally linked to /usr/bin, not /sbin; while a wrong link here could cause issues, it would more likely produce missing-command errors rather than this specific init failure.

Answer

B. /unix is attempting to boot a 32-bit kernel /unix pointing to a 32-bit kernel would cause hardware compatibility issues at kernel load time, well before the 0553 LED stage which occurs during init.

Answer

C. /bin/bsh should be pointing to /opt/freeware/bin/bash The location /bin/bsh pointing elsewhere is a symptom of the problem, but it does not explain the technical mechanism that causes the failure - D provides the actual causal reason.

An existing LPAR hangs with an LED code of 0553 after a scheduled reboot. An administrator boots the LPAR into a maintenance mode to investigate the cause of the issue. All filesystems fsck cleanly…

Question

Exhibit

Options

How the community answered

Why each option

Topics

Community Discussion