Error Opening Disk0 /.private/startup-config No Such File Or Directory
Contents |
ASA 5500-X Series FirewallsTroubleshoot and AlertsTroubleshooting TechNotes ASA 8.x: Troubleshooting ASA Flash Errors Download Print Available Languages Download
%error Copying System:/running-config (not Enough Space On Device)
Options PDF (13.1 KB) View with Adobe Reader on a variety fsck disk0 of devices Updated:Jan 31, 2012 Contents Introduction Prerequisites Requirements Components Used Conventions Background Information Mitigate Cisco ASA
%error Opening Disk0:/.private/startup-config (no More Processes)
Flash Corruption Issues Run the "fsck" utility Format the Flash Replace the flash card manually Error Messages Useful FAQ Can I hot-swap the flash drive? For example, cisco asa delete file from disk0 is it possible to change the flash drive when Cisco ASA is powered ON and running? Can I use third party flash drives on Cisco ASA? What do I do if I accidentally erase flash by mistake? Does formatting the flash affect the running connections on Cisco ASA? Can I use external flash as internal flash? cisco asa rommon show flash Related Information Introduction This document describes different possible errors that occur because of the Cisco ASA flash corruption and also points the possible solutions. Prerequisites Requirements There are no specific requirements for this document. Components Used The information in this document is based on these software and hardware versions: Cisco ASA 5500 series with software version 8.0 and later The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Background Information Cisco ASA maintains its filesystem in an internal flash memory and stores all the files in flash memory. This is a memory card inserted into a slot in the ASA. The capacity of this depends on the ASA hardware model. Refer to the Technical Spe
2012 Posted in: Uncategorized. Tagged: ASA, Cisco, firewall, GNS3. 4 Comments If you use Cisco ASA in GNS3, you’ll be notice that “wr mem”
%error Opening Disk0:/.private/startup-config (too Many Open Files)
command can’t be used to save a configuration. The following error message cisco asa too many open files occurs once you run “wr mem”. ciscoasa# wr mem Building configuration… Cryptochecksum: 6e33e06b 255d8b92 90c27d70 9f5b4de4 %Error
%error Show Flash: (no Such Device)
opening disk0:/.private/startup-config (No such file or directory) Error executing command [FAILED] ciscoasa# SOLUTION Instead of using “wr mem”, use the following command to save your configuration to Cisco http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/113266-asa-flash-error-ts.html ASA in GNS3. copy run disk0:/.private/startup-config ciscoasa(config)# copy run disk0:/.private/startup-config Source filename [running-config]? Destination filename [/.private/startup-config]? %Warning:There is a file already existing with this name Do you want to over write? [confirm] Cryptochecksum: 6e33e06b 255d8b92 90c27d70 9f5b4de4 1471 bytes copied in 2.20 secs (735 bytes/sec)open(ffsdev/2/write/41) failed open(ffsdev/2/write/40) failed ciscoasa(config)# Share this:TwitterFacebookLike this:Like Loading... Related Posts navigation ← Check https://firewallengineer.wordpress.com/2012/05/05/solved-how-to-save-configuration-cisco-asa-in-gns3/ Point books How to “wr mem” Cisco ASA inGNS3? → 4 comments on “[solved] How to save configuration Cisco ASA inGNS3?” Pingback: How to “wr mem” Cisco ASA in GNS3? | Firewall Engineer Gaius on December 16, 2012 at 11:48 pm said: ASA1# copy run disk0:/.private/startup-config Source filename [running-config]? Destination filename [/.private/startup-config]? %Warning:There is a file already existing with this name Do you want to over write? [confirm] Cryptochecksum: d727dda0 d36c9e3b 8134252c 442be728 %Error opening disk0:/.private/startup-config (No such file or directory) Reply Malik on July 3, 2013 at 2:46 pm said: ciscoasa(config)# copy run disk0:/.private/startup-config Source filename [running-config]? Destination filename [/.private/startup-config]? %Warning:There is a file already existing with this name Do you want to over write? [confirm] Cryptochecksum: ee705876 919667d5 d6fd3cd9 b0f1bcda %Error opening disk0:/.private/startup-config (No such file or directory) any solution ? Reply StanleySaf on September 11, 2013 at 12:08 pm said: I use this command on all my cisco: ASA1# copy run startup-config Source filename [running-config]? Destination filename [startup-config]? Cryptochecksum: d727dda0 d36c9e3b 8134252c 442be728 1248 bytes copied i
List CCNP/CCIE Security Book List ACI Design Books VMware Arista Linux Self Improvement Google Docs List Links About Us\Contact Us Cisco ASA %Error opening disk0:/ (too many open http://www.nycnetworkers.com/self-improvement/cisco-asa-error-opening-disk0-many-open-files/ files) by William Zambrano | Sep 10, 2014 | Bugs, Real World, Security, Self Improvement | 0 comments Ran into a strange issue today with a pair of Cisco ASA 5525x series routers. The FW are configured in a A/S setup, and we ran into a bug that required us to upgrade the code. Problem was, one of the ASAs in the pair didn't error opening even let me get to the disk0 via #dr while the other ASA constantly failed to upload the image via FTP. FW01/pri/act# dir Directory of disk0:/ %Error opening disk0:/ (Too many open files) 8238202880 bytes total (4793798656 bytes free) Googling around I found a few articles stating that the flash of the ASA could of gone bad and one could try to reformat the error opening disk0 flash. http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/113266-asa-flash-error-ts.html Not a good look when the ASA is in ANOTHER country in a datacenter with NO ONE around! Trying other commands to get to the flash/disk resulted in similar outputs FW01/pri/act# show flash: filesys %Error show flash: (No such device) FW01/pri/act# show flash: all %Error show flash: (No such device) FW01/pri/act# show disk0: all %Error show disk0: (No such device) FW01/pri/act# show disk0: controller %Error show disk0: (No such device) So to me it looks like the whole ASA is running off RAM! Real bad! I could either risk loosing the config and rebooting the box or hoping it'll clear out the disk issue once it reboots and it comes back online working OK. I also couldnt upload a new .bin file to the disk0 of the device, seeing how the ASA itself couldn't even see it! Aftering attempting to run the checkdisk, it all showed failed. FW01/sec/act# fsck disk0: fsck of disk0: complete WARNING: Restoring security context mode failed. WARNING: Restoring cluster interface mode failed. Looked to me like rebooting this guy would cause an RMA call to TAC. And sure enough -- it did. Turns out