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.
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