For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

purna_256577's avatar
purna_256577
Icon for Nimbostratus rankNimbostratus
Jul 13, 2017

We are getting error "maximal mount count reached, running e2fsck is recommended"

We are getting error "maximal mount count reached, running e2fsck is recommended" in /var/log/kern.log, we don't see f5 is booted for 300 + days. any recommendation in f5, version is 11.x.  
BIG-IP
devops
LTM
security
purna_256577's avatar
purna_256577
Icon for Nimbostratus rankNimbostratus
Jul 17, 2017

I have further checked with senior engineer , below are the findings

 

"warning kernel: EXT2-fs warning: maximal mount count reached, running e2fsck is recommended"

 

The BIG-IP system is counting mount times for filesystems and if it reached to maximum counts then system will log this messages in /var/log/kern.log to recommend to run e2fsck. This is just a notification that system recommend to run an e2fsck to check whether the Disk and the filesystem has problem or not when you reached maximum mount count.

 

You may safely ignore this message as it won't affect any system operation. Or you may consider to force the BIG-IP to run a file system check. Please refer to the below solution for more details: K10328: Forcing a file system check on the next system reboot (10.x - 11.x) https://support.f5.com/csp/article/K10328