Unsolved
This post is more than 5 years old
7 Posts
0
12700
June 9th, 2009 13:00
Updating code on PowerConnect 5224 - not enough free space
A feature listed for the PowerConnect 5224 (and many other PC models) is support for dual firmware images and configuration files. However, I'm having a rough go, figuring out how to get the second image to my 5224. Here is the directory listing currently:
file name file type startup size (byte)
-------------------------------- -------------- ------- -----------
Diag-V1-0-0-5 Boot-Rom image Y 116392
ES4524B-77-V2-0-0-27 Operation Code Y 1570724
Factory_Default_Config.cfg Config File N 2686
start Config File Y 2793
startup-config Config File N 2890
-------------------------------------------------------------------
Total free space: 1441792
However, the 3.1.0.13 image is 1570724 bytes, which is slightly larger than the free space currently available. I can't overwrite the existing firmware image, nor can I remove the diagnostic Boot-ROM image. Was there a batch of these switches made that do not support dual firmware images? Or were the original firmware images significantly smaller? Or has some sort of filesystem fragmentation eaten up the necessary free bytes? Any strategies for updating the code for this switch?
Can I delete a firmware image if I break into the firmware update mode on boot, which should free enough space to allow me to upload an image via XMODEM?
Thanks,
Kevin
0 events found
j_cherian
5 Posts
0
November 27th, 2009 13:00
I had the exact same problem with one of our PowerConnect 5224s. I saw your post and was disappointed that there was no reply.
I was able to firmware update the first 5224. But I had no free space to do the second 5224. I compared the two 5224s and found that there were two startup config files in the switch that had no free space. I deleted the one that was not set to be startup and then voila, I had the free space and the firmware updated successfully.
So in your case, you would have to delete the file "startup-config" which according to your screen shot is NOT set to be the startup script. This will leave your "start" as your startup script and you will have the free space to do the firmware update.
Good luck.
John