This is a kernel message. I believe it is saying that the kernel can run in virtualised mode but as you are not it will ignore the mode. So it is just an informational warning, not an error.
This indicates that at some time you had a usb stick or some other disk drive formatted in FAT that was disconnected before it was unmounted. The warning here is that you might need to check that drive for potential corruption. This is not related to the IPFire disk drive as that runs in ext4, xfs or reiserfs depending on what you selectd when you installed IPFire originally.
With the words Unmatched Entries I suspect there were some more lines in the log after this line that listed what the unmatched entries are.
This would suggest some programs that are supposed to be started or stopped, depending when this message was created, were found not to have an entry in the initttab.d directory. That is either a corrupted error on the disk or a permissions problem.
This and the subsequent graphs lines suggest a permissions problem. Did you find these after an upgrade or when?
This indicates that you have set a fixed IP lease on the dhcp page but that ip (192.168.1.2) is also within the dynamic range that you have defined on that page.
Any fixed lease ip’s should not be in the dynamic range. See the Note: under IP Address in the following wiki page/section https://wiki.ipfire.org/configuration/network/dhcp#current-fixed-leases
No don’t use 192.168.1.3 It is in your dynamic range of 192.168.1.2 to 192.168.1.20
Use any number from 192.168.1.21 to 192.168.1.254
Then your fixed ip address will not be in the dynamic range.
Having a fixed ip in the dynamic range can work but at some time in the future depending on various circumstances you could end up with a problem where your pc will not be able to get its fixed ip because it will have been given to another machine as a dynamic ip.
Tell us what the list of unmatched entries were in the log. Then we can compare that with what you have in your inittab.d directory.
So also provide a listing of that directory
ls -hal /etc/inittab.d/
Then based on what we find we can decide if this is related to a permissions problem or to something else.
Were the following two entries in your log at or shortly after the upgrade from 157 to 158 was carried out. We need to see if those errors are related to that upgrade or come from prior to the upgrade.
I have changed dynamic range of 192.168.1.2 to 192.168.1.20 a dynamic range of 192.168.1.3 to 192.168.1.20
but is not good i change to 192.168.1.21 to 192.168.1.254 if you can confirm, thank you
That was my fault for not looking in the directory structure first.
As you point out there is no such thing as /etc/inittab.d/ and this is why there is a message in the log about the directory not being found. In that case I thing that message can be ignored unless you are having a problem with programs starting or stopping when doing a reboot.
So for this message
Are you having any problems with being able to see any of the graphs?
you underline, the /etc/inittab.d/ directory does not exist
if the /etc/inittab.d/ directory is working I’m in with winscp
i have look a permissions a /etc/inittab.d/
is /etc/init.d 0777 Is it good?
IPFire has the ability to run virtual machines using addons.
It looks like the processor you are using in your IPFire has the capability to run nested virtualisations.
This means that you could have IPFire in a virtualised system (not recommended for production systems, only for development test beds) and then run another virtualised system inside that.
However you are running your system on a physical machine and you don’t have any of the virtualisation addons installed so the kernel has the capability but there is nothing to use that capability.
