WAVE-574 Rescue CDROM

Answered Question
Aug 30th, 2010

Hi, we have a wave 574-k9 and we need to run the rescue cdrom to clean the database and upgrade the software to the version 4.1.5.a4

We download the ISO image from the web, and make the dvd. We put on the server and reload, all like the manual said!!!

We run all step, first #2 to format the Flash, then #3 to copy the cookie, then #5 to copy de sysimg from the cdrom, and then #8 to copy the image (.img) to local disk.

But we have a problem when run the step 8, the message said:

   MODEL: OE574
   FLASH: found, directory validated
  COOKIE: valid
   IMAGE: 4.1.5a.4
FLASHDEV: /dev/sdb

Installer Main Menu:
    1. Configure Network
    2. Manufacture flash
    3. Install flash cookie
    4. Install flash image from network
    5. Install flash image from cdrom
    6. Install flash image from disk
    7. Recreate RAID device (WAE-674/7341/7371 only)
    8. Wipe out disks and install .bin image
    9. Exit (Eject and reboot)
Choice [0]: 8
Enter full URL of .bin image to install.
   ftp://[user:pass@]ip_addr/path/to/file
  http://[user:pass@]ip_addr/path/to/file
  file:/local/path/to/to/file
URL for .bin image [file:/cdrom/images/WAAS41.bin]:
Continue?  This will wipe out all disks! [n]: y
Scrogging sda done
Saving random seed...
dd: opening `/state/random-seed': No such file or directory
  No volume groups found
Missing system-use partitions; creating them on disk00
+ /sbin/sfdisk -f -uS /dev/sda
Found No SYSFS partition on /dev/sda, create it now.
Disk disk00: removing old disk partitions ...
Disk disk00: applying new partitioning scheme ...
single disk in mirror: (device disk00) is /dev/sda; disk mirror status: OFF
mdadm: cannot access superblock on /dev/sda1.
mdadm: cannot access superblock on /dev/sda2.
mdadm: cannot access superblock on /dev/sda3.
mdadm: cannot access superblock on /dev/sda5.
mdadm: cannot access superblock on /dev/sda6.
mdadm: cannot access superblock on /dev/sda7.
Creating filesystem on device [/dev/md0]...
/ruby/bin/ruby_disk: Formatting /dev/md0 failed. (1,1)
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md0
command /sbin/e2fsck  -y /dev/md0 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md0 (1,8)
e2fsck_device(/dev/md0) returns 2048
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md0
command /sbin/e2fsck  -y /dev/md0 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md0 (1,8)
disk00/00 (SYSTEM USE) is being recovered. All data on this partition is lost.
You may need to re-install software.
Creating filesystem on device [/dev/md0]...
/ruby/bin/ruby_disk: Formatting /dev/md0 failed. (1,1)
fsck_ext2_partition(/dev/md0) returns -1
Creating filesystem on device [/dev/md1]...
/ruby/bin/ruby_disk: Formatting /dev/md1 failed. (1,1)
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md1
command /sbin/e2fsck  -y /dev/md1 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md1 (1,8)
e2fsck_device(/dev/md1) returns 2048
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md1
command /sbin/e2fsck  -y /dev/md1 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md1 (1,8)
disk00/01 (SYSTEM USE) is being recovered. All data on this partition is lost.
You may need to re-install software.
Creating filesystem on device [/dev/md1]...
/ruby/bin/ruby_disk: Formatting /dev/md1 failed. (1,1)
fsck_ext2_partition(/dev/md1) returns -1
Creating filesystem on device [/dev/md2]...
/ruby/bin/ruby_disk: Formatting /dev/md2 failed. (1,1)
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md2
command /sbin/e2fsck  -y /dev/md2 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md2 (1,8)
e2fsck_device(/dev/md2) returns 2048
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md2
command /sbin/e2fsck  -y /dev/md2 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md2 (1,8)
disk00/02 (SYSTEM USE) is being recovered. All data on this partition is lost.
You may need to re-install software.
Creating filesystem on device [/dev/md2]...
/ruby/bin/ruby_disk: Formatting /dev/md2 failed. (1,1)
fsck_ext2_partition(/dev/md2) returns -1
Creating filesystem on device [/dev/md4]...
/ruby/bin/ruby_disk: Formatting /dev/md4 failed. (1,1)
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md4
command /sbin/e2fsck  -y /dev/md4 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md4 (1,8)
e2fsck_device(/dev/md4) returns 2048
e2fsck 1.38 (30-Jun-2005)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md4
command /sbin/e2fsck  -y /dev/md4 2>&1 >> /tmp/ruby_disk_debug.txt returns 2048
Can't clean file system /dev/md4 (1,8)
disk00/04 (SYSFS) is being recovered. All data on this partition is lost.
Creating filesystem on device [/dev/md4]...
/ruby/bin/ruby_disk: Formatting /dev/md4 failed. (1,1)
fsck_ext2_partition(/dev/md4) returns -1
Can't detect device mode: No such file or directory
Assume it's CE (default mode).
Can't detect device mode: No such file or directory
Assume it's CE (default mode).
Can't detect device mode: No such file or directory
Assume it's CE (default mode).
Creating filesystem on device [/dev/data1/vbsp]...
/ruby/bin/ruby_disk: Formatting /dev/data1/vbsp failed. (1,1)
ruby_disk: write signature: write device failed: /dev/sda: Connection refused
touch: creating `/state/disk_init_now': No such file or directory
No prior RAID level set; saving RAID-1
ruby_disk: check io: read: Connection refused
disk00 is bad. Check cable or replace it.
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_open or media_open
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_create or media_init
SSMGR RETURNING: 10 (No such file or directory)
Reading and installing image, it may take a few minutes, please wait...
remote size / mtime: 440836082 / 1254534290
swstore not mounted
Reclaiming unused flash safe state sectors ... Done.

