ONTAP Hardware

FAS2240-2 controller-A doesnt boot

E3AP
5,829 Views

HI!

FAS2240-2 controller-A stuck at boot with next errors:

 

Phoenix SecureCore(tm) Server
Copyright 1985-2008 Phoenix Technologies Ltd.
All Rights Reserved
BIOS version: 8.1.0
Portions Copyright (c) 2008-2011 NetApp, Inc. All Rights Reserved

CPU = 1 Processors Detected, Cores per Processor = 2
Intel(R) Xeon(R) CPU C3528 @ 1.73GHz
Testing RAM
512MB RAM tested
6144MB RAM installed
256 KB L2 Cache per Processor Core
4096K L3 Cache Detected
System BIOS shadowed
USB 2.0: MICRON eUSB DISK
BIOS is scanning PCI Option ROMs, this may take a few seconds...
WARNING
02A1: SP Not Found
ERROR
No Response to Controller FRU ID Read Request via IPMI
ERROR
No Response to Midplane FRU ID Read Request via IPMI


Boot Loader version 4.1
Copyright (C) 2000-2003 Broadcom Corporation.
Portions Copyright (C) 2002-2011 NetApp

CPU Type: Intel(R) Xeon(R) CPU C3528 @ 1.73GHz
BIOS POST Failure(s) detected. Abort AUTOBOOT
LOADER-A>

 

 

 

Trying to boot in any way looks like this:

LOADER-A> boot_diags
Loading X86_64/freebsd/image1/kernel:0x100000/9522152 0xa14be8/3138480 Entry at 0x8016d930
Loading X86_64/freebsd/image1/platform.ko:0xd13000/683920 0xe7f998/630720 0xdb9fa0/41224 0xf19958/44064 0xdc40a8/92946 0xddabba/69132 0xdeb9e0/146624 0xf24578/171072 0xe0f6a0/16 0xe0f6b0/2136 0xf4e1b8/6408 0xe0ff80/0 0xe0ff80/320 0xf4fac0/960 0xe100c0/1744 0xf4fe80/5232 0xe10790/1528 0xf512f0/4584 0xe10d88/184 0xf524d8/552 0xe10e40/448 0xe48560/13562 0xe7f896/253 0xe4ba60/122688 0xe699a0/89846
Starting program at 0x8016d930
NetApp Data ONTAP 8.2P3 7-Mode

PANIC : The 0 is not a supported platform

version: 8.2P3: Wed Sep 11 21:30:48 PDT 2013
conf : x86_64
cpuid = 0
Uptime: 1s

The operating system has halted.
Please press any key to reboot.

System halting...
cpu_reset called on cpu#0

 

 

And the scariest thing is:

 

LOADER-A> printenv

Variable Name Value
-------------------- --------------------------------------------------
CPU_NUM_CORES 4
BOOT_CONSOLE sp0a
BIOS_VERSION 8.1.0
BIOS_DATE 05/08/2012
SYS_MODEL 0
SYS_REV 0
SYS_SERIAL_NUM 0
MOBO_MODEL 0
MOBO_REV 0
MOBO_SERIAL_NUM 0
CPU_SPEED 1730
CPU_TYPE Intel(R) Xeon(R) CPU C3528 @ 1.73GHz
savenv saveenv
ENV_VERSION 1
BIOS_INTERFACE 9FC7
BOOT_FLASH flash0a
LOADER_VERSION 4.1
ARCH X86_64
BOARDNAME SB_XIX
PRIMARY_KERNEL_URL fat://boot0/X86_64/kernel/primary.krn
BACKUP_KERNEL_URL fat://boot0/backup/X86_64/kernel/primary.krn
GX_PRIMARY_KERNEL_URL fat://boot0/X86_64/freebsd/image1/kernel
GX_DIAG_URL fat://boot0/X86_64/freebsd/image1/kernel
GX_BACKUP_KERNEL_URL fat://boot0/X86_64/freebsd/image2/kernel
ntap.init.kernelname X86_64/freebsd/image1/kernel
FIRMWARE_URL fat://boot0/X86_64/firmware/SB_XIX/firmware.img
boot_ontap autoboot boot0
boot_primary setenv BOOTED_FROM PRIMARY; boot -elf64 $GX_PRIMARY_KERNEL_URL $PRIMARY_KERNEL_URL
boot_backup setenv BOOTED_FROM BACKUP; boot -elf64 $GX_BACKUP_KERNEL_URL $BACKUP_KERNEL_URL
netboot setenv BOTED_FROM NETWORK; boot -elf64
boot_diags boot -sld -elf64 $GX_DIAG_URL $PRIMARY_KERNEL_URL
ldkern load -elf64 $GX_PRIMARY_KERNEL_URL $PRIMARY_KERNEL_URL
update_flash flash -backup $FIRMWARE_URL flash0a
version printenv BIOS_VERSION LOADER_VERSION
BT_BIOS_VERSION 8.1.0
BT_LOADER_VERSION 4.1
AUTOBOOT true
AUTOBOOT_FROM PRIMARY
AUTO_FW_UPDATE true

 

 

Cant it be just stuck SP firmware or "this is the end" )) and it`s time to replace controller?

1 ACCEPTED SOLUTION

andris
5,760 Views

It sure looks like the SP is nonresponsive.

 

If you press "Ctrl-G" at the console, it switches over to the SP CLI prompt. Can you get a response?

 

A simple resolution would be to fully power cycle the controller/chassis or just pull the PCM out for a minute -- then re-insert it.  Monitor the console for what happens after re-insertion.

 

If nothing changes, looks like the controller is toast.

View solution in original post

2 REPLIES 2

andris
5,761 Views

It sure looks like the SP is nonresponsive.

 

If you press "Ctrl-G" at the console, it switches over to the SP CLI prompt. Can you get a response?

 

A simple resolution would be to fully power cycle the controller/chassis or just pull the PCM out for a minute -- then re-insert it.  Monitor the console for what happens after re-insertion.

 

If nothing changes, looks like the controller is toast.

AlexDawson
5,663 Views

Or potentially the midplane, but probably the controller as I understand it.

 

If you have another DS2246 chassis, and can take the downtime to swap all the drives and controller across, you could try that, but chances aren't good.

Public