000-221 · Question #196
After successfully mirroring rootvg using the mirrorvg command, why must the bosboot command be run against the introduced disk?
The correct answer is C. To customize the bootrec of the newly mirrored drive. After mirroring rootvg, bosboot must be run against the new disk to write a valid boot image to its boot logical volume so the system can boot from it.
Question
After successfully mirroring rootvg using the mirrorvg command, why must the bosboot command be run against the introduced disk?
Options
- ATo update the boot list held in NVRAM
- BTo record from which disk the system will boot
- CTo customize the bootrec of the newly mirrored drive
- DTo synchronize the boot record between the mirrored drives
How the community answered
(45 responses)- A7% (3)
- B13% (6)
- C76% (34)
- D4% (2)
Why each option
After mirroring rootvg, bosboot must be run against the new disk to write a valid boot image to its boot logical volume so the system can boot from it.
Updating the NVRAM boot list is the function of the bootlist command, not bosboot.
Recording which disk the system will boot from is also the role of the bootlist command, not bosboot.
The bosboot command creates a boot image and writes it directly to the boot logical volume (hd5) of the specified disk. Without this step, the newly mirrored disk has no valid boot record and cannot be used as a boot device. This is distinct from updating the NVRAM boot list, which is a separate step handled by the bootlist command.
bosboot writes a boot image to a single specified disk; it does not synchronize boot records between mirrored drives.
Concept tested: AIX bosboot command and mirrored rootvg boot setup
Source: https://www.ibm.com/docs/en/aix/7.3?topic=b-bosboot-command
Topics
Community Discussion
No community discussion yet for this question.