The following table lists the boot error messages that might appear after the filer has completed the BIOS and system tests and begins to load the operating system.
Boot error message
|
Explanation
|
Fatal?
|
Corrective action
|
|---|
No /etc/rc
|
The /etc/rc file is corrupted.
|
No
|
- At the hostname> prompt,
enter the following
command:
setup
- At the system prompts for
system configuration
information, use the
information you recorded
in the filer configuration
information worksheet in
the Getting Started Guide.
For more information about the filer setup program, see the Data ONTAP System Administrator's Guide.
|
No /etc/rc, running setup
|
The system cannot find the /etc/rc file and automatically starts setup.
|
No
|
At the system prompts for system configuration information, use the information you recorded in the filer configuration information worksheet in the Getting Started Guide.
For more information about the filer setup program, see the Data ONTAP System Administrator's Guide.
|
Cannot initialize labels
|
When the system tries to create a new file system, it cannot initialize the disk labels.
|
Yes
|
Usually, you do not need to create and initialize a file system; do so only after consulting Network Appliance Technical Support.
|
Cannot read labels
|
When the filer tries to initialize a new file system, it has a problem reading the disk labels it wrote to the disks.
This problem might be because
- The system failed to read the disk size
- The written disk labels were invalid
|
Yes
|
Usually, you do not need to create and initialize a file system; do so only after consulting Network Appliance Technical Support.
|
Disk label processing failed
|
The filer detects that the disk is not in the correct drive bay.
|
Yes
|
Make sure that the disk is in the correct bay. Move it if it is not 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.
|
Yes
|
Contact Network Appliance Technical Support for instructions about repairing the file system.
|
No disk controllers!
|
The system cannot detect any SCSI disk controllers.
|
Yes
|
Turn off the filer power and verify that all SCSI adapters are properly seated in the appropriate expansion slots.
|
No disks!
|
The system cannot detect any SCSI disks.
|
Yes
|
- Verify that all disks are
properly seated in the
drive bays.
- Check the cabling.
|
Drive decimal_value.decimal_value not supported
|
decimal_value--The SCSI disk number; decimal_value--The disk ID number. The system detects an unsupported disk drive.
|
Yes
|
- 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.
|
File system may be scrambled
|
One of the following errors causes the file system to be inconsistent:
|
|
|
- An unclean shutdown when the filer is in degraded mode and when NVRAM is not working.
|
Yes
|
Contact Network Appliance Technical 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.
|
Yes
|
Make sure that all disks on the system are properly installed in the disk shelf.
|
- The system encounters a read error while reconstructing parity.
|
Yes
|
Contact Network Appliance Technical Support.
|
- A disk failed at the same time the system crashed.
|
Yes
|
Contact Network Appliance Technical Support to learn how to repair the file system.
|
Invalid PCI card slot decimal_value
|
decimal_value--The expansion slot number. The system detects an adapter that is not supported by Network Appliance.
|
Yes
|
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 has been exhausted, because either
- There are too many PCI adapters in the system
- An adapter is demanding too many resources
|
Yes
|
Verify that all expansion adapters in the filer are supported.
Contact Network Appliance Technical Support. Have a list ready of all expansion adapters installed in the filer.
|
No network interfaces!
|
The system cannot detect any network interfaces.
|
Yes
|
Turn off the system and verify that all NICs are seated properly in the appropriate expansion slots.
If the problem persists, contact Network Appliance Technical Support.
|
ServerNet: wrong pci slot
|
The system detects that the cluster interconnect adapter is in the wrong expansion slot.
|
Yes
|
Remove the cluster interconnect adapter; it is not supported.
|
No NVRAM present
|
The system cannot detect the NVRAM adapter.
|
Yes
|
Turn off the power and make sure that the NVRAM adapter is securely installed in expansion slot 1.
|
Replace NVRAM battery
|
The NVRAM battery is low. The system shuts down immediately.
|
Yes
|
Replace the battery.
|
NVRAM #n downrev!
|
n--The serial number of the NVRAM adapter. The NVRAM adapter is an early revision that cannot be used with the system.
|
Yes
|
Check the console for information about which revision of the NVRAM adapter is required. Replace the NVRAM adapter.
|
NVRAM test failed
|
The system NVRAM produces an error when the system is starting.
|
Yes
|
Contact Network Appliance Technical Support.
|
Unsupported NVRAM size decimal_value MB
|
decimal_value--The amount of memory on the NVRAM adapter. The specified size is not supported.
|
Yes
|
Verify that the system has 64 MB of NVRAM.
|
