4321 bootflash space issue

[marklafond]

Good day,

I have a 4321 router that I need to upgrade from IOS-XE 17.09.04a to 17.12.4. Unfortunately, I cannot copy the new image to bootflash: as the router falsely reports that there is not enough space. The 17.9.4 image is the only image stored on bootflash.

When I do a "show flash: all" and total up the sizes of all files and folders, the total size is 1,527,112,062, which should leave me 1,705,365,122 free space from the total bootflash size of 3,232,477,184.

For some reason, output of "dir" shows only 513,896,448 available. I have dug through the filesystem and deleted what I can which is mostly tracelog files, but that only gains me a small amount.

Does anyone know of a procedure to restore the available space on bootflash so that I can copy the new image to the router? Note that this router is at a remote site, so hands-on methods like changing ROMMON to boot from tftp are off the table.

Thanks to all.

[liviu.gheorghe]

Hello @marklafond ,

you can use the dir bootflash: command to examine the bootflash. It also tells you how much space is used and what you have free.

To clean up the bootflash, try using the request platform software package clean command.

Also take a look at the crashinfo directory on the bootflash - dir crashinfo: for crashinfo files saved by the router which you can erase to recover some space.

HTH

[marklafond]

Hello to you @liviu.gheorghe, and thank you for your reply,

My router had no crashinfo files stored in bootflash:

I tried the commands you suggested and end up with roughly the same amount of free space (which is not enough for a new image):

RTR#request platform software package clean
This operation may take several minutes...
Cleaning up unnecessary package files
No path specified, will use booted path bootflash:sysboot/packages.conf
Cleaning bootflash:sysboot
Scanning boot directory for packages ... done.
Preparing packages list to delete ...
done.

Files that will be deleted:
packages.conf

Do you want to proceed? [y/n]y
Deleting file bootflash:sysboot/packages.conf ... done.
SUCCESS: Files deleted.

