40m
QIL
Cryo_Lab
CTN
SUS_Lab
TCS_Lab
OMC_Lab
CRIME_Lab
FEA
ENG_Labs
OptContFac
Mariner
WBEEShop
|
40m Log |
Not logged in |
 |
|
Mon Jul 10 09:49:02 2017, gautam, Update, General, All FEs down
|
Mon Jul 10 11:20:20 2017, gautam, Update, General, All FEs down
|
Mon Jul 10 17:46:26 2017, gautam, Update, General, All FEs down
|
Mon Jul 10 19:15:21 2017, gautam, Update, General, All FEs down
|
Mon Jul 10 21:03:48 2017, jamie, Update, General, All FEs down
|
Mon Jul 10 22:07:35 2017, Koji, Update, General, All FEs down
|
Tue Jul 11 15:03:55 2017, gautam, Update, General, All FEs down
|
Tue Jul 11 15:12:57 2017, Koji, Update, General, All FEs down
|
Wed Jul 12 10:21:07 2017, gautam, Update, General, All FEs down
|
Wed Jul 12 14:46:09 2017, gautam, Update, General, All FEs down
|
Wed Jul 12 14:52:32 2017, jamie, Update, General, All FEs down
|
Fri Jul 14 17:47:03 2017, gautam, Update, General, Disks from LLO have arrived
|
|
Message ID: 13107
Entry time: Mon Jul 10 19:15:21 2017
In reply to: 13106
Reply to this: 13108
|
Author: |
gautam |
Type: |
Update |
Category: |
General |
Subject: |
All FEs down |
|
|
The Jetstor RAID array is back in its nominal state now, according to the web diagnostics page. I did the following:
- Powered down the FB machine - to avoid messing around with the RAID array while the disks are potentially mounted.
- Turned off all power switches on the back of the Jetstor unit - there were 4 of them, all of them were toggled to the "0" position.
- Disconnected all power cords from the back of the Jetstor unit - there were 3 of them.
- Reconnected the power cords, turned the power switches back on to their "1" position.
After a couple of minutes, the front LCD display seemed to indicate that it had finished running some internal checks. The messages indicating failure of power units, which was previously constantly displayed on the front LCD panel, was no longer seen. Going back to the control room and checking the web diagnostics page, everything seemed back to normal.
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. |