First, the phenomenon of failure
Business side Feedback Current Network A SuSE11 host is found to be unable to start properly after reboot, and the discovery host is unable to start properly after the set System time to the present hardware clock interface through the HP ILO port. The specific interface is as follows:
Second, the failure to deal with
1, through the restart of the host into the repair mode, through the Hwclock-w sync error, prompted to find the/dev/rtc file, by using--debug parameters, look up the following information:
#hwclock--debug
Hwclock from util-linux-2.19.1
Hwclock:open OF/DEV/RTC failed, errno=19:no such file or directory
No usable clock interface found.
Cannot access the hardware Clock via any known method.
After looking at the/DEV/RTC does not have the file exists, through the date command to view the local system time, found that the wrong, and use the date command to modify the system time first. Reset the host to enter the system BIOS again, after confirming the host hardware time is not correct, in the BIOS when the hardware time modified, reboot the host system, the system was found to remain on the set system time to the current hardware clock interface, Waiting for 30 minutes or so has not changed.
2, restart the host again into a single user, will start to call the time synchronization of the script file Boot.clock file moved to another place
# Mv/etc/init.d/boot.clock
After the move is complete, check the contents of the next/etc/fstab, comment out the swap and storage mount items, and start the host again. The host succeeds, modifies/etc/fstab after success, and re-enable the contents of the annotation, and mount-a.
Summarize:
This obstacle, the main test is the starting sequence of the host and start related documents to understand, and there is not much to pay attention to things. Back online also looked at the relevant information, looks like a system bug, this should follow up and SUSE engineer communication after confirmation.