INFORMATIONAL

This message is sent when a system completes disk boot.

(None).

%s boot complete. Last disk update written at %s

ver (STRING): (long) version of the OS which just booted
last_write_time (STRING): time at which the previous OS last wrote to disk

NOTICE

This message is sent when a system completes a 25/7 boot.

(None).

%s floppy boot complete (after 25/7).

ver (STRING): (long) version of the OS which just booted

INFORMATIONAL

This message is sent when a system completes a plain old floppy boot.

(None).

%s floppy boot complete.

ver (STRING): (long) version of the OS which just booted

EMERGENCY

This message is sent when a system completes a bypass_media boot.

(None).

%s floppy boot complete (with disk media errors bypassed).

ver (STRING): (long) version of the OS which just booted

INFORMATIONAL

This message is sent when a system completes a prev_cp boot.

(None).

%s floppy boot complete (after prev_cp).

ver (STRING): (long) version of the OS which just booted

INFORMATIONAL

This event marks the end of populating the mroot during the boot sequence; this event is generated immediately after the process of populating the mroot has completed.

(None).

(None).

(None).

INFORMATIONAL

This event marks the start of populating the mroot during the boot sequence; this event is generated immediately before the process of populating the mroot begins.

(None).

(None).

(None).

NOTICE

This message is sent when a system boots with a different OS version from before, and the previous version is known.

(None).

This system is running a new version of %s (was %s, now %s)

osName (STRING): The flavor of operating system (Data ONTAP or NetCache)
oldOsVersion (STRING): The previous OS version
newOsVersion (STRING): The new OS version

ALERT

This message occurs when a node does not reach a stable state within 5 minutes after system boot. The system will continue booting while waiting for a stable state. Under a takeover scenario, the node has to be stable for giveback to be completed.

Run the "storage failover show" command for takeover status. If the issue persists, contact NetApp technical support for assistance.

The node has not reached a stable state within 5 minutes after system boot. Retries are in progress.

(None).

ERROR

This message occurs when the system firmware is determined to be too old.

For more information about upgrading your system firmware, check your support provider's web site or knowledgebase.

The current system firmware version %s is too old. Upgrade to the minimum version %s or later.

currentFW (STRING): Current system firmware version.
newFW (STRING): Desired system firmware version.

INFORMATIONAL

This event marks the end of populating the pmroot during the boot sequence; this event is generated immediately after the process of populating the pmroot has completed.

(None).

(None).

(None).

INFORMATIONAL

This event marks the start of populating the pmroot during the boot sequence; this event is generated immediately before the process of populating the pmroot begins.

(None).

(None).

(None).

Deprecated as of ONTAP 9.1. Last used in 9.0x.

ALERT

This message occurs when a system detects an un-responsive process during system boot. The system will continue booting while waiting for the process to respond.

Contact NetApp technical support to diagnose the issue further.

The %s process is not responding. Error: %s

process (STRING): The process that is hung.
error (STRING): An error message about the problem.

EMERGENCY

This message is sent when a system boots for abnormal reasons (panic, watchdog, etc). The message contains the reboot reason.

(None).

%s

reboot_reason (STRING): reboot reason

NOTICE

This message is sent when a system boots for normal reasons (halt/reboot command, etc). The message contains the reboot reason.

(None).

%s

reboot_reason (STRING): reboot reason

ERROR

This message occurs during system initialization when the local system finds that the number of disks that it can use to create a partitioned root aggregate is different than on the partner node.

To create a system with an equal number of automatically partitioned disks on the local and partner systems: 1. Make sure that any failed disks in the internal shelf are replaced. 2. Remove ownership from all disks. The system automatically assigns one half of the disks to the local system and the other half to the partner node. To remove disk ownership, boot into maintenance mode and manually remove ownership by using the "disk remove_ownership" command.

Warning: Unequal number of disks will be used for auto-partitioning of the root aggregate on the local system and HA partner. The local system will use %d disks but the HA partner will use %d disks. To correct this situation, boot both controllers into maintenance mode and remove the ownership of all disks.

n_local (INT): Number of partitionable disks that are used by the local system.
n_partner (INT): Number of partitionable disks that are used by the partner system.