(Read-only file system) ,EXT3-fs error (device sda6) in start_transaction, FOR MY MCS7825I3-K9-CMC1

[mohd355355]

I got this problem for my cucm version System version: 7.0.2.20000-5

Product Part Number: MCS7825I3-K9-CMC1

java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)

log4j:ERROR No output stream or file set for the appender named [CLI_LOG].

EXT3-fs error (device sda6) in start_transaction: Journal has aborted   SeverityMatch - Critical kernel: EXT3-fs error (device sda6) in start_transaction: Journal has aborted   SeverityMatch - Critical kernel: EXT3-fs error (device sda6) in

Any Advice to solve this issue ?

Kind Regards

Mohammed khamis

java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)
        at java.io.RandomAccessFile.open(Native Method)
        at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.restoreIndex(c                                                                            iscoRollingFileAppender.java:100)
        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.setFile(ciscoR                                                                            ollingFileAppender.java:43)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.                                                                            java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces                                                                            sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.jav                                                                            a:196)
        at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.jav                                                                            a:155)
        at org.apache.log4j.xml.DOMConfigurator.setParameter(DOMConfigurator.jav                                                                            a:530)
        at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.ja                                                                            va:182)
        at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurat                                                                            or.java:140)
        at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfi                                                                            gurator.java:153)
        at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOM                                                                            Configurator.java:415)
        at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:3                                                                            84)
        at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
        at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java                                                                            :666)
        at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java                                                                            :616)
        at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java                                                                            :584)
        at org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:6                                                                            87)
        at sdMain.main(sdMain.java:511)
java.lang.NullPointerException
        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.updateIndex(ci                                                                            scoRollingFileAppender.java:117)
        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.nextFileName(c                                                                            iscoRollingFileAppender.java:92)
        at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.append(ciscoRo                                                                            llingFileAppender.java:74)
        at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
        at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders                                                                            (AppenderAttachableImpl.java:57)
        at org.apache.log4j.Category.callAppenders(Category.java:187)
        at org.apache.log4j.Category.forcedLog(Category.java:372)
        at org.apache.log4j.Category.info(Category.java:674)
        at sdMain.main(sdMain.java:525)
log4j:ERROR No output stream or file set for the appender named [CLI_LOG].

   Welcome to the Platform Command Line Interface

admin:java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only f                                                                            ile system):java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only f                                                                            ile system)

[Manish Gogna]

Hi,

You can use the recovery disk to correct the file system errors. If you don't have the disk, you can download it from the following link and burn it on a dvd

https://software.cisco.com/download/release.html?mdfid=281941895&flowid=45893&softwareid=282074294&release=7.0%282%29&relind=AVAILABLE&rellifecycle=&reltype=latest

If this is not fixed by recovery disk, a reinstall might be required.

HTH

Manish

[mohd355355]

Hello

Thanks Manish .

I found many articles in cisco which says that this error is related to the bug which need firmware upgrade , but I don't have support from cisco because EOS.

https://supportforums.cisco.com/document/49511/updated-16-february-2011-ibm-7816-i4-782x-i4-filesystem-errors

Solution

The file-system going read-only issue which has recently been affecting server models MCS-7816-I4, MCS-7825-I4, and MCS-7828-I4 (or their IBM equivilants) in the field is addressed by CSCti52867 - "IBM 7816-I4 and 782x-I4 READONLY file system".

The fix for CSCti52867 is now available and requires the application of two patch files.  Install both of these patch files in the order listed below.

1. First install ciscocm.ibm-diskex-1.0.cop.sgn 
     The Readme file ciscocm.ibm-diskex-1.0.cop.sgn includes installation instructions for this .cop.sgn.

     Make sure to only install this utility when show hardware CLI output indicates the array is in a healthy state.

     If your server has never had the filesystem go readonly then this step is optional. 
2. Next install Cisco-HDD-FWUpdate-3.0.1-I.ISO .
     The Readme file Cisco-HDD-FWUpdate-3.0.1-I.Readme.pdf includes installation instructions for this ISO.

     This installer is completely independant of the OS installed on the server.

Note:  Installing the FWUpdate v3.0(1) or later will get you firmware with the fix for this defect.  It is always recommended that you apply the latest FWUCD available for your server.

Refer to the Release Note of CSCti52867 and the Readme file for each of the above mentioned patch files for more details.

Symptoms

• The file system goes READONLY, then CUCM services may go down, the server may become "unresponsive" meaning that it is not possible to ssh into the server, login to the console, or web into the server although it may still respond to pings.
• Traces from all services stop writing (including syslog)
• You see the following error on the server console

EXT3-fs error (device sda6) in start_transaction: Jornal has aborted

[Manish Gogna · Accepted solution]

Hi,

The workaround and the complete fix involves using the recovery disk as well as mentioned in the bug:

1. Reboot the server via CLI if you can, otherwise power-cycle the server by
holding down the power button for 5 seconds or more.
2. Boot from a CUCM recovery disk and selection option f to perform a
filesystem check. If it finds errors then a reinstall and restore from backup
may be the only way to recover completely.
3. Apply Disk exerciser utility to clear any existing file system
issues(ciscocm.ibm-diskex-1.0.cop.sgn ):

http://software.cisco.com/download/release.html?mdfid=282152197&softwareid=283046743&release=3.0%281%29

4. Apply Cisco FW update CD (Cisco-HDD-FWUpdate-3.0.1-I.ISO):

http://software.cisco.com/download/release.html?mdfid=282152197&softwareid=283046743&release=3.0%281%29
 

You can try using the recovery disk first to see if it helps and regarding the end of support issue you should contact your Cisco Account team or Customer services.

HTH

Manish