System should be running properly before upgrade begins.
It seems system software was not correctly installed on
this device. Please, reload the device and retry the software install.
Upgrade failed.


73728 bytes transferred in 2.5 seconds (29.23 kBps)

fetch: -: Inappropriate ioctl for device
Error, image NOT installed.

Someone help me??

Thank you in advance

Juan

I have this problem too.
0 votes
Correct Answer by Bhavin Yadav about 6 years 3 months ago

Well, you probably want to look at the LED status on disks. if you do not see any LEDs blinking on disks, this will be a bad hardware case and will need to be RMA'ed.

If you do see the LEDs blinking, then you can use recovery CD to install WAAS image.

As you are using WAVE 574 appliance, please do not use 64 bit image. The 64 bit images can be downloaded from CCO and are meant only for 674/7341 and 7371 for reimaging the flash.

Please look at the relase notes for more details on which image to use and how to download them.

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v423/release/notes/ws423xrn.html#wp96756

Hope this helps.

Regards.

PS: Please mark this Answered if this answers your question.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Bhavin Yadav Mon, 08/30/2010 - 11:53

Hi Juan,

Look like it is either disk issue or raid controller issue. Try booting unit threu flash (it will boot thru flash automatically if disk do not have boot image). once at the login prompt, get the output of : show disk details and show disk tech

This output will tell us if we there is a disk / raid controller failure.

One more thing: Do you see any blinking LEDs / disk alarm raised in the front panel of unit?

Regards.

jgranata Mon, 08/30/2010 - 12:08

Here is the output

NO-HOSTNAME#sh disk detail

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.
NO-HOSTNAME#

NO-HOSTNAME#sh disk tech 
=== disk00 ===
disk00: Not present or not responding
=== disk01 ===
disk01: Not present or not responding
NO-HOSTNAME#

And we have only one disk (Disk00) with the led off, and we don´t see any alarms.

Thank you

Juan

Bhavin Yadav Mon, 08/30/2010 - 12:36

This means that WAE is not able to identify any disks inside the unit.

Few thigns you can do yourself:

1. Try re-seating the disk inside the bay.

2. Try re-seating the disk in a different bay.

If you still do not see any LEDs, you may want to open a TAC case and RMA the disk or unit.

Hope this helps.

Regards.

PS: If this resovles your issue, please mark it as Answered.

jgranata Tue, 08/31/2010 - 09:44

Hi,

We did all you suggested but don´t works.

I have another question, in some paper said:

"The system image used depends on your device. For WAVE-274/474/574 and WAE-674/7341/7371 devices (64-bit platforms), use the system image named WAAS-4.x.x.x-K9.x86_64.sysimg. For all other devices, use the system image named WAAS-4.x.x.x-K9.sysimg."

We trying to download this image ("WAAS-4.x.x.x-K9.x86_64.sysimg") but we can´t  found it... could you help me to understand if it´s correct and where we can find it??

Thank you

Juan

Correct Answer
Bhavin Yadav Tue, 08/31/2010 - 12:42

Well, you probably want to look at the LED status on disks. if you do not see any LEDs blinking on disks, this will be a bad hardware case and will need to be RMA'ed.

If you do see the LEDs blinking, then you can use recovery CD to install WAAS image.

As you are using WAVE 574 appliance, please do not use 64 bit image. The 64 bit images can be downloaded from CCO and are meant only for 674/7341 and 7371 for reimaging the flash.

Please look at the relase notes for more details on which image to use and how to download them.

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v423/release/notes/ws423xrn.html#wp96756

Hope this helps.

Regards.

PS: Please mark this Answered if this answers your question.

Actions

This Discussion