Hard Drive fills up after format

Page 1 of 3 123 LastLast

  1. Posts : 10
    Windows 10 Pro 64-bit
       #1

    Hard Drive fills up after format


    Before I start, I must say that I am completely new to these forums. I literally just made an account so I could get some help with this problem. I apologise beforehand if my formatting or general mannerisms are not right.

    There's a TL;DR at the bottom for those who don't want to hear the entire backstory to this issue.

    Anyways, as the title says, I'm having a rather weird issue with one of my drives, namely, my D drive on my laptop (the one that doesn't have the boot on it, I presume). You see, recently I noticed my laptop was getting rather full, so I figured I'd try and clean up a bit. I have two SSDs, both about 500 GB. Originally, one was some sort of RAID for the other? But something went horribly wrong during a stay in America. The entire laptop was completely unresponsive. Luckily, the guy I was staying with knew a guy who knew quite a bit about computers. So, he was able to get her running quite well again. Apparently, something went wrong with the RAID or something? I dunno, the guy either didn't explain it very well or I didn't understand.

    Well, the laptop works again, but as far as I can tell, the D drive is still nigh unusable. I tried installing Steam to it so I could use that as my gaming drive, but Steam simply refuses to run. If Steam's installed on the C drive, it runs fine. There's still some files on the D drive which I can read just fine, but programs seem to be an issue.

    So then whenever I try to format my second drive, it seems to simply reset to a previous state. In this state, it has about 68 GB of space left. So when I manually go in and delete things, like my Steam folder (which is usually rather big) and then go and format the drive, it goes from having 278 GB free to 68 GB free! Even though I formatted it!

    TL;DR
    Formatting my D drive just resets it to a previous (usually more filled) state, from what I can gather.

    Thanks ahead for any help with this issue and for your time reading this thread!

    - Denzel
      My Computer


  2. Posts : 13,301
    Windows 10 Pro (x64) 21H2 19044.1526
       #2

    Open Disk Management and post a picture if you can. To give us a better look at what you mean.
      My Computers

  3.   My Computer


  4. Posts : 10
    Windows 10 Pro 64-bit
    Thread Starter
       #4

    thomaseg1 said:
    Open Disk Management and post a picture if you can. To give us a better look at what you mean.
    Oh, okay! Here you go!

    Hard Drive fills up after format-partitions.png
      My Computer


  5. Posts : 8,111
    windows 10
       #5

    It looks like it's still raid as it looks like a mirror of the c drive disk sizes look the same. In the BIOS is there a raid set?
      My Computer


  6. Posts : 13,301
    Windows 10 Pro (x64) 21H2 19044.1526
       #6

    It looks as if D is mirroring C in a raid formation.
    Raid is definitely not my forte.....
    Sorry
      My Computers


  7. Posts : 10
    Windows 10 Pro 64-bit
    Thread Starter
       #7

    Samuria said:
    It looks like it's still raid as it looks like a mirror of the c drive disk sizes look the same. In the BIOS is there a raid set?
    Oh, uhm, where and how do I check this?

    - - - Updated - - -

    thomaseg1 said:
    It looks as if D is mirroring C in a raid formation.
    Raid is definitely not my forte.....
    Sorry
    Hey, no problem! Thank you for taking the time to reply anyway ^^
      My Computer


  8. Posts : 13,301
    Windows 10 Pro (x64) 21H2 19044.1526
       #8

    Oh, uhm, where and how do I check this?
    As Samuria suggested The Bios is the first place to look to see what your sata is set to raid/achi/?
      My Computers


  9. Posts : 41,480
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    By default the columns are compressed when opening disk management.
    Please widen the Status column so that the contents within the parenthesis are in full view and none of the characters are cutoff.

    The cause of the laptop unresponsiveness was not reported.
    Was this a hang, freeze, crash?
    What troubleshooting steps had been performed?
    Do you use backup images or only RAID?
    Had you had any drive problems or tested the drives? (SMART, benchmark, or error scan)
    If the computer is using RAID do you want to turn off RAID?
    Do you want to delete the partitions or format the second drive and use it as a storage drive?

    Open administrative powershell and copy and paste:

    a) sfc /scannow
    b) dism /online /cleanup-image /restorehealth
    c) chkdsk /scan
    d) bcdedit /enum
    e) bcdedit | find "osdevice"
    f) reagentc /info

    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    Open administrative powershell and copy and paste:

    Code:
    $dp = "list volume" | diskpart | ? { $_ -match "^  [^-]" }
    
    echo `<`<`<local`>`>`>
    foreach ($row in $dp) {
    	# skip first line
    	if (!$row.Contains("Volume ###")) {
    		# best match RegExp from http://www.eventlogblog.com/blog/2012/02/how-to-make-the-windows-softwa.html
    		if ($row -match "\s\s(Volume\s\d)\s+([A-Z])\s+(.*)\s\s(NTFS|FAT)\s+(Mirror|RAID-5|Stripe|Spiegel|Spiegelung|Übergreifend|Spanned)\s+(\d+)\s+(..)\s\s([A-Za-z]*\s?[A-Za-z]*)(\s\s)*.*")  {
    			$disk = $matches[2] 
    			# 0 = OK, 1 = WARNING, 2 = CRITICAL
    			$statusCode = 1
    			$status = "WARNING"
    			$text = "Could not parse line: $row"
    			$line = $row
    			
    			if ($line -match "Fehlerfre |OK|Healthy") {
    				$statusText = "is healthy"
    				$statusCode = 0
    				$status = "OK"
    			}
    			elseif ($line -match "Rebuild") {
    				$statusText = "is rebuilding"
    				$statusCode = 1
    			}
    			elseif ($line -match "Failed|At Risk|Fehlerhaf") {
    				$statusText = "failed"
    				$statusCode = 2
    				$status = "CRITICAL"
    			}
    		
    			echo "$statusCode microsoft_software_raid - $status - Software RAID on disk ${disk}:\ $statusText"
    		}
    	}
    }v
    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    Run HD Tune: (free or trial version) (test all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Heath (SMART)
    b) Benchmark
    c) Full error scan


    There are log collectors used in another forum.
    Run both V2 and DM log collectors and upload results into this thread.
    BSOD - Posting Instructions


    https://www.tenforums.com/tutorials/...dows-10-a.html
    Last edited by zbook; 30 May 2019 at 18:03.
      My Computer


  10. Posts : 10
    Windows 10 Pro 64-bit
    Thread Starter
       #10

    Alright, uh, throwing a lot my way. Okay so here's the first thing you asked me to do.
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.

    PS C:\WINDOWS\system32> sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.
    PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.17134.1

    Image Version: 10.0.17134.765

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    PS C:\WINDOWS\system32> chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    493824 file records processed.
    File verification completed.
    14038 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    554 reparse records processed.
    615392 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    554 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    60785 data files processed.
    CHKDSK is verifying Usn Journal...
    39046048 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    498713566 KB total disk space.
    208196768 KB in 264455 files.
    171524 KB in 60786 indexes.
    0 KB in bad sectors.
    622606 KB in use by the system.
    65536 KB occupied by the log file.
    289722668 KB available on disk.

    4096 bytes in each allocation unit.
    124678391 total allocation units on disk.
    72430667 allocation units available on disk.
    PS C:\WINDOWS\system32> bcdedit /enum

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    default {current}
    resumeobject {6a35d80e-e56a-11e8-9324-9d05d8590be3}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 0

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \WINDOWS\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {6a35d810-e56a-11e8-9324-9d05d8590be3}
    displaymessageoverride Recovery
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \WINDOWS
    resumeobject {6a35d80e-e56a-11e8-9324-9d05d8590be3}
    nx OptIn
    bootmenupolicy Standard
    PS C:\WINDOWS\system32> bcdedit | find "osdevice"
    FIND: Parameter format not correct
    PS C:\WINDOWS\system32> bcdedit | find osdevice
    FIND: Parameter format not correct
    PS C:\WINDOWS\system32> bcdedit | find "osdevice"
    FIND: Parameter format not correct
    PS C:\WINDOWS\system32> reagentc /info


    - - - Updated - - -

    I sat there for a solid 15 minutes and it didn't do anything past reagentc /info. It wouldn't accept any further input either.

    - - - Updated - - -

    Oh, Powershell isn't closing either.

    Great.

    - - - Updated - - -

    Oh, hey it closed! Neat. I'll continue with the rest now.

    - - - Updated - - -

    Alright, second request... didn't seem to do much? Am I doing something wrong?

    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.

    PS C:\WINDOWS\system32> $dp = "list volume" | diskpart | ? { $_ -match "^ [^-]" }
    >>
    >> echo `<`<`<local`>`>`>
    >> foreach ($row in $dp) {
    >> ^I# skip first line
    >> ^Iif (!$row.Contains("Volume ###")) {
    >> ^I^I# best match RegExp from http://www.eventlogblog.com/blog/2012/02/how-to-make-the-windows-softwa.html
    >> ^I^Iif ($row -match "\s\s(Volume\s\d)\s+([A-Z])\s+(.*)\s\s(NTFS|FAT)\s+(Mirror|RAID-5|Stripe|Spiegel|Spiegelung|Übergreifend|Spanned)\s+(\d+)\s+(..)\s\s([A-Za-z]*\s?[A-Za-z]*)(\s\s)*.*") {
    >> ^I ^I^I$disk = $matches[2]
    >> ^I^I^I# 0 = OK, 1 = WARNING, 2 = CRITICAL
    >> ^I^I^I$statusCode = 1
    >> ^I^I^I$status = "WARNING"
    >> ^I^I^I$text = "Could not parse line: $row"
    >> ^I^I^I$line = $row
    >> ^I^I^I
    >> ^I^I^Iif ($line -match "Fehlerfre |OK|Healthy") {
    >> ^I^I^I^I$statusText = "is healthy"
    >> ^I^I^I^I$statusCode = 0
    >> ^I^I^I^I$status = "OK"
    >> ^I^I^I}
    >> ^I^I^Ielseif ($line -match "Rebuild") {
    >> ^I^I^I^I$statusText = "is rebuilding"
    >> ^I^I^I^I$statusCode = 1
    >> ^I^I^I}
    >> ^I^I^Ielseif ($line -match "Failed|At Risk|Fehlerhaf") {
    >> ^I^I^I^I$statusText = "failed"
    >> ^I^I^I^I$statusCode = 2
    >> ^I^I^I^I$status = "CRITICAL"
    >> ^I^I^I}
    >> ^I^I
    >> ^I^I^Iecho "$statusCode microsoft_software_raid - $status - Software RAID on disk ${disk}:\ $statusText"
    >> ^I^I}
    >> ^I}
    >> }v
    <<<local>>>
    v : The term 'v' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
    spelling of the name, or if a path was included, verify that the path is correct and try again.
    At line:34 char:2
    + }v
    + ~
    + CategoryInfo : ObjectNotFound: (v:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    PS C:\WINDOWS\system32>
    PS C:\WINDOWS\system32> $dp = "list volume" | diskpart | ? { $_ -match "^ [^-]" }
    >>
    >> echo `<`<`<local`>`>`>
    >> foreach ($row in $dp) {
    >> ^I# skip first line
    >> ^Iif (!$row.Contains("Volume ###")) {
    >> ^I^I# best match RegExp from http://www.eventlogblog.com/blog/2012/02/how-to-make-the-windows-softwa.html
    >> ^I^Iif ($row -match "\s\s(Volume\s\d)\s+([A-Z])\s+(.*)\s\s(NTFS|FAT)\s+(Mirror|RAID-5|Stripe|Spiegel|Spiegelung|Übergreifend|Spanned)\s+(\d+)\s+(..)\s\s([A-Za-z]*\s?[A-Za-z]*)(\s\s)*.*") {
    >> ^I^I^I$disk = $matches[2]
    >> ^I^I^I# 0 = OK, 1 = WARNING, 2 = CRITICAL
    >> ^I^I^I$statusCode = 1
    >> ^I^I^I$status = "WARNING"
    >> ^I^I^I$text = "Could not parse line: $row"
    >> ^I^I^I$line = $row
    >> ^I^I^I
    >> ^I^I^Iif ($line -match "Fehlerfre |OK|Healthy") {
    >> ^I^I^I^I$statusText = "is healthy"
    >> ^I^I^I^I$statusCode = 0
    >> ^I^I^I^I$status = "OK"
    >> ^I^I^I}
    >> ^I^I^Ielseif ($line -match "Rebuild") {
    >> ^I^I^I^I$statusText = "is rebuilding"
    >> ^I^I^I^I$statusCode = 1
    >> ^I^I^I}
    >> ^I^I^Ielseif ($line -match "Failed|At Risk|Fehlerhaf") {
    >> ^I^I^I^I$statusText = "failed"
    >> ^I^I^I^I$statusCode = 2
    >> ^I^I^I^I$status = "CRITICAL"
    >> ^I^I^I}
    >> ^I^I
    >> ^I^I^Iecho "$statusCode microsoft_software_raid - $status - Software RAID on disk ${disk}:\ $statusText"
    >> ^I^I}
    >> ^I}
    >> }
    <<<local>>>
    PS C:\WINDOWS\system32>
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:39.
Find Us




Windows 10 Forums