Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Marcus
New Contributor

Upgrade problem

I have Fortigate 100D with firmware version v4.0,build4196,120717 (MR3). I am trying to update to version: OS 4.0 mr3 patch10 and after that i want to go to a 5.0 firmware version. Sadly the fortigate goes into a loop. It reboots itself after some error messages i see when i' m connected via PuTTy session. I also tried to ' update' to version OS 4.0 MR3 patch 8(632) but same problem. So i go to a backup version and i' m back online but how to solve this problem? Any ideas how i can upgrade to a newer version? THX!
4 REPLIES 4
ede_pfau
SuperUser
SuperUser

hi, and welcome to the forums! The official Supported Upgrade Paths document states that you go this way: 4.3.x -> 4.3.11 -> 4.3.15 -> 5.0.7 -> 5.0.9 http://docs.fortinet.com/fortigate/release-information# You should have a backup of your configuration before you start, in plain text format. Reboot your FGT before any attempt to upgrade. If the upgrade to 4.3.11 fails with a reboot loop I would rebuild it like this: - reboot - stop by hitting a key - format the disk (this erases firmware, logs, configuration!) - reload the firmware using a TFTP server (e.g. running on a locally attached notebook) - reload the config file Upgrading should then proceed without problems. Of course a hardware error will still persist so that a RMA is in order.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Marcus
New Contributor

Thanks for the quick reply! I know the procedure that i have to go in steps but i can' t even upgrade to any 4.3.x version. I tried 4.3.10 and 4.3.8. Everytime in goes into a reboot loop. In my management connection i see messages: Formating shared data partitions ... Using default data disk. failed, status=256! Cannot mount shared data partition. blablabla..... Abort booting! unknown operation mode(0) The system is going down NOW !! And all above starts again. BUT i will try the 4.3.11 and get back here with an answer. Hopefully a happy one.
ede_pfau
SuperUser
SuperUser

Try to reformat the boot device during boot. If that fails the hardware is broken.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
ShrewLWD
Contributor

It seems Marcus did in fact attempt to format during the boot, if I read his ' formatting shared data partitions' line correct. Two quick things...Unless I am mistaken, the ' shared partition' is the partition where the logging occurs, and is formatted using the ' exec formatlogdisk' option once in the firmware. It' s odd it is trying to format that, early in the process. But, if you can get any firmware on, attempt to format that using the command above. Second, if you are going to factory wipe it, there is no need to go down the upgrade path... simply jump straight to the latest 5.0.9.
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors