Update to 2.1 Nano, 'file system full'.
-
I am having a similar issue upgrading from 2.03 to 2.1 on an Alix 2D3 w/4 GB card and nano image:
Both procedures below end up with the following errors:
Generating RRD graphs...done. Updating configuration...............Generating RRD graphs...done. ...Update RRD database wan-traffic.rrd. Update RRD database wan-packets.rrd. Update RRD database lan-traffic.rrd. Update RRD database lan-packets.rrd. Update RRD database ipsec-traffic.rrd. Update RRD database ipsec-packets.rrd. Generating RRD graphs...done. pid 786 (rrdtool), uid 0 inumber 2050 on /var: filesystem full /var: write failed, filesystem is full ....done.
At reboot I get:
Enter an option: pfSense is now shutting down ... /var: write failed, filesystem is full /var: write failed, filesystem is full Sep 16 18:26:51 lighttpd[33063]: (server.c.1546) server stopped by UID = 0 PID = 1
Procedures (How I got the errors:)
1. Auto upgrade using webgui (2.03 -> 2.1)
2a. Backup 2.03 config
2b. Wipe SD card; flash 2.1
2c. Restore 2.03 configSo it seems that I have no good upgrade path from 2.03 to 2.1 unless I'm missing something. Also, following a 2.1 upgrade, I get following at subsequent boots:
Generating RRD graphs...ERROR: No tag found ERROR: Incompatible file version, detected version . This is not supported by the version 0003 restore tool. ERROR: Incompatible file version, detected version . This is not supported by the version 0003 restore tool. ERROR: Incompatible file version, detected version . This is not supported by the version 0003 restore tool. ERROR: Incompatible file version, detected version . This is not supported by the version 0003 restore tool. done.
Many thanks in any help with this.
-
I assume you mean CF card not SD?
I had those RRD incompatible version errors. They didn't seem to cause much of a problem. I think lost some traffic data from one WAN. Only had it one one boot though.
Steve
-
Hmm, may have spoken too soon:
Sep 18 00:00:05 kernel: pid 60237 (rrdtool), uid 0 inumber 4091 on /var: filesystem full Sep 18 00:00:04 kernel: pid 59098 (rrdtool), uid 0 inumber 4084 on /var: filesystem full
Time to increase /var perhaps.
Steve
-
Ohhhhhhhh how the mighty have fallen… ;D
Give it 10 minutes of tinkering and you will be all aces again ;)
-
I got too system full but my hard disk had 29G free ???
-
Hmm, odd. You hadn't chosen to use a ramdisk for /var?
Steve
-
No flash drives, no ram disks here:
[root@xxx]/root: mount
/dev/ad0s1a on / (ufs, local)
devfs on /dev (devfs, local)
/dev/md0 on /var/run (ufs, local)
devfs on /var/dhcpd/dev (devfs, local)[root@xxx]/root: df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s1a 35G 2.8G 29G 9% /
devfs 1.0k 1.0k 0B 100% /dev
/dev/md0 3.6M 48k 3.3M 1% /var/run
devfs 1.0k 1.0k 0B 100% /var/dhcpd/dev -
Has anyone found an answer to this, i'm in the same boat as NetVicious, except I have a 236GB Hdd i'm running the firewall off with 4Gb ram, i'm to scared to reboot as my whole network uses this firewall, its currently My internet connection, and bridges 3 networks together, Cant run the WEB gui, i get Fatal error: Unknown: apc_fcntl_rdlock failed: in Unknown on line 0 the Firewall monitor is also saying something about the Hdd's Inode's hard drive formatted incorrectly? not sure.
Any one fixed it? -
I fixed the errors I was seeing by expanding /var from 60 to 80MB. Your problem looks bigger than that though.
Steve
Edit: typo
-
On my Alix I did not find a solution. I finally reflashed my compact flash card with a fresh pfSense 2.1. I've described this besides other experiences in this thread: http://forum.pfsense.org/index.php/topic,68531.0.html.
As my WLAN card remains dead after upgrading I am currently forced to stay with pfSense 2.0.3.
-
I fixed the errors I was seeing by expanding /var from 60 to 80MB. Your problem looks bigger than that though.
Steve
Edit: typo
Can you tell me how? I have the same problem. It raises when I configure IGMP Proxy on a clean install of 2.1.
When I delete the two gateways, everything runs normal….Matthias
-
There's an option to do it in System: Advanced: Miscellaneous:
You have to reboot to see the change.Steve