%SYSMGR-3-CFGWRITE_SRVFAILED: Service "zone" failed to store its configurat

spcheng · ‎06-25-2008

Hi,

It is found that two MDS 9140 can't write configuration:

Here are the error:

2007 Nov 10 15:20:40 hkgsan02 %SYSTEMHEALTH-4-OHMS_SUP_BOOTFLASH_ERRORS: Bootflash test has encountered an error on module 1 Reason (13).

2007 Nov 10 15:21:40 hkgsan02 %SYSTEMHEALTH-4-OHMS_SUP_BOOTFLASH_ERRORS: Bootflash test has encountered an error on module 1 Reason (12).

2007 Nov 10 15:21:45 hkgsan02 %SYSTEMHEALTH-4-OHMS_SUP_BOOTFLASH_ERRORS: Bootflash test has encountered an error on module 1 Reason (12).

2007 Nov 10 15:21:45 hkgsan02 %KERN-3-SYSTEM_MSG: Aborting journal on device ide1(22,3).

2007 Nov 10 15:21:51 hkgsan02 %KERN-2-SYSTEM_MSG: ext3_abort called.

2007 Nov 10 15:21:51 hkgsan02 %KERN-2-SYSTEM_MSG: EXT3-fs abort (device ide1(22,3)): ext3_journal_start: Detected aborted journal

2007 Nov 10 15:21:51 hkgsan02 %KERN-2-SYSTEM_MSG: Remounting filesystem read-only

2008 Jun 24 21:15:37 hkgsan02 %PSS-0-PSS_WRITE_LOG_FAILURE: zone: failed to write log: Read-only file system

2008 Jun 24 21:15:37 hkgsan02 %KERN-2-SYSTEM_MSG: EXT3-fs error (device ide1(22,3)) in start_transaction: Journal has aborted

2008 Jun 24 21:15:39 hkgsan02 snmpd: SNMPD_SYSLOG_CONFIG_I: Configuration update from 1952_10.152.88.135 user/community name : admin

2008 Jun 24 21:15:40 hkgsan02 %ZONE-2-ZS_INIT_FAILED: Failed to save persistent configuration

2008 Jun 24 21:15:40 hkgsan02 %ZONE-2-ZS_INIT_FAILED: pss_create failure, code = 0x80480011, URL = sync:/mnt/pss/zone_zs_active_zset_cfg

2008 Jun 24 21:15:40 hkgsan02 %SYSMGR-3-CFGWRITE_SRVFAILED: Service "zone" failed to store its configuration (error-id 0xFFFFFFFF).

2008 Jun 24 21:15:41 hkgsan02 %SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.

2008 Jun 24 21:15:41 hkgsan02 %SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id 0x401E0000).

2008 Jun 24 21:15:46 hkgsan02 snmpd: SNMPD_SYSLOG_CONFIG_I: Configuration update from 1952_10.152.88.135 user/community name : admin

The problem seems to be caused by bootflash. Is there anyway to fix it?

Thanks.

Rgds,

Ivan Cheng

`show version`

Cisco Storage Area Networking Operating System (SAN-OS) Software

TAC support: http://www.cisco.com/tac

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software may be covered under the GNU Public

License or the GNU Lesser General Public License. A copy of

each such license is available at

http://www.gnu.org/licenses/gpl.html and

http://www.gnu.org/licenses/lgpl.html

Software

BIOS: version 1.1.0

loader: version unavailable [last: 1.2(2)]

kickstart: version 3.1(3a)

system: version 3.1(3a)

BIOS compile time: 10/24/03

kickstart image file is: bootflash:/m9100-s1ek9-kickstart-mz.3.1.3a.bin

kickstart compile time: 5/22/2007 17:00:00 [06/17/2007 00:22:16]

system image file is: bootflash:/m9100-s1ek9-mz.3.1.3a.bin

system compile time: 5/22/2007 17:00:00 [06/17/2007 00:38:13]

Gary Ross · ‎06-26-2008

I ran into something like this back in SAN-OS 1.2.x. Please do a SHOW CORES from the CLI on the switch. Thanks.

Gary

dmcloon · ‎06-27-2008

Bad bootflash on module 1 causing it to enter a read only state. Replace module 1 is your best option. Reload of module 1 is only a short term workaround.