2.2.4 and how I enabled TRIM
-
Just for the record: I tried the same with the second Samsung 850 EVO SSD, installed 2.2.6, copied over config.xml, booted from USB in single user mode, activated TRIM, reboot.
At "mounting filesystems" during boot I ended in the same errors as given above. No way to have TRIM with pfSense on these drives, apparently…
Question: Would it help to do a fresh install every 6 months to avoid the problems related to deactivated TRIM?
-
Greetings and I wish everyone a great New Year !!!!!
I posted in here August 04, 2015 about my getting pfSense to enable TRIM for my SSD.
Well, I'm happy to say my SSD is working great and has never faulted in any way, ever!!! I was careful vetting the SSD when I purchased the "cheapie" drive –- it was purchased from the Ama--- site and I carefully read the characteristics and that it supported TRIM, and further that TRIM support worked for several folks under FreeBSD. I took the gamble the drive would work with TRIM enabled and the rest has been a very pleasant history ... for me.
I am so happy that my list of instructions has benefited others too .... I mean, after all, when playing with the cutting edge you could open a vein if not careful <smile>.
Anyway, today I upgraded my box from 2.2.5 to 2.2.6 and my TRIM status is still properly set (I did see where someone else apparently did a fresh 2.2.5 install and my instructions to enable TRIM worked for them {yay}.)
So far 2.2.6 is working great, TRIM is taking care of my storage -- the world spins on .......
*except something is broken in the 2.2.6 Traffic Shaper and I'll post separately about that soon ...</smile> -
So TRIM does work on the Samsung Evo 850 then? I'm using a Mac mini as my pfsense box and I would like to replace my 5400rpm disk with a EVO 850 I have on my NAS for cache!
-
eeh, what' the meaning of the word "ERROR" in your language? OIo
..please read my posts above again, just in case…
-
I have a 120gb Samsung 840 EVO SSD and I was able to enable TRIM using ThePOO's instructions without incident. I'm running pfsense 2.2.6 and I booted off my pfsense 2.2.6 USB installer. So far no issues.
I will say that my experience with this Samsung drive and it's use in 2 other systems hasn't been stellar which is why I've never purchased another Samsung and won't in the future. For the record, my other SSDs are:
-
120GB PNY (Sandforce based)
-
240GB Toshiba
-
240GB OCZ ARC100
The PNY is "slow" by today's standards but just works (been in 3 systems) and the Toshiba and post Toshiba buyout OCZ are great.
-
-
Just to avoid confusion: I'm referring to my experience with 2 Samsung EVO 850 SSDs, MetalGeek has a EVO 840 ;-)
-
Just to avoid confusion: I'm referring to my experience with 2 Samsung EVO 850 SSDs, MetalGeek has a EVO 840 ;-)
Not exactly sure why anyone in here is caring about TRIM. I've been running a pfsense box for at least a few years now on a samsung ssd. I think it's a 60 or 80gb 830 pro. I've had 0 issues with it. I don't even know if trim is on or not but I've made 0 effort to find out or change it.
-
See above my post on the esoteric side of the TRIM discussion. But as a matter of fact I have here 2 Samsung EVO 850 120GB SSDs, for both I could not activate TRIM without corrupting pfSense, while it worked fine the same way on a 30GB Kingston NOW…
-
I just performed my first install on a new machine running pfsesnse 2.2.6 and TRIM was indeed not enabled. Followed OP's instructions, and TRIM is now enabled for my Intel 535.
Confirming OP's instructions are still needed and work for SSD users on 2.2.6
-
I must confess I'm a little disturbed now, as I recognized that the problem with TRIM is apparently not related to the Samsung EVO 850, but to the i386 version of pfsense 2.2.6
I have a Kingston 30 GB SSD, which was doing fine with x64 pfsense full 2.2.6, but when installing i386 pfsense on boot it hangs on TRIM activation…
 -
but to the i386 version of pfsense 2.2.6
Earlier or later this version (32Bit) will be not available, so anybody should take the chance to settle over
to the x86_64 version, perhaps we will see that changing is coming earlier as we all could expect or imagine it. -
To see if the problem has to do with the activation of TRIM on my 64bit BSD, I followed exactly the steps given in the first post of this thread, same result, same hanging on booting.
This whole TRIM thing is a pile of sh*t on i386 BSD…
-
I wonder if it is a batch of bad Samsung ssd's
I recently built out a new box on supermicro MB. Enabled trim without error. I did have to use 64bit, and installed off of usb 2.0 port and disable AHCI. Legacy IDE only. No issues so far!
Samsung 850 Pro
-
" I did have to use 64bit,"
64bit worked here too, but not 32 bit–-
-
–---- I was pretty frustrated getting TRIM enabled in 2.2.4
------ This is what worked for me to get the trim status set to enabled for my SSD.
[…]
Thanks for this guide, I just successfully enabled TRIM on the 16GB mSATA SSD module of the apu2c4!
-
Thank you very much, this very help me.
-
me too, did it last night on 64bit pfsense 2.3, and an Intel SSD.
-
Thank you to @ThePOO
It worked for me. -
Thank you for sharing this guide, ThePOO
-
Devices purchased from the pfSense store are loaded with TRIM enabled since we know the hardware and disks are capable (or at least in some cases do not have a negative reaction to it)
This wasn't the case with a new set of HA rack mount SG-4860's just purchased (thread https://forum.pfsense.org/index.php?topic=113803.0). Has this changed? Should the HA set of SG-4860's have TRIM enabled?
Thanks,
Frank
