The pfSense Store

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - w0w

Pages: [1] 2 3 4 5 ... 36
1
 I know that Asrock Rack boards do really have this problem  - even if you have dedicated port for IPMI, the first port is also shared for IPMI, this can cause a lot of problems, like huge packet loss or non working IPMI, bit I am not sure is this applicable to supermicro boards also.

2
General Questions / Re: Two Problems
« on: November 21, 2017, 09:53:04 pm »
Does it answer your second question? Do you running pfSense on VM?

3
Official pfSense Hardware / Re: Bricked SG-2220
« on: November 18, 2017, 11:12:35 pm »
I would contact Netgate. I'd guess it had the same Atom bug as the 2440 and larger Rangely boxes. If you didn't update the bios to fix it, it may indeed be bricked. IIRC, they are covering Atom failures for three years from purchase, but contact them to confirm.
There is no any BIOS fix regarding AVR54, it's a hardware bug.

You are only partially right.
as ADI boards don't use SERIQ bus , AVR54 can be mitigated by powering off this bus. and that exacly bios update i think .12 is doing.
It's not solving problem permanentny but prolongs life of affected CPU.
Exactly. You are right, the description of BIOS update was not clear enough and I've missed the point.

4
Official pfSense Hardware / Re: Bricked SG-2220
« on: November 18, 2017, 06:06:59 am »
I would contact Netgate. I'd guess it had the same Atom bug as the 2440 and larger Rangely boxes. If you didn't update the bios to fix it, it may indeed be bricked. IIRC, they are covering Atom failures for three years from purchase, but contact them to confirm.
There is no any BIOS fix regarding AVR54, it's a hardware bug.

5
I hope it does not matter 8)

6
There are a lot of improvements since 2013, but also igb4 still have a lot of bugs, AFAIK kern.ipc.nmbclusters=1000000 at least still needed  to maintain stabilty, also I would recommend to disable TSO and LRO (System/Advanced/Networking), and I am using hw.igb.num_queues=1 also since 2.3, I know something was improved since, but I still seeing problems reported again and again.
But... Honestly I have never encountered a cyclic state change of the igb network adapter, so it can be hardware issue as well... or it depends on hardware in my case it just gives me kernel panic and in yours it cycling adapter, I am not sure.


7
General Questions / Re: pfsense is not making sense
« on: November 14, 2017, 01:51:36 pm »
Generally it's a bad idea to use the usb NICs, I see no one have luck with this crap. If it's impossible to install pci-e intel card, but you have one embedded then use VLANs and VLANs capable switch, otherwise you will need different hardware setup to make things work as desired.

8
Installation and Upgrades / Re: pfSense installation failing
« on: November 10, 2017, 11:49:40 pm »
I think it's possible to install pfSense on this hardware.
https://forum.pfsense.org/index.php?topic=132528.msg730118#msg730118
Did you read that topic? May be you will find some tips, like bios settings.
Also you can try VMware ESXi on it, if it runs fine just install the pfSense there.
https://doc.pfsense.org/index.php/PfSense_on_VMware_vSphere_/_ESXi

9
Installation and Upgrades / Re: pfSense keeps crashing
« on: November 10, 2017, 01:43:34 pm »
Quote from: telendt
Yeah, I'll try that. Playing with different builds is the only thing that's left I guess (except of trying with different hardware, which I don't really have).
Not really only one, but definitely better to try it first. You can also try to disable TSO AND LRO on SYSTEM>ADVANCED>NETWORKING, but if it's a freebsd bug 213903 then there is no other way, only to try the new build.

11
Yep, confirmed on 2.4.2.a.20171107.1444

12
Installation and Upgrades / Re: No ZFS pool located error - intermittent
« on: November 07, 2017, 09:46:12 pm »
I think it is FreeBSD related bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234
Here is another thread - https://groups.google.com/forum/m/#!msg/bsdmailinglist/MbV1CIBXG4g/L12CTKg6yFIJ
I am not sure but you can try to create two virtual disks on your raid 10 and try to install on second one.
Also it is possible that you have some usb or other device that have problems with detecting on boot so be sure you do not have anything plugged in USB or disable unnecessary devices in uefi or bios.
Another one solution is to install VMware ESXI and then install pfSense on it, ESXI listing your raid controller as supported.

13

And if your system is stable after update, don't forget to switch it back!

14
Installation and Upgrades / Re: Problem after upgrade to 2.4.1
« on: October 31, 2017, 03:15:02 pm »
How did you install pfSense for the first time?  :o

15
Installation and Upgrades / Re: Problem after upgrade to 2.4.1
« on: October 30, 2017, 10:38:19 pm »
Upgrade to 2.4.1 seemed to work okay

...

FreeBSD 10.1-RELEASE-p24 amd64



No, it's not.
2.4.x is based on FreeBSD 11, so your install possibly broken and it is better to do clean install just save your configuration and restore it after.

Pages: [1] 2 3 4 5 ... 36