RTR#sh bootflash: all
-#- --length-- ---------date/time--------- path
1 4096 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/
2 16384 Oct 05 2018 20:29:30.0000000000 +00:00 /bootflash/lost+found
3 4096 Feb 26 2025 22:21:38.0000000000 +00:00 /bootflash/.prst_sync
4 763872162 Dec 10 2023 16:57:32.0000000000 +00:00 /bootflash/isr4300-universalk9.17.09.04a.SPA.bin
5 4096 Mar 05 2025 07:41:45.0000000000 +00:00 /bootflash/.installer
6 4096 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback
7 4096 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points
8 4096 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0
9 8216 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/packages.conf
10 0 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/bundle_mode
11 0 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/patch0.sta
12 10 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/patch.sta
13 13 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/bootdir
14 669 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/pkginfo
15 61 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rollback_points.txt
16 50 Mar 05 2025 07:38:30.0000000000 +00:00 /bootflash/.installer/last_pkgconf_shasum
17 5 Mar 05 2025 07:38:29.0000000000 +00:00 /bootflash/.installer/install_global_trans_lock
18 11 Mar 05 2025 07:39:32.0000000000 +00:00 /bootflash/.installer/watchlist
19 4096 Dec 10 2023 18:21:00.0000000000 +00:00 /bootflash/core
20 4096 Dec 10 2023 18:21:00.0000000000 +00:00 /bootflash/core/modules
21 1 Mar 07 2025 20:40:21.0000000000 +00:00 /bootflash/core/.callhome
22 4096 Oct 05 2018 21:08:38.0000000000 +00:00 /bootflash/.rollback_timer
23 32768 Mar 07 2025 18:14:08.0000000000 +00:00 /bootflash/tracelogs
24 65889 Feb 27 2025 01:51:36.0000000000 +00:00 /bootflash/tracelogs/dmesg
25 10 Feb 27 2025 01:51:36.0000000000 +00:00 /bootflash/tracelogs/timestamp
26 1260582 Mar 05 2025 17:59:50.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_2.20250305141644.bin.gz
27 1216032 Mar 07 2025 10:48:04.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_13.20250307070811.bin.gz
28 1218052 Mar 07 2025 14:30:48.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_14.20250307104803.bin.gz
29 1212991 Mar 07 2025 18:14:08.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_15.20250307143048.bin.gz
30 1346135 Mar 03 2025 18:02:44.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_31.20250303142355.bin.gz
31 1347710 Mar 03 2025 21:41:57.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_32.20250303180243.bin.gz
32 48908 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250227_232218_UTC_1740698538.tar.gz
33 1350300 Mar 04 2025 01:17:19.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_33.20250303214157.bin.gz
34 1345993 Mar 04 2025 04:56:07.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_34.20250304011718.bin.gz
35 1346460 Mar 04 2025 08:34:56.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_35.20250304045607.bin.gz
36 1346166 Mar 04 2025 12:13:46.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_36.20250304083456.bin.gz
37 1343725 Mar 04 2025 15:52:46.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_37.20250304121345.bin.gz
38 1340228 Mar 04 2025 19:31:59.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_38.20250304155245.bin.gz
39 49007 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250228_232218_UTC_1740784938.tar.gz
40 1341904 Mar 04 2025 23:10:55.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_39.20250304193158.bin.gz
41 1342498 Mar 05 2025 02:46:15.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_40.20250304231055.bin.gz
42 1543461 Mar 05 2025 10:33:24.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_0.20250305073936.bin.gz
43 1260653 Mar 05 2025 21:42:52.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_3.20250305175950.bin.gz
44 1257742 Mar 06 2025 01:26:12.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_4.20250305214252.bin.gz
45 1257763 Mar 06 2025 05:09:33.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_5.20250306012611.bin.gz
46 1257342 Mar 06 2025 08:49:27.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_6.20250306050932.bin.gz
47 49238 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250301_232218_UTC_1740871338.tar.gz
48 1259874 Mar 06 2025 12:32:08.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_7.20250306084927.bin.gz
49 1242071 Mar 06 2025 16:15:26.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_8.20250306123207.bin.gz
50 1215255 Mar 06 2025 19:58:45.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_9.20250306161525.bin.gz
51 1217038 Mar 06 2025 23:41:32.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_10.20250306195845.bin.gz
52 1216212 Mar 07 2025 03:24:52.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_11.20250306234131.bin.gz
53 1215707 Mar 07 2025 07:08:12.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_12.20250307032452.bin.gz
54 49286 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250302_232218_UTC_1740957738.tar.gz
55 1455 Mar 05 2025 07:38:36.0000000000 +00:00 /bootflash/tracelogs/cyaninit_R0-0.2575_0.20250305073836.bin.gz
56 49172 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250303_232218_UTC_1741044138.tar.gz
57 49257 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250304_232218_UTC_1741130538.tar.gz
58 1258698 Mar 05 2025 14:16:44.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_1.20250305103323.bin.gz
59 40099 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250305_084017_UTC_1741164017.tar.gz
60 40805 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250306_084017_UTC_1741250417.tar.gz
61 41018 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250307_084018_UTC_1741336818.tar.gz
62 30 Mar 05 2025 07:39:59.0000000000 +00:00 /bootflash/throughput_monitor_params
63 4096 Dec 10 2023 18:28:43.0000000000 +00:00 /bootflash/.dbpersist
64 4096 Mar 01 2025 20:08:49.0000000000 +00:00 /bootflash/.dbpersist/DMI_STATE_DB
65 15861 Mar 01 2025 20:08:49.0000000000 +00:00 /bootflash/.dbpersist/DMI_STATE_DB/DMI_STATE_DB
66 173 Mar 05 2025 07:39:29.0000000000 +00:00 /bootflash/.dbpersist/DMI_STATE_DB/DMI_STATE_DB.meta
67 6272 Mar 05 2025 07:39:29.0000000000 +00:00 /bootflash/.dbpersist/stats
68 4096 Dec 10 2023 18:28:43.0000000000 +00:00 /bootflash/.dbpersist/history
69 4096 May 04 2020 13:22:36.0000000000 +00:00 /bootflash/virtual-instance
70 4096 May 04 2020 13:23:48.0000000000 +00:00 /bootflash/onep
71 4096 May 04 2020 13:23:48.0000000000 +00:00 /bootflash/onep/apps-cli
72 4096 Mar 07 2025 20:50:10.0000000000 +00:00 /bootflash/sysboot
73 65536 Feb 26 2025 22:20:09.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dreamliner.17.09.04a.SPA.pkg
74 6799360 Feb 26 2025 22:20:09.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dsp_analogbri.17.09.04a.SPA.pkg
75 2007040 Feb 26 2025 22:20:09.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dsp_sp2700.17.09.04a.SPA.pkg
76 18649088 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dsp_tilegx.17.09.04a.SPA.pkg
77 11497472 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_ngwic_t1e1.17.09.04a.SPA.pkg
78 13139968 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_async.17.09.04a.SPA.pkg
79 4894720 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_bri_st_fw.17.09.04a.SPA.pkg
80 17960960 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_cwan.17.09.04a.SPA.pkg
81 2994176 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_ge.17.09.04a.SPA.pkg
82 11714560 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_shdsl.17.09.04a.SPA.pkg
83 5431296 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_ssd.17.09.04a.SPA.pkg
84 5677056 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_xdsl.17.09.04a.SPA.pkg
85 10412032 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_prince.17.09.04a.SPA.pkg
86 2527232 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_10g.17.09.04a.SPA.pkg
87 11366400 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_1t3e3.17.09.04a.SPA.pkg
88 14557184 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_async.17.09.04a.SPA.pkg
89 2138112 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_dsp_sp2700.17.09.04a.SPA.pkg
90 587202560 Feb 26 2025 22:20:18.0000000000 +00:00 /bootflash/sysboot/isr4300-mono-universalk9.17.09.04a.SPA.pkg
91 4096 Dec 10 2023 18:27:21.0000000000 +00:00 /bootflash/SHARED-IOX
92 1364 Mar 05 2025 07:39:09.0000000000 +00:00 /bootflash/mode_event_log
93 137940 Mar 05 2025 07:39:39.0000000000 +00:00 /bootflash/memleak.tcl
94 20109 Dec 10 2023 18:28:38.0000000000 +00:00 /bootflash/ios_core.p7b
95 1923 Dec 10 2023 18:28:38.0000000000 +00:00 /bootflash/trustidrootx3_ca_092024.ca
96 4096 Dec 10 2023 18:29:07.0000000000 +00:00 /bootflash/.geo
97 4096 Mar 05 2025 07:40:08.0000000000 +00:00 /bootflash/license_evlog
98 102 Mar 01 2025 20:08:49.0000000000 +00:00 /bootflash/license_evlog/SAEventRegular20250226_222205.log
99 2297 Mar 05 2025 08:40:11.0000000000 +00:00 /bootflash/license_evlog/SAEventRegular20250305_074006.log

