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

Warning: Signature is missing or invalid.

I have a FortiGate 80F, and when I power it on, it shows this error

Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 224, path: /data/lib/libips.so
Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 273, path: /data/lib/libips.so
Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 224, path: /etc/ips.cfgscript.gz
Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 224, path: /etc/ips.mudb.rules

I haven't deployed this FortiGate yet, and I have formatted and installed FortiOS 7.2.4 because once it didn't boot in FortiOS; it said 'File - 0 seems to be corrupted.':

FortiGate-80F (17:33-07.27.2021)
Ver:05000025
Serial number: FGT80FTK*********
CPU: 1200MHz
Total RAM: 4 GB
Initializing boot device...
Initializing MAC... NP6XLITE#0
Please wait for OS to boot, or press any key to display configuration menu......

Booting OS...
File - 0 seems to be corrupted
'/rootfs.gz' read size wrong: 206f8f0->ffffffff
Failed to load file - 1: -1
Image load failed.
Error: Default firmware boot failed!!!
Switch to BACKUP after 0 seconds. Press any key to stop....

 

And when I keep it on for a bit of time, it reboots and shows this:

 

Rebooting in 5 seconds..BUG: failure at mm/vmalloc.c:1341/__get_vm_area_node()!
Kernel panic - not syncing: BUG!
Call trace:
[<ffffffc000085490>] dump_backtrace+0x0/0x140
[<ffffffc000493f48>] dump_stack+0x14/0x1c
[<ffffffc000494700>] panic+0xb8/0x1dc
[<ffffffc000123574>] __get_vm_area+0x0/0x3c
[<ffffffc000123da8>] get_vm_area_caller+0x28/0x30
[<ffffffc00008d4b4>] __ioremap_caller+0x64/0xf0
[<ffffffc00008d554>] __ioremap+0x14/0x20
[<ffffffc00008a4a4>] fgt_soc4_sys_reset+0x24/0x80
[<ffffffc000084404>] machine_restart+0x34/0x60
[<ffffffc0000afdd8>] emergency_restart+0x18/0x20
[<ffffffc0004947d0>] panic+0x188/0x1dc
[<ffffffc000123574>] __get_vm_area+0x0/0x3c
[<ffffffc000123da8>] get_vm_area_caller+0x28/0x30
[<ffffffc00008d4b4>] __ioremap_caller+0x64/0xf0
[<ffffffc00008d554>] __ioremap+0x14/0x20
[<ffffffc00008a4a4>] fgt_soc4_sys_reset+0x24/0x80
[<ffffffc000084404>] machine_restart+0x34/0x60
[<ffffffc0000afdd8>] emergency_restart+0x18/0x20
[<ffffffc0004947d0>] panic+0x188/0x1dc
[<ffffffc000123574>] __get_vm_area+0x0/0x3c
[<ffffffc000123da8>] get_vm_area_caller+0x28/0x30
[<ffffffc00008d4b4>] __ioremap_caller+0x64/0xf0
[<ffffffc00008d554>] __ioremap+0x14/0x20
[<ffffffc00008a4a4>] fgt_soc4_sys_reset+0x24/0x80
[<ffffffc000084404>] machine_restart+0x34/0x60
[<ffffffc0000afdd8>] emergency_restart+0x18/0x20
[<ffffffc0004947d0>] panic+0x188/0x1dc
[<ffffffc000123574>] __get_vm_area+0x0/0x3c
[<ffffffc000123da8>] get_vm_area_caller+0x28/0x30
[<ffffffc00008d4b4>] __ioremap_caller+0x64/0xf0
[<ffffffc00008d554>] __ioremap+0x14/0x20
[<ffffffc00008a4a4>] fgt_soc4_sys_reset+0x24/0x80
[<ffffffc000084404>] machine_restart+0x34/0x60
[<ffffffc0000afdd8>] emergency_restart+0x18/0x20
[<ffffffc0004947d0>] panic+0x188/0x1dc
[<ffffffc000123574>] __get_vm_area+0x0/0x3c
[<ffffffc000123da8>] get_vm_area_caller+0x28/0x30
[<ffffffc00008d4b4>] __ioremap_caller+0x64/0xf0
[<ffffffc00008d554>] __ioremap+0x14/0x20
[<ffffffc00008a4a4>] fgt_soc4_sys_reset+0x24/0x80
[<ffffffc000084404>] machine_restart+0x34/0x60
[<ffffffc0000afdd8>] emergency_restart+0x18/0x20
[<ffffffc0004947d0>] panic+0x188/0x1dc
[<ffffffc000123574>] __get_vm_area+0x0/0x3c
[<ffffffc000123da8>] get_vm_area_caller+0x28/0x30
[<ffffffc00008d4b4>] __ioremap_caller+0x64/0xf0
[<ffffffc00008d554>] __ioremap+0x14/0x20
[<ffffffc00008a4a4>] fgt_soc4_sys_reset+0x24/0x80
[<ffffffc000084404>] machine_restart+0x34/0x60
[<ffffffc0000afdd8>] emergency_restart+0x18/0x20
[<ffffffc0004947d0>] panic+0x188/0x1dc
[<ffffffc000123574>] __get_vm_area+0x0/0x3c
[<ffffffc000123da8>] get_vm_area_caller+0x28/0x30
[<ffffffc00008d4b4>] __ioremap_caller+0x64/0xf0
[<ffffffc00008d554>] __ioremap+0x14/0x20
[<ffffffc00008a4a4>] fgt_soc4_sys_reset+0x24/0x80
[<ffffffc000084404>] machine_restart+0x34/0x60
[<ffffffc0000afdd8>] emergency_restart+0x18/0x20
[<ffffffc0004947d0>] panic+0x188/0x1dc
[<ffffffc0000e1680>] watchdog_timer_fn+0x29c/0x33c
[<ffffffc0000c02c8>] __run_hrtimer.constprop.0+0x48/0x164
[<ffffffc0000c0dd0>] hrtimer_run_queues+0xf0/0x180
[<ffffffc0000aa564>] update_process_times+0x34/0x94
[<ffffffc0000cbee8>] tick_periodic+0x38/0xb0
[<ffffffc0000cbffc>] tick_handle_periodic+0x28/0x8c
[<ffffffc0003757d0>] arch_timer_handler_phys+0x30/0x40
[<ffffffc0000e5aec>] handle_percpu_devid_irq+0x7c/0xa0
[<ffffffc0000e1ba4>] generic_handle_irq+0x34/0x50
[<ffffffc000083aa8>] handle_IRQ+0x48/0xd0
[<ffffffc000080b5c>] gic_handle_irq+0x3c/0x7c
Exception stack(0xffffffc0e6db3e20 to 0xffffffc0e6db3f40)
3e20: e6db0000 ffffffc0 e6db0000 ffffffc0 e6db3f60 ffffffc0 00084260 ffffffc0
3e40: 00084250 ffffffc0 00000000 00000000 effce0cc ffffffc0 00000000 01000000
3e60: e6db0000 ffffffc0 00000000 00000000 ffffffff 00ffffff b43b7102 00000008
3e80: 3b9aca00 00000000 e6db3d80 ffffffc0 027683c0 00000000 000014a0 00000000
3ea0: 0000148f 00000000 0005f95d 00000000 0005f892 00000000 00000000 00000000
3ec0: 000d1a04 ffffffc0 00000000 00000000 000c3bed 00000000 e6db0000 ffffffc0
3ee0:

 

 

