| 27 | | This is a good opportunity to look at the output of the image loading process. At first glance, it can look like a lot of text, but there is some useful information there to help you understand what is going on. Here is the output of running the above command: |
| 28 | | |
| 29 | | [[Image(image-save.png)]] |
| 30 | | |
| 31 | | We can see from this output that the image loading process has two phases: the first, noted in red, in which OMF is waiting for the nodes to boot up and load a client which will receive the omf image data and write it to disk; and the second, noted in blue, in which OMF actually performs the imaging process. This output shows a successful imaging process-- we can tell because of the text noted in pink, which says that the imaging process is done and there were two nodes successfully imaged. The filename displayed there will contain a list of all the nodes which were successfully imaged. |
| 32 | | |
| 33 | | Once in a while, you may see an imaging process where some or all of the nodes fail to image. This can happen because something goes wrong either in the first step (a node fails to boot up and register with the imaging process) or in the second step (the node fails to load the image onto its hard disk). If there is a failure, it will be noted in the output at the end of the imaging process-- there will be additional files listed for nodes that fail to check in, and nodes in which imaging failed. |
| 34 | | |
| 35 | | Always check the output to make sure that your nodes were successfully imaged. |
| | 27 | The output of this command can be a little intimidating, but make sure you should look for confirmation that both of your nodes were successfully imaged. An example of the output is below, with the outcome of the loading process highlighted in red. |
