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 0xe0000-0xea7ff pnpid ORM0000 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 80<clock_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

Reply via email to