Can TRIM work on a drive that never rests?

[Coup27]

They clearly did not understand your question and were telling you about booting an OS using GPT (something that drive does not need to be aware of to happen) not that they tested with GPT to ensure a dangerous GC algorithm does not corrupt it.

I also got the feeling it was a classic generic response to a technical question, but when I ran gdisk on my UEFI/GPT install with the 320 it worked fine as did their SSD optimiser so I'm not sure if I'm going to get anymore from them.

It is possible then that the issue was with their SSD Magician software manually trimming "unpartitioned" space and not recognizing GPT. And that they silently fixed it (in order to avoid losing face and lawsuits that eventually ensue from any public admission of fault)

I don't think so. Neither my SSD firmware or Magician version number has changed since techvslife's thread and now.

If you press go on the Samsung SSD optimiser then it just errors on screen and produces a log. Shame I haven't got a copy of that log file anymore. When I did my tests last weekend I checked gdisk before and after attempting to run the optimiser and it didn't show any curruption at any point. Techvslife did say he was using a beta [I think] of RSTe where as I use the latest official RST.


I really don't know where this leaves SSDs in relation to UEFI/GPT. Over the next decade it will push BIOS/MBR out of the picture but it would be supremely stupid from Samsung or Intel to design a drive which is inherently incompatible with GPT. My tests were to try and find a reliable UEFI/GPT imaging program. Acronis doesn't support boot GPT, neither does Ghost. Paragon claims to work but doesn't and now this.

I haven't had the time to read that study linked to above but I will certainly do so.

 

[lsv]

Drives like Intel do garbage collection during writes. OCZ drives do garbage collection during idle time.

 

[wpcoe]

There may be a chance that you could speed up your boot procedure by physically disconnecting the optical drive, instead of merely disabling it in windows. Could you try that, and see if your boot-up time improves?

Actually, my boot-up time is quick enough that I didn't consider disconnecting the drive. I don't want to disconnect as I don't want to have to reboot any time I want to use the drive.

No need to disable the drive. If it's the same as the XP problem (likely) all you have to do is disable auto-insert notification for the drive.

How does one disable auto-insert/auto-play in Windows 7 Home Premium? Group Policy Editing is not enabled in Home Premium.

 

[happyboy]

Some trim support have to be enabled and some are enbaled when the mobo recognizes it.

 

[kbp]

How does one disable auto-insert/auto-play in Windows 7 Home Premium? Group Policy Editing is not enabled in Home Premium.[/QUOTE]

Control Panel / Default Programs / Change Auto-Play Settings

 

[groberts101]

Some trim support have to be enabled and some are enbaled when the mobo recognizes it.

the mobo has absolutely nothing to do with trim pass-through. That's down to the SSD firmware and OS/drivers it's being used on.

 

[wpcoe]

No need to disable the drive. If it's the same as the XP problem (likely) all you have to do is disable auto-insert notification for the drive.

How does one disable auto-insert/auto-play in Windows 7 Home Premium? Group Policy Editing is not enabled in Home Premium.

Well, fussing with auto-play settings was an exercise in futility. All those settings do is tell Windows what to do if it detects something in the drive.

What I would need is something to prevent Windows from trying to detect if something is in the drive. I thought maybe unchecking 'Use AutoPlay for all media and devices" would to that, but that's not the case.

DVD drive back to disabled.

 

[taltamir]

You can disable it via the registery or group services (I am positive there is also a service you can disable but I didn't find it in the 3 minutes I took searching for you)
http://www.computerperformance.co.uk/windows7/windows7_autoplay.htm

 

[Coup27]

Going back to the original coversations for a moment, I made a sort of friend at the company Samsung use for their end user support and she advised me yesterday that an updated SSD Magician is being released either this month or next.

When I emailed Samsung asking about UEFI/GPT support a while back they said they were looking into it and may include support for it in the next release of Magician, which would be this one.

Have to wait and see.

 

[catilley1092]

While I don't like to 'dig open' old Topics, this is one that has baffled me. I've allowed my SSD's up to 12 hours of idle time for TRIM/GC, and have even resorted to the trick of unplugging the data cable & done the same.

Yet using Recuva, have found & recovered many intact files.....some from back in 2010 & with MD5, SHA1 & SHA256 checksums! If TRIM is working as should be, files that are deleted are supposed to be forever gone, or that's my understanding. Yet it's not the case, or I have a total misunderstanding of how TRIM works. I've assumed SSD's to be like a privacy barrier, destroying files by the magic of TRIM & GC, evidently that's not always the case.

While I may need to open a new Topic to address my concerns, some of the theories presented here about TRIM & GC are at a minimum, a bit misleading, or a lot left out to be guessed at. While it may free some cells for future use, these files are not totally gone, unless a backup image is performed first of the drive (or clean install afterwards) & then run a secure erase utility, I use the free version of Parted Magic from MajorGeeks. What I don't know is if the Enhanced Secure Erase is better than a plain out secure one (it's always been offered), though I decline & go with the total zeros to the entire drive. May be wrong here also, have read that the 'Enhanced' type zeros out so many of the first & last sectors & encrypts the rest. If so, that's not what I want.

However, one would think that with TRIM & GC on a modern OS, on modern hardware, all of these files should be cleaned up (100% unrecoverable in a readable state) so that a Secure Erase isn't necessary. Just a quick format & reinstall, or use the diskpart tool for the cleaning prior to formatting. Windows knows according to OS & MBR or GPT (or BIOS/UEFI), how to create needed partitions, though I'll always leave 10% unformatted space at the end of drive for overprovisioning.

While it may be best for me to create my own Topic in regards to this, a Google Search led me to this Topic, was the first 'hit', and found it an interesting read, so posted here. At a minimum, my posting will keep the Topic at the top of the charts for awhile longer.;-)

Cat

 

[Elixer]

Just because the drive gets the TRIM command, doesn't mean that it will reuse that NAND cell(s) right away, in fact, usually, it will not.
The SSD has a ton of things to do before it can actually use the same NAND cell again. It really is pretty complex. The wear leveling algorithm main job is not to use the same NAND cell too often, so they spread the writes out, and thus, if you don't write a ton of info to the SSD, then, yes, that data may still be in the NAND.