RAID-5 critical error

Question

I have 7371 which had disk00 failure. I reloaded the WAE during week end. Now I do not see the disk00 failure.. But I see RAID-5 critical when I do 'show disk details'. Everything looks normal. But does any one know how to get rid of RAID-5 critical error ?

Answer 1

you must run a script (the WAAS disk check tool) that checks the file system for errors that may result from a RAID synchronization failure.
You may obtain the WAAS disk check tool from the following URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/waas40
When you run the WAAS disk check tool, you will be logged out of the device. The device automatically reboots after it has completed checking the file system. Because this operation results in a reboot, we recommend that you perform this operation after normal business hours.
To run the WAAS disk check tool, follow these steps:
Step 1 Copy the script to your WAE device by using the copy ftp disk command.
WAE# copy ftp disk disk_check.sh
Step 2 Run the script from the CLI, as shown in the following example:
WAE# script execute disk_check.sh
This script will check if there is any file system issue on the attached disks
Activating the script will result in:
Stopping all services. This will log you out.
Perform file system check for few minutes.
and record the result in the following files:
/local1/disk_status.txt - result summary
/local1/disk_check_log.txt - detailed log
System reboot
If the system doesn't reboot in 10 minutes, please re-login and check the result files.
Continue?[yes/no] yes
Please disk_status.txt after reboot for result summary
umount: /state: device is busy
umount: /local/lPAM_unix[26162]: ### pam_unix: pam_sm_close_session (su) session closed
for user root
waitpid returns error: No child processes
No child alive.
Step 3 After the device reboots and you log in, locate and open the following two files to view the file system status:
•disk_status.txt- Lists each file system and shows if it is "OK," or if it contains an error that requires attention.
•disk_check_log.txt-Contains a detailed log for each file system checked.
If no repair is needed, then each file system will be listed as "OK," as shown in the following example:
WAE# type disk_status.txt
Thu Feb 1 00:40:01 UTC 2007
device /dev/md1 (/swstore) is OK
device /dev/md0 (/sw) is OK
device /dev/md2 (/state) is OK
device /dev/md6 (/local/local1/spool) is OK
device /dev/md5 (/local/local1) is OK
device /dev/md4 (/disk00-04) is OK
Step 4 If a file system contains errors, follow the instructions in the disk_status.txt file to repair the file system.
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/release/notes/ws4013rn.html#wp272874
kindly send the out of the following command :
show disks details
can read this section.
Might be it give you some relevant information regading your case.
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/configuration/guide/maint.html#wp1144150
Kind regards,
Sachin garg