513912832 bytes available (2554359808 bytes used)

Filesystem: bootflash
Filesystem Path: /bootflash
Filesystem Type: ext2
Mounted: Read/Write

As you can see, after a couple of reloads I again have tracelog files, but they do not add up to much used space.

I'm really baffled by this phantom use of free space.

[marklafond]

Hello @liviu.gheorghe and thank you for the reply.

I tried replying to this with output from my router, but that reply post seems to have disappeared. I must have violated some rule or something.

"dir bootflash:" is what I used to navigate the filesystem and make deletions of tracelog files. That only gained back a very small amount of free space.

"request platform software package clean" only deleted the single "bootflash/sysboot/packages.conf" file, saving 8216 bytes.

The router does not have a crashinfo: directory.

Again, I am stumped by this. Perhaps the flash memory is faulty.

[liviu.gheorghe]

Can you share the last lines of the show version output - the ones that describe the platform, number of interfaces, RAM and flash.

Also the output of the dir command - can you try and share it again?

What is the uptime of your router?

[marklafond]

@liviu.gheorghe 

As requested:

Last few lines of show version:

cisco ISR4321/K9 (1RU) processor with 1653723K/3071K bytes of memory.
Processor board ID FLM2240W15M
Router operating mode: Autonomous
3 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
3207167K bytes of flash memory at bootflash:.

Configuration register is 0x2102

Output of dir:

dir
Directory of bootflash:/

128513 drwx 32768 Mar 7 2025 21:56:55 +00:00 tracelogs
353409 drwx 4096 Mar 7 2025 20:50:10 +00:00 sysboot
257025 drwx 4096 Mar 5 2025 07:41:45 +00:00 .installer
369476 drwx 4096 Mar 5 2025 07:40:08 +00:00 license_evlog
14 -rw- 30 Mar 5 2025 07:39:59 +00:00 throughput_monitor_params
29 -rw- 137940 Mar 5 2025 07:39:39 +00:00 memleak.tcl
28 -rwx 1364 Mar 5 2025 07:39:09 +00:00 mode_event_log
369473 drwx 4096 Feb 26 2025 22:21:38 +00:00 .prst_sync
369474 drwx 4096 Dec 10 2023 18:29:07 +00:00 .geo
160641 drwx 4096 Dec 10 2023 18:28:43 +00:00 .dbpersist
16067 -rw- 1923 Dec 10 2023 18:28:38 +00:00 trustidrootx3_ca_092024.ca
30 -rw- 20109 Dec 10 2023 18:28:38 +00:00 ios_core.p7b
369475 drwx 4096 Dec 10 2023 18:27:21 +00:00 SHARED-IOX
80321 drwx 4096 Dec 10 2023 18:21:00 +00:00 core
26 -rw- 763872162 Dec 10 2023 16:57:32 +00:00 isr4300-universalk9.17.09.04a.SPA.bin
192769 drwx 4096 May 4 2020 13:23:48 +00:00 onep
176705 drwx 4096 May 4 2020 13:22:36 +00:00 virtual-instance
112449 drwx 4096 Oct 5 2018 21:08:38 +00:00 .rollback_timer
11 drwx 16384 Oct 5 2018 20:29:30 +00:00 lost+found

3232477184 bytes total (514035712 bytes free)

Uptime:

uptime is 2 days, 15 hours, 13 minutes

[Joseph W. Doherty]

Just want to mention, often overlooked is IOS installations using considerable storage space within subdirectories.  That's not the case, correct, and you're sure?

In the past I've done countless IOS upgrades where the device had insufficient flash for both the currently running and the newer IOS.  (Very, very often, device was remote, sometimes really remote [as in thousands of miles away].  Fortunately, almost all remote sites had two remote WAN routers, so if the one being upgraded "went wrong", it wasn't usually a disaster, just a PIA.)

Of course, the problem with not having the current and new IOS files on the device, "much fun" if something goes wrong.

There are different ways to minimize the "went wrong" and different ways to try to allow for remote recovery.  If device supports booting from, and has, a flash device slot for CF or USB, you might be able to have both current and new IOS on device, concurrently.

[marklafond]

Hello @Joseph W. Doherty 

The only command I have found to show all the files in the filesystem is "show bootflash: all" and here is the output:

sh bootflash: all
-#- --length-- ---------date/time--------- path
1 4096 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/
2 16384 Oct 05 2018 20:29:30.0000000000 +00:00 /bootflash/lost+found
3 4096 Feb 26 2025 22:21:38.0000000000 +00:00 /bootflash/.prst_sync
4 763872162 Dec 10 2023 16:57:32.0000000000 +00:00 /bootflash/isr4300-universalk9.17.09.04a.SPA.bin
5 4096 Mar 05 2025 07:41:45.0000000000 +00:00 /bootflash/.installer
6 4096 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback
7 4096 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points
8 4096 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0
9 8216 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/packages.conf
10 0 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/bundle_mode
11 0 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/patch0.sta
12 10 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/patch.sta
13 13 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/bootdir
14 669 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rb_points/0/pkginfo
15 61 Dec 10 2023 18:28:46.0000000000 +00:00 /bootflash/.installer/rollback/rollback_points.txt
16 50 Mar 05 2025 07:38:30.0000000000 +00:00 /bootflash/.installer/last_pkgconf_shasum
17 5 Mar 05 2025 07:38:29.0000000000 +00:00 /bootflash/.installer/install_global_trans_lock
18 11 Mar 05 2025 07:39:32.0000000000 +00:00 /bootflash/.installer/watchlist
19 4096 Dec 10 2023 18:21:00.0000000000 +00:00 /bootflash/core
20 4096 Dec 10 2023 18:21:00.0000000000 +00:00 /bootflash/core/modules
21 1 Mar 07 2025 23:10:22.0000000000 +00:00 /bootflash/core/.callhome
22 4096 Oct 05 2018 21:08:38.0000000000 +00:00 /bootflash/.rollback_timer
23 32768 Mar 07 2025 21:56:55.0000000000 +00:00 /bootflash/tracelogs
24 65889 Feb 27 2025 01:51:36.0000000000 +00:00 /bootflash/tracelogs/dmesg
25 10 Feb 27 2025 01:51:36.0000000000 +00:00 /bootflash/tracelogs/timestamp
26 1260582 Mar 05 2025 17:59:50.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_2.20250305141644.bin.gz
27 1216032 Mar 07 2025 10:48:04.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_13.20250307070811.bin.gz
28 1218052 Mar 07 2025 14:30:48.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_14.20250307104803.bin.gz
29 1212991 Mar 07 2025 18:14:08.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_15.20250307143048.bin.gz
30 1223698 Mar 07 2025 21:56:55.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_16.20250307181407.bin.gz
31 1347710 Mar 03 2025 21:41:57.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_32.20250303180243.bin.gz
32 48908 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250227_232218_UTC_1740698538.tar.gz
33 1350300 Mar 04 2025 01:17:19.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_33.20250303214157.bin.gz
34 1345993 Mar 04 2025 04:56:07.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_34.20250304011718.bin.gz
35 1346460 Mar 04 2025 08:34:56.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_35.20250304045607.bin.gz
36 1346166 Mar 04 2025 12:13:46.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_36.20250304083456.bin.gz
37 1343725 Mar 04 2025 15:52:46.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_37.20250304121345.bin.gz
38 1340228 Mar 04 2025 19:31:59.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_38.20250304155245.bin.gz
39 49007 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250228_232218_UTC_1740784938.tar.gz
40 1341904 Mar 04 2025 23:10:55.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_39.20250304193158.bin.gz
41 1342498 Mar 05 2025 02:46:15.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.7248_40.20250304231055.bin.gz
42 1543461 Mar 05 2025 10:33:24.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_0.20250305073936.bin.gz
43 1260653 Mar 05 2025 21:42:52.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_3.20250305175950.bin.gz
44 1257742 Mar 06 2025 01:26:12.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_4.20250305214252.bin.gz
45 1257763 Mar 06 2025 05:09:33.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_5.20250306012611.bin.gz
46 1257342 Mar 06 2025 08:49:27.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_6.20250306050932.bin.gz
47 49238 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250301_232218_UTC_1740871338.tar.gz
48 1259874 Mar 06 2025 12:32:08.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_7.20250306084927.bin.gz
49 1242071 Mar 06 2025 16:15:26.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_8.20250306123207.bin.gz
50 1215255 Mar 06 2025 19:58:45.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_9.20250306161525.bin.gz
51 1217038 Mar 06 2025 23:41:32.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_10.20250306195845.bin.gz
52 1216212 Mar 07 2025 03:24:52.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_11.20250306234131.bin.gz
53 1215707 Mar 07 2025 07:08:12.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_12.20250307032452.bin.gz
54 49286 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250302_232218_UTC_1740957738.tar.gz
55 1455 Mar 05 2025 07:38:36.0000000000 +00:00 /bootflash/tracelogs/cyaninit_R0-0.2575_0.20250305073836.bin.gz
56 49172 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250303_232218_UTC_1741044138.tar.gz
57 49257 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250304_232218_UTC_1741130538.tar.gz
58 1258698 Mar 05 2025 14:16:44.0000000000 +00:00 /bootflash/tracelogs/utf_R0-0.5928_1.20250305103323.bin.gz
59 40099 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250305_084017_UTC_1741164017.tar.gz
60 40805 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250306_084017_UTC_1741250417.tar.gz
61 41018 Mar 07 2025 08:40:58.0000000000 +00:00 /bootflash/tracelogs/memmon_log_20250307_084018_UTC_1741336818.tar.gz
62 30 Mar 05 2025 07:39:59.0000000000 +00:00 /bootflash/throughput_monitor_params
63 4096 Dec 10 2023 18:28:43.0000000000 +00:00 /bootflash/.dbpersist
64 4096 Mar 01 2025 20:08:49.0000000000 +00:00 /bootflash/.dbpersist/DMI_STATE_DB
65 15861 Mar 01 2025 20:08:49.0000000000 +00:00 /bootflash/.dbpersist/DMI_STATE_DB/DMI_STATE_DB
66 173 Mar 05 2025 07:39:29.0000000000 +00:00 /bootflash/.dbpersist/DMI_STATE_DB/DMI_STATE_DB.meta
67 6272 Mar 05 2025 07:39:29.0000000000 +00:00 /bootflash/.dbpersist/stats
68 4096 Dec 10 2023 18:28:43.0000000000 +00:00 /bootflash/.dbpersist/history
69 4096 May 04 2020 13:22:36.0000000000 +00:00 /bootflash/virtual-instance
70 4096 May 04 2020 13:23:48.0000000000 +00:00 /bootflash/onep
71 4096 May 04 2020 13:23:48.0000000000 +00:00 /bootflash/onep/apps-cli
72 4096 Mar 07 2025 20:50:10.0000000000 +00:00 /bootflash/sysboot
73 65536 Feb 26 2025 22:20:09.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dreamliner.17.09.04a.SPA.pkg
74 6799360 Feb 26 2025 22:20:09.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dsp_analogbri.17.09.04a.SPA.pkg
75 2007040 Feb 26 2025 22:20:09.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dsp_sp2700.17.09.04a.SPA.pkg
76 18649088 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_dsp_tilegx.17.09.04a.SPA.pkg
77 11497472 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_ngwic_t1e1.17.09.04a.SPA.pkg
78 13139968 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_async.17.09.04a.SPA.pkg
79 4894720 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_bri_st_fw.17.09.04a.SPA.pkg
80 17960960 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_cwan.17.09.04a.SPA.pkg
81 2994176 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_ge.17.09.04a.SPA.pkg
82 11714560 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_shdsl.17.09.04a.SPA.pkg
83 5431296 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_ssd.17.09.04a.SPA.pkg
84 5677056 Feb 26 2025 22:20:10.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_nim_xdsl.17.09.04a.SPA.pkg
85 10412032 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_prince.17.09.04a.SPA.pkg
86 2527232 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_10g.17.09.04a.SPA.pkg
87 11366400 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_1t3e3.17.09.04a.SPA.pkg
88 14557184 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_async.17.09.04a.SPA.pkg
89 2138112 Feb 26 2025 22:20:11.0000000000 +00:00 /bootflash/sysboot/isr4300-firmware_sm_dsp_sp2700.17.09.04a.SPA.pkg
90 587202560 Feb 26 2025 22:20:18.0000000000 +00:00 /bootflash/sysboot/isr4300-mono-universalk9.17.09.04a.SPA.pkg
91 4096 Dec 10 2023 18:27:21.0000000000 +00:00 /bootflash/SHARED-IOX
92 1364 Mar 05 2025 07:39:09.0000000000 +00:00 /bootflash/mode_event_log
93 137940 Mar 05 2025 07:39:39.0000000000 +00:00 /bootflash/memleak.tcl
94 20109 Dec 10 2023 18:28:38.0000000000 +00:00 /bootflash/ios_core.p7b
95 1923 Dec 10 2023 18:28:38.0000000000 +00:00 /bootflash/trustidrootx3_ca_092024.ca
96 4096 Dec 10 2023 18:29:07.0000000000 +00:00 /bootflash/.geo
97 4096 Mar 05 2025 07:40:08.0000000000 +00:00 /bootflash/license_evlog
98 102 Mar 01 2025 20:08:49.0000000000 +00:00 /bootflash/license_evlog/SAEventRegular20250226_222205.log
99 2297 Mar 05 2025 08:40:11.0000000000 +00:00 /bootflash/license_evlog/SAEventRegular20250305_074006.log

514035712 bytes available (2554236928 bytes used)

Filesystem: bootflash
Filesystem Path: /bootflash
Filesystem Type: ext2
Mounted: Read/Write

Unfortunately, there is no additional USB or CF memory on this router, nor is anyone going to be visiting this remote site in the foreseeable future. I've only ever experienced something like this with local hardware where a wiping/formatting of the flash followed by copying over a new image via xmodem was what worked.

[Joseph W. Doherty · Accepted solution]

Okay, took your dir listing stats, and I got a total file allocation of 1,527,151,296, pretty darn close to your OP value.

As to where the additionally storage went, possibly some of it is tied up in actual space allocations for those files.  Remember, actual file space allocations are more than a file's logical size.

The ext2 filesystem type, allows up to 8K block sizes, so with just about 100 files, a minimum of 800,000 bytes would be allocated (I would allow for about half of that for the unused allocated space at the end of each file), and then there's also the need for the data control structures too.  Still, the forgoing wouldn't seem to account for the missing 1GB.  (If we had access to full Linux we could determine the impact of this, much better.)

Possibly a simple test:  copy a 1 byte file into flash, and make note of reported space usage before and after the file is created.

I also wonder about any hidden files.

Regardless, as I see .pkg files in flash, you're running in "install mode"?  If so, and assuming I don't misunderstand, the .bin doesn't need to be on the device, and deleting /bootflash/isr4300-universalk9.17.09.04a.SPA.bin should free up lots of space, about 3/4 GB.

