#Error: Failed to determine the board type. Contact technical support for assistance.

1 messages · Page 1 of 1 (latest)

opal vine
#

Hi Team.

Due to electrical work in the customer's data center, the filer was shut down today and then restarted. However, node 2 is not booting up properly.

Technical support was received, and the X3320A part was replaced. However, when attempting to install the same version of ONTAP that was previously used, the USB is not recognized, and e0M is also not recognized.

I have reviewed all accessible knowledge base articles, but it seems I still cannot find a solution. What could be the problem, and how should it be resolved?

#

LOADER> boot_recovery Bootable external device not found! Boot Recovery failed

LOADER> ifconfig e0M -addr=10.10.10.11 -mask=255.255.255.0 -gw=10.10.10.1 Network interface setup for IPv4 Could not activate network interface 'e0M': Error *** command status = Error(-1)

# 
  Intel(R) Xeon(R) CPU D-1587 @ 1.70GHz (CPU 0)
  CPUID: 0x00050664. Cores per Processor = 16
131072 MB System RAM Installed.
SATA (AHCI) Device: SV9MST6D120GLM41NP

Boot Loader version 6.0
Copyright (C) 2000-2003 Broadcom Corporation.
Portions Copyright (C) 2002-2016 NetApp, Inc. All Rights Reserved.

LOADER-A> BIOS Version: 11.1
Portions Copyright (C) 2014-2017 NetApp, Inc. All Rights Reserved.
Error: Failed to determine the board type. Contact technical support for assistance.
BIOS Version: 11.1
Portions Copyright (C) 2014-2017 NetApp, Inc. All Rights Reserved.
Error: Failed to determine the board type. Contact technical support for assistance.
cursive burrow
#

For starters I would 100% reseat everything. Memory. USB boot device. Everything. Try again. You may want to find the kb to update the firmware first provided you can get NetBoot working in on e0M. Alternatively update the firmware from usb. There are in fact some versions of loader that will not boot on older firmware.

opal vine
cursive burrow
#

Hence the reset EVERYTHING

opal vine
#

Include coin cell?

opal vine
cursive burrow
#

Everything. Anything you can reseat, do it. If it’s going to be RMA’d can’t be any worse

opal vine
#

Ok.... i will try it

opal vine
cursive burrow
#

Yes. But no need. Just make sure everything is fully and properly seated

opal vine
#

Yup i will try it rn

opal vine
#

(NVRAM, bootdevice, mem, coin cell)

#

My USB drive partition style is MBR and File system is FAT32.
and i've tried those three steps for connect usb but failed.

  1. Connect the USB while the power is on, then execute "LOADER> bye -g" to reboot the LOADER and check again.
  2. Log in to the SP and execute the "service power cycle" command to reboot, then check again.
  3. Log in to the SP and execute the "service power off" command to shut down the power, connect the USB, remove the controller, reconnect it 15 seconds later, and then power it up to check again.
cerulean elbow
#

Continue to work with support. There’s a rare but unpleasant failure mode for the A300/FAS8200 which stops the UNIMPAIRED board from booting while the one with the actual fault works fine.

opal vine
#

Problem resolved!

cerulean elbow
#

Yay, what happened?

opal vine
#

I dont know about the root cause but we changed a controller and it works normal!

#

Hahaha

open girder
#

It's very rare but sometimes replacement parts can go bad..