Tag Info

New answers tagged

0

It's a series of layers - at least two. Blocks within each volume (e.g. C:) are managed by the file system driver. (In fact, a good definition of "volume" is "one instance of file system metadata". Each volume defines one and only one root directory \.) Volume(s) within a physical disk are managed by a partition driver and a volume driver. The volume ...


1

Although the concept is similar (take a bunch of disks and act like it's one storage device), they actually function on a different level. JBOD runs close to the hardware, often as part of a disk controller configuration. Microsoft's storage pools run on the OS level. To illustrate this point: suppose you have a server with JBOD configured on the RAID ...


-3

Not even reliable solutions have their uses. If availability is more important in your case, you should pay a look at other types of Raid. If you prefer, you can make out the probability of failure of the Raid. But remember, do not Raid for reliability and storage of data, and to increase accessibility.


0

What works for me was lowering space for Previous versions of files (http://windows.microsoft.com/en-us/windows/previous-versions-files-faq#1TC=windows-7). Click Start Icon Left Click on "Computer" and click on Properties Click on "System Protection" on left side Click on Disk and "Configure" Lower your quota


0

It's not recommended to disable Hibernation on Windows 8, as it is used for the Fast Startup feature. Upon shutdown, the Fast Startup feature closes the user sessions, but hibernates the kernel session to hiberfil.sys. This system state is then used to speed up the next boot. Windows allocates an equivalent amount of your system’s RAM to hiberfil.sys. So, ...


1

Based on the nebulous and insufficient data provided in your question, I believe the cause to be that your laptop was previously the victim of hackers. They have recently decided they no longer need your PII and have removed 10g worth of hacking related files from this laptop. You could prove this hypothesis wrong by including greater details of logs, etc. ...


0

It's most likely a backup or a leftover temporary file for a download. Also found huge files (~1GB) in the exact same spot with no file extension and named 00000001 and 00000002. Opened the files using VLC (free video player capable of playing pretty much any video file) and found out that the files were actually videos I downloaded ages ago, but for some ...


0

Warning: Do NOT delete this folder. Most suggestions above, including Fuhrmanator's, might hurt installer data and you will have to reinstall software. There is a simple (and open source) tool called WICleanup that removes only the unused files in the Installer folder. Download it here: http://appnee.com/wicleanup/


1

If you looked in the status column in the area above the portion of the Disk Management window you cropped, you likely would see them identified as a recovery partition and EFI System partition. Regarding the EFI System Partition, the EFI System Partition Wikipedia article notes: The EFI System partition (ESP) is a partition on a data storage device ...


1

Those are the default recovery and uefi boot loader partitions for Windows. They were introduced in Windows 7. You can't remove them, sorry to say. However, you don't have to display them as a drive letter, if you just don't want to see them.


0

I finally fixed the problem using GetDataBackSimple, after having no success with other tools like Recuva, ntfs-3g or Windows' chkdsk. This tool will recover the files to a different unit, and place the found items in the originally-broken unit under a found.xxx directory, that can be deleted after the recovery.


1

I wasn't aware of shadows, and it was the cause. vssadmin list shadowstorage Thanks to this command I found out I had 47Gb of backups. I just shrank the allowed shadow space to a few Gb, and I recovered all my disk space.


0

I'm working for JAM Software and we have a product called ServerSentinel that could help you here. It's a monitoring tool that comes with a lot of sensors. One of them should solve your problem. Simply look for the ServerSentinel Disk Space Sensor. I'm a developer of ServerSentinel, so if you have any questions, just drop me a line, I'm happy to help.


3

According to some postings over on the Microsoft forums, http://support.microsoft.com/kb/2795944/EN-US should have resolved that bug and cleaned up the excess files... can you verify that you have that update or something that supersedes it?



Top 50 recent answers are included