Menu
My laptop right now runs Ubuntu Kylin, and has no Windows on it after accidentally wiping it when I updated the Ubuntu version. I'm trying to access a SSD from Samsung that used to work fine with windows.There's an.exe file to activate it. However, right now I can't seem to get the file to open. It opens briefly and then closes. I've tried installing exfat-utils which I read somewhere solved other people's problems, but still I'm having no relief to my issue.
I've tried using Wine, but I'm unfamiliar and can't get that to operate properly either. Samsung's proprietary software appears to be only for encryption. You won't be able to access any encrypted files on the drive from Linux since Samsung doesn't support that.If the drive is encrypted and you don't have any (valuable) data on the drive or moved it somewhere else (temporarily), you can repartition, reformat and use the SSD in Linux without additional software.If the drive is not encrypted you should be able to use it in Ubuntu right away or at least after installing the exfat-fuse package. If you can't, please edit your question or open a new question and include the output of lsusb, sudo lsblk -f and a screenshot of the drive as seen by GParted.If you want to encrypt your data on Linux (or any operating system really), it's always better to opt for vendor-independent, non-proprietary solutions.
![Not Not](/uploads/1/2/5/6/125614985/977519138.jpg)
The Samsung Portable SSD Software for PCs and Macs based on the AES 256-bit hardware data encryption makes it easy to configure security settings and receive the latest firmware and software updates. Hello, I'm a new poster with my first 850 EVO 2.5 SATAIII SSD. I can't seem to find any install guides here at the Samsung site? All the ones I see online deal with Cloning.
Popular examples for disk encryption system on Linux are.LUKS (Linux and BSD with cryptsetup, Windows with LibreCrypt (beta), OS X only through Linux guest system) and.TrueCrypt/VeraCrypt (Linux, BSD with cryptsetup, Windows, OS X).
Click to expand.Irresponsible and oft-repeated misinformation based entirely on one user's own circumstantial experience.When that problem-free SSD he keeps basing this declaration of TRIM's irrelevance on does eventually die it may have been twice as fast as it would have in a TRIM-enabled machine.No, TRIM does not work over USB in macOS and yes, TRIM absolutely does make a difference in performance and significantly reduces write amplification.The lifetime of an SSD is calculated in write cycles. TRIM DOES NOT matter that much any more.It's Sushi's 'advice' that is misinformation.I stand by this post.An open request to anyone reading this that is currently booting and running an iMac or Mini via USB:Has the lack of TRIM mattered much for you?If so, have you been able to document the information?I say to Sushi:Put up, or shut up.Produce documented info if you have it.For someone with an older Mac (2012-2015), who has only a platter-based hard drive inside, and who wants to 'squeeze more years of use' from it, adding an external USB3 SSD is a cost-effective solution. No breaking open the machine, no risk of breaking something inside.It will greatly speed up the computer, and so long as the user leaves a good amount of free space on the SSD, it will probably continue to perform well long enough to 'outlive' the computer itself.
I'm curious if anyone can shed some light on this:1) Why/How does Windows support trim on this particular SSD external drive (Samsung T5) over usb compared to Mac OS? Is the limitation of TRIM predominately based on the OS rather then the physical connection of the drive being used?2) What if I am using Parallels (Windows 10) in conjunction with With Mac OS Sierra via USB-C. Would TRIM work when Parallels is running? Or how about using a windows 10 desktop and also a 2016 Mabook Pro. IF I am going back and forth between different computers, does trim work when connected to the windows 10 desktop?Thanks for the info everyone. Much appreciated! You are correct.
USB cannot pass along the SATA TRIM command.What some people have read and it has caused confusion, is some UASP (USB-attached SCSI protocol) enclosure chipsets can convert the SCSI Unmap command (similar to TRIM) to TRIM commands at the drive. Windows can run this SCSI Unmap command with the Powershell command Optimize-Volume and the -ReTrim option.
OS X cannot run the SCSI Unmap command (at least not that I have been able to find). So at this point, no matter what chipset you use, you are not going to get TRIM over USB on a Mac.There is some discussion at the bottom of.
TRIM DOES NOT matter that much any more.It's Sushi's 'advice' that is misinformation.I stand by this post.An open request to anyone reading this that is currently booting and running an iMac or Mini via USB:Has the lack of TRIM mattered much for you?If so, have you been able to document the information?I say to Sushi:Put up, or shut up.Produce documented info if you have it.For someone with an older Mac (2012-2015), who has only a platter-based hard drive inside, and who wants to 'squeeze more years of use' from it, adding an external USB3 SSD is a cost-effective solution. No breaking open the machine, no risk of breaking something inside.It will greatly speed up the computer, and so long as the user leaves a good amount of free space on the SSD, it will probably continue to perform well long enough to 'outlive' the computer itself. Click to expand.Relying on garbage collection instead of TRIM is viable to some degree but not ideal. I bought a Mac Mini in 2012. I didn't want to go through the trouble of switching the internal drive to an SSD so I bought a 2.5' SSD and put it in an external enclosure and used that as my boot drive. It worked well for about 2 years but then I started experiencing horrible slowdowns if I wrote more than 1GB to the drive over the course of a few minutes.
Clearly I was exceeding the ability of the drive to free up empty blocks. It didn't happen often enough but the slowdowns were bad enough that I had to do something about it. (The system would hang for several seconds if it tried to write ANYTHING to the drive past 1GB and it would stay like that for 15-30 minutes.) I bit the bullet and installed the drive internally, enabled TRIM, and that eliminated the slowdowns. Click to expand.Hi all, Im new here.Mac TRIM over USB possible new info. So I got an Samsung Evo 860 into a USB 3.1 Gen2 enclosure. Driver formatted to APFS. Using BlackMagic Speed.
Used the 5GB test, initial bursts speed were even higher than below (probably drive cache). Result: Write: around 480MB/s Read around 500MB/s. Turned TRIM on via terminal (even though TRIM is not suppose to be supported over USB). Same Test = Write: around 520MB/s Read around 1600 -1700 MB/s. Then turned TRIM off again.
Speeds went back to 480MB/s Read around 500MB/s. Then turned TRIM ON again. Speeds went back up to 520/1600+MB/sSo people, what do you make of this test? Is TRIM now supported over USB? The Mac system profiler doesn't show this however, how do you explain the above test.
What's going on? Hi all, Im new here.Mac TRIM over USB possible new info. So I got an Samsung Evo 860 into a USB 3.1 Gen2 enclosure. Driver formatted to APFS. Using BlackMagic Speed. Used the 5GB test, initial bursts speed were even higher than below (probably drive cache).
Result: Write: around 480MB/s Read around 500MB/s. Turned TRIM on via terminal (even though TRIM is not suppose to be supported over USB). Same Test = Write: around 520MB/s Read around 1600 -1700 MB/s. Then turned TRIM off again. Speeds went back to 480MB/s Read around 500MB/s. Then turned TRIM ON again. Speeds went back up to 520/1600+MB/sSo people, what do you make of this test?
Is TRIM now supported over USB? The Mac system profiler doesn't show this however, how do you explain the above test. What's going on? Post Merged, Feb 28, 2019 -Another data point re: TRIM and garbage collection.I have a 3rd party SATA drive mounted in my 2012 Mac Mini.
When I installed it, I enabled TRIM via 'TRIM Enabler' and it worked fine.A couple months ago, I felt like my computer was slower than it should be when writing to the drive. Turns out that since I installed the drive, TRIM Enabler had stopped working. Blackmagic was reporting write speeds to the drive of around 50 to 120 MB/s.I re-enabled TRIM via Apple's newish 'trimforce' utility and write speeds are back over 400 MB/s for the drive.So to anybody thinking that garbage collection is somehow a replacement for TRIM, or eliminates the usefulness of TRIM, that is absolutely not true.Meanwhile, I did some research and apparently there are some external USB drive enclosures that support the UASP protocol and translate the SCSI UNMAP command to the SATA TRIM command.
So now it is possible to have TRIM over USB although I don't know if MacOS sends these UNMAP commands to UASP drives. Maybe somebody else knows the answer to that. You are correct. USB cannot pass along the SATA TRIM command.What some people have read and it has caused confusion, is some UASP (USB-attached SCSI protocol) enclosure chipsets can convert the SCSI Unmap command (similar to TRIM) to TRIM commands at the drive. Windows can run this SCSI Unmap command with the Powershell command Optimize-Volume and the -ReTrim option.
OS X cannot run the SCSI Unmap command (at least not that I have been able to find). So at this point, no matter what chipset you use, you are not going to get TRIM over USB on a Mac.There is some discussion at the bottom of. Click to expand.Interesting, thanks. It sounds like the Windows command is just to force-TRIM a drive's empty space. Just because MacOS doesn't have a similar force-TRIM/force-UNMAP command doesn't mean it doesn't send UNMAP commands to UASP drives as files are deleted.Somebody could test MacOS's UNMAP support by taking a blank, properly-TRIMMED drive, benchmarking it, then filling it up completely with data, then deleting some of that data, and then benchmarking it again.
If the benchmark results are the same then it would be a clue that UNMAP commands are being issued.I would do this myself but I don't have an appropriate drive or enclosure for such a test.