From 2.1.5 to 2.2 - Supermicro, SSD, Insane reboot, crash - Bsdlabel invalid
-
Probably a really good suggestion. I wouldn't be the one to configure something like that in BSD without doing some reading first.
Got a link for how to do something like that so the OP can read it? -
The installer has an option to create and install to a RAID mirror. In 2.2, you even have a GUI to manage the RAID (forget dead drives and replace them…), widget and notifications.
https://doc.pfsense.org/index.php/Create_a_Software_RAID1_%28gmirror%29
-
That is a cool option to have!
"Starting with pfSense 2.2, e-mail alerts will be sent if the status of an array changes."
I like it.
-
This what you were thinking of?:
https://forum.pfsense.org/index.php?topic=87272.msg479191#msg479191Steve
-
Yes - Thats exactly what I was remembering.
But I like doctornotors suggestion also. Seems like this guy was using a hardware raid and thats cool, but software may also work great.
I am not running raid on mine, so I can't say but I'm waiting to see if OP can make it work.
-
It seem more like an uncool 'hardware' raid! :P Why expose the discs and the array to the OS?
You mean disable the raid controller and use a GEOM mirror instead? I agree and Chris suggests that. His initial suggestion seems to be just to allow the box to boot.
Steve
-
Yes - I also like the idea that pfsense will email me if I have a dead disk - Assuming I ran raid.
I expect my particular SSD will outlast the foundation of my house… Its slow and reliable.
Its far my likely I'd eventually get tired of it than it would fail.
BUT - This thread has me thinking that running a raid of very fast MLC drives might make good sense using GEOM for future builds.
Long as I can easily know when my flakey SSDs need replacing. -
Adding info to this thread:
Regarding the limiter and kernel crash = reboot - Here is the bug report: https://redmine.pfsense.org/issues/4310
It appears to happen only when running CARP. -
Adding info to this thread:
Regarding the limiter and kernel crash = reboot - Here is the bug report: https://redmine.pfsense.org/issues/4310
It appears to happen only when running CARP.Seems like there is a patch ready now? or am i wrong? Can we use "pfSsh.php playback gitsync RELENG_2_2" to apply the patch ?
-
You can gitsync to bring in everything or apply single patches using the System Patches package.
If the fix is a single patch I would try just that first. If you gitsync you may pull in something undesireable. ;)
Both those options are unsupported etc….Steve
-
I couldn't find anywhere else to get an answer to this, but you are doing what I'm curious to try. I would like to know if two Intel SSD's (the support TRIM) are able to be used in the softraid 1 (The option the pfsense installer gives) with TRIM enabled? It seems as though TRIM gives them longer life, and RAID firther extends system uptime. I wouldn't want to throw dual SSD's in a system only to find that TRIM can't be enabled and they would have shorter lifespans that a single one!
Thanks for any heads up or help you guys can give.
