Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Confused on enabling TRIM

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    1 Posts 1 Posters 783 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F Offline
      fthomasr
      last edited by

      So since nano is going away I'm tasked with upgrading a lot of APUs I have out there from Nano on an SD card over to a Sandisk 16GB mSATA (mini PCI-E). My plan is to take an APU I have laying around not used (but with different NICs) and load each SSD with 2.3.3 memstick serial full kernel and then restore the existing backed up config over to it then pull it out and take it over to the box in place to minimize downtime for each.

      However this TRIM business is confusing. After going through a bunch of guides and forum posts I have some questions to try and clear this up. Hopefully this discussion will benefit others.

      1. It has been stated the first step is to enable AHCI. So edit the /boot/loader.conf.local and add ahci_load="YES". Once you do this and restart how do you know it was successfully enabled/implemented? Can you run a shell command or see something in the GUI? (a side question to this one is that on my v2.4 pf there is no /boot/loader.conf.local? Why? Do I need to create the file manually?)

      2. So the next step is to gather your specific device and mountpoint (using cat /etc/fstab) and copy it ie. /dev/ufsid/563dee910aa6a80a. So since I'm going to run this on the SSD on in house APU and then take it to another APU. Will that mountpoint change thereby making it useless to do it on the in house APU first? I'm trying to avoid being on site with a serial cable and a laptop running all this costing valuable uptime, so the goal is to do it all in the lab and quick swap the SD to SSD.

      3. You can't just throw a command in some boot loader to auto enable it on the hard drive next boot?

      4. So say you run the command to enable it for said device, ie /sbin/tunefs -t enable /dev/ufsid/563dee910aa6a80a and then reboot. I read to check to ensure it's enabled successfully that you just run tunefs -p /. Ok but that just shows tunefs: trim: (-t) enabled. Does that mean trim is enabled overall? That's what it looks like to me. How do you know it's enabled for the SPECIFIC drive that is so important to SPECIFY above?

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.