Firebox X500 shutdown issue!!!

periko

Hi guys.

I got a watchguard firebox x500, I setup pfsense 2.0.1 on a CF card, is working no issue here, I even had my null cable for the console, but I just got this on screen:

done.
Starting package squid…done.
Starting package RRD Summary...done.
Starting /usr/local/etc/rc.d/nrpe2.sh...done.
Starting /usr/local/etc/rc.d/proxy_monitor.sh...done.
Bootup complete

Is all I see, I have try to change some settings in my hyperterminal from windows but I had not had luck here.

The main issue is that I cannot shutdown my box, doesn't accept any shutdown command, the only one is shutdown -r now, the other flags say:

System shutdown time has arrived
but you'll have to do it yourself

I have to have my console open to see went I can turn off my box after a reboot command.

I had seen others people here in the list working with this box and they can interact with the serial console but don't know if they can turn off their boxes without issues?.

If some one could give me any tip I will appreciated, thanks!!!

stephenw10

The serial console issue is known.
There is a work around, serialbandaid.sh, see this post.
However this isn't working for me.
Some people have reported that installing 1.2.3 and then upgrading leaves the serial console operational.

Are you running the NanoBSD install? If you are you can just turn the box off.

Steve

Edit: This post has a better explanation from the scripts author.

periko

Yes, nano version, I will give a try and let u know, thanks stephew10 :)

Are you running the NanoBSD install? If you are you can just turn the box off.

If I do this, everytime I turn on the machine, u can see the famous message: / wasn't umount correctly :(

stephenw10

Whilst I agree that shuting down the system with shutdown -h now is the correct way to do this I have never had a problem on any firebox when running Nano.

In the NanoBSD install the filesystem on the CF is mounted read only and it runs almost entirely from ram. You could be very unlucky and switch it off just as it was writing some rrd data for instance.

I have just found a post from another user who said that he found the console menu could still be accessed but was running at 115,200 instead of 9,600. Might be worth trying that first.

Steve