Active IQ and AutoSupport Discussions
Active IQ and AutoSupport Discussions
Hi
I have a FAS2020 with dual controllers, set up by someone else and I'm trying to start again.
I managed to unassign all the disks, reassign 3 disks to controller 1 and create a root volume. Now when it boots I get an error about SMTP server and autosupport and then it fails to boot the BIOS.
I press Ctrl-G to go into the bmc menu and run sensors show and get the following:
bmc shell -> sensors show
Name State Id Reading Crit-Low Warn-Low Warn-High Crit-High
-------------------------------------------------------------------------------------
1.1V Normal #77 1121 mV 955 mV -- -- 1239 mV
1.2V Normal #76 1227 mV 1038 mV -- -- 1357 mV
1.5V Normal #75 1498 mV 1309 mV -- -- 1699 mV
1.8V Normal #74 1829 mV 1569 mV -- -- 2029 mV
12.0V Normal #70 12000 mV 10160 mV -- -- 13840 mV
2.5V Normal #73 2520 mV 2116 mV -- -- 2870 mV
3.3V Normal #72 3351 mV 2808 mV -- -- 3799 mV
BIOS Status Error #f0 POST #01 -- -- -- --
Batt 8.0V Normal #50 8064 mV -- -- 8512 mV 8576 mV
Batt Amp Normal #59 0 mA -- -- 2112 mA 2208 mA
Batt Capacity Normal #54 2016 mAh -- -- -- --
Batt Run Time Normal #55 202 h 72 h 80 h -- --
Batt Temp Normal #51 26 C 0 C 10 C 45 C 60 C
Board Temp Bot Normal #08 34 C -3 C 7 C 69 C 79 C
Board Temp Top Normal #07 31 C -3 C 7 C 54 C 62 C
CPU 1.2V Normal #71 1180 mV 1038 mV -- -- 1357 mV
CPU Status Normal #f1 Ok -- -- -- --
CPU Temp Normal #09 42 C -- -- -- 126 C
Charger Amp Normal #53 0 mA -- -- -- --
Charger Cycles Normal #58 1 -- -- 250 251
Charger Volt Normal #52 8192 mV -- -- -- --
NVMEM 1.8V Normal #0b 1804 mV 1621 mV 1706 mV 1889 mV 1974 mV
NVMEM 8.0V Normal #0a 7839 mV -- -- 8508 mV 8604 mV
Power Status Normal #d1 Power On -- -- -- --
SAS Status Normal #b6 Ok -- -- -- --
bmc shell ->
How can I resolve this? Can I reflash the BIOS somehow either from the bmc or from the other controller?
I've successfully got the other controller up and running, upgraded it to 7.3.5.1 and FilerView now runs without Java errors.
Any help most gratefully received.
Regards
Barry
Solved! See The Solution
Looks like you need to RMA the Controller...
http://now.netapp.com/eservice/submitRMA.do?moduleName=RMA
You can give it a try and pull it out and reseat it after waiting for 10 secs. With ab it of luck it gets past the error. Otherwise see above.
Peter
Looks like you need to RMA the Controller...
http://now.netapp.com/eservice/submitRMA.do?moduleName=RMA
You can give it a try and pull it out and reseat it after waiting for 10 secs. With ab it of luck it gets past the error. Otherwise see above.
Peter
Thanks Peter
I'm working through with support to get this resolved now.
Regards
Barry
Sorry for the long gap between posts but now it's working I thought I should post an update. After working through with support they gave me instructions to reflash the BIOS. I'd taken the second controller out and had it sitting on my desk for a couple of weeks and when I put it in, it booted straight past the error. So, same suggestion that Peter made but instead of 10 secs, I waited 2-3 weeks. I then reflashed the BIOS and all has been fine since.
Regards
Barry
Thanks for the update, good to know.
Peter
I find nothing more frustrating on a forum thread than not knowing the outcome of a suggestion so it wouldn’t do to be guilty of the same myself.
Thanks for the help
Barry
instructions can be.