Fatal Error Unable to create lock file: No space left on device
-
@bdjackson check for deleteable boot environments:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-shrink.htmlOr
https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-usage.html -
Neither worked. Does not complete a boot. I can get to the Marvell> prompt and that is about it.
Brent
-
@bdjackson Hmm that makes it difficult to do much I suppose. Reinstalling is probably the quickest way back. Then restore from a backup config file.
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html
The lock file message is showing at boot then?
-
Yes. Lock file at boot.
Brent
-
I also received this error on my SG2100 after attempting to update to 24.03. I can't do anything except get into the shell via console. Every other option gives me the error:
Fatal Error Unable to create lock file: No space left on device (28)
I looked at the documents posted by @SteveITS but not very helpful. Any other options than reinstalling?
I was able to get into Single User Mode and attempted to run
fsck -fy /but I received this error message:fsck: cannot open `pfSense/ROOT/default_20240426094800': No such file or directory
Any ideas?
-
Run:
bectl list -
BE Active Mountpoint Space Created
auto-default-20230628094454 - - 589M 2023-06-28 09:44
auto-default-20230628102402 - - 829M 2023-06-28 10:24
auto-default-20240223110046 - - 885M 2024-02-23 11:00
auto-default-20240407101025 - - 563M 2024-04-07 10:10
default - - 1.10G 2024-04-26 09:48
default_20240426094800 NR / 4.98G 2022-06-22 15:27 -
@jlrobinson2171 Delete some of those, for instance the 2022 and 2023 ones.
bectl destroy default_20240426094800
or auto-default-20230628094454, etc.
If it isn't a 2100 max then it's only an 8 GB disk.
-
Yup I would delete those first two BEs and then reboot.
The 2022 BE is the one marked for next boot though so I would not delete that.
If it still fails you can try activating the most recent BE (2024-04-07). That is probably the one created at the last upgrade/attempt.
-
@SteveITS and @stephenw10
Thank you for your assistance. After removing just one, I was able to reboot and log back in.
-
Found this through Google after I ran into the same issue with my SG-2100. Managed to resolve by following the instructions here, thanks!
Maybe the installer should do a check for sufficient space before continuing and when necessary provide an option to cleanup old instances to prevent this happening in the future?
-
-
@SteveITS Thank you very much for the response. You rescued us.
