If you are able to take a look at the log file indicated, there may be more information useful to identifying the problem.
/var/log/update_*.txt
The log file will have a date stamp on it based on when the update was run. So you can look at the last few lines in that log and let us know what that says, it may help.
Also, for curiosity sake, why re-image a second time? Did the previous re-image complete properly? Has the node been rebooted after the re-image? I could see a further re-image being blocked because the current activities have locked the boot drives to wait for a reboot in order to complete the boot-time activities of the re-image before.
chughh
122 Posts
925
1
Posted February 18th, 2015 06:00
Hello,
It seems to be boot drive issue try reseat boot drives and re image once again..
Thanks
Hemant