Skip to main content
NetApp Knowledge Base

What happens when a disk fails and does not have a hot spare installed?

Views:
502
Visibility:
Public
Votes:
0
Category:
data-ontap-7
Specialty:
hw
Last Updated:

Applies to

  • Data ONTAP 7 and earlier
  • Disk Drive

Answer

No hot spare disk

The following events occur when a disk fails in a filer that is not equipped with a hot spare disk:

  1. The storage system enters a state called degraded mode. In this state, the RAID feature allows the storage system to continue to run without losing data (although the storage system's performance might be affected).
Warning: Replace all reported failed disk as soon as possible, as additional disk failures will cause data loss within the affected raid group.

2. The storage system logs one of the following warning messages in the /etc/messages file and to the system console every hour:

Parity disk is broken. Halting in m hours.
Data disk n is broken. Halting in m hours.

where "n" is the disk ID number, and "m" is the number of hours before the system halts.


3. Immediately before the system halts, a message similar to the following is sent to /etc/messages and the console:

Sat Oct 29 13:26:42 PDT [statd]: When a disk is broken, the system shuts down automatically every 24 hours to encourage you to replace the disk.
If you reboot the system it will run for another 24 hours before shutting down.

4. The system shuts down after the specified time period if it is still running in degraded mode. The shutdown ensures that you notice the disk failure. You can restart the storage system without fixing the disk, but the storage system will continue to shut itself off at the specified intervals until the issue is fixed.

Note: By default, the storage system shuts down after 24 hours. You can change this time interval with the raid.timeout option.
For Example: options raid.timeout [time] where [time] is the time in hours that the system runs before automatic shutdown.

Additional Information

additionalInformation_text