Boot error messages might appear after the hardware passes all POSTs and your storage engine begins to load the operating system.
The following table describes the error messages that might appear on the LCD if your storage engine encounters errors while starting up.
Boot error message
|
Explanation
|
Corrective action
|
No /etc/rc
|
The /etc/rc file is corrupted.
|
- At the hostname> prompt, enter
setup.
- As the system prompts for system
configuration information, use the
information you recorded in your
storage engine configuration
information worksheet in the
Getting Started Guide.
For more information about your storage engine setup program, see the System Administration Guide.
|
No /etc/rc, running setup
|
The system cannot find the /etc/rc file and automatically starts setup.
|
As the system prompts for system configuration information, use the information you recorded in your storage engine configuration information worksheet in the Getting Started Guide.
For more information about your storage engine setup program, see the System Administration Guide.
|
Cannot initialize labels
|
When the system tries to create a new file system, it cannot initialize the disk labels.
|
Usually, you do not need to create and initialize a file system; do so only after consulting Network Appliance Customer Support.
|
Cannot read labels
|
When your storage engine tries to initialize a new file system, it has a problem reading the disk labels it wrote to the disks.
This problem can be because the system failed to read the disk size, or the written disk labels were invalid.
|
Usually, you do not need to create and initialize a file system; do so only after consulting Network Appliance Customer Support.
|
Disk label processing failed
|
Your storage engine detects that the disk is not in the correct drive bay.
|
Make sure that the disk is in the correct bay.
|
Dirty shutdown in degraded mode
|
The file system is inconsistent because you did not shut down the system cleanly when it was in degraded mode.
|
Contact Network Appliance Customer Support for instructions about repairing the file system.
|
Halted: firmware too old
|
Not supported.
|
Contact Network Appliance Customer Support.
|
No disks
|
The system cannot detect any disks.
|
Verify that all disks are properly seated in the drive bays.
|
No disk controllers
|
The system cannot detect any disk controllers.
|
Turn off your storage engine power and verify that all NICs are properly seated in the appropriate expansion slots.
|
Drive %s.%d not supported
|
%s--The disk number; %d--The disk ID number. The system detects an unsupported disk drive.
|
- Remove the drive immediately or
the system drops down to the
PROM monitor within 30
seconds.
- Check the System Configuration
Guide at http://now.netapp.com to
verify support for your disk drive.
|
FC-AL loop down, adapter %d
|
The system cannot detect the FC-AL loop or adapter.
|
- Identify the adapter by entering
the following command:
storage show adapter
- Turn off the power on your
storage engine and verify that the
adapter is properly seated in the
expansion slot.
- Verify that all Fibre Channel
cables are connected.
|
Halted: Illegal configuration
|
Incorrect cluster configuration.
|
R200 does not support clustering.
|
File system may be scrambled
|
One of the following errors causes the file system to be inconsistent:
|
|
- An unclean shutdown when your storage engine is in degraded mode and when NVRAM is not working.
|
Contact Network Appliance Customer Support to learn how to start the system from a system boot diskette and repair the file system.
|
- The number of disks detected in the disk array is different from the number of disks recorded in the disk labels. The system cannot start when more than one disk is missing.
|
Make sure that all disks on the system are properly installed in the disk shelves.
|
- The system encounters a read error while reconstructing parity.
|
Contact Network Appliance Customer Support for help.
|
- A disk failed at the same time the system crashed.
|
Contact Network Appliance Customer Support to learn how to repair the file system.
|
Invalid PCI card slot %d
|
%d--The expansion slot number. The system detects a adapter that is not supported by Network Appliance.
|
Replace the unsupported adapter with an adapter that is included in the System Configuration Guide at http://now.netapp.com.
|
Configuration exceeds max PCI space
|
The memory space for mapping PCI adapters is exhausted, because either
- There are too many PCI adapters in the system
- An adapter is demanding too many resources
|
Verify that all expansion adapters in your storage engine are supported.
Contact Network Appliance Customer Support for help. Have a list ready of all expansion adapters installed in your storage engine.
|
No network interfaces
|
The system cannot detect any network interfaces.
|
- Turn off the system and verify that
all NICs are seated properly in the
appropriate expansion slots.
- Run diagnostics to check the
onboard Ethernet port.
If the problem persists, contact Network Appliance Customer Support.
|
No NVRAM present
|
n--The serial number of the NVRAM adapter. The NVRAM adapter is an early revision that cannot be used with the system.
|
Check the console for information about which revision of the NVRAM adapter is required. Replace the NVRAM adapter.
|
NVRAM #n downrev
|
%d--The amount of memory on the NVRAM adapter. The specified size is not supported.
|
Verify that the system has 256 MB of NVRAM.
|