IBM
C9010-022 · Question #108
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…
The correct answer is D. Bash can interpret the AIX startup scripts differently to the default shell. See the full explanation below for the reasoning.
Question
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? # ls -al /bin/bin/bsh /bin/sh /lib /u /unix 1rwXrwXrwX 1 bin bin 8 Aug 5 2012 /bin -> /usr/bin -r-xr-xr-x 3 bin bin 25622 4 Jun 4 2012 /bin/bsh lrwxrwxrwx 2 bin bin 22 4 Jun 4 2012 /bin/sh -> ../opt/freeware/bin/bash lrwxrwxrwx 1 bin bin 8 Aug 5 2012 /lib -> /usr/lib lrwxrwxrwx 1 bin bin 5 Aug 5 2012 /u -> /home lrwxrwxrwx 1 root system 18 Aug 5 2012 /unix -> /usr/lib/boot/unix #
Options
- A/bin should be linked to/sbin
- B/unix is attempting to boot a 32-bit kernel
- C/bin/bsh should be pointing to /opt/freeware/bin/bash
- DBash can interpret the AIX startup scripts differently to the default shell
How the community answered
(32 responses)- A6% (2)
- B19% (6)
- C6% (2)
- D69% (22)
Community Discussion
No community discussion yet for this question.