×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

ASA file system is read only (SOLVED)

Unanswered Question
Apr 29th, 2014
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

I am working on a customer ASA5525X and have run into a very strange situation. I am able to go into config mode and to make changes. But when I try to save to startup config I get an error message that it failed because the file system is read only. I also get a similar message about file system is read only if I attempt to copy new code to disk0.

 

Has anyone had symptoms like this for an ASA? Anyone have suggestions what to do about it? Current version is 9.1(1).

 

HTH

 

Rick

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Marvin Rhoads Tue, 04/29/2014 - 10:34
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 Firewalling, Network Management, VPN

Hi Rick,

I have seen the ASA report file system errors when trying to upgrade 9.1(1) directly to 9.1(3). The release notes do note that you have to go up to 9.1(2) first. When you go that path, the error doesn't manifest.

I've not seen that issue when doing a simple configuration change though.

johnlloyd_13 Wed, 04/30/2014 - 09:28
User Badges:
  • Blue, 1500 points or more
Hi Rick, We have a 5525-X but never had this problem. It could be some RADIUS or TACACS+ issue? Try 'copy run disk0:'
Richard Burts Sat, 06/14/2014 - 10:05
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

It has taken longer than I expected but we have resolved the issue and I want to report back on this. It turns out that the error reporting that the file system is read only was caused by errors on the disk. I did open a case with TAC who diagnosed it as disk errors. Their first suggestion was to format the disk. We did that and then had to restore the entire content of the disk (no surprise there). It provided temporary relief. It did allow us to save the config, and to upgrade code (now running 9.1(5)). But pretty soon the problem came back. So TAC generated an RMA. We swapped out the original ASA last Thursday and it looks like our problem is resolved.

 

HTH

 

Rick

Marvin Rhoads Sat, 06/14/2014 - 11:33
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 Firewalling, Network Management, VPN

Thanks for letting us know the final resolution, Rick.

Another data point in the universe of odd ASA behavior is always good to have. :)

mahesh18 Sat, 06/14/2014 - 17:41
User Badges:

 

Thanks for updating us Rick

Regards

MAhesh

Actions

This Discussion