After upgrade firmware. Display "Disk usage changed, please wait for reboot.."

maruto5555 · ‎11-30-2019

When I upgrade 1500D from 5.6.11 to 6.0.7, during 1500D boot up, it is display "System storage='HDD2' disk-usage changed, please 'execute disk format 32'

Disk usage changed, please wait for reboot..."

It will cause fortigate reboot again after firmware upgrade. Then I cannot see config-error-log after the fortigate reboot again.

Any way to [style="background-color: #ff0000;"]avoid[/style] fortigate disk usage changed when upgrade firmware?

Firmware upgrade in progress ... Done. The system is going down NOW !! Please stand by while rebooting the system. Restarting system. FortiGate-1500D (11:00-06.07.2016) Ver:05000006 Serial number:XXXXXXXX RAM activation CPU(00:000306e4 bfebfbff): MP initialization CPU(01:000306e4 bfebfbff): MP initialization CPU(02:000306e4 bfebfbff): MP initialization CPU(03:000306e4 bfebfbff): MP initialization CPU(04:000306e4 bfebfbff): MP initialization CPU(05:000306e4 bfebfbff): MP initialization CPU(06:000306e4 bfebfbff): MP initialization CPU(07:000306e4 bfebfbff): MP initialization CPU(08:000306e4 bfebfbff): MP initialization CPU(09:000306e4 bfebfbff): MP initialization CPU(0a:000306e4 bfebfbff): MP initialization CPU(0b:000306e4 bfebfbff): MP initialization Total RAM: 16384MB Enabling cache...Done. Scanning PCI bus...Done. Allocating PCI resources...Done. Enabling PCI resources...Done. Zeroing IRQ settings...Done. Verifying PIRQ tables...Done. Boot up, boot device capacity: 30533MB. Press any key to display configuration menu... ............................. Reading boot image 2809378 bytes. Initializing firewall... System is starting... The config file may contain errors, Please see details by the command 'diagnose debug config-error-log read' System storage='HDD2' disk-usage changed, please 'execute disk format 32'. Disk usage changed, please wait for reboot... Formatting the disk... - unmounting /data2 : ok - unmounting /var/log : ok Partitioning and formatting /dev/sdc label WANOPTXX6189651B ... Sending request for partno=0 start=2048 stop=133624230 Sending request for partno=1 start=133625856 stop=267248460 Sending request for partno=2 start=267249664 stop=445414150 done The system is going down NOW !! Please stand by while rebooting the system. Restarting system. FortiGate-1500D (11:00-06.07.2016) Ver:05000006 Serial number:XXXXXX RAM activation CPU(00:000306e4 bfebfbff): MP initialization CPU(01:000306e4 bfebfbff): MP initialization CPU(02:000306e4 bfebfbff): MP initialization CPU(03:000306e4 bfebfbff): MP initialization CPU(04:000306e4 bfebfbff): MP initialization CPU(05:000306e4 bfebfbff): MP initialization CPU(06:000306e4 bfebfbff): MP initialization CPU(07:000306e4 bfebfbff): MP initialization CPU(08:000306e4 bfebfbff): MP initialization CPU(09:000306e4 bfebfbff): MP initialization CPU(0a:000306e4 bfebfbff): MP initialization CPU(0b:000306e4 bfebfbff): MP initialization Total RAM: 16384MB Enabling cache...Done. Scanning PCI bus...Done. Allocating PCI resources...Done. Enabling PCI resources...Done. Zeroing IRQ settings...Done. Verifying PIRQ tables...Done. Boot up, boot device capacity: 30533MB. Press any key to display configuration menu... ............................. Reading boot image 2809378 bytes. Initializing firewall... System is starting...

Toshi_Esumi · ‎11-30-2019

Based on my experiences with upgrading 5.6 to 6.0, no. It's not avoidable. If you have checked its disk partitioning before with 5.6 then checked it again after the upgrade (diag hard device disk), you must have noticed the log disk was split to three partitions. It was one or two before. We don't use WAN optimization or even local disk logging, but it had to happen.