On Mon, Jun 4, 2018 at 7:50 AM, David Collier-Brown via talk <[email protected]> wrote: > On 03/06/18 10:57 PM, o1bigtenor via talk wrote: >> >> On Sun, Jun 3, 2018 at 5:54 PM, William Park via talk <[email protected]> >> wrote: >>> >>> On Sun, Jun 03, 2018 at 02:47:13PM -0500, o1bigtenor via talk wrote: >>>> >>>> Greetings >>>> >>>> I am quite new at running a server so hopefully the question isn't too >>>> out there. >>>> >>>> My server has been operational for about a year and I am working on a >>>> number of different projects on it. Twice now (this last friday and 5 >>>> weeks early I came into the office to find that the server has somehow >>>> been taken down and has rebooted itself (process setup in the bios) >>>> but as it doesn't quite complete the boot process, I have to hit a key >>>> to tell it to continue and then finally to log in to read Debian >>>> (stable). >>> >>> Who does the stopping? BIOS or Linux kernel? >> >> Bios - - - need to hit F2 (IIRC) to kick the bios in the pants and >> then I can get >> to the os prompt a little later. > > > Google for "Server stuck at F1 or F2 prompt". Depending on your vendor, you > will get quite a bit of information on probable causes and diagnostic > processes. I had to debug a work Dell with that a while ago, and sometime > in my Copious Spare Time Intel server (;-)) >
This beast has been set up in the expectation that a tech is available 24-7. Oh well - - - it is easy to see that management has not ever had these demands placed upon them so they think its quite 'normal' to ask for this. Thanks for the tips! Dee --- Talk Mailing List [email protected] https://gtalug.org/mailman/listinfo/talk