[marklafond]

@Joseph W. Doherty 

Your last paragraph about "install mode" gave me the confidence to delete the old image to make room for the new. It was not cut-and-dry, but it worked:

RTR#del isr4300-universalk9.17.09.04a.SPA.bin
Delete filename [isr4300-universalk9.17.09.04a.SPA.bin]?
Delete bootflash:/isr4300-universalk9.17.09.04a.SPA.bin? [confirm]
Warning: This system software is in use, deleting system file might cause system instability.
Delete of bootflash:/isr4300-universalk9.17.09.04a.SPA.bin aborted!
Please use "install remove file <filename>" to see if file can be safely removed.
"delete /force <filename>" can be used to force deletion.

RTR#install remove file bootflash:isr4300-universalk9.17.09.04a.SPA.bin
install_remove: START Sat Mar 08 01:56:48 UTC 2025
install_remove: Removing IMG
/bootflash/isr4300-universalk9.17.09.04a.SPA.bin

Do you want to remove the above files? [y/n]y

Deleting file /bootflash/isr4300-universalk9.17.09.04a.SPA.bin ... done.
SUCCESS: Files deleted.

--- Starting Post_Remove_Cleanup ---
Performing REMOVE_POSTCHECK on all members
Finished Post_Remove_Cleanup
SUCCESS: install_remove Sat Mar 08 01:56:56 UTC 2025
RTR#dir
Directory of bootflash:/

257025 drwx 4096 Mar 8 2025 01:56:57 +00:00 .installer
128513 drwx 32768 Mar 8 2025 01:39:54 +00:00 tracelogs
353409 drwx 4096 Mar 7 2025 20:50:10 +00:00 sysboot
369476 drwx 4096 Mar 5 2025 07:40:08 +00:00 license_evlog
14 -rw- 30 Mar 5 2025 07:39:59 +00:00 throughput_monitor_params
29 -rw- 137940 Mar 5 2025 07:39:39 +00:00 memleak.tcl
28 -rwx 1364 Mar 5 2025 07:39:09 +00:00 mode_event_log
369473 drwx 4096 Feb 26 2025 22:21:38 +00:00 .prst_sync
369474 drwx 4096 Dec 10 2023 18:29:07 +00:00 .geo
160641 drwx 4096 Dec 10 2023 18:28:43 +00:00 .dbpersist
16067 -rw- 1923 Dec 10 2023 18:28:38 +00:00 trustidrootx3_ca_092024.ca
30 -rw- 20109 Dec 10 2023 18:28:38 +00:00 ios_core.p7b
369475 drwx 4096 Dec 10 2023 18:27:21 +00:00 SHARED-IOX
80321 drwx 4096 Dec 10 2023 18:21:00 +00:00 core
192769 drwx 4096 May 4 2020 13:23:48 +00:00 onep
176705 drwx 4096 May 4 2020 13:22:36 +00:00 virtual-instance
112449 drwx 4096 Oct 5 2018 21:08:38 +00:00 .rollback_timer
11 drwx 16384 Oct 5 2018 20:29:30 +00:00 lost+found

3232477184 bytes total (1278795776 bytes free)

I then copied 17.12.04 image over via scp with this as the result:

RTR#dir
Directory of bootflash:/

48193 -rw- 776466178 Mar 8 2025 02:11:18 +00:00 isr4300-universalk9.17.12.04.SPA.bin
257025 drwx 4096 Mar 8 2025 01:56:57 +00:00 .installer
128513 drwx 32768 Mar 8 2025 01:39:54 +00:00 tracelogs
353409 drwx 4096 Mar 7 2025 20:50:10 +00:00 sysboot
369476 drwx 4096 Mar 5 2025 07:40:08 +00:00 license_evlog
14 -rw- 30 Mar 5 2025 07:39:59 +00:00 throughput_monitor_params
29 -rw- 137940 Mar 5 2025 07:39:39 +00:00 memleak.tcl
28 -rwx 1364 Mar 5 2025 07:39:09 +00:00 mode_event_log
369473 drwx 4096 Feb 26 2025 22:21:38 +00:00 .prst_sync
369474 drwx 4096 Dec 10 2023 18:29:07 +00:00 .geo
160641 drwx 4096 Dec 10 2023 18:28:43 +00:00 .dbpersist
16067 -rw- 1923 Dec 10 2023 18:28:38 +00:00 trustidrootx3_ca_092024.ca
30 -rw- 20109 Dec 10 2023 18:28:38 +00:00 ios_core.p7b
369475 drwx 4096 Dec 10 2023 18:27:21 +00:00 SHARED-IOX
80321 drwx 4096 Dec 10 2023 18:21:00 +00:00 core
192769 drwx 4096 May 4 2020 13:23:48 +00:00 onep
176705 drwx 4096 May 4 2020 13:22:36 +00:00 virtual-instance
112449 drwx 4096 Oct 5 2018 21:08:38 +00:00 .rollback_timer
11 drwx 16384 Oct 5 2018 20:29:30 +00:00 lost+found

3232477184 bytes total (501563392 bytes free)

I changed the boot variable to the new image and executed a reboot. Router is now running the new version.

As an old IOS (pre-XE) guy, I still don't understand all of this virtualization stuff, nor the difference between install mode and batch mode. 

[Leo Laohoo]

Bundle Mode means the router, switch, WLC boots the BIN file.  Because the BIN file is the compact form of the firmware, the packages are extracted in the memory of the platform.  This means the boot-up time is longer and utilizes more CPU and memory resources.  It is NOT possible to install any SMU in Bundle Mode.  

Install Mode means all the packages files are fully extracted and the switch goes through the list to boot the different packages in order.  Because the package files are already extracted into the flash, the boot-up time is faster and uses less memory and CPU resources.  Because the package files are fully extracted, the stack master is capable (if the commands are present or enabled) to push the firmware down to any stack member joining the stack with incorrect firmware version.

For obvious reasons, Cisco TAC recommends Install Mode and only use Bundle Mode in "extreme cases" such as booting a platform in ROMMON.

[Joseph W. Doherty]

BTW, in ye olden times, I recall it was possible to decompress the older IOS files, and boot those (which would save the time to decompress during normal booting).  The disadvantage was the decompressed IOS usually needed twice as much flash space.

[Leo Laohoo]

Copy the 17.12.4 BIN file into the flash. 

Change the boot variable string to point to the 17.12.4 BIN file. 

Reboot the router.

Once the router has boot into 17.12.4 (Bundle Mode), initiate Install Mode.  

Change the boot variable string to point to the "packages.conf" file.

Reboot again.

[marklafond]

@Joseph W. Doherty @Leo Laohoo @liviu.gheorghe 

I've been working with Cisco devices since about 1996 and have never had to personally post to any forum for answers. I have always been able to just Google and find the answer, usually on this forum and from knowledgeable folks like yourselves. I thank you all for the direct assistance on this and the indirect assistance on so many other issues. You all are great!