[pfSense Support] pfsense 1.2.3 problem with vpn ipsec (can ping, but nothing else ?)
Hi, I've upgraded to the 1.2.3 version on one end, and have a monowall at my end... whenever I ping a host over the tunnel, they reply... But doing anything else (http, rdp, ...) it simply does nothing at all ! (eventually, I got a timeout) - but the tunnel is up, and I can ping. My rules on the firewall are on both ends setup to allow all traffic (since both networks are trusted to each other) - any ideas ? The issue why I upgraded to 1.2.3 is somewhat funny... I had a 1.2.1rc1, that I wanted to upgrade to 1.2.2 remotely... but it never came up again (so I drove over to the company, to do a manual upgrade, but since I had no internet at the office, and only my latest revision to test on my home-box, I decided to put it on the production server) In my effort in trying to solve this, I removed the tunnel on both sides, deleted the rules - and recreated them... on the pfsense I got this when making a small change to the new tunnel : Warning: unlink(/tmp/spd.conf.reload.1233394121.y9DXI8): No such file or directory in /etc/inc/vpn.inc on line 1193 kind regards, Michel - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] pfsense 1.2.3 problem with vpn ipsec (can ping, but nothing else ?)
look at this http://forum.pfsense.org/index.php/topic,13847.0.html On Sat, Jan 31, 2009 at 10:37 AM, Michel Servaes mic...@mcmc.be wrote: Hi, I've upgraded to the 1.2.3 version on one end, and have a monowall at my end... whenever I ping a host over the tunnel, they reply... But doing anything else (http, rdp, ...) it simply does nothing at all ! (eventually, I got a timeout) - but the tunnel is up, and I can ping. My rules on the firewall are on both ends setup to allow all traffic (since both networks are trusted to each other) - any ideas ? The issue why I upgraded to 1.2.3 is somewhat funny... I had a 1.2.1rc1, that I wanted to upgrade to 1.2.2 remotely... but it never came up again (so I drove over to the company, to do a manual upgrade, but since I had no internet at the office, and only my latest revision to test on my home-box, I decided to put it on the production server) In my effort in trying to solve this, I removed the tunnel on both sides, deleted the rules - and recreated them... on the pfsense I got this when making a small change to the new tunnel : Warning: unlink(/tmp/spd.conf.reload.1233394121.y9DXI8): No such file or directory in /etc/inc/vpn.inc on line 1193 kind regards, Michel - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org -- Ermal - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] pfsense 1.2.3 problem with vpn ipsec (can ping, but nothing else ?)
G R E A T, many thanks - this works out just like pointed out in this forum!!! On Sat, Jan 31, 2009 at 11:22 AM, Ermal Luçi ermal.l...@gmail.com wrote: look at this http://forum.pfsense.org/index.php/topic,13847.0.html On Sat, Jan 31, 2009 at 10:37 AM, Michel Servaes mic...@mcmc.be wrote: Hi, I've upgraded to the 1.2.3 version on one end, and have a monowall at my end... whenever I ping a host over the tunnel, they reply... But doing anything else (http, rdp, ...) it simply does nothing at all ! (eventually, I got a timeout) - but the tunnel is up, and I can ping. My rules on the firewall are on both ends setup to allow all traffic (since both networks are trusted to each other) - any ideas ? The issue why I upgraded to 1.2.3 is somewhat funny... I had a 1.2.1rc1, that I wanted to upgrade to 1.2.2 remotely... but it never came up again (so I drove over to the company, to do a manual upgrade, but since I had no internet at the office, and only my latest revision to test on my home-box, I decided to put it on the production server) In my effort in trying to solve this, I removed the tunnel on both sides, deleted the rules - and recreated them... on the pfsense I got this when making a small change to the new tunnel : Warning: unlink(/tmp/spd.conf.reload.1233394121.y9DXI8): No such file or directory in /etc/inc/vpn.inc on line 1193 kind regards, Michel - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org -- Ermal - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] 1.2.2 TCP Disconnects (sessions)
are these on a managed switch so you can see if there are any errors, short frames, overruns etc? One of the offices has a semi-managed switch, on which, looking at the stats I can't see anything obviously wrong. The other office just has an el-cheapo 5 port switch. do you have tcp hand-off, polling or other option enabled? Hardware offloading is enabled. Polling is disabled. The pfSense boxes in question are ALIX 2c0 boards, and the options (offloading on, polling off) are the same as the settings on the 1.2-RELEASE boxes. MTU problems (unlikely)? None that I can see. I can try upgrading the pfSense box (same hardware) at my home to 1.2.2 this weekend and see if I can introduce the same issue, if that's of any help diagnosing the issue? Regards, Chris - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] 1.2.2 TCP Disconnects (sessions)
Thanks for your thoughts on this one. For me, it ended up being a dotnet application pool issue on the server set to 60 minutes instead of a specific time or 24 hours :). Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com On Sat, Jan 31, 2009 at 8:36 AM, Chris Bagnall li...@minotaur.cc wrote: are these on a managed switch so you can see if there are any errors, short frames, overruns etc? One of the offices has a semi-managed switch, on which, looking at the stats I can't see anything obviously wrong. The other office just has an el-cheapo 5 port switch. do you have tcp hand-off, polling or other option enabled? Hardware offloading is enabled. Polling is disabled. The pfSense boxes in question are ALIX 2c0 boards, and the options (offloading on, polling off) are the same as the settings on the 1.2-RELEASE boxes. MTU problems (unlikely)? None that I can see. I can try upgrading the pfSense box (same hardware) at my home to 1.2.2 this weekend and see if I can introduce the same issue, if that's of any help diagnosing the issue? Regards, Chris - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
AW: [pfSense Support] Squid / swap.state issue
Try using the log-rotate-feature... So every night your swap.state should be compacted... Are you on the latest pfsense release and the newest squid package ? Regards, Martin -Ursprüngliche Nachricht- Von: Wayne Langdon [mailto:wa...@langdon.co.za] Gesendet: Freitag, 30. Januar 2009 05:40 An: support@pfsense.com Betreff: [pfSense Support] Squid / swap.state issue Hi, Yesterday I encountered a concerning problem with my pfSense 1.2 box. I added a site to my Squid access list to be blocked which worked perfectly. However shortly thereafter users where unable to use the proxy (all sites timedout). Disabling the proxy worked fine. When I disabled the transparent mode on the proxy, they also appeared to be able to browse for a while. What also appeared strange is that the error was not consistent to all users, some could work and some not. I later found that my swap.state file had suddenly increased to 109gb causing my disk to be 100%. Can anyone advise as to whether they have experienced this and perhaps the cause for this as I do need this site blocked but for now have allowed access to it again. Thank you in advance, Wayne. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] 1.2.2 TCP Disconnects (sessions)
Thanks for your thoughts on this one. For me, it ended up being a dotnet application pool issue on the server set to 60 minutes instead of a specific time or 24 hours :). Just to confirm, are you saying that 1.2.2 has definitely *not* introduced any new issues in your environment? Regards, Chris - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] 1.2.2 TCP Disconnects (sessions)
On Sat, Jan 31, 2009 at 3:15 PM, Chris Bagnall li...@minotaur.cc wrote: Thanks for your thoughts on this one. For me, it ended up being a dotnet application pool issue on the server set to 60 minutes instead of a specific time or 24 hours :). Just to confirm, are you saying that 1.2.2 has definitely *not* introduced any new issues in your environment? That's what it sounds like, the issues he noted weren't anything like the ones you and LJ noted in this thread. If there are issues, they aren't widespread. Between our developers and commercial support customers, I know many of the biggest installs out there are on 1.2.2 and have no issues. The mail issue noted in this thread and the issues you noted, Chris, sound like they could be state keeping regressions for some rare edge cases. I'm curious if the newer FreeBSD in 1.2.3 snapshots changes anything, but recommend approaching it with caution as the change to 7.1 isn't widely tested yet. I know 7.1 has fixed hardware regressions from 6.2 to 7.0 for multiple people, and there are many people running it without problems, but still approach with caution at this point. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] 1.2.2 TCP Disconnects (sessions)
Confirmed... pfSense 1.2.2 has NOT had an adverse effect on our network. The problem was found on the Web server and has been 100% verified as the root cause. Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com On Sat, Jan 31, 2009 at 2:45 PM, Chris Buechler c...@pfsense.org wrote: On Sat, Jan 31, 2009 at 3:15 PM, Chris Bagnall li...@minotaur.cc wrote: Thanks for your thoughts on this one. For me, it ended up being a dotnet application pool issue on the server set to 60 minutes instead of a specific time or 24 hours :). Just to confirm, are you saying that 1.2.2 has definitely *not* introduced any new issues in your environment? That's what it sounds like, the issues he noted weren't anything like the ones you and LJ noted in this thread. If there are issues, they aren't widespread. Between our developers and commercial support customers, I know many of the biggest installs out there are on 1.2.2 and have no issues. The mail issue noted in this thread and the issues you noted, Chris, sound like they could be state keeping regressions for some rare edge cases. I'm curious if the newer FreeBSD in 1.2.3 snapshots changes anything, but recommend approaching it with caution as the change to 7.1 isn't widely tested yet. I know 7.1 has fixed hardware regressions from 6.2 to 7.0 for multiple people, and there are many people running it without problems, but still approach with caution at this point. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] Problem when rebooting... Embedded on ALIX
I have managed (thanks to help on this list) to get my ALIX board running a full install of pfSense on 8GB CF card, so that I could enable Snort service (default install with embedded kernel). I ran into the problem of it downloading the snort rules and it would fail. After adjusting the time timeouts, it managed to finally update. Doing this remotely, I adjusting the time periods forced me to reboot, via the terminal pfsense menu option. After waiting 5 minutes, I couldn't reconnect. Argh, I had to into the datacenter. When I looked at the terminal, the following was on screen (I couldn't capture everything). + Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6 Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6Enter the LAN interface name or 'a' for auto-detection: Network interface mismatch -- Running interface assignment option. Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6 Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6 Valid interfaces are: vr0 00:0d:b9:16:1c:f4 vr1 00:0d:b9:16:1c:f5 Do you want to set up VLANs first? If you are not going to use VLANs, or only for optional interfaces, you should say no here and use the webConfigurator to configure VLANs later, if required. Do you want to set up VLANs now [y|n] Looked like it lost all my settings. I unplugged the pfSense box at this point, and then plugged it back in. It seemed to have found the lost settings this time. Below is the bootup sequence. + ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: EHCI (generic) USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: AMD EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1 uhub1: 4 ports with 4 removable, self powered orm0: ISA Option ROM at iomem 0xe-0xea7ff pnpid ORM on isa0 ppc0: parallel port not found. sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled RTC BIOS diagnostic error 80clock_battery Timecounter TSC frequency 498053972 Hz quality 800 Timecounters tick every 10.000 msec Fast IPsec: Initialized Security Association Processing. ad0: 7815MB SanDisk SDCFH2-008G HDX 4.32 at ata0-master WDMA2 Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ___ ___/ f \ / p \___/ Sense \___/ \ \___/ Welcome to pfSense 1.2.2 on thWe 'pfSense' platAform... RMounting filesysNtems...ING: R/W mount of / denied. Filesystem is not clean - run fsck mount: W/dev/ad0s1a A: RNING: R/W mount of / denied. Filesystem is not clean - run fsck Operation not permitted mount: : Operation not permitted ** /dev/ad0s1a ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=23595 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23596 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23597 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23598 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23600 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes SUMMARY INFORMATION BAD SALVAGE? yes BLK(S) MISSING IN BIT MAPS SALVAGE? yes 4058 files, 50393 used, 962618 free (210 frags, 120301 blocks, 0.0% fragmentatio n) * FILE SYSTEM MARKED CLEAN * * FILE SYSTEM WAS MODIFIED * done. Creating symlinks..done. Launching PHP init system... done. Does anyone know why it would have lost all settings when it rebooted? Yet another reboot and it's working. Unfortunately, I don't have the full first reboot screen capture (so I didn't see any errors about the flash). So unsure if the CF flash was the cause of the problems. The manual power on/off might explain the second screen capture of not being shut down properly. Are there any know issues that might cause this or suggestions on how to figure out what's going on? I'd really like to be able to reboot it remotely without having to go into the datacenter. Regards, Chuck
Re: [pfSense Support] Problem when rebooting... Embedded on ALIX
On Sat, Jan 31, 2009 at 8:31 PM, Chuck Mariotti cmario...@xunity.com wrote:
I have managed (thanks to help on this list) to get my ALIX board running a
full install of pfSense on 8GB CF card, so that I could enable Snort service
(default install with embedded kernel).
I ran into the problem of it downloading the snort rules and it would fail.
After adjusting the time timeouts, it managed to finally update.
Doing this remotely, I adjusting the time periods forced me to reboot, via
the terminal pfsense menu option. After waiting 5 minutes, I couldn't
reconnect. Argh, I had to into the datacenter.
When I looked at the terminal, the following was on screen (I couldn't
capture everything).
+
Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on
line 32
6
Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on
line 32
6Enter the LAN interface name or 'a' for auto-detection:
Network interface mismatch -- Running interface assignment option.
Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on
line 32
6
Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on
line 32
6
Valid interfaces are:
vr0 00:0d:b9:16:1c:f4
vr1 00:0d:b9:16:1c:f5
Do you want to set up VLANs first?
If you are not going to use VLANs, or only for optional interfaces, you
should
say no here and use the webConfigurator to configure VLANs later, if
required.
Do you want to set up VLANs now [y|n]
Looked like it lost all my settings. I unplugged the pfSense box at this
point, and then plugged it back in. It seemed to have found the lost
settings this time. Below is the bootup sequence.
+
ehci0: [ITHREAD]
usb1: EHCI version 1.0
usb1: companion controller, 4 ports each: usb0
usb1: EHCI (generic) USB 2.0 controller on ehci0
usb1: USB revision 2.0
uhub1: AMD EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1
uhub1: 4 ports with 4 removable, self powered
orm0: ISA Option ROM at iomem 0xe-0xea7ff pnpid ORM on isa0
ppc0: parallel port not found.
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
RTC BIOS diagnostic error 80clock_battery
Timecounter TSC frequency 498053972 Hz quality 800
Timecounters tick every 10.000 msec
Fast IPsec: Initialized Security Association Processing.
ad0: 7815MB SanDisk SDCFH2-008G HDX 4.32 at ata0-master WDMA2
Trying to mount root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted
___
___/ f \
/ p \___/ Sense
\___/ \
\___/
Welcome to pfSense 1.2.2 on thWe 'pfSense' platAform...
RMounting filesysNtems...ING: R/W mount of / denied. Filesystem is not
clean -
run fsck
mount: W/dev/ad0s1a A: RNING: R/W mount of / denied. Filesystem is not
clean -
run fsck
Operation not permitted
mount: : Operation not permitted
** /dev/ad0s1a
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=23595 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 31 00:49 2009
CLEAR? yes
UNREF FILE I=23596 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 31 00:49 2009
CLEAR? yes
UNREF FILE I=23597 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 31 00:49 2009
CLEAR? yes
UNREF FILE I=23598 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 31 00:49 2009
CLEAR? yes
UNREF FILE I=23600 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 31 00:49 2009
CLEAR? yes
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? yes
SUMMARY INFORMATION BAD
SALVAGE? yes
BLK(S) MISSING IN BIT MAPS
SALVAGE? yes
4058 files, 50393 used, 962618 free (210 frags, 120301 blocks, 0.0%
fragmentatio
n)
* FILE SYSTEM MARKED CLEAN *
* FILE SYSTEM WAS MODIFIED *
done.
Creating symlinks..done.
Launching PHP init system... done.
Does anyone know why it would have lost all settings when it rebooted? Yet
another reboot and it's working.
Unfortunately, I don't have the full first reboot screen capture (so I
didn't see any errors about the flash). So unsure if the CF flash was the
cause of the problems. The manual power on/off might explain the second
screen capture of not being shut down properly.
Are there any know issues that might cause this or suggestions on how to
figure out what's going on? I'd really like to be able to reboot it remotely
without having to go into the datacenter.
Not sure what happened but your interfaces configuration was zapped it appears:
foreach($config['interfaces'] as $name = $int) {
[pfSense Support] RE: Problem when rebooting... Embedded on ALIX
I should add, that I have rebooted 5 times since then without issue. From: Chuck Mariotti [mailto:cmario...@xunity.com] Sent: Saturday, January 31, 2009 8:31 PM To: support@pfsense.com Subject: [pfSense Support] Problem when rebooting... Embedded on ALIX I have managed (thanks to help on this list) to get my ALIX board running a full install of pfSense on 8GB CF card, so that I could enable Snort service (default install with embedded kernel). I ran into the problem of it downloading the snort rules and it would fail. After adjusting the time timeouts, it managed to finally update. Doing this remotely, I adjusting the time periods forced me to reboot, via the terminal pfsense menu option. After waiting 5 minutes, I couldn't reconnect. Argh, I had to into the datacenter. When I looked at the terminal, the following was on screen (I couldn't capture everything). + Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6 Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6Enter the LAN interface name or 'a' for auto-detection: Network interface mismatch -- Running interface assignment option. Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6 Warning: Invalid argument supplied for foreach() in /etc/inc/util.inc on line 32 6 Valid interfaces are: vr0 00:0d:b9:16:1c:f4 vr1 00:0d:b9:16:1c:f5 Do you want to set up VLANs first? If you are not going to use VLANs, or only for optional interfaces, you should say no here and use the webConfigurator to configure VLANs later, if required. Do you want to set up VLANs now [y|n] Looked like it lost all my settings. I unplugged the pfSense box at this point, and then plugged it back in. It seemed to have found the lost settings this time. Below is the bootup sequence. + ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: EHCI (generic) USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: AMD EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1 uhub1: 4 ports with 4 removable, self powered orm0: ISA Option ROM at iomem 0xe-0xea7ff pnpid ORM on isa0 ppc0: parallel port not found. sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled RTC BIOS diagnostic error 80clock_battery Timecounter TSC frequency 498053972 Hz quality 800 Timecounters tick every 10.000 msec Fast IPsec: Initialized Security Association Processing. ad0: 7815MB SanDisk SDCFH2-008G HDX 4.32 at ata0-master WDMA2 Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ___ ___/ f \ / p \___/ Sense \___/ \ \___/ Welcome to pfSense 1.2.2 on thWe 'pfSense' platAform... RMounting filesysNtems...ING: R/W mount of / denied. Filesystem is not clean - run fsck mount: W/dev/ad0s1a A: RNING: R/W mount of / denied. Filesystem is not clean - run fsck Operation not permitted mount: : Operation not permitted ** /dev/ad0s1a ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=23595 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23596 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23597 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23598 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes UNREF FILE I=23600 OWNER=root MODE=100644 SIZE=0 MTIME=Jan 31 00:49 2009 CLEAR? yes ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes SUMMARY INFORMATION BAD SALVAGE? yes BLK(S) MISSING IN BIT MAPS SALVAGE? yes 4058 files, 50393 used, 962618 free (210 frags, 120301 blocks, 0.0% fragmentatio n) * FILE SYSTEM MARKED CLEAN * * FILE SYSTEM WAS MODIFIED * done. Creating symlinks..done. Launching PHP init system... done. Does anyone know why it would have lost all settings when it rebooted? Yet another reboot and it's working. Unfortunately, I don't have the full first reboot screen capture (so I didn't see any errors about the flash). So unsure if the CF flash was the cause of the problems. The manual power on/off might explain the second screen capture of not being shut down properly. Are there any know issues that might cause this or suggestions on how to figure out what's going on? I'd really like to be able to reboot it remotely without having to go into the datacenter. Regards, Chuck
