Fatal Error Unable to create lock file: No space left on device (28)
-
Unable to access the pfsense via gui and so I connected via console. After typing exit I keep on getting this error (Fatal Error Unable to create lock file: No space left on device (28)) that keeps on looping and looping. This allows me to not type anything, and the fw is basically unresponsive. I suspect the disk space is full as I recently installed Snort and this log files must have filed up all the space, but I'm unable to get in and make the changes to fix this.
Urgent guidance is greatly appreciated! The FW acts as the DHCP for production PCs, and pcs are already losing connection and not able to renew their leases.
-
@srgwilliams your best chance is rebooting the firewall while connected to the console (not SSH but physically to the machine).
And then boot into single user mode - boot menu entry 2 - and check and remove the snort logfile (in directory /var/log/snort/) if that is the reason. Your issue could also be a failing disk.
-
I was able to power cycle using the button on the phyiscal fw after production was done for the day, and Iwas able to communicate with the fw again.
now the issue is that the fw which is the dchp has not started issuing and renewing ips normally, what would you suggest could be a fix? -
@srgwilliams said in Fatal Error Unable to create lock file: No space left on device (28):
now the issue is that the fw which is the dchp has not started issuing and renewing ips normally, what would you suggest could be a fix?
It seems you booted into an older ZFS snapshot now. Is that on purpose?
Your prompt reads 23.09-RELEASE now and first it was 25.07.1-RELEASE. Switching the snapshot also includes the config which may or may not be different to your configuration before.
-
@patient0 no this was not on purpose. Booted automatically, it was the first time I was able to have any type of info entered into the firewall again. I appreciate your quick replies. How would I boot up into the previous snapshot 25.07.1?
-
@srgwilliams said in Fatal Error Unable to create lock file: No space left on device (28):
How would I boot up into the previous snapshot 25.07.1?
At the boot menu, entry 8 is "Boot Environments" where you can choose which snapshot you want to boot from.
Netgate Documentation: Selecting Boot Environments in the Loader Menu
Btw: if in the 25.07.1 you may still get the out of space issue. In that case you will have to reboot into the single user mode. Since no services are being startet in that mode you may have a better chance to delete the snort log.
-
@patient0
I tried booting into the different boot environment. It's not showing all the information I believe. I haven't done this process before but I don't think it's supposed to look like thisAfter hitting pause
After hitting 8
After hitting up key to cycle to 2 out of 7
3 out of 7
4 out of 7
and so forth for 5,6,7.
Do I disregard all this and just try troubleshooting in the single user mode?
-
@srgwilliams said in Fatal Error Unable to create lock file: No space left on device (28):
Do I disregard all this and just try troubleshooting in the single user mode?
You do have to select the right snapshot otherwise you are ending up cleaning up another snapshot.
The snapshot/boot environment naming contains the date and time, e.g. default_20251004112311 would be 04 October 2025 11:23:11.
But the lasted boot environment is usually called 'default' which would be 3 of 7 in your case.
I see you tried number 3 and it did not boot but automatically reboot?
If you get it to boot into 23.09 that be a start if you can access the GUI from there and check the boot environments. In the GUI you see the pfSense+ version.
If you have lots of snapshot - let's say older than 23.09 - you can make space be deleting at least one of them. That maybe is enough to reboot successfully into 25.07.1. Don't delete any of 23., 24. or 25.* yet.
-
@srgwilliams
Is the GUI still accessible? When you boot into 23.09-RELEASE? Go to the System - Boot environments and post the screenshot. -
And maybe check if you have all information for a potential reinstall:
- pfSense+ installation ISO/USB or other image
- the new installer need internet connection: WAN settings will be needed
- configuration backup
If Automatic Configuration Backup is/was enabled (maybe you can check when it's possible to boot into an older snapshot) then you would need the device key and the encryption password. With these infos you can restore the latest backup if no current config backup file is available.
-
@patient0 @w0w No I'm not able to access the GUI. When I load into 1/7 I have internet connection but still not able to access the gui.
After loading 3/7 again, it has loaded into 25.07.1-Release and I am able to see my configured interfaces for my vlan again
The fw is still not issuing IPs, though.
-
If you're here :
then : option 8.
Thencd /var/log/look (use ls -al) for any 'snort' log files. Maybe its using a sub folder, if so :
cd snort ls -alIf you find some big log files 'kill them all' ^^
-
@srgwilliams said in Fatal Error Unable to create lock file: No space left on device (28):
The fw is still not issuing IPs, though.
Have you cleared out space? And if yes restart the GUI (11).
If DHCP is not giving out IPs and you can't access the GUI because the client doesn't get an IP, you can set a static IP on your client in the same IP range and try again.
-
@Gertjan said in Fatal Error Unable to create lock file: No space left on device (28):
cd /var/log/
okay, this doesn't seem to do anything though
@patient0 said in Fatal Error Unable to create lock file: No space left on device (28):
Have you cleared out space? And if yes restart the GUI (11).
haven't cleared out any space on this snapshot but this is how space looks currently
-
I believe the dhcp service wasn't working due to lack of memory but I'm not sure anymore
I've already tried statically assigning ips from clients on each vlan but that doesn't seem to work
-
For context. I have a pc that I connect to the firewall through Anydesk. It isolated to disclose the fw log in page (for PCI requirement). This pc and the fw is on the 92.x subnet. The pc is normally 92.3 and the fw 92.1
-
@srgwilliams and does it work now?
You can check if the GUI service is running by issuing on the firewall (if it runs on the standard ports:
[25.11-RELEASE][root@pfp.home.arpa]/root: sockstat | egrep ':(80|443)' root nginx 84995 5 tcp4 *:443 *:* root nginx 84995 6 tcp6 *:443 *:* root nginx 84995 7 tcp4 *:80 *:* root nginx 84995 9 tcp6 *:80 *:* root nginx 84900 5 tcp4 *:443 *:* root nginx 84900 6 tcp6 *:443 *:* root nginx 84900 7 tcp4 *:80 *:* root nginx 84900 9 tcp6 *:80 *:* root nginx 84524 5 tcp4 *:443 *:* root nginx 84524 6 tcp6 *:443 *:* root nginx 84524 7 tcp4 *:80 *:* root nginx 84524 9 tcp6 *:80 *:*@srgwilliams said in Fatal Error Unable to create lock file: No space left on device (28):
This pc and the fw is on the 92.x subnet. The pc is normally 92.3 and the fw 92.1
Mmmh, that is odd, can you ping the firewall 93.1 from the 92.3 client? And the other way around, can you ping the 92.3 client?
are the LAN (lan) -> lagg0.4091 (or which ever interface you are connecting to) IPs shown correct?
-
That's the thing. At this company they chose to have not to enable ICMP so I'm not able to ping anything, which is frustrating at times.
The WAN is correct. The LAN lagg.4091 is 192.168.92.1/29 which is correct
-
@srgwilliams said in Fatal Error Unable to create lock file: No space left on device (28):
The GUI is listening then, that looks ok
At this company they chose to have not to enable ICMP so I'm not able to ping anything
Can you
ncat -v 192.168.92.1 443from the client? You're supposed to be on the same broadcast domain as the router, that should work. Have you used that client before, no Windows firewall active?And anything in the /var/log/nginx.log that indicates you're connection attempt?
-
@patient0 said in Fatal Error Unable to create lock file: No space left on device (28):
ncat -v 192.168.92.1 443 from the client?
I get Ncat: TIMEOUT
but no Windows Firewall active
@patient0 said in Fatal Error Unable to create lock file: No space left on device (28):
/var/log/nginx.log
I get an access denied message unfortunately.
Privacy Policy · Cookie Policy