Troubleshooting hardware problems

CFE (common firmware environment) won't boot. Last console status code might be [ZBSS], [L12F], or [CERR].

This indicates that something is wrong with the memory DIMM.

To fix this problem, begin with the first procedure in the following list. If that doesn't solve the problem, continue down to the next troubleshooting tip on the list until the problem is solved.

• Unplug the battery in the CPU module for 5 seconds, plug the battery back in, and try booting the appliance.

  Note
  Unplugging the battery might reset the clock.

• Reseat the DIMM on the CPU module.
• Replace the DIMM.
• Replace the CPU module.

CFE comes up but [CERR] is printed out when booting the kernel

This is a problem with NVMEM. NVMEM is mainly for power outages. Handling the CPU module outside the shelf while NVMEM is valid might corrupt memory.

• If the CPU module was not handled, contact Network Appliance Customer Service.
• Otherwise, unplug the battery in the CPU module for 5 seconds, plug the battery back in, and try booting the appliance.

  Note
  Unplugging the battery might reset the clock.

CFE comes up but can't boot anything from the CompactFlash card.

Contents of the CompactFlash card are not correct.

Try entering this command at the CFE prompt, which is equivalent to `dir c:' from a PC:

test fatfs ide0.0

If no errors occur and nothing is shown on the console, the contents of the CompactFlash card are not valid.

If there is an error, replace the CompactFlash card.

Real-Time Clock (RTC) loses its time.

The rechargeable battery for NVMEM also powers the real-time clock. If this battery is disconnected for more than a few seconds or the battery is discharged, the real-time clock might be reset.

Plug the battery back in to the motherboard and reset the clock to the correct time.

The appliance does not recognize any of the installed disk drives.

The 1 Gb/2 Gb switch is not set to the 1 Gb position.

1. Power off the appliance.
2. Move the switch to the 1 Gb position. See Step 6 of Connecting your appliance to a network.
3. Power on the appliance.

I replaced a CPU module and now the new module can't see the disks

The disk ownership mechanism ties disks to CPU module system IDs. If you replace a CPU module with a new one in, the disks are still stamped with the system ID of the old module.

Perform a `disk reassign' command. Use the help command to get the exact syntax.

I have unowned disks; how come Data ONTAP didn't use them to reconstruct a failed drive?

The disks need to be "SPARES", not "unowned."

Assign the disks as spares.

The battery is discharged and Data ONTAP won't boot.

The battery voltage is too low to hold data for 3 days during a power-out condition.

If you turn on the machine and let it sit at the firmware (CFE) prompt, it will not turn on the charger. You need to boot Data ONTAP to get the software to turn on the battery charger.

You have two main options at this point:

1. Leave the appliance alone for a few hours to let the battery charge.
2. Press Ctrl-C to override this check.

Executing a priv set advanced and an nv command shows you the current status of the battery (if you pressed Ctrl-C to override the stall condition). You can also try out the environ chassis Battery command (note that "Battery" is case-sensitive).

In either case, the battery charger is turned on and recharges the battery over the next few hours.

CFE failed, creating a POST code.

CFE firmware runs a series of Power-On-Self-Tests (POST) before trying to load Data ONTAP. If any of the POSTs fail, a code is printed out.

See POST error messages for a description of the error.

Fibre Channel adapter 0b appears to be unattached or disconnected.

You have an open loop. Fibre Channel needs a closed/completed loop to communicate.

• Check the terminate switch on the CPU module. If an expansion shelf is attached to your system, the terminate switch should be OFF. If there's no expansion shelf, you must have the terminate switch set to ON.
• If you have expansion shelves, the last shelf must have its terminate switch set to ON. All other shelves in the loop (including the CPU module) must have the terminate switches set to OFF.
• If that doesn't fix it, you might have a faulty shelf, drive, or cable. Try removing items until the loop closes and then add them back until you see the failure. While removing/adding, be sure to set the terminate switches appropriately.
• If that still doesn't fix it, you might have a bad adapter on the CPU module (rare case). You'll have to do a CPU module replacement.

The appliance won't stop beeping.

It is the kernel's responsibility to "ping" the ops panel occasionally so the ops panel's watchdog timer doesn't start beeping.

Push the MUTE button on the back of the shelf to stop the beeping. If beeping continues, contact NetApp Customer Service.