Can this be fixed, or am I dealing with a paperweight? (I get different errors from time to time. too many to list here)

11 REPLIES 11
AEK
Honored Contributor

It looks like hardware issue (probably disk corruption or RAM).

You may try format and install 7.0.11 (more stable). If the error persists then this may confirm a hardware failure.

AEK
AEK
S-K
New Contributor

Unfortunately, that doesn't change anything.

Kangming
Staff
Staff

Can try to format the CF card and load the image(v7.2.5GA) in the bios via tftp.

Thanks

Kangming

S-K
New Contributor

I have tried the formatting and TFTP the OS 3 times. and once it went to a boot loop and one of the other was this:

Connect to tftp server 192.168.1.120 ...


T ###############################################################################################################################################################################
Image Received.
Checking image... OK
This firmware image is certified!
Save as Default firmware/Backup firmware/Run image without saving:[D/B/R]?d

Programming the boot device now. The system must re-layout the boot device to install this firmware.
The default and backup firmware will be lost.
Continue:[Y/N]?
.. OK
Verifying... OK
.done


Booting OS...
Initializing firewall...

System is starting...
Resizing shared data partition...done
Formatting shared data partition ... done!
Starting system maintenance...
Scanning /dev/mmcblk0p1... (100%)
Scanning /dev/mmcblk0p3... (100%)


