Changes

====Resynchronising a Failed RAID====

====Resynchronising a Failed RAID====

Sometimes a partition will be taken offline automatically. This will happen if, for example, a read or write error is detected in a disk in the RAID set. When this happens, the details of the raid can be seen by inspecting the mdstat file. In the following example, partition hda2 (hard disk 'a', partition 2) is offline:

Sometimes a partition will be taken offline automatically. This will happen if, for example, a read or write error is detected in a disk in the RAID set, or a disk does not respond fast enough, causing a timeout. When this happens, the details of the raid can be seen by inspecting the mdstat file. In the following example, partition hda2 (hard disk 'a', partition 2) is offline:

<pre>[root@sme]# cat /proc/mdstat

<pre>[root@sme]# cat /proc/mdstat

</pre>

</pre>

If this action is required regularly, you should test your disks for SMART errors and physical errors, check your disk cables, and make sure no two hard drives share the same IDE port.

If this action is required regularly, you should test your disks for SMART errors and physical errors, check your disk cables, and make sure no two hard drives share the same IDE port. Also check your driver cards, since a faulty card can destroy the data on a full RAID set as easily as it can a single disk.

<noinclude>[[Category:Howto]]</noinclude>

<noinclude>[[Category:Howto]]</noinclude>