Firebox x1250e crash after upgrading
-
So got it to boot once. Now after turning it off and turning it on today I get:
(ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 51 8d 1d 46 00 00 00 00 01 00
(ada0:ata0:0:0:0): CAM status: ATA Status Error
(ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
(ada0:ata0:0:0:0): RES: 51 40 51 8d 1d 06 06 00 00 01 00And it just keeps going and going. I had it up and running for an hour before shutting it down for the night.
-
Hmm, looks a lot like this:
https://doc.pfsense.org/index.php/DMA_and_LBA_Errors#Fatal_Errors
How do you have the drive mounted? Could it be a loose cable or something similar?Steve
-
I started over, ill let you know what happens with a new install same drive. I do have another and another type of drive. I did secure the HDD in there so I would guess it the cable/adapter are not loose.
-
New install worked, but now I have to figure out why the LCD works, but shows no info
-
All I get on the LCD whether I use a custom package or install the one from packages through PFSense is
PFSense B8
Booting OS . . . . -
have you tried this ? ;)
https://forum.pfsense.org/index.php/topic,7920.msg344513.html#msg344513
-
If you're still seeing 'Booting OS' then the lcdproc daemon isn't starting at all. What have you tried?
Steve
-
Not much, I did find that thread but while under the whether I thought I would try moving the conf today. Got the custom LCD package from another member and only thing I get is this:
:file /path to conf file
Before installing the package or the custom LCD the LCD shows:
Booting OS….
Once installing the custom it adds:
PFSense B8 at the top.
Running the sh to start and stop the custom LCD it makes sounds when it starts and stops, but nothing on the LCD, the few times I got something to show up it was gibberish.
I did try after installing the package pulling the LCDProc, LCDExec and LCDd and putting it into the custom LCD package and now after reading that thread I wonder if its looking for the conf in the fix posted by SW10 since it was installed by PFSense. Any way to tell where the custom LCD package is looking for the conf? In about 1.5 hrs I am pulling the box back out and trying to tinker with it again so I will be able to provide more info on just having the custom LCD installed.
-
Just to confirm, when you say 'custom LCD package' do you mean software or hardware?
Steve
-
Software, was built from LCDProc package 0.5.6 on FreeBSD 10.1. One question, does the LCDd come from that same package? I noticed in the files I got the LCDd had an older date while the LCDProc and LCDExec show 02/2015.
-
Ok, with the custom LCDProc/Exec/LCDd installed I got some errors to go off of:
Error connecting to LCD server localhost on port 13666.
Check to see that the server is running and operating normally.
sock_connect: connect failed
lcdexec error connecting to server
Check to see that the server is running and operating normally.I am starting and stopping with a custom sh script. When I installed the package I got it to work but still no info besides the server connection screen and an options screen with very little options.
-
You are right SW10, its having issues starting, I am getting
Missing pbi options file: /usr/local/share/lcdd/LCDd.pbiopt
But this is a custom built LCD package and have no idea why it wants a pbi file. I may try to just copy over my conf files after installing LCDProc via the web gui.
-
Anyone know how to get mbmon installed on FreeBSD 10 or was it replaced and by what package?
I get manifest not found errors when trying to install the TBZ file. Google got me nothing on how to get past that error, most pointed to installing from a repo, but install lists no package available…
-
The drivers for the watchguard lcd are in the lcdproc_dev package as far as i know.
-
The client is reporting it cannot connect to the server. That's probably because the server isn't running for some reason. If it is running, and you have the correct driver selected, then you will see something on the LCD.
The two LCDproc packages have recently been rebuilt to address the PBI issues and are now both at 0.57.
There is an issue with IPv6 in which the client attempts to use the IPv6 localhost address which the server should be listening on but isn't for some reason. Let me see if I can find that post…...here:
https://forum.pfsense.org/index.php?topic=7920.msg484265#msg484265Steve
-
Hey SW10, on your firebox site where I got the BIOS, I saw and updated WPXepc file. I am using that one, are the other files listed what I can use to play with the code and build it?
-
I installed LCDProc from the packages list and did get to show info after a reboot. Anyway around having to reboot to get it to show info?
-
Yes the source for WGXepc is there at my googlesite.
I assume you installed lcdproc-dev? You mean you have to reboot the box repeatedly? If you're using the official package start method it should be started automatically (though it was very temperamental last time a tried it). You can restart it in Status > Services or by changing a setting in the lcdproc menu and saving it. Personally I don't run it like that because it starts 'sometimes' and crashes often! I do this:
https://forum.pfsense.org/index.php/topic,7920.msg344513.html#msg344513Steve
-
Ill use that cmd if I need to start it again, after installing, moving the conf and choosing the options it showed "pfsense starting" and until I rebooted the box it did not show the actual info chosen in the gui. Which file is the source? The one I pulled works just fine, I just wanted to learn more about that file since I was able to get the files for the custom LCD to play with and actually rebuild LCDd last night. Did you or do you know what the LED option for the LCD do? Does it use the ARM LED? I thought about giving it a try, but didnt want to have to reboot just to have the changes take affect.
-
Nevermind about MBMON, got it installed and working with my custom PHP status pages to show the temp of the box.
