40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Mon Jul 10 09:49:02 2017, gautam, Update, General, All FEs down CDS_down_10Jul2017.png
    Reply  Mon Jul 10 11:20:20 2017, gautam, Update, General, All FEs down 
       Reply  Mon Jul 10 17:46:26 2017, gautam, Update, General, All FEs down 
          Reply  Mon Jul 10 19:15:21 2017, gautam, Update, General, All FEs down 
             Reply  Mon Jul 10 21:03:48 2017, jamie, Update, General, All FEs down 
                Reply  Mon Jul 10 22:07:35 2017, Koji, Update, General, All FEs down 
                   Reply  Tue Jul 11 15:03:55 2017, gautam, Update, General, All FEs down 
                      Reply  Tue Jul 11 15:12:57 2017, Koji, Update, General, All FEs down 
                         Reply  Wed Jul 12 10:21:07 2017, gautam, Update, General, All FEs down 
                            Reply  Wed Jul 12 14:46:09 2017, gautam, Update, General, All FEs down 
                               Reply  Wed Jul 12 14:52:32 2017, jamie, Update, General, All FEs down 
                                  Reply  Fri Jul 14 17:47:03 2017, gautam, Update, General, Disks from LLO have arrived 
Message ID: 13108     Entry time: Mon Jul 10 21:03:48 2017     In reply to: 13107     Reply to this: 13110
Author: jamie 
Type: Update 
Category: General 
Subject: All FEs down 

 

Quote:
 

However, FB still will not boot up. The error is identical to that discussed in this thread by Intel. It seems FB is having trouble finding its boot disk. I was under the impression that only the FE machines were diskless, and that FB had its own local boot disk - in which case I don't know why this error is showing up. According to the linked thread, it could also be a problem with the network card/cable, but I saw both lights on the network switch port FB is connected to turn green when I powered the machine on, so this seems unlikely. I tried following the steps listed in the linked thread but got nowhere, and I don't know enough about how FB is supposed to boot up, so I am leaving things in this state now. 

It's possible the fb bios got into a weird state.  fb definitely has it's own local boot disk (*not* diskless boot).  Try to get to the BIOS during boot and make sure it's pointing to it's local disk to boot from.

If that's not the problem, then it's also possible that fb's boot disk got fried in the power glitch.  That would suck, since we'd have to rebuild the disk.  If it does seem to be a problem with the boot disk then we can do some invasive poking to see if we can figure out what's up with the disk before rebuilding.

ELOG V3.1.3-