SoftRAID 3 Manual Excerpts:
Mirror Essentials
Page 1 | Page 2 | Page 3
Out-of-sync - An out-of-sync mirror state indicates that one or more of the secondary disks do not match the Primary disk. This state occurs if SoftRAID did not detect all of the disks at startup, if a disk has been turned off while the volume was being used, or if one (or more, but not all) of the disks has experienced an i/o error.
Although SoftRAID will continue writing to an out-of-sync Mirror volume, it is highly recommended that the volume be rebuilt using the Rebuild Mirror command in the Volume menu. If the “Automatically Start Mirror Rebuilds” option is set in the Driver Preferences dialog, the SoftRAID driver will immediately start the process as soon as the out-of-sync state is detected. The volume can still be used while the Rebuild proceeds.
An out-of-sync state can also occur if the Mac crashed while the Volume was in use. Use the Rebuild Mirror command to copy all the data from the Primary disk to the out-of-sync secondary disk(s).
Out-of-sync, missing secondary - This state would occur if a Mirror volume is out-of-sync AND if one of the secondary disks was missing.
No secondary disk - This state occurs if there is only one disk available for the a Mirror volume. This volume can have up to 15 secondary disks added to it with the Add Secondary Disk command in the Volume menu.
Return to the top
Failed - The failed state can occur in a Mirror volume or a disk and is the result of an error in writing data to disks - an i/o error. A disk is marked failed when it experiences an i/o error. The disk will still be written to but its tile will show the failed state.
If the disk with the errors is a Primary disk and there is an intact secondary disk available, SoftRAID will turn that secondary into a Primary and mark the volume out-of sync.
A volume is marked failed if i/o errors occur on all of the disks. A failed mirror can still be used but data integrity is no longer assured.
The failed state of a Mirror volume or a secondary disk is often indicative of a hardware failure and the defective hardware should be eliminated or replaced to ensure intact Mirror volumes.
Note: To determine when a failure happened (which may help you determine the cause), you can consult the System Log. Read the section Using the System Log in the Stripe Essentials section of this Manual for more information on this feature.
To clear a failed disk state: Remove the failed secondary disk and the volume tile will change to missing secondary disk. This state can then be cleared with the Remove Missing Secondary Disks command described later in this section.
The failed disk can also be split off from the Mirror volume using the Split Mirror command. It can then be removed and replaced.
To clear a failed Mirror: A failed Mirror volume may indicate that a cable or card is malfunctioning or may be caused by a crash or brownout. To troubleshoot this state, the Recover Failed Mirror command may be used. This rebuilds the Mirror and clears the failed state from the Volume tile. If the cause is malfunctioning hardware, I/O errors are likely to recur, and the hardware should be replaced. If a failed Mirror is caused by a crash or power brownout, then the errors are not likely to recur after the Mirror is recovered.
Return to the top
1 | 2 | 3
|
