cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1096
Views
0
Helpful
6
Replies

File System Corrupted when upgrading from 6.34 to 7.01.

derekc
Level 1
Level 1

File System Corrupted when upgrading from 6.34 to 7.01.

Totally corrupted. I can't FSCK, can't format or erase. The DOWNGRADE command gives erase block error.

Now I am stucked in monitor mode with a unwriteable flash file system. Loading PIX701.bin to memory is ok but I couldn't fix up the flash file system to copy anything into it.

What can I do? Please help.

6 Replies 6

derekc
Level 1
Level 1

I am getting these error messages when copying pix701.bin:

===================================================

flashfs[7]: Checking block 14...block number was (29271)

flashfs[7]: erasing block 14...done.

flashfs[7]: Checking block 120...block number was (0)

flashfs[7]: erasing block 120...

intel_sfmm_erase_sector: erase block error

flashfs[7]: erasing block, flash handle 0x173fa08, device 0, offset 0xf40000: Operation Failed

flashfs[7]: unable to check filesystem.

flashfs[7]: Initialization complete.

Saving the configuration

Error saving configuration

Failed to save the activation key

Failed to save the firewall mode to flash

The version of image file in flash is not bootable in the current version of

software.

Use the downgrade command first to boot older version of software.

The file is being saved as image_old.bin anyway.

Error saving image_old.bin

Upgrade process complete

Need to burn loader....

Erasing sector 0...

intel_sfmm_erase_sector: erase block error[Failed]

ERROR: Unable to read firewall mode from flash

Writing default firewall mode (single) to flash

ERROR: Unable to write firewall mode to flashRunning Activation Key: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000

This activation key is not valid, use default settings only

--------------------------------------------------------------------------

. .

| |

||| |||

.|| ||. .|| ||.

.:||| | |||:..:||| | |||:.

C i s c o S y s t e m s

--------------------------------------------------------------------------

Cisco PIX Security Appliance Software Version 7.0(1)

Additional 1 interface(s) are disabled

Copyright (c) 1996-2005 by Cisco Systems, Inc.

Restricted Rights Legend

Use, duplication, or disclosure by the Government is

subject to restrictions as set forth in subparagraph

(c) of the Commercial Computer Software - Restricted

Rights clause at FAR sec. 52.227-19 and subparagraph

(c) (1) (ii) of the Rights in Technical Data and Computer

Software clause at DFARS sec. 252.227-7013.

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, California 95134-1706

open or write(ffsdev/2/write/32) failed

Could not initialize system files in flash.

************************************************************************

** **

** *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING *** **

** **

** ----> Current image running from RAM only! <---- **

** **

** When the PIX was upgraded in Monitor mode the boot image was not **

** written to Flash. Please issue "copy tftp: flash:" to load and **

** save a bootable image to Flash. Failure to do so will result in **

** a boot loop the next time the PIX is reloaded. **

** **

************************************************************************

Type help or '?' for a list of available commands.

pixfirewall>

===================================================

Tried on three PIX515/PIX515E. Same thing. Am I the only one?

And when I tried copying the pix701.bin to flash, it will give an error opening flash:/pix701.bin (Invalid argument):

=========================================

pixfirewall#

pixfirewall# copy tftp://192.168.0.100/pix701.bin flash:

Address or name of remote host [192.168.0.100]?

Source filename [pix701.bin]?

Destination filename [pix701.bin]?

Accessing tftp://192.168.0.100/pix701.bin...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Writing file flash:/pix701.bin...

%Error opening flash:/pix701.bin (Invalid argument)

pixfirewall#

bphan
Level 1
Level 1

Hi Derek:

If you can login to PIX (running in RAM), you can try 'clear flashfs' or 'flashfs downgrade' commands. This will clear the file system part of flsah memory in the PIX.

Let us know how it turns out.

Thanks,

Binh

Yes, I could load PIX701 into RAM and run it.

But the FLASHFS command is no longer available in v7.01.

I tried the new FSCK, WR MEM, and FORMAT FLASH. All indicated that flash file system is corrupted and not formattable or FSCK-able.

I am on three PIX515s. All the same.

==================================================

pixfirewall# flashfs ?

ERROR: % Unrecognized command

pixfirewall# flashfs

^

ERROR: % Invalid input detected at '^' marker.

pixfirewall#

pixfirewall# fsck flash:

Fsck operation may take a while. Continue? [confirm]

flashfs[7]: Checking block 120...block number was (0)

flashfs[7]: erasing block 120...

intel_sfmm_erase_sector: erase block error

flashfs[7]: erasing block, flash handle 0x173fa08, device 0, offset 0xf40000: Operation Failed

%Error fscking flash:: (I/O error)

WARNING: Restoring security context mode failed.

pixfirewall#

pixfirewall#

pixfirewall# wr mem

Building configuration...

Cryptochecksum: xxxx

%Error opening flash:/.private/startup-config (Invalid argument)

[OK]

pixfirewall#

pixfirewall# format flash:

WARNING: Saving activation key file failed. Proceed with operation? [confirm]

Format operation may take a while. Continue? [confirm]

Format operation will destroy all data in "flash:". Continue? [confirm]

intel_sfmm_erase_sector: erase block error

flashfs[7]: erasing block, flash handle 0x173fa08, device 0, offset 0xf40000: Operation Failed

flashfs[7]: filesystem marked down. Use "fsck" to recover.

%Error formatting flash (I/O error)

WARNING: Restoring security context mode failed.

pixfirewall#

pixfirewall#

==================================================

Derek:

My Apologies about the flashfs command. It is no longer available on 7.0 code.

Just out of curiosity, how much RAM do you have on your 515E? You want to make sure that the minimum RAM requirement stated below is met:

http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_70/pix_upgd/pixupgrd.htm#wp1032446

In the mean time,I'll continue to look into this issue.

Thanks,

Binh

128MB. Looking forward to resolving this problem.