enjay Posted November 5, 2007 Posted November 5, 2007 When restarting our server earlier, I saw a couple of error messages come up during the POST, but they were too quick to actually read. Is there any way that I can get at them without restarting the server 20 times? Do such messages get logged or recorded anywhere?
tech_guy Posted November 5, 2007 Posted November 5, 2007 Can't you use your camera phone or a video camera to record the post? That's what we do then play it back slowly. We had to do this when we couldn't pause the post.
enjay Posted November 5, 2007 Author Posted November 5, 2007 I suppose I could, but I'd rather find a way that doesn't involve having to restart the server during the day.
Ex-MGSTech Posted November 5, 2007 Posted November 5, 2007 Why not hit pause on the keyboard? press enter to continue post when you have read them? Steve
Ric_ Posted November 5, 2007 Posted November 5, 2007 Some BIOS menus give you an option to read a log of any messages too.
Michael Posted November 5, 2007 Posted November 5, 2007 As MGSTech said, the pause/break is what you need, but of course you still need to reboot! Presumably (despite the errors), it POSTs ok as you're using the server? I wouldn't worry too much if that's the case, but I suppose whilst you're in Windows you could look at the event log and ensure all memory and disk drives are correct. One other thought - ensure your CPUs are operating at a good temp and that the fans are spinning normally. CPU fans are one source of POST screen errors, but usually it wouldn't continue to boot Windows.
enjay Posted November 6, 2007 Author Posted November 6, 2007 @Michael - yes, the server boots okay except for the error messages. I'm fairly sure one of them refers to the duff CD drive in the server, since I can catch the words "check cable" in it, the other one concerns me a bit more since its written in red! I really would like to find a way of doing this without having to reboot our main server during the day - people get funny when I do that. Obviously, it's better to inconvenience them a bit as I reboot it and can then resolve whatever the error is rather than have it fall over for a day or so, but I would much rather have a reboot-free option if one exists.
Ex-MGSTech Posted November 6, 2007 Posted November 6, 2007 What model is your server? for example HP Proliant servers have a windows app to read the server health logs including any post errors. Also don't fret too much, the Boot rom for most SCSI RAID drivers displays it's boot sequence in colour... MGSTech
enjay Posted November 6, 2007 Author Posted November 6, 2007 Its an RM server, Intel mobo; not sure much else off the top of my head. It is definitely an error message though, not just some SCSI config display, partly because I think it says "error" and also because it used not to do it.
Ex-MGSTech Posted November 6, 2007 Posted November 6, 2007 If its a server mobo then there may be some utilities on Intels website to allow you to view BIOS messages from windows?
PiqueABoo Posted November 6, 2007 Posted November 6, 2007 Intel -> Chances are the red message you get is "System Event Log full" and that will happen from rebooting it not-too-many times. You can boot it with a floppy to run the selview(?) util to review and clear the log. A few times I've seen the windows Intel Server Management Thingummy leak enough memory to kill the server in about 24 hours. To be fair that may have been a specific version, or because of problems with something else it relies on on the system - don't know, I decided it was much easier to stop caring and live without it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now