07-16-2025 07:44 AM
Cisco 4321 ISR running Cisco IOS XE Software, Version 03.16.01a.S - Extended Support Release
On boot I get this error
%FLASH_CHECK-3-DISK_QUOTA: Flash disk quota exceeded [free space is 1495100 kB] - Please clean up files on bootflash.
So i thought i would try to clean up the drive. When trying request platform software package clean I get this error.
Cleaning up unnecessary package files
No path specified, will use booted path consolidated:packages.conf
Cleaning sw/isos
Scanning boot directory for packages ... done.
Preparing packages list to delete ...
mkdir: cannot create directory `.CLEANUP_IN_PROGRESS': Read-only file system
FAILED: Failed to create directory .CLEANUP_IN_PROGRESS
Can someone help me with this?
07-16-2025 08:39 AM
It looks like you're facing two separate issues:
Flash Disk Quota Exceeded: Your Cisco ISR 4321 has exceeded its flash disk quota during boot, which is preventing further operations from being performed due to a lack of free space.
Read-Only File System: The command request platform software package clean is failing because it cannot create the required temporary directory (.CLEANUP_IN_PROGRESS) due to the file system being mounted as read-only.
Let's address both issues step-by-step:
1. Resolving the Flash Disk Quota Exceeded Issue
The error message %FLASH_CHECK-3-DISK_QUOTA: Flash disk quota exceeded means that there isn't enough free space on the bootflash to continue normal operation. You need to clean up files manually to free up space. Here’s how you can do it:
Step 1: Verify Disk Usage
First, confirm the disk usage and check which files are taking up space:
Show the disk usage on the device:
bash
dir flash:
This will show you a list of all the files on the bootflash and their sizes. Take note of large files like old IOS images, logs, or old configuration backups.
Check the filesystem usage:
bash
show file systems
This will show the amount of space used and free on each file system. Look for any file system that is nearly full, especially bootflash.
Step 2: Clean Up Old Files
Here are some common files you can delete to free up space:
Old IOS images: Check for old or unused IOS images. These images can often be quite large.
bash
dir flash: # List files in the flash directory
If you find old image files that are no longer required, you can delete them:
bash
delete flash:<filename>
Be sure to only delete the images that are not being used as the current boot image.
Old configuration backups: Sometimes configuration backups or other old files can accumulate over time.
Delete unnecessary backups:
bash
delete flash:<backup-file>
Log files: Cisco devices can generate large log files. Check for and clean up debug logs or syslogs.
bash
dir flash:/logs
delete flash:/logs/*
Step 3: Reboot After Cleanup
Once you've deleted unnecessary files, reboot the device to see if it resolves the disk quota exceeded issue:
bash
reload
2. Resolving Read-Only File System (Filesystem Issues)
Since the request platform software package clean command is failing due to the file system being mounted as read-only, we need to resolve the read-only file system issue.
Step 1: Verify File System Mount Status
First, check if the file system is indeed read-only by running:
bash
show file systems
If you see something like Read-Only in the status, that confirms the issue.
Step 2: Remount the File System as Read-Write
In some cases, the file system might be mounted as read-only due to errors or file system corruption. Try remounting the bootflash file system as read-write.
Try to remount the file system:
bash
mount -o remount,rw bootflash:
After remounting, attempt the cleanup again:
bash
request platform software package clean
Step 3: Check for File System Errors
If remounting fails, the file system might be corrupted. You can try to repair it using the following command:
bash
fsck bootflash:
This will check for and repair any file system issues on the bootflash. After that, remount the file system and attempt the cleanup again.
Step 4: Reboot if Needed
If you're still unable to remount as read-write or the file system shows signs of corruption, you might need to reload the device and see if that resolves the issue:
bash
reload
3. Use "request" Commands for Cleanup (If File System is Writable)
Once you've cleared up space and resolved the read-only file system issue, you should be able to run the following command to clean up the package files:
bash
request platform software package clean
This will automatically clean up unnecessary software packages.
4. Consider Increasing Flash Storage (If Needed)
If you continue running into disk space issues, it may be worth considering upgrading the flash storage on your Cisco 4321 ISR.
Summary of Steps:
Clean up old files like old IOS images, logs, and backups.
Remount the file system as read-write if it's in read-only mode.
Run the cleanup command once you have space and the file system is writable.
Check for file system errors and repair them if necessary.
Reboot the device to ensure all changes are applied.
07-16-2025 09:09 AM
dir flash output
48961 drwx 4096 Sep 14 2020 11:37:12 -05:00 .installer
146881 drwx 4096 Sep 14 2020 11:36:55 -05:00 sysboot
16 drwx 4096 Oct 14 2020 09:30:41 -05:00 lost+found
17 -rw- 453662720 Jul 16 2025 09:51:07 -05:00 super.iso
12 -rw- 35 Sep 14 2020 11:39:55 -05:00 pnp-tech-time
13 -rw- 63883 Sep 14 2020 11:40:06 -05:00 pnp-tech-discovery-summary
40801 drwx 4096 Aug 20 2020 22:48:25 -05:00 core
187681 drwx 4096 Jul 16 2025 09:52:25 -05:00 .prst_sync
57121 drwx 4096 Aug 20 2020 22:46:32 -05:00 .rollback_timer
130561 drwx 4096 Aug 20 2020 22:46:33 -05:00 gs_script
65281 drwx 45056 Jul 16 2025 09:56:55 -05:00 tracelogs
89761 drwx 4096 Sep 14 2020 11:56:54 -05:00 .dbpersist
97921 drwx 4096 Aug 20 2020 22:46:50 -05:00 virtual-instance
73441 drwx 4096 Aug 20 2020 22:46:50 -05:00 vman_fdb
14 -rw- 30 Jul 16 2025 09:52:24 -05:00 throughput_monitor_params
114241 drwx 4096 Aug 20 2020 22:48:02 -05:00 onep
15 -rw- 2157 Sep 14 2020 11:50:48 -05:00 licsave.lic
11 -rw- 468823968 Sep 14 2020 11:52:49 -05:00 isr4300-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin
already cleaned tracelogs, dont see any old configs or images. After a reload still have the same error.
Output of show file systems
Size(b) Free(b) Type Flags Prefixes
- - opaque rw system:
- - opaque rw tmpsys:
* 3174936576 1533743104 disk rw bootflash: flash:
8160542720 800522240 disk rw usb0:
- - opaque rw null:
- - opaque ro tar:
- - network rw tftp:
- - opaque wo syslog:
33554432 33529138 nvram rw nvram:
- - network rw rcp:
- - network rw pram:
- - network rw ftp:
- - network rw http:
- - network rw scp:
- - network rw https:
- - opaque ro cns:
21137846272 16177074176 disk rw harddisk:
Seems that bootflash is mounted in rw mode.
mount is not a command listed on the router or in config t mode. Still same error.
Output of fsck bootflash:
umount: /bootflash: device is busy
umount: /bootflash: device is busy
%Error: could not unmount bootflash
warning: can't open /etc/fstab: No such file or directory
mount: /dev/bootflash1 already mounted or /bootflash busy
mount: according to mtab, /dev/bootflash1 is already mounted on /bootflash
fsck error: can not unmount /bootflash, device is busy
warning: can't open /etc/fstab: No such file or directory
mount: /dev/bootflash1 already mounted or /bootflash busy
mount: according to mtab, /dev/bootflash1 is already mounted on /bootflash
%Error checking bootflash: (I/O error)
07-16-2025 09:50 AM
Directory of bootflash:/
48961 drwx 4096 Sep 14 2020 11:37:12 -05:00 .installer
146881 drwx 4096 Sep 14 2020 11:36:55 -05:00 sysboot
16 drwx 4096 Oct 14 2020 09:30:41 -05:00 lost+found
17 -rw- 453662720 Jul 16 2025 09:51:07 -05:00 super.iso
12 -rw- 35 Sep 14 2020 11:39:55 -05:00 pnp-tech-time
13 -rw- 63883 Sep 14 2020 11:40:06 -05:00 pnp-tech-discovery-summary
40801 drwx 4096 Aug 20 2020 22:48:25 -05:00 core
187681 drwx 4096 Jul 16 2025 09:52:25 -05:00 .prst_sync
57121 drwx 4096 Aug 20 2020 22:46:32 -05:00 .rollback_timer
130561 drwx 4096 Aug 20 2020 22:46:33 -05:00 gs_script
65281 drwx 45056 Jul 16 2025 09:56:55 -05:00 tracelogs
89761 drwx 4096 Sep 14 2020 11:56:54 -05:00 .dbpersist
97921 drwx 4096 Aug 20 2020 22:46:50 -05:00 virtual-instance
73441 drwx 4096 Aug 20 2020 22:46:50 -05:00 vman_fdb
14 -rw- 30 Jul 16 2025 09:52:24 -05:00 throughput_monitor_params
114241 drwx 4096 Aug 20 2020 22:48:02 -05:00 onep
15 -rw- 2157 Sep 14 2020 11:50:48 -05:00 licsave.lic
11 -rw- 468823968 Sep 14 2020 11:52:49 -05:00 isr4300-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin
I dont see any old images or configs. No log files listed to clean. Not sure what directories are needed here.
Here is the output of my filesystems
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - opaque rw system:
- - opaque rw tmpsys:
* 3174936576 1533743104 disk rw bootflash: flash:
8160542720 800522240 disk rw usb0:
- - opaque rw null:
- - opaque ro tar:
- - network rw tftp:
- - opaque wo syslog:
33554432 33529138 nvram rw nvram:
- - network rw rcp:
- - network rw pram:
- - network rw ftp:
- - network rw http:
- - network rw scp:
- - network rw https:
- - opaque ro cns:
21137846272 16177074176 disk rw harddisk:
as you can see boorflash is mounted as rw.
#fsck bootflash:
umount: /bootflash: device is busy
umount: /bootflash: device is busy
%Error: could not unmount bootflash
warning: can't open /etc/fstab: No such file or directory
mount: /dev/bootflash1 already mounted or /bootflash busy
mount: according to mtab, /dev/bootflash1 is already mounted on /bootflash
fsck error: can not unmount /bootflash, device is busy
warning: can't open /etc/fstab: No such file or directory
mount: /dev/bootflash1 already mounted or /bootflash busy
mount: according to mtab, /dev/bootflash1 is already mounted on /bootflash
%Error checking bootflash: (I/O error)
after a reload still have the same errors and still will not do "request platform software package clean"
07-16-2025 03:17 PM
The bootflash disk must have enough free space to store two core dumps. This condition is monitored, and if the bootflash disk is too small to store two core dumps, a syslog alarm is generated, as shown in the following example (same log you share)
I still not find solution when I get one I will update you
MHM
07-17-2025 06:39 AM
Maybe I just need to format the bootflash so I can start clean. Do you know how to accomplish this and restore my configs?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide