31 replies
by -hochiminh- Accepted solution
by older mycroft Accepted solution
What do you mean by 'dedicated drive' ?
What is 'naturally limited disk space' ?
Why do you think Diskeeper will damage your D: drive when it has already been helpful for your C: drive ?
I see no reason why you cannot run it as you already have on C:. :)
by -hochiminh- Accepted solution
by older mycroft Accepted solution
Sorry - I wasn't familiar with your terminology of 'Dedicated Drive'.
Knowing now that you meant the Recovery Partition, you should [b]NOT[/b] under any circumstances go anywhere near it with a defragmentation routine. Indeed, you shouldn't even be able to SEE it.
Almost every recovery partition that I've ever seen has at least 2 fragments - that's just the way that it's made and the low free space should never be counted as 'low free space' because the partition is NOT INTENDED for normal use and should not be available to the operating system until called upon to perform the one function that it was created for - to Recover a failing system.
LEAVE IT ALONE - IGNORE IT - DO NOT DEFRAG.
by boxfiddler Hot topic Accepted solution
how a drive that just sits there waiting for something to do, a drive that has no daily activity, gets fragged in the first place.
???
by the scummy one Accepted solution
when defragmenting
If your drive is low on disk space, or is suffering from other problems, make a backup of your data BEFORE defragmenting the drive.
If there is not enough disk space, I do not defragment the drive until space has been cleaned up from it. You should be wary of defragmentation warnings, and if you receive a warning, make sure your data backup is up to date before continuing.
by ---tk--- Accepted solution
by the scummy one Accepted solution
complains if 15% is not free, however even with 15% free it may still hiccup, so you are correct. 20% free is much better.
Thank You
by -hochiminh- Accepted solution
by the scummy one Accepted solution
after the backup, cleanup enough space (more than 15%-20%). I would go for temps, temp IE files, cookies, and run a disk cleanup. Afterwards, I would determine what things do not need to be on there, and sometimes I have even reduced the amount of disk space for things (like the recycle bin) (and empty it).
Following this should reduce problems, and give you a good place to be (with a backup) in case disaster happens.
Have fun with it :D
Hope it goes well :D
by ---tk--- Accepted solution
by the scummy one Accepted solution
that the recycle bin holds space, even if it shows as empty.
along with system restore, and other stuff.
by vindasel Accepted solution
Only the older versions of Diskeeper had trouble with low disk space. Diskeeper 2009 pro (current version) has fully defragged a 250GB Seagate of mine that had just about 5% free space and bad fragmentation. The key is to run Diskeeper in automatic mode under low space conditions. When you hit < 15% space, defrag is going to take a while, but DK completes it nonetheless.
by rob miners Accepted solution
by -hochiminh- Accepted solution
by seanferd Accepted solution
Is this a Recovery Partition that came on the drive as part of the installation when you bought the system? If so, nothing should be added to this drive. It would probably never require defragmentation. If you ran a scan on it, the utility would probably report that a defrag is unnecessary.
If this is your personal backup drive, that saves your user-created files, go ahead and defrag once you've cleaned it up a bit. Of course, if it is that full, you won't be able to back up to it much more anyway.
Defrag adds no info to the drive.
Edit: I see your other post pretty much answered this. If it is the OEM recovery partition, there should be no need to defrag. This partition will not be accessed during the course of normal operation, anyway. You won't get any performance boost even if you did defrag.
by rob miners Accepted solution
If there was nothing at all saved to that drive other than recovery information that was added by System restore, I would disregard what it is saying. The last thing that you need is a corrupt recovery partition. I would also turn off Monitoring of that Drive through System Restore.
It's also a good idea to make 2 Backup sets just in case one is corrupted if you can. You shouldn't be accessing that drive in the first place. They are normally hidden from the users view and only accessed when doing a Full System Restore.
Keep us informed as to your progress if you require further assistance.
If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D
by seanferd Accepted solution
by rob miners Accepted solution
by seanferd Accepted solution
by older mycroft Accepted solution
I'm only human (believe it or not !!).
I woke up and realised what 'Dedicated Drive' actually meant to the OP, didn't bother reading any of the rest of the thread, and just launched straight in, just in case the OP took me at my previous word and went ahead blindly defragging the recovery partition.
I now realise you all had the situation covered. :D ;)
by seanferd Accepted solution
and for thinkins as well.
You did the right thing, and I, for one, wouldn't have it any other way. B-)
Like I said, I like an "Oh, for the love of God, no!", kind of warning to get the import across. You do it so well. :)
by w2ktechman Accepted solution
Do nothing to this partition unless you want to lose the ability to recover your system, perform diagnostics, etc..
Sorry ma'an, I mis-interpreted 'dedicated drive' to mean a second hard drive without an OS.
by w2ktechman Accepted solution
I am late to the party :(
too bad I had to make dinner and call the tv shop
by w2ktechman Accepted solution
some system builders limit how many recovery sets that can be created :0
My system is limited to 1 set. When I went to rebuild it wouldnt let me create one because I already had created it (a few years ago). I found the ones that I created and the 2nd disk gave me shlt. After trying each and every disk 4 times, it finally accepted that disk 2 was, in fact, disk 2.....
When I booted back up, one of the first things I did was to create a new set, and it warned me that I could only create 1.
by rob miners Accepted solution
by seanferd Accepted solution
This has been a party all day. OM just walked in before you.
(Tell the TV shop to GTFO, tell 'em it was from me.)
by -hochiminh- Accepted solution
by seanferd Accepted solution
by seanferd Accepted solution
Seems that you got attention first, all shouty and at the top of the thread. That was the smart way to go.
You rock, OM!
by rob miners Accepted solution
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending