OK 

The device is functioning properly. If mounted, the file system is logging and will not be checked at boot (that is, the file system will not be checked by fsck at boot).

None. 

Detach Log (in progress) 

The trans metadevice log will be detached when the Trans metadevice is unmounted or at the next reboot. 

None. 

Detach Log (scheduled) 

The trans metadevice log will be detached the next time you click the Commit button. 

Click Commit to detach the log. The detach takes place at the next reboot, or when the file system is unmounted and remounted. 

Attention 

There is a problem with the trans metadevice, but there is no immediate danger of losing data. 

Continue to monitor the status of the trans metadevice. 

Urgent 

There is a problem with the trans metadevice and it is only one failure away from losing data. This state can only exist if the trans metadevice contains a RAID5 metadevice or mirror. 

Fix the errored mirror or RAID5 master device. See "Overview of Replacing and Enabling Slices in Mirrors and RAID5 Metadevices".

Critical (log missing) 

The trans metadevice does not have a logging device attached. 

Attach a logging device. Logging for the file system cannot start until a logging device is attached. 

Critical (log hard error) 

A device error or file system panic has occurred while the device was in use. An I/O error is returned for every read or write until the device is closed or unmounted. The first open causes the device to transition to the Error state. 

Fix the trans metadevice. See "How to Recover a Trans Metadevice With a File System Panic (Command Line)", or "How to Recover a Trans Metadevice With Hard Errors (Command Line)".

Critical (error) 

The device can be read and written. The file system can be mounted read-only. However, an I/O error is returned for every read or write that actually gets a device error. The device does not transition back to the Hard Error state, even when a later device error of file system panic occurs. 

Fix the trans metadevice. See "How to Recover a Trans Metadevice With a File System Panic (Command Line)", or "How to Recover a Trans Metadevice With Hard Errors (Command Line)". Successfully completing fsck(1M) or newfs(1M) transitions the device into the Okay state. When the device is in the Hard Error or Error state, fsck automatically checks and repairs the file system at boot time. newfs destroys whatever data may be on the device.