#How to run a disk check on a raid array full#

It’s not a thorough check of the drive itself, but it does force the system to periodically verify that (almost) every file can be read successfully off the disk. I also have a cron job that runs the following command once a month: tar c /dir/of/raid/filesystem > /dev/null For example, to check the array on /dev/md0, run as root: echo check > /sys/block/md0/md/sync_action

You can force a check of the entire array while it's online. Depending on your MTA, you may need to run the newaliases command after editing /etc/aliases. If you choose remote delivery, make sure that your MTA is configured for that. With most MTAs, the address can be configured in /etc/aliases you should have a line like root: djsmiley2kįor local delivery, or root: remote delivery. This can be your account on the local machine, or an external email address. Redirect mail going to system accounts (at least root) to an address that you read regularly. All distributions come with suitable MTAs, pick anything (but not nullmailer if you want the email to be delivered locally). The MTA must be set up at least to allow local mail delivery. Test this by sending root a mail: echo hello | mail -s test Usually, a proper email setup requires two things: Make sure that you do receive mail send to root on the local machine (some modern distributions omit this, because they consider that all email goes through external providers - but receiving local mail is necessary for any serious system administrator). Then you will receive an email notification as soon as an error (a degraded array) occurs. Make sure that you have MAILADDR root in /etc/nf (some distributions (e.g. In addition to these spot checks, mdadm can notify you as soon as something bad happens.

#How to run a disk check on a raid array full#

Some /sys entries are writable as well for example you can trigger a full check of md0 with echo check >/sys/class/block/md0/md/sync_action. You can get information about a RAID device in /sys/class/block/md*/md/* as well see Documentation/md.txt in the kernel documentation. You can also get a quick summary of all RAID device status by looking at /proc/mdstat. You can show the current status of an array with mdadm -D: # mdadm -D /dev/md0įurthermore the return status of mdadm -D is nonzero if there is any problem such as a failed component (1 indicates an error that the RAID mode compensates for, and 2 indicates a complete failure). The point of RAID with redundancy is that it will keep going as long as it can, but obviously it will detect errors that put it into a degraded mode, such as a failing disk. I monitor SMART on all the drives and also have mdadm set to email me in case of failure but I'd like to know my drives occasionally 'check' themselves too. How would you check a running RAID to make sure all disks are still preforming normally? However looking for these scripts again now I'm finding it hard to find anything which seems similar to what I ran before and I feel I'm out of date and not understanding whatever has changed. Obviously backups are important and I'm taking care of that also, however I know I've previously seen scripts which claim to help against this problem and allow you to check your RAID while its running. However I've heard various stories about data getting corrupted on one drive and you never noticing due to the other drive being used, up until the point when the first drive fails, and you find your second drive is also screwed (and 3rd, 4th, 5th drive). Its currently mdadm RAID-1, going to RAID-5 once I have more drives (and then RAID-6 I'm hoping for). I'm starting to get a collection of computers at home and to support them I have my 'server' linux box running a RAID array.