WAAS Upgraded Failed - Disk Based Software not Installed

Unanswered Question
May 21st, 2010

Greetings,

We have upgraded several WAE-7341 devices from 4.1.3a to 4.1.5f, however the last upgrade failed. When we log into the device we get the error message stating "Disk based software not installe". Has anyone run into this?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Zach Seils Fri, 05/21/2010 - 10:21

WAAS has both disk-based and flash-based software components.  For some reason, your upgrade failed on this device.  You'll need to go through the upgrade process again.

Regards,

Zach

j.shrewsbury Fri, 05/21/2010 - 10:30

Zach,

Do you know if just repeating the upgrade process will work, or do we need to use the recovery CD? Also, do you happen to know if going from 4.1.3a to 4.1.5f directly is supported? We were informed that a direct upgrade was possible, but are now being told that we should go to 4.1.3b first.

Thanks for your response!

Zach Seils Fri, 05/21/2010 - 10:36

You can just try again with installing from the binary image.  Upgrading directly from 4.1.3 a or b to 4.1.5f is fine.

Regards,

Zach

j.shrewsbury Mon, 05/24/2010 - 10:48

Unfortunately, it does not look like we can reload the image from the CM. The device is not talking to the CM and shows offline in the GUI. Any ideas as to how this could have happened? It looks like we are going to have to rebuild the machine from disk. Any thoughts as to what could have happened? We uploaded 4 other devices successfully.

Zach Seils Mon, 05/24/2010 - 11:10

Do you have IP connectivity to the device?  If so, you can try upgrading again from the CLI using the command copy [http | ftp] install ... .

In terms of what originally happened, it's possible that there was some corruption during the initial transfer of the image to the WAAS device.

Zach

dhanasekaran.r Mon, 05/24/2010 - 12:18

Hi Zach,

I also hit on the same problem . I tried to grep thru the syslog and i got message stating bad disk "thbkwa1.kcc.com 2010 May 22 13: kernel: %WAAS-SYS-2-900000: SCSI I/O error: POSSIBLE BAD DISK -- device 0x800, sector 412882768"

When i do sh disk de ,, i see an error "RAID Logical drive information:
  Drive 1:      RAID-5  Okay       (Hard Disk controller's problem is reported)"

Does that mean the disk failed or possible bad image?

Zach Seils Tue, 05/25/2010 - 07:28

Can you please provide the output of the command show disks tech-support?

Thanks,

Zach

dhanasekaran.r Tue, 05/25/2010 - 07:44

Please find the output of the Sh disk tech ::

Controllers found: 1

----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
   Controller Status                   : Okay
   Channel description                 : SAS/SATA
   Controller Model                    : IBM ServeRAID 8k   
   Controller Serial Number            : 1BCD0520
   Physical Slot                       : 0
   Installed memory                    : 256 MB
   Copyback                            : Disabled
   Data scrubbing                      : Disabled
   Defunct disk drive count            : 0
   Logical drives/Offline/Critical     : 1/0/0
   ---------------------------------------------------
   Controller Version Information
   ---------------------------------------------------
   BIOS                                : 5.2-0 (15427)
   Firmware                            : 5.2-0 (15427)
   Driver                              : 1.1-5 (24495)
   Boot Flash                          : 5.1-0 (15411)
   ---------------------------------------------------
   Controller Battery Information
   ---------------------------------------------------
   Status                              : Okay
   Over temperature                    : No
   Capacity remaining                  : 100 percent
   Time remaining (at current draw)    : 4 days, 20 hours, 40 minutes
   ---------------------------------------------------
   Controller Vital Product Data
   ---------------------------------------------------
   VPD Assigned#                       : 39R8875
   EC Version#                         : J85096
   Controller FRU#                     : 25R8076
   Battery FRU#                        : 25R8088

----------------------------------------------------------------------
Logical drive information
----------------------------------------------------------------------
Logical drive number 1
   Logical drive name                  : Drive 1
   RAID level                          : 5
   Status of logical drive             : Okay
   Size                                : 572000 MB
   Read-cache mode                     : Enabled
   Write-cache mode                    : Enabled (write-back)
   Write-cache setting                 : Enabled (write-back) when protected by battery
   Partitioned                         : Yes
   Number of chunks                    : 3
   Stripe-unit size                    : 256 KB
   Stripe order (Channel,Device)       : 0,0 0,1 0,2
   Bad stripes                         : No

----------------------------------------------------------------------
Physical Device information
----------------------------------------------------------------------
      Device #0
         Device is a Hard drive
         State                         : Online
         Supported                     : Yes
         Transfer Speed                : SAS 3.0 Gb/s
         Reported Channel,Device       : 0,0
         Vendor                        : IBM-ESXS
         Model                         : MBA3300RC
         Firmware                      : SA06
         Serial number                 : BJ505FRA
         World-wide name               : 500000E112A685F1
         Size                          : 286102 MB
         Write Cache                   : Disabled (write-through)
         FRU                           : 43X0817
         PFA                           : No
      Device #1
         Device is a Hard drive
         State                         : Online
         Supported                     : Yes
         Transfer Speed                : SAS 3.0 Gb/s
         Reported Channel,Device       : 0,1
         Vendor                        : IBM-ESXS
         Model                         : MBA3300RC
         Firmware                      : SA05
         Serial number                 : BJ503WBK
         World-wide name               : 500000E01EADE411
         Size                          : 286102 MB
         Write Cache                   : Disabled (write-through)
         FRU                           : 43X0817
         PFA                           : No
      Device #2
         Device is a Hard drive
         State                         : Online
         Supported                     : Yes
         Transfer Speed                : SAS 3.0 Gb/s
         Reported Channel,Device       : 0,2
         Vendor                        : IBM-ESXS
         Model                         : ST3300656SS
         Firmware                      : BA49
         Serial number                 : 3QP2BJPG
         World-wide name               : 5000C50016A3FB68
         Size                          : 286102 MB
         Write Cache                   : Disabled (write-through)
         FRU                           : 43X0805
         PFA                           : No
      Device #3
         Device is an Enclosure
            Reported Channel,Device    : 2,0
            Type                       : SES2
            Vendor                     : IBM-ESXS
            Model                      : VSC7160
            Firmware                   : 1.07
         Status of Enclosure
            Temperature status         : Normal


Command completed successfully.

Zach Seils Tue, 05/25/2010 - 09:07

It would be really helpful to see a sysreport from this device.  Can you try to generate one and upload it?

Thanks,

Zach

dhanasekaran.r Tue, 05/25/2010 - 09:14

Hi Zach,

The device is not able to create sysreport. Its throwing error

Generating sysreport ...
mkdir: cannot create directory `/local/local1/sysreport.26264': No such file or directory
Could not generate sysreport in location /local/local1/thbkdisk.tar.gz
Could not generate sysreport. status(1.1)

Zach Seils Tue, 05/25/2010 - 10:28

Ok ... so none of the partitions are mounted.  Let's try recreating the RAID array before you replace the device.  From the CLI, execute the following commands:

    (config)#disk logical shutdown
    reload
    disk recreate-raid
    (config)#no disk logical shutdown
    reload

Regards,

Zach

dhanasekaran.r Wed, 05/26/2010 - 03:32

Hi Zach,

Is there any such commands for 574. I have the same issue disk based software not installed in 574.

Zach Seils Wed, 05/26/2010 - 05:58

The 574 uses a different type of disk subsystem.  Can you provide the sh disk det and sh disk tech output?

Thanks,

Zach

dhanasekaran.r Wed, 05/26/2010 - 06:46

No directory /local/local1/./!
Logging in with home = "/".
System Initialization Finished.
Disk based software not installed.
Some applications may not run correctly!
574wa1#sh disk details

Physical disk information:
  disk00: Not present or not responding
  disk01: Not present or not responding

Mounted file systems:
MOUNT POINT      TYPE       DEVICE                SIZE     INUSE      FREE USE%

No RAID devices present.

Disk encryption feature is disabled.
574wa1#sh disk tech   
=== disk00 ===
disk00: Not present or not responding
=== disk01 ===
disk01: Not present or not responding
cnhkwa1#

Zach Seils Thu, 05/27/2010 - 06:35

You can try the following, although it may fail:

(config)# disk disk disk00 shut

(config)# no disk disk disk00 shut

If this fails (which is very well may), I would suggest having he device replaced.

Regards,

Zach

edwardwaithaka Tue, 12/02/2014 - 08:58

Hi Zach,

I have the same issue on a WAVE 594 running 4.4.5. Any commands I can use to recover the appliance?

sureka111 Thu, 09/08/2016 - 17:22

For my case, we had disk replacement after that disks are online but not mounted.

It has the same error.

System Initialization Finished.
Disk based software not installed.
Some applications may not run correctly!

unable to sync CMS due to ...../sw/merlot/bin/spen: No such file or directory

could you suggest commands to recover the file system.

j.shrewsbury Wed, 05/26/2010 - 10:38

Zach, I thought I would put this out there with all the details this time just in case there is something we missed.

We upgraded one of our 7341 core waas devices (after successfully upgrading 4 other non-core devices) from 4.1.3b to 4.1.5f. The core devices were configured for load balancing. One of the four non-core devices that we upgraded successfully was also 7341.

The process we followed was:

1. "no wccp version 2"

2. "show statistics connection" - to verify all connections moved off of this device and failed over to the other device

3. Went to CM and enabled CIFS through GUI - This was due to the fact CIFS was disabled because of MS bug. If we enabled it after the reboot, we would of had to reboot again to clear the CM alarm that gets generated when enabling a service.

4. "show accelerators" to verify CIFS went from shutdown to running.

5. "reload"

6. logged back in and did "show disk details" - noticed all disks were ok and volumes mounted.

7. "show accelerators" - This is when we noticed the services were shutdown.

8. ran "dir" command and noticed that some software that is on all other waas devices were missing, e.g. "actona" directory.

I am told that we are going to have to reload from scratch rather than just reinstall the image because there appears to be missing software.

I guess I would like to see if there is anything wrong with the process we followed to upgrade this device, and second verify if the files missing actually mean that we need to rebuild from CD. I am including the disk details, show accelerators, and dir output in the attached txt file for both the work and non working devices.

Thanks for all of your help!

Zach Seils Thu, 05/27/2010 - 06:57

On the surface I don't see an issue with the way you upgraded the device.  Can you send me a system report from the device that had the problems with the upgrade?

Thanks,

Zach

Actions

This Discussion