<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RAID-5 critical error in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109343#M22652</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may obtain the WAAS disk check tool from the following URL: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/pcgi-bin/tablebuild.pl/waas40" target="_blank"&gt;http://www.cisco.com/pcgi-bin/tablebuild.pl/waas40&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To run the WAAS disk check tool, follow these steps: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Step 1 Copy the script to your WAE device by using the copy ftp disk command. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WAE# copy ftp disk &lt;FTP-SERVER&gt; &lt;REMOTE_FILE_DIR&gt; disk_check.sh&lt;/REMOTE_FILE_DIR&gt;&lt;/FTP-SERVER&gt;&lt;/P&gt;&lt;P&gt;Step 2 Run the script from the CLI, as shown in the following example: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WAE# script execute disk_check.sh &lt;/P&gt;&lt;P&gt;This script will check if there is any file system issue on the attached disks &lt;/P&gt;&lt;P&gt;Activating the script will result in: &lt;/P&gt;&lt;P&gt;Stopping all services. This will log you out. &lt;/P&gt;&lt;P&gt;Perform file system check for few minutes. &lt;/P&gt;&lt;P&gt;and record the result in the following files: &lt;/P&gt;&lt;P&gt;/local1/disk_status.txt - result summary &lt;/P&gt;&lt;P&gt;/local1/disk_check_log.txt - detailed log &lt;/P&gt;&lt;P&gt;System reboot &lt;/P&gt;&lt;P&gt;If the system doesn't reboot in 10 minutes, please re-login and check the result files. &lt;/P&gt;&lt;P&gt;Continue?[yes/no] yes &lt;/P&gt;&lt;P&gt;Please disk_status.txt after reboot for result summary &lt;/P&gt;&lt;P&gt;umount: /state: device is busy &lt;/P&gt;&lt;P&gt;umount: /local/lPAM_unix[26162]: ### pam_unix: pam_sm_close_session (su) session closed &lt;/P&gt;&lt;P&gt;for user root &lt;/P&gt;&lt;P&gt;waitpid returns error: No child processes &lt;/P&gt;&lt;P&gt;No child alive.&lt;/P&gt;&lt;P&gt;Step 3 After the device reboots and you log in, locate and open the following two files to view the file system status: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢disk_status.txt- Lists each file system and shows if it is "OK," or if it contains an error that requires attention. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢disk_check_log.txt-Contains a detailed log for each file system checked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If no repair is needed, then each file system will be listed as "OK," as shown in the following example: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WAE# type disk_status.txt &lt;/P&gt;&lt;P&gt;Thu Feb 1 00:40:01 UTC 2007 &lt;/P&gt;&lt;P&gt;device /dev/md1 (/swstore) is OK &lt;/P&gt;&lt;P&gt;device /dev/md0 (/sw) is OK &lt;/P&gt;&lt;P&gt;device /dev/md2 (/state) is OK &lt;/P&gt;&lt;P&gt;device /dev/md6 (/local/local1/spool) is OK &lt;/P&gt;&lt;P&gt;device /dev/md5 (/local/local1) is OK &lt;/P&gt;&lt;P&gt;device /dev/md4 (/disk00-04) is OK&lt;/P&gt;&lt;P&gt;Step 4 If a file system contains errors, follow the instructions in the disk_status.txt file to repair the file system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/release/notes/ws4013rn.html#wp272874" target="_blank"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/release/notes/ws4013rn.html#wp272874&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;kindly send the out of the following command :&lt;/P&gt;&lt;P&gt;show disks details &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can read this section.&lt;/P&gt;&lt;P&gt;Might be it give you some relevant information regading your case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/configuration/guide/maint.html#wp1144150" target="_blank"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/configuration/guide/maint.html#wp1144150&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin garg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Aug 2008 01:17:44 GMT</pubDate>
    <dc:creator>sachinga.hcl</dc:creator>
    <dc:date>2008-08-05T01:17:44Z</dc:date>
    <item>
      <title>RAID-5 critical error</title>
      <link>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109342#M22651</link>
      <description>&lt;P&gt;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 ?&lt;/P&gt;</description>
      <pubDate>Mon, 04 Aug 2008 01:55:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109342#M22651</guid>
      <dc:creator>rhegde</dc:creator>
      <dc:date>2008-08-04T01:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: RAID-5 critical error</title>
      <link>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109343#M22652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may obtain the WAAS disk check tool from the following URL: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/pcgi-bin/tablebuild.pl/waas40" target="_blank"&gt;http://www.cisco.com/pcgi-bin/tablebuild.pl/waas40&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To run the WAAS disk check tool, follow these steps: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Step 1 Copy the script to your WAE device by using the copy ftp disk command. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WAE# copy ftp disk &lt;FTP-SERVER&gt; &lt;REMOTE_FILE_DIR&gt; disk_check.sh&lt;/REMOTE_FILE_DIR&gt;&lt;/FTP-SERVER&gt;&lt;/P&gt;&lt;P&gt;Step 2 Run the script from the CLI, as shown in the following example: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WAE# script execute disk_check.sh &lt;/P&gt;&lt;P&gt;This script will check if there is any file system issue on the attached disks &lt;/P&gt;&lt;P&gt;Activating the script will result in: &lt;/P&gt;&lt;P&gt;Stopping all services. This will log you out. &lt;/P&gt;&lt;P&gt;Perform file system check for few minutes. &lt;/P&gt;&lt;P&gt;and record the result in the following files: &lt;/P&gt;&lt;P&gt;/local1/disk_status.txt - result summary &lt;/P&gt;&lt;P&gt;/local1/disk_check_log.txt - detailed log &lt;/P&gt;&lt;P&gt;System reboot &lt;/P&gt;&lt;P&gt;If the system doesn't reboot in 10 minutes, please re-login and check the result files. &lt;/P&gt;&lt;P&gt;Continue?[yes/no] yes &lt;/P&gt;&lt;P&gt;Please disk_status.txt after reboot for result summary &lt;/P&gt;&lt;P&gt;umount: /state: device is busy &lt;/P&gt;&lt;P&gt;umount: /local/lPAM_unix[26162]: ### pam_unix: pam_sm_close_session (su) session closed &lt;/P&gt;&lt;P&gt;for user root &lt;/P&gt;&lt;P&gt;waitpid returns error: No child processes &lt;/P&gt;&lt;P&gt;No child alive.&lt;/P&gt;&lt;P&gt;Step 3 After the device reboots and you log in, locate and open the following two files to view the file system status: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢disk_status.txt- Lists each file system and shows if it is "OK," or if it contains an error that requires attention. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;â&amp;#128;¢disk_check_log.txt-Contains a detailed log for each file system checked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If no repair is needed, then each file system will be listed as "OK," as shown in the following example: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WAE# type disk_status.txt &lt;/P&gt;&lt;P&gt;Thu Feb 1 00:40:01 UTC 2007 &lt;/P&gt;&lt;P&gt;device /dev/md1 (/swstore) is OK &lt;/P&gt;&lt;P&gt;device /dev/md0 (/sw) is OK &lt;/P&gt;&lt;P&gt;device /dev/md2 (/state) is OK &lt;/P&gt;&lt;P&gt;device /dev/md6 (/local/local1/spool) is OK &lt;/P&gt;&lt;P&gt;device /dev/md5 (/local/local1) is OK &lt;/P&gt;&lt;P&gt;device /dev/md4 (/disk00-04) is OK&lt;/P&gt;&lt;P&gt;Step 4 If a file system contains errors, follow the instructions in the disk_status.txt file to repair the file system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/release/notes/ws4013rn.html#wp272874" target="_blank"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/release/notes/ws4013rn.html#wp272874&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;kindly send the out of the following command :&lt;/P&gt;&lt;P&gt;show disks details &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can read this section.&lt;/P&gt;&lt;P&gt;Might be it give you some relevant information regading your case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/configuration/guide/maint.html#wp1144150" target="_blank"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4013/configuration/guide/maint.html#wp1144150&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sachin garg&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 01:17:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109343#M22652</guid>
      <dc:creator>sachinga.hcl</dc:creator>
      <dc:date>2008-08-05T01:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: RAID-5 critical error</title>
      <link>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109344#M22653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply..  This is how the show disk details look..&lt;/P&gt;&lt;P&gt;ACC#sh disk det&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RAID Physical disk information:&lt;/P&gt;&lt;P&gt;  disk00: Online                 J8VU2HYC        286102 MB&lt;/P&gt;&lt;P&gt;  disk01: Online                 J8VV6E5C        286102 MB&lt;/P&gt;&lt;P&gt;  disk02: Online                 J8VU2D0C        286102 MB&lt;/P&gt;&lt;P&gt;  disk03: Online                 J8VV6EVC        286102 MB&lt;/P&gt;&lt;P&gt;  disk04: Online                 J8VU27LC        286102 MB&lt;/P&gt;&lt;P&gt;  disk05: Online                 J8VU2E1C        286102 MB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RAID Logical drive information:&lt;/P&gt;&lt;P&gt;  Drive 1:      RAID-5  Critical&lt;/P&gt;&lt;P&gt;                Enabled   (read-cache) Enabled (write-back)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mounted file systems:&lt;/P&gt;&lt;P&gt; MOUNT POINT      TYPE       DEVICE                SIZE     INUSE      FREE USE%&lt;/P&gt;&lt;P&gt; /sw              internal   /dev/sda1            991MB     615MB     376MB  62%&lt;/P&gt;&lt;P&gt; /swstore         internal   /dev/sda2            991MB     281MB     710MB  28%&lt;/P&gt;&lt;P&gt; /state           internal   /dev/sda3           7935MB     190MB    7745MB   2%&lt;/P&gt;&lt;P&gt; /local/local1    SYSFS      /dev/sda7          55548MB     953MB   54595MB   1%&lt;/P&gt;&lt;P&gt; /disk00-05       CONTENT    /dev/sda6        1289499MB 1105872MB  183627MB  85%&lt;/P&gt;&lt;P&gt; .../local1/spool PRINTSPOOL /dev/sda8            991MB      16MB     975MB   1%&lt;/P&gt;&lt;P&gt;Disk encryption feature is disabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Oddly CM GUI shows only disk00 enabled when you look at the Monitoring--&amp;gt; Disks but WAE CLI lists all the disks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We opened a TAC case on this and TAC engineer suggested , it may be due to bad disk and suggested us to replace it.  This is being one of the core data center, we have scheduled the disk replacement during the week end..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 16:04:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109344#M22653</guid>
      <dc:creator>rhegde</dc:creator>
      <dc:date>2008-08-05T16:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: RAID-5 critical error</title>
      <link>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109345#M22654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RAVEENDRA,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You want to check the output of 'sh disk tech' and see if "PFA" is set to 'Yes' for any of the drives.  If so, replace the drive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Zach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Aug 2008 03:56:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109345#M22654</guid>
      <dc:creator>Zach Seils</dc:creator>
      <dc:date>2008-08-06T03:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: RAID-5 critical error</title>
      <link>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109346#M22655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Zach,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I do 'sh disk tech' and I see all the disks but none of them are set with PFA is set to YES. I see RAID critical. But on CM GUI, I see only disk00 is enabled as shown in my attached doc.. Can you take a look ??&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;ravi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Aug 2008 15:53:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109346#M22655</guid>
      <dc:creator>rhegde</dc:creator>
      <dc:date>2008-08-06T15:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: RAID-5 critical error</title>
      <link>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109347#M22656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need to take a look at more detailed system information.  Can you please unicast me a sysreport from the device?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Zach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Aug 2008 22:16:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/raid-5-critical-error/m-p/1109347#M22656</guid>
      <dc:creator>Zach Seils</dc:creator>
      <dc:date>2008-08-11T22:16:31Z</dc:date>
    </item>
  </channel>
</rss>