FortiGate-80F login: System file integrity monitor check failed!


The system is going down NOW !!

The system is halted.

 

this is what I get when it boot loops.

FortiGate-80F (17:33-07.27.2021)
Ver:05000025
Serial number: FGT80FTK
CPU: 1200MHz
Total RAM: 4 GB
Initializing boot device...
Initializing MAC... NP6XLITE#0
Please wait for OS to boot, or press any key to display configuration menu......

Booting OS...
Initializing firewall...

System is starting...
Starting system maintenance...
Scanning /dev/mmcblk0p1... (100%)
Scanning /dev/mmcblk0p3... (100%)


FortiGate-80F login:

FortiGate-80F login: fos_ima: fos_process_appraise 110: Executable File(/bin/init) doesn't match previous hash, it has been changed
fos_ima: fos_process_appraise 110: Executable File(/bin/init) doesn't match previous hash, it has been changed
Restarting system.


FortiGate-80F (17:33-07.27.2021)
Ver:05000025
Serial number: FGT80FTK
CPU: 1200MHz
Total RAM: 4 GB
Initializing boot device...
Initializing MAC... NP6XLITE#0
Please wait for OS to boot, or press any key to display configuration menu......

Booting OS...
Initializing firewall...

akristof

Hello,

Regarding this line "fos_ima: fos_process_appraise 110: Executable File(/bin/init) doesn't match previous hash, it has been changed" You should have this problem only on 7.2.5 (or 7.0.12, 6.4.13 probably). This is already under investigation as this is bug after new integrity check was introduced. So either go with 7.2.4 or open ticket for investigation.

Regarding 7.2.4 and kernel issue with File 0 missing, so far I never seen it. So I would just format the device, install fresh image and if anything, open sup ticket.

Adrian
S-K
New Contributor

I have installed 7.2.4 and on boot, I get this... it runs but I don't know if this is stable to be deployed. 

Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 208, path: /data/lib/libips.so
Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 262, path: /data/lib/libips.so
Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 208, path: /etc/ips.cfgscript.gz
Warning: Signature is missing or invalid. level:1, sign_status:2, pid: 208, path: /etc/ips.mudb.rules

akristof

Hello,

I am curious, can you share with me output:

get sys status

 

Based on the output, security level is still set to 1.

Adrian
S-K
New Contributor

get sys status
Version: FortiGate-80F v7.2.4,build1396,230131 (GA.F)
Firmware Signature: certified
Virus-DB: 1.00000(2018-04-09 18:07)
Extended DB: 1.00000(2018-04-09 18:07)
AV AI/ML Model: 0.00000(2001-01-01 00:00)
IPS-DB: 6.00741(2015-12-01 02:30)
IPS-ETDB: 0.00000(2001-01-01 00:00)
APP-DB: 6.00741(2015-12-01 02:30)
INDUSTRIAL-DB: 6.00741(2015-12-01 02:30)
IPS Malicious URL Database: 1.00001(2015-01-01 01:01)
IoT-Detect: 0.00000(2022-08-17 17:31)
Serial-Number: FGT80FTK
BIOS version: 05000025
System Part-Number: P25604-20
Log hard disk: Not available
Hostname: FortiGate-80F
Private Encryption: Disable
Operation Mode: NAT
Current virtual domain: root
Max number of virtual domains: 10
Virtual domains status: 1 in NAT mode, 0 in TP mode
Virtual domain configuration: disable
FIPS-CC mode: disable
Current HA mode: standalone
Branch point: 1396
Release Version Information: GA
System time: Mon Jul 28 12:42:46 1975
Last reboot reason: kernel panic

akristof

Hi,

There is something wrong with, not sure if flash wasn't formatted correctly, but this warning should not be visible on 7.2.4 or lower.

Adrian
Top Kudoed Authors