2.2.4 and how I enabled TRIM
-
Boot from an USB pen drive and then activate TRIM support in pfSense.
-
Did fsck in PC-BSD and disabled TRIM. Booted to USB and enabeled TRIM again. Same problem. I do a fresh install on the SSD as apparently Samsung is to dull to handle TRIM in some OS, Linux has a known problem with the 8xx series, apparently, dunno if BSD is also involved…
https://en.wikipedia.org/wiki/Trim_%28computing%29
see "Shortcommings"
So I will go without TRIM.
Wuuuuuaaaaaa what a mess!
-
So I will go without TRIM.
But then it would be a perhaps fast dieing because the data will be not marked correctly for overwriting
and the SSD drive will be perhaps in short time lame and dieing.Wuuuuuaaaaaa what a mess!
Right, but if it works for so many other peoples, it must also working for you!
You might be do it again and boot from a USB pen drive into "single user mdoe"
to activate it right! -
@BlueKobold:
So I will go without TRIM.
But then it would be a perhaps fast dieing because the data will be not marked correctly for overwriting
and the SSD drive will be perhaps in short time lame and dieing.TRIM cleans up after files are deleted (to insure fast writing to those deleted sectors).
Edit: Incorrect (TRIM does indeed lower write amplification of the drive making it last longer):
The 'Wear Leveling' routine of the drive's firmware should work in the background to move sectors around to give the drive a nice, full life. Edit 2: TRIM does indeed help because of the lower write amplification.
-
But this Samsung drives have data corruption with TRIM enabled, see Wikipedia above. It takes some time to make fresh SSD pfSense again and then copy the config.xml, I don't want to go through that over and over again.
I could not revive the first install by disabeling TRIM again, the installation was corrupt afterwards, fschk did not resolve that. Should I really try again to enable TRIM on this Samsung trash?
I think this TRIM is kind of voodooo and highly emotional when it comes to discussions. Any opinions on the importance of TRIM and how much it will influence the life-expectance of the SSD?
Merry Christmas everybody! :-)
chemlud
-
TRIM cleans up after files are deleted (to insure fast writing to those deleted sectors).
if a file is wiped, it is not really away and gone, and TRIM is then marking this data can be overwritten
so that the wear level algorithm is knowing that new data can be written on this sectors/blocks.If the data will not be marked for overwriting the wear leveling algorithm gets even less and more less
sectors where the data can be written on and then the mSATA or SSD will be slowing down before dieing
then after a while.It does nothing that I have read about to make the drive last longer.
If the wear leveling algorithm is getting less and more less free sectors/blocks to write on
until there are no free ones this might be then the end of the drive, but if the TRIM command
is marking this sectors/blocks as free for new write cycles the wear leveling algorithm get even
again and again new free sectors/blocks where it can be writing on. And so the lifetime will be
enlarged or hold.The 'Wear Leveling' routine of the drive's firmware should work in the background to move sectors around to give the drive a nice, full life.
There are only one amount of sectors/blocks that can be used to write on and the wear level algorithm is
using them in a balanced way thats all.I think this TRIM is kind of voodooo and highly emotional when it comes to discussions.
If this will be right, why then all peoples care about this "voodoo"? Why not then let them out or inactive?
Any opinions on the importance of TRIM and how much it will influence the life-expectance of the SSD?
You could use your Samsung drive without TRIM support and report it here for us.
-
Have no alternative, hu?
btw: Why should it matter if the BSD is started in single-user mode for switching to TRIM?
If there was kind of "mega"-nano image (16 or 32 GB) I would run the SSD with that, but there were experts in the past that denied this is helpful (more space, faster degradation of card/SSD, no joke).
Worst thing: I have another Samsung 850 here, I wanted to install some Linux to. Maybe better I bring it back before opening up… sigh...
-
After reading (searching), I stand corrected on this. Sorry about that and thanks BlueKobold.
With that said, how is TRIM triggered in FreeBSD. In Windows, it's triggered when you empty the recycle bin. I'm curious as to how and how often TRIM is triggered when running a program like pfsense with FreeBSD?
-
..I think I will go without TRIM for the while, I can simply not assess the importance of this "issue" for the time being
http://www.digitaltrends.com/computing/six-dead-solid-state-drives-prove-theyll-last-longer-than-you-imagined/
My guess: The Atom board with the SSD with break before the SSD goes south. Anything to be monitored in the Syslogs (besides the SMART status) to control for read/write errors?
-
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…
![TRIM kingston 30 GB.JPG](/public/imported_attachments/1/TRIM kingston 30 GB.JPG)
![TRIM kingston 30 GB.JPG_thumb](/public/imported_attachments/1/TRIM kingston 30 GB.JPG_thumb) -
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.