Jump to content

So after doing a bit of research last night this is what I have found, if you have a SSD you will greatly benefit from sitting down and giving this all a read for 15 mins. I didn't even realise it was happening.

Long story short you can't do a normal defrag on an SSD, it is REALLY bad for it. Scheduled maintenance by defaults covers all drives, inc any SSDs, and it is messing  them up.

 

You basically have to tell it what kind of defrag it needs to do, schedule that as a task, and remove from the normal schedule. But I will let you read more in depth, well worth it.

 

 

http://www.outsidethebox.ms/why-windows-8-defragments-your-ssd-and-how-you-can-avoid-this/#_Toc352763197

“THE EDGE, there is no honest way to explain it because the only people who really know where it is are the ones who have gone over.”
― Hunter S. Thompson

Link to comment
https://linustechtips.com/topic/146204-ssd-win-7-win-8-defrag-bug-important/
Share on other sites

Link to post
Share on other sites

Defrag is disabled on 8.1 for me? It automatically TRIMS. I never heard of this problem. Even in the history from that PowerShell command, it only said that it has defragged my HDD and not my SSD. So I dont understand what is the problem?

Motherboard - ASUS P6X58D-E Processor - Intel i7 930 Bloomfield OC'd @ 4.01Ghz, 1.28v | RAM - 12GB Corsair Dominator @ 8-8-8-12, 1600mhz | Graphics Card - EVGA Geforce GTX660 SC 3GB @ +75mhz core, +500mhz mem | Power Supply - Seasonic X650 Gold

CPU Cooler, Fans - Corsair H-90 w/ Noctua FN14 push/pull, Gelid Wings UV Blue  | Case - Fractal Design Arc MIDI R2 |

 

Link to post
Share on other sites

Yeah it does TRIM. But unless you have changed ur schedule to exclude the SSD, it does do it as well as the TRIM. So TRIM fixes it, then defrag fucks it. I was just as surprised.

 

Happens in Win 7, 8, and 8.1

 

Wait, if you have never heard of it...must mean it doesn't happen then right?  :P

“THE EDGE, there is no honest way to explain it because the only people who really know where it is are the ones who have gone over.”
― Hunter S. Thompson

Link to post
Share on other sites

Basically exporting the existing defrag schedule, open in notepad and change the argument values to "<Arguments>C: D: -l -h</Arguments>" save and then import back into scheduler. Change the description in the file to like 'SSD Trim' or something. Under 'description'.

 

Then exclude the SSD via the defrag program itself. Under 'change settings'.

Can also run this command in dos prompt, (run as administrator).

'defrag /o /u /v C:'

 

I have attached the ammended schedule if anyone wants it. Just need to import into Task Scheduler.

 

TRIM-SSD.xml

“THE EDGE, there is no honest way to explain it because the only people who really know where it is are the ones who have gone over.”
― Hunter S. Thompson

Link to post
Share on other sites

Wheew, you scared me there for a moment. I actually logged my install steps and indeed disabled C: (SSD) from being defragged. Sigh of relief. Yes I checked the logs and no defrag of C: is listed, yeay me!

I roll with sigs off so I have no idea what you're advertising.

 

This is NOT the signature you are looking for.

Link to post
Share on other sites

I think you have read something wrong. The whole point of the article is that it will defrag, unless told not to, and to need to tell it to do a different scan. It wont recognise the SSD otherwise, just sees it as files that are no longer used, just like the other 'normal' drives.

 

@IdeaStormer - that's awesome you did that. I didn't.. :( haha

 

Might want to check if TRIM is working tho. Or just add that schedule in place like I mentioned....


This whole thing kinda surprised me. SSDs have been a pretty hot topic over the last couple of years, and we all hear about how awesome and fast they are. Not once did someone tell me I can't defrag them, and that I am actually shortening the lifespan by using up NAND write cycles, which it only has a limited amount of.

 

I have been known to defrag every day...fs.

“THE EDGE, there is no honest way to explain it because the only people who really know where it is are the ones who have gone over.”
― Hunter S. Thompson

Link to post
Share on other sites

Ill have to check the article but I have not yet encountered a system with Win7sp1 and newer where defrag on the SSD hasnt been disabled. Also if you have the samsung or intel tools they will have a field for that as well.

Link to post
Share on other sites

It has done it to me with my initial SSD and win 7, now both of them in RAID with win 8.1. Ran a couple of tests recommended by that guy, and they were definitely being defrag'd.

“THE EDGE, there is no honest way to explain it because the only people who really know where it is are the ones who have gone over.”
― Hunter S. Thompson

Link to post
Share on other sites

It has done it to me with my initial SSD and win 7, now both of them in RAID with win 8.1. Ran a couple of tests recommended by that guy, and they were definitely being defrag'd.

What kind of raid and to me its not unexpected in raid because in most cases especially with win 7 the os doesnt know that raid array is made of ssds. Hell geeting trim to work in raid 0/1 took how long.

Link to post
Share on other sites

RAID 0. And you are exactly right, I even installed Samsung Magician (SSD Manager), and it didn't recognise it's own drives. I also did a couple of tests and it seems as tho I wont be able to get TRIM running on a RAID-0 volume. I did run this tho  --  'defrag /o /u /v C:'  --  and it gives you a pre and post report, and the stats had dramatically improved. So I'm not really sure what I should do....if TRIM doesn't work on RAID, what did that command just do?

 

Can't defrag, can't TRIM. Limited space that doesn't get overwritten....this isn't going to go well for me is it...

“THE EDGE, there is no honest way to explain it because the only people who really know where it is are the ones who have gone over.”
― Hunter S. Thompson

Link to post
Share on other sites

RAID 0. And you are exactly right, I even installed Samsung Magician (SSD Manager), and it didn't recognise it's own drives. I also did a couple of tests and it seems as tho I wont be able to get TRIM running on a RAID-0 volume. I did run this tho  --  'defrag /o /u /v C:'  --  and it gives you a pre and post report, and the stats had dramatically improved. So I'm not really sure what I should do....if TRIM doesn't work on RAID, what did that command just do?

 

Can't defrag, can't TRIM. Limited space that doesn't get overwritten....this isn't going to go well for me is it...

trim should work on raid 0 depending on your setup

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×