[Fault Type]
VM startup failure
[Keyword]
SLES 10 VM startup failure, OS installation, disk loading failure due to had=noprobe
[Application Scope]
All FusionCompute versions
[Symptom]
During the installation of the SUSE Linux Enterprise Server (SLES) 10 SP4 operating system (OS), the VM cannot be started properly, as shown in Figure 1-257
Figure 1-1 VM startup failure
[Alarm Information]
None
[analysis]
When the OS is installed in the ISO mode, disks /dev/hda1 and /dev/hda2 cannot be found because hda=noprobe is specified in the menu.lst configuration file. As a result, the system fails to load the disks.
[Solution]
1. Click 
in the VNC login window to forcibly restart the VM.
l When a dialog box is displayed during the restart, click Yes to reconnect.
l During the OS installation, do not close the VNC login window. If the VNC login window is incorrectly closed, mount the ISO image file of the OS.
2. When the VM displays the window shown in Figure 1-258 uring the restart, press e. The window changes, as shown in Figure 1-259.
If you failed to press e in time during the VM restart, the VM displays the window shown in Figure 1-260. In this case, you can forcibly restart the VM and perform this step.
Figure 1-2 VM startup window 1
Figure 1-3 VM startup window 2
Figure 1-4 VM startup failure window
3. Select the second line (kernel /boot/vmlinuz) in Figure 1-259, and then press e. The editing window is displayed, as shown in Figure 1-261.
Figure 1-5 VM startup window 3
4. Use the arrow keys to move the cursor to the place indicated in Figure 1-262.
Figure 1-6 VM startup window 4
5. Delete hda=noprobe and press Enter to save the modification.
After the modification is saved, the system returns to the window of the previous step, as shown in Figure 1-263.
Figure 1-7 VM startup window 5
6. Press b to continue the OS installation.
7. After the OS is installed, log in to the VM OS as the root user.
8. Run the following command on the command-line interface (CLI) to open the menu.lst file in the vi editor:
vi /boot/grub/menu.lst
9. Press i to enter the editing mode.
Figure 1-8 File configuration example
10. Delete hda=noprobe.
hda=noprobe indicates that the system does not detect the hda disk, which is the cause of the disk loading failure.
11. Press Esc to exit the editing mode and enter :wq to save the modification.
[Conclusion & Suggestions]
None.
