Also nothing :-/
san01::*> event log show -message-name nvmem.battery.discFET*
There are no entries matching your query.
san01::*>
But it didn’t happen again since then, so I’m not sure if this was just a hickup or an issue that will get bigger in the future…
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Weber, Mark A [mailto:mark-a-weber@uiowa.edu]
Gesendet: Donnerstag, 2. März 2017 17:26
An: Alexander Griesser <AGriesser@anexia-it.com>
Cc: toasters@teaparty.net
Betreff: RE: NVMEM discharge FET off?
Check the event log in diag mode – I just had one but it cleared itself 10 seconds later:
****1::*> event log show -message-name nvmem.battery.discFET*
Time Node Severity Event
------------------- ---------------- ------------- ---------------------------
3/2/2017 10:07:02 ****1-03 NOTICE nvmem.battery.discFET.normal: The NVMEM battery discharge FET is on.
3/2/2017 10:06:52 ****1-03 EMERGENCY nvmem.battery.discFET.off: The NVMEM battery discharge FET is off. To prevent data loss, the system will shut down in 5 minutes.
2 entries were displayed.
But the normal message doesn’t show unless you are in advanced/diag
m
From:
toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net]
On Behalf Of Alexander Griesser
Sent: Thursday, March 2, 2017 5:49 AM
To: Mark Flint <mf1@sanger.ac.uk>
Cc: toasters@teaparty.net
Subject: AW: NVMEM discharge FET off?
Hi,
I couldn’t find entries with „NVMEM“ in the name, but here’s everything that has „BAT“ in its name – is that what we’re looking for?
san01::> system node environment sensors show -name Bat*
Node Sensor State Value/Units Crit-Low Warn-Low Warn-Hi Crit-Hi
---- --------------------- ------ ----------- -------- -------- ------- -------
san01n01
Bat Present normal
PRESENT
Bat Temp normal
24 C 0 5 53 58
Bat Volt normal
8100 mV 5500 5600 8500 8600
Bat Curr normal
0 mA - - 2320 2600
Bat Rem Cap normal
3328 mA*hr - - - -
Bat Full Cap normal
3328 mA*hr - - - -
Bat Charge Curr normal
0 mA - - 2200 2300
Bat Charge Volt normal
8200 mV - - 8900 9000
Bat Initial FCC normal
3200 mA*hr - - - -
Bat Dstg Cycles normal
21 cycles 2 5 - -
Bat Power Fault normal
GOOD
Bat Dcharge FET normal
ON
Bat Charge FET normal
ON
Bat Cycle Count normal
4 cycles - - - -
san01n02
Bat Present normal
PRESENT
Bat Temp normal
24 C 0 5 53 58
Bat Volt normal
8100 mV 5500 5600 8500 8600
Bat Curr normal
0 mA - - 2320 2600
Bat Rem Cap normal
3328 mA*hr - - - -
Bat Full Cap normal
3328 mA*hr - - - -
Bat Charge Curr normal
0 mA - - 2200 2300
Bat Charge Volt normal
8200 mV - - 8900 9000
Bat Initial FCC normal
3200 mA*hr - - - -
Bat Dstg Cycles normal
21 cycles 2 5 - -
Bat Power Fault normal
GOOD
Bat Dcharge FET normal
ON
Bat Charge FET normal
ON
Bat Cycle Count normal
3 cycles - - - -
28 entries were displayed.
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Mark Flint [mailto:mf1@sanger.ac.uk]
Gesendet: Donnerstag, 2. März 2017 12:16
An: Alexander Griesser <AGriesser@anexia-it.com>
Betreff: Re: NVMEM discharge FET off?
Take a look at the output from system sensors, should show you the battery, whether it’s charging or not,
And at what voltage
System node environment sensors show
And look for the nvmem battery info
`Mark
From: <toasters-bounces@teaparty.net>
on behalf of Alexander Griesser <AGriesser@anexia-it.com>
Date: Saturday, 25 February 2017 at 20:42
To: "toasters@teaparty.net" <toasters@teaparty.net>
Subject: NVMEM discharge FET off?
Hi,
anyone ever had these?
2/25/2017 19:39:32 san01n01 EMERGENCY nvmem.battery.capLowCrit: The NVMEM battery capacity is critically low (0 cycles). To prevent data loss, the system will shut down in 20 minutes.
2/25/2017 17:43:26 san01n02 EMERGENCY nvmem.battery.discFET.off: The NVMEM battery discharge FET is off. To prevent data loss, the system will shut down in 5 minutes.
2/25/2017 17:32:26 san01n02 ALERT nvmem.battery.FET.off: The NVMEM battery charge FET is off. To prevent data loss, the system will shut down in 24 hours.
2/25/2017 17:29:27 san01n01 EMERGENCY nvmem.battery.capLowCrit: The NVMEM battery capacity is critically low (0 cycles). To prevent data loss, the system will shut down in 20 minutes.
2/25/2017 16:20:52 san01n01 EMERGENCY nvmem.battery.discFET.off: The NVMEM battery discharge FET is off. To prevent data loss, the system will shut down in 5 minutes.
The system did not shut down and all `system health` related commands I’m aware of tell me, that everything is good.
This is a brand new AFF A300, but it’s been running since about a month now, so it’s not been powered on today or anything like that which would rectify these messages sometimes.
Best,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail:
AGriesser@anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
-- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457
and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.