Search the Community

So I know this problem happens a lot and I've been browsing a lot of "solutions" with no success thus far. I have taken several steps to try to troubleshoot and the information I get back has been giving mixed results. As seen above, chkdsk does in fact find errors detected and my drive is marked as dirty, but every time I try to restart, it does the repair but the errors do not go away. Errors are also found in the drive properties. Repairing and restarting here yields the same result as before. Crystaldisk shows my drive as healthy Samsung Magician also shows my drive as healthy and running the latest firmware. As for what has caused the problems, I have had a few instances of unsafe shutdowns due to blown breakers and I have had some game crashes lately that result in the game as well as any running applications closing and putting me back at the desktop. So for example, the game will freeze and after a moment or two I am back at the desktop with the game, discord, browser etc all having been closed. Is this a sign of something going wrong or could something else with the game itself be causing crashes by overloading my drive? My PC still boots rather quickly, despite the scanning and repairing and otherwise runs very smoothly, I just don't know if this is a sign of a bigger issue or if the PC is just thinking there is a problem from a bad restart. Any tips? (I am currently using Samsung Magician to run a full scan on my drive and will post the screenshot of that when it is finished.)

Recently my laptop was a little buggy and slower than usual , So I did a general disk cleanup , driver reinstallation and a chkdsk , which apparently found errors in the C drive (A SSD partitioned to 3 drives C,E,F the D drive is a HDD) , which it fixes when i run a chkdsk command But then I realised that , even with consecutive runs , i.e I run a chkdsk C: /f /r /x (or) a chkdsk C: /f /r (or) chkdsk C: /r (I mean i dont think it really matters :/) , it fixes errors everytime , even when i run the same command twice after successful reboots I am not sure if my SSD is broken , coz the E and F partition comes out clean with a chkdsk command or should I just reinstall windows ?

For some time i wanted to replace a drive in my laptop. I take up 200GBs of space on a 700GB disc so I bought a 256GB SSD. I thought I'll jus run Macrium Reflect cloning and it will go smoothly, but the process always stops at 37% even though the connection is secure and there is no antivirus enabled. I tried to check the sectors using EaseUS partition master and it showed 2 bad sectors. I cannot use EaseUS disk copy because I can't resize partitions in this program. I know i could run CHKDSK but im extremely scared it will damage the drive and destroy my windows copy and all the important files. What do you think I should do? I'm scared i can't do anything. If I don't run CHKDSK i will not be able to copy the disc files, but if I do there is a chance I'll lose everything. Is there a solution I can't see? Maybe I could copy the contents of the drive onto the new one some other, safe way.

My friend gave me his broken laptop to try to get the files from the HDD that's inside. The laptop didn't boot so I took out the drive and connected it to my laptop with a SATA to USB cable. I couldn't access the drive, error message: "E:\ is not accessible. The parameter is incorrect." After watching a few videos, i decided to do a chkdsk on cmd. It took like 12h and now it looks like it's complete but I still can't access the drive yet. What do I have to do? Log: C:\Users\User1>chkdsk E: /f /r The type of the file system is NTFS. CHKDSK is verifying files (stage 1 of 5)... 0 percent complete. (6 of 256 file records processed) Deleting corrupt attribute record (128, "") from file record segment 6. 5 percent complete. (131 of 256 file records processed) File record segment 131 is unreadable. 5 percent complete. (136 of 256 file records processed) File record segment 136 is unreadable. 5 percent complete. (137 of 256 file records processed) File record segment 137 is unreadable. 5 percent complete. (148 of 256 file records processed) File record segment 148 is unreadable. 5 percent complete. (152 of 256 file records processed) File record segment 152 is unreadable. 6 percent complete. (156 of 256 file records processed) File record segment 156 is unreadable. 6 percent complete. (157 of 256 file records processed) File record segment 157 is unreadable. 6 percent complete. (158 of 256 file records processed) File record segment 158 is unreadable. 6 percent complete. (159 of 256 file records processed) File record segment 159 is unreadable. 6 percent complete. (164 of 256 file records processed) File record segment 164 is unreadable. 6 percent complete. (165 of 256 file records processed) File record segment 165 is unreadable. 7 percent complete. (180 of 256 file records processed) File record segment 180 is unreadable. 7 percent complete. (184 of 256 file records processed) File record segment 184 is unreadable. 8 percent complete. (216 of 256 file records processed) File record segment 216 is unreadable. 8 percent complete. (224 of 256 file records processed) File record segment 224 is unreadable. 8 percent complete. (225 of 256 file records processed) File record segment 225 is unreadable. 8 percent complete. (228 of 256 file records processed) File record segment 228 is unreadable. 8 percent complete. (229 of 256 file records processed) File record segment 229 is unreadable. 8 percent complete. (230 of 256 file records processed) File record segment 230 is unreadable. 9 percent complete. (231 of 256 file records processed) File record segment 231 is unreadable. 9 percent complete. (232 of 256 file records processed) File record segment 232 is unreadable. 9 percent complete. (233 of 256 file records processed) File record segment 233 is unreadable. 9 percent complete. (234 of 256 file records processed) File record segment 234 is unreadable. 9 percent complete. (235 of 256 file records processed) File record segment 235 is unreadable. 9 percent complete. (236 of 256 file records processed) File record segment 236 is unreadable. 9 percent complete. (237 of 256 file records processed) File record segment 237 is unreadable. 9 percent complete. (238 of 256 file records processed) File record segment 238 is unreadable. 9 percent complete. (239 of 256 file records processed) File record segment 239 is unreadable. 9 percent complete. (240 of 256 file records processed) File record segment 240 is unreadable. 9 percent complete. (241 of 256 file records processed) File record segment 241 is unreadable. 9 percent complete. (242 of 256 file records processed) File record segment 242 is unreadable. 256 file records processed. File verification completed. 0 large file records processed. 31 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 10 percent complete. (137 of 272 index entries processed) File record segment 140 is unreadable. 10 percent complete. (142 of 272 index entries processed) File record segment 141 is unreadable. 10 percent complete. (145 of 272 index entries processed) File record segment 144 is unreadable. 10 percent complete. (146 of 272 index entries processed) File record segment 145 is unreadable. 10 percent complete. (149 of 272 index entries processed) File record segment 160 is unreadable. 10 percent complete. (165 of 272 index entries processed) File record segment 168 is unreadable. 10 percent complete. (181 of 272 index entries processed) File record segment 188 is unreadable. 10 percent complete. (201 of 272 index entries processed) File record segment 200 is unreadable. 10 percent complete. (202 of 272 index entries processed) File record segment 201 is unreadable. 10 percent complete. (205 of 272 index entries processed) File record segment 204 is unreadable. 10 percent complete. (213 of 272 index entries processed) File record segment 212 is unreadable. 10 percent complete. (214 of 272 index entries processed) File record segment 213 is unreadable. 10 percent complete. (217 of 272 index entries processed) File record segment 220 is unreadable. 10 percent complete. (249 of 272 index entries processed) File record segment 248 is unreadable. 10 percent complete. (250 of 272 index entries processed) File record segment 249 is unreadable. 10 percent complete. (251 of 272 index entries processed) File record segment 250 is unreadable. 10 percent complete. (252 of 272 index entries processed) File record segment 251 is unreadable. 272 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 256 file SDs/SIDs processed. Security descriptor verification completed. Inserting data attribute into file 6. 9 data files processed. CHKDSK is verifying file data (stage 4 of 5)... 240 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 122077875 free clusters processed. Free space verification is complete.

Does anyone know if the Samsung Magician application and its "diagnostic scan" performs the same function as the 'chkdsk' feature in the command prompt? Or is it different?

This happens when I try to write to it. This happens when i try to scan for errors Some maps are readable, some are not I can't replicate it, but it sometimes shows 100% utilization on the drive, showing that system is using it and when looking at what specifically is using it it shows ntoskrnl.exe This is way beyond my league, any ideas on how could I fix this?

A friendly hello to you all First of all the brief backstory to my problem: Two hdd in a hdd docking station and one hdd on a sata to usb adaptor All on the same powered usb hub suddenly the two hdd are not recognized anymore During a transfer of some files with TotalCommander I got some errors from the file verification. Soon the two drives were gone. In fact they were still visible in TotalCommander and WinExplorer, also in DiskManagement (as RAW) but i cannot access my data. So far I tried: changing the hdd to another sata usb adaptor on different usb ports using the Error Checking Tool which said it cannot access the drive using chkdsk /f/r which says (transladed roughly) "the version and state of the volume cannot be detected and chkdsk is aborted" using Easeus Partition Master with no option to repair the file system Do you have any idea what else I could try? (he asked desperately and with tears and insanity in his eyes ) If it helps I could provide scrennshots (with german text though)

I turned my PC on yesterday and left the room, when I came back it prompted me to hit a key to cancel Chkdsk, I was too late and it already started doing it's thing. It has been about 14 hours now and it is only at 18% progress with an ETA of 65 hours and increasing. I haven't really had problems with the hard drive, it is 5 years old but the worse thing that happens is Windows Explorer is a bit slow, and to fix this I sign out and sign back in (Could this have caused Chkdsk?) With the current speed it should finish in 10 days. I have bought a new HDD to clone the data on to, but with the way this is going I don't know if I'll have a chance. I am contemplating shutting the PC down but I don't wanna lose important data, but I don't know how long this will take, it could take weeks but I need this for university work. Help guys, please.

My computer crashed and ran Windows Autorepair, it failed. I was stuck in an Autorepair loop and tried running chldsk for some reason and probably made it worse, what the fuck do I do, Ive tried Resetting the PC as an option too but it refuses to do it.

Hello there ! The Problem : My computer has been stuck for 8 hours+ on "Scanning and repairing drive (C:):...". No percentage was ever showned. The wheel is still turning. Nothing changed in 8h. The Context : chkdsk started automatically by Windows. The computer was safely shutdown prior to this chkdsk. The last time I checked Samsung Magician (mid-september) the SSD was perfectly healthy. My PC is about 7 month old, self built. Yesterday (9dec2022), I updated Windows 11 to 22H2 .This is my main suspect but I also updated my drivers for GPU and motherboard through Armourycrate and installed Blender 3.4 and FL Studio 21 through their websites the same day. From what I understood chdsk seems a bit useless for SSDs but since windows flagged my disk as dirty, something must be up. The Question : Now, Can I force shutdown my computer (power button) without major damage done to the system or to the data while chkdsk is "running" ? (Also, any Idea of why no percentage has ever shown, SSD thing ?) CPU AMD Ryzen 7 5800X Motherboard ASUS B550 F Wifi II RAM 2x16GB Kingston Fury Renegade 3600 MHz DDR4 GPU 1x Asus Strix 3070ti OC edition Case Phanteks P500 DRGB Storage 1Tb M2 NVME Samsung 980 Pro PSU Corsair HX750 (750W) Cooling Arctic Liquid Freezer II 360 ARGB Operating System Windows 11 22H2

So I got a bit bad news from chkdsk during a routine check, telling me I have bad sector/files I tried recover the files use Recuva, but not sure which ones are actually the problem files. I assume it's the files that missing their file path/name are the corrupted ones? (I recognized some of them, but didn't seem able to find any difference visually between the one on the corrupted drive, the recovered file and a backup) Other advices on recovering files after finding corruption with CHKDSK are appreciated.

So, I just bought a new hard drive. I'm upgrading my mass storage drive in my main PC from a 2.0TB one to a 5.0TB one. It's better all around. It's where I keep music, videos, pictures, and games. After stealing an extra SATA cable from my brother's DVD drive, I got to work. However, soon after scouring the internet to find the best cloning software, to get my 2TB drive's contents onto the 5TB one, I encountered an issue. When I installed the suggested program, Macrium Reflect, everything was working fine. Until, at 2% into the clone, every time, without fail, I get this error: Clone Failed - Read Failed - 13 - 32 Why is this? I've tried at least 6 times, each time changing settings, including the advanced settings, and even telling it to clone everything without checks. Still nothing. I then tried to run chkdsk E: /r, but that didn't work either: failing at about 60% the first time and failing when I wasn't watching the second time overnight. Here is the chkdsk copied directly from command prompt: Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>cskdsk E: /r /f 'cskdsk' is not recognized as an internal or external command, operable program or batch file. C:\WINDOWS\system32>chkdsk E: /r /f The type of the file system is NTFS. Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) y Volume dismounted. All opened handles to this volume are now invalid. Volume label is Local Disk 2. Stage 1: Examining basic file system structure ... 812544 file records processed. File verification completed. 3251 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 890300 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 38879 data files processed. CHKDSK is verifying Usn Journal... 39875560 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... Windows replaced bad clusters in file 53 of name \DOWNLO~1\GEFORC~4.EXE. Windows replaced bad clusters in file 9070 of name \MYPICT~1\WALLPA~1\MEGA_M~1.PNG. Windows replaced bad clusters in file 11178 of name \Steam\STEAMA~1\common\Portal 2\portal2\maps\SPEAF6~1.BSP. Windows replaced bad clusters in file 11249 of name \Steam\STEAMA~1\common\Portal 2\portal2\media\SP_A5_~1.BIK. Windows replaced bad clusters in file 14098 of name \DOWNLO~1\QUICKT~1.EXE. Windows replaced bad clusters in file 38996 of name \Steam\STEAMA~1\common\WARTHU~1\res\AIRCRA~1\NIMROD~1.BIN. Windows replaced bad clusters in file 48334 of name \Steam\STEAMA~1\common\BIOSHO~2\XGame\Movies\FITZRO~1.BIK. Windows replaced bad clusters in file 85542 of name \MYPICT~1\ALLOFT~1\iPod 5\2014-0~1\AL5154~1.MOV. Windows replaced bad clusters in file 225839 of name \Steam\STEAMA~1\common\SPACEE~1\Content\Textures\Models\CHARAC~1\Wildlife\CYBERW~1\CYBERW~1.DDS. Windows replaced bad clusters in file 248624 of name \ITUNES~1\Music\KOJIKO~2\THELEG~1\49THEL~1.MP3. Windows replaced bad clusters in file 252153 of name \MYPICT~1\ALLOFT~1\NIKOND~2\_DSC0759.NEF. Windows replaced bad clusters in file 253004 of name \MYPICT~1\ALLOFT~1\NIKOND~1\_DSC0760.JPG. Windows replaced bad clusters in file 253301 of name \MYPICT~1\ALLOFT~1\NIKOND~2\_DSC0760.NEF. Windows replaced bad clusters in file 268117 of name \Videos\YOUTUB~1\Videos\VIDEOA~1\SEQUEN~2.GIF. Windows replaced bad clusters in file 271506 of name \Steam\STEAMA~1\common\MIRROR~1\TdGame\CookedPC\Maps\SP04\SU2EDE~1.ME1. Windows replaced bad clusters in file 309589 of name \Videos\YOUTUB~1\PREMIE~1\ADOBEP~1\GREEN'~1.PRV\RENDER~1.AVI. Windows replaced bad clusters in file 477911 of name \SAVEDG~1\GAMEFI~1\SPECIE~1.0(A\SPECIE~1.0\Species.exe. Windows replaced bad clusters in file 544833 of name \MYPICT~1\ALLOFT~1\IPHONE~1\20ECEB~1\IPBB65~1.PNG. 812528 files processed. File data verification completed. An unspecified error occurred (766f6c756d652e63 470). I then tried a second time, with the same results. Here are those as well, for compeletion's sake. C:\WINDOWS\system32>chkdsk E: /r The type of the file system is NTFS. Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) n Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N) n C:\WINDOWS\system32>chkdsk E: /r The type of the file system is NTFS. Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) y Volume dismounted. All opened handles to this volume are now invalid. Volume label is Local Disk 2. Stage 1: Examining basic file system structure ... 812544 file records processed. File verification completed. 3247 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 890300 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 38879 data files processed. CHKDSK is verifying Usn Journal... 39884752 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... Windows replaced bad clusters in file 252153 of name \MYPICT~1\ALLOFT~1\NIKOND~2\_DSC0759.NEF. Windows replaced bad clusters in file 253004 of name \MYPICT~1\ALLOFT~1\NIKOND~1\_DSC0760.JPG. 812528 files processed. File data verification completed. An unspecified error occurred (766f6c756d652e63 470). C:\WINDOWS\system32> I would really not have to reinstall all ~200 of my games and reset all the programs that have stuff hooked to the drive. Any solution to this problem would be worthwhile, as long as it doesn't result in data loss.

i need help retrieving the files from found.000 that was created after running chkdsk on my pc.it's not showing up on any folders. It's being detected by yodot recovery (which is i don't want to spend $50 and using it just one time). i just need to know if there's a free software recovery for the found.000 folder or if there's none, how can i delete that folder that is not showing anywhere on my hard drive. please help

Hi, I am not sure what to do, I ran a chkdsk C: /f /x /r on my 7 months 3TB barracuda, it dismounted it, found a ton of bad clusters however it is taking forever to finish. ETA is 21 hours I suspect because of the message: the disk does not have enough space to replace bad clusters ( picture ) I ran seatools but it cannot see the drive. I am trying to salvage important data off of it but it is inaccessible. Can I just reboot and try to see if I could access the files? or is there a better way may be? Any help is appreciated. Regards. Ido

So I’m having an issue with my hard drive lately. I’ve been experiencing random blue screens and A LOT of freezing. I’ve spent this whole week trying to troubleshoot the issue and I’ve determined a few things: The HDD or OS is the source of the problem (I’ve tested running the system on a different install of windows on a different HDD) Running Chkdsk won’t help (the freezing happens so often that while running Chkdsk /r it freezes) The problem isn’t reported in event Viewer (I check there every time it blue screens and NO errors or warnings show at the time the PC crashed) If anybody has any tips that they think could help it would be greatly appreciated. (Image of HDD Specs below)

Hello Guys, I have an HP External Hard Drive of model PX3100, recently when i tried to open some specific folder or file from the hard drive, for a few minutes Explorer will not respond and the drive will disconnect and reconnect automatically, so i thought of formatting the drive but while taking backup the same things happened like re-connecting with the same specific files and folders, some of the files were rar and iso so i tried to extract/mount then copy from it but no use it stopped in the mid way with an alert message "Either the File is corrupted or missing files" kind of thing. After doing somethings i found out that MFT (Master File Table) is corrupted. So what are the things I've Done. 1. Tried using chkdsk 2. Tried using clean all 3. Tried to repair mbr 4. Tried all those three with Windows installation repair 5. Tried using Third Party Apps for repairing mbr and so END RESULT - Nothing couldn't resolve anything. If you guys know anything it would be helpful, i have spent lot of time and effort resolving this but couldn't, a normal quick surface test by a software took more than 6 hrs then think of how much time it would've taken for chkdsk and clean all commands and repeated for many times. Note: This is the second time some problem arised in this hard drive, already there was a problem and replaced it since i had an warranty. And all this within 2 years. I have another hard drive (Seagate) and I'm using it for more than 5 years, i didn't have any problems since now. Now you might ask why did i even bought from hp, i bought it for an extra offer when i bought a hp laptop. There are lot of weirdness going on hp products and i don't know why. And finally sorry for this long message.

Its been months since my hard drive has started giving issues. 1. Every time I boot up my PC, I get this error in the notification area - Scan to Repair Drive Errors. 2. It happened twice that after the chkdsk repair utility was executed, the files on my hard drive disappeared yet consuming space on the hard drive. 3. I had to run a data recovery software in order to recover those files. On research, I found that the files disappeared because of the chkdsk utility. The problem keeps arising although the S.M.A.R.T. status of my drive shows "Good" (used Speccy) I don't know if my HDD is about to die. The solution to this problem will be very much appreciated. Respect. - Sarvesh K.

So this morning, I remembered that the drive I use as an external HDD (via USB) has a Vista partition on it from the time when said HDD was on another laptop. I used to boot it from time to time just for fun but I hadn't done it in a long while. Since I was planning to delete the windows install from it and wanted to know what programs/data I should be looking to export before format, I decided to boot it again as an external HDD. I boot it up, I get the Vista loading bar then blue screen with a STOP code. I thought it must be some driver error or something of the sort. I try again in safe mode, same BSOD. At this point I don't look further into it since the partition was for another laptop and decided to just reboot Win 7 from my main drive. When rebooting, the drive just stopped working. When plugged, it would show up after 20-30 seconds as Local Disk (D:) but remains inaccessible with no size information or anything of that sort. I proceeded to install the drive on my second HDD bay to see if it's a faulty external HDD case. Same result. Drive shows up, can't be read from, chkdsk d: stays stuck on a blank line (doesn't even retrieve drive info, let alone start the check) and diskmgmt.msc keeps loading endlessly. The thing is, I know it's only a logical error and that there is no lost data because 1) No physical damage was done to the disk throughout this entire process, I've moved drives around countless times and 2) I went back after the drive became unreadable and tried to boot Vista again. It worked. Same Vista loading bar, same BSOD. The partition still works. But I don't know why my OS can't checkdisk the drive. So help would be appreciated Tell me if you need anymore info. Update: The drive is showing up as a device (Toshiba+model number), but the drive itself is still inaccessible/uncheckable. Some Minitool Partition Wizard screens (Check file system doesn't work, starts and remains stuck): https://imgur.com/a/GCC6Hmc https://imgur.com/a/XnfxDP1 https://imgur.com/a/O2k9pb9

I have a USB Stick 64 GB 2.0 (i know) which after formating and converting it to a bootable linux drive refuses to cooperate anymore what so ever. As soon as I try to format it a message pops up saying "No medium found on drive E:, put in a medium and try again". I can't open it manually, it shows me the same message but without the yellow warning sign. Using diskpart didn't help either, I can select the disk (size: 0B, free: 0B, neither Dyn nor GPT is marked asterisk) but as soon as I list the partitions, a message in the cmd window tells me that "there's no partitions on this drive that can be shown" When I try to create a primary partition on the usb stick via diskpart, a giant message pops up in the cmd window -> " Yes its plugged into a 2.0 Port, I tried other ones too and even 3.0. Chkdsk tells me :"cannot open volume for direct access"

lets first start with a little backstory. my 1tb hdd was constantly running on 100% in task manager so i looked up a fix online that worked. when i rebooted my pc the "scanning and repairing drive" window popped up, which i assumed was normal because i had to mess around in the cmd to fix the hard drive. however i had a short power outage and my pc just shut off, now im running the scan again and it has been stuck on 15% for over 4 hours. which is also the percentage it was at when the power went out. is my hdd fucked or is it normal for it to be taking so long?

So, recently I noticed my drive was running slowly, so I ran chkdsk.exe on it. I eventually cancelled it, since it was taking ages and the problem had goen away. When I got back to my computer the next day, I noticed that my hard drive (in Windows Explorer) had been given a group, which says "File Folder." I'm not sure why it was put there, or even how, but I know it was put there immediately after I cancelled the program. Here is what I mean. This is a comparison between my two drives in Windows Explorer. For some reason, my second drive has this "File Folder (7)" there. I have no clue why, or how do remove that. It's not that much of an issue, but it's just kind of annoying. I just don't like it there. I was wondering if anyone had any idea on how to remove it. Thanks, Matt.

.... Soo CHDSK just viped my 3tb mass storage drive ... I was backing up some data, moved a HDD from my NAS to my PC, disconnected one drive to be able to connect another drive. Restarting my PC to get the drive I just connected to show up, and when the PC booted up CHKDSK wanted to check the drive (I didn't watch it closely enough to cancel in time). When PC booted up after running CHKDSK, the WD 3Tb I just connected, had been assigned the drive name of the drive previously connected to that SATA port. In short -> I disconnected ":1TB#1" -> connected ":WD3Tb" -> restarted the PC -> the 3TB drive previously named ":WD3Tb" had now been renamed to ":1TB#1" and the drive was empty. Already tried some free data recovery tools, but to no avail. I have kept the drive disconnected since the incident. Log file found on the drive: _______________________________________________________________________________________ Checking file system on Q: The type of the file system is NTFS. Volume label is 1 TB # 1. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... Attribute record of type 0x80 and instance tag 0x8 is cross linked starting at 0xb68a9 for possibly 0x41 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x8 in file 0x9 is already in use. Deleting corrupt attribute record (128, $SDS) from file record segment 9. 256 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 276 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... The security data stream is missing from file 0x9. The security data stream size 0x0 should not be less than 0x40000. Deleting an index entry with Id 256 from index $SII of file 9. Deleting an index entry with Id 257 from index $SII of file 9. Deleting an index entry with Id 258 from index $SII of file 9. Deleting an index entry with Id 259 from index $SII of file 9. Deleting an index entry with Id 260 from index $SII of file 9. Deleting an index entry with Id 261 from index $SII of file 9. Deleting an index entry with Id 262 from index $SII of file 9. Deleting an index entry with Id 263 from index $SII of file 9. Deleting an index entry with Id 264 from index $SII of file 9. Deleting an index entry with Id 265 from index $SII of file 9. Deleting an index entry with Id 266 from index $SII of file 9. Deleting an index entry with Id 267 from index $SII of file 9. Deleting an index entry with Id 268 from index $SII of file 9. Deleting an index entry with Id 260 from index $SDH of file 9. Deleting an index entry with Id 267 from index $SDH of file 9. Deleting an index entry with Id 262 from index $SDH of file 9. Deleting an index entry with Id 258 from index $SDH of file 9. Deleting an index entry with Id 266 from index $SDH of file 9. Deleting an index entry with Id 256 from index $SDH of file 9. Deleting an index entry with Id 257 from index $SDH of file 9. Deleting an index entry with Id 261 from index $SDH of file 9. Deleting an index entry with Id 263 from index $SDH of file 9. Deleting an index entry with Id 264 from index $SDH of file 9. Deleting an index entry with Id 265 from index $SDH of file 9. Deleting an index entry with Id 259 from index $SDH of file 9. Deleting an index entry with Id 268 from index $SDH of file 9. Replacing invalid security id with default security id for file 0. Replacing invalid security id with default security id for file 1. Replacing invalid security id with default security id for file 2. Replacing invalid security id with default security id for file 6. Replacing invalid security id with default security id for file 8. Replacing invalid security id with default security id for file 9. Replacing invalid security id with default security id for file 11. Replacing invalid security id with default security id for file 24. Replacing invalid security id with default security id for file 25. Replacing invalid security id with default security id for file 26. Replacing invalid security id with default security id for file 27. Replacing invalid security id with default security id for file 29. Replacing invalid security id with default security id for file 30. Replacing invalid security id with default security id for file 31. Replacing invalid security id with default security id for file 32. Replacing invalid security id with default security id for file 33. Replacing invalid security id with default security id for file 34. Replacing invalid security id with default security id for file 35. Replacing invalid security id with default security id for file 36. 256 file SDs/SIDs processed. Security descriptor verification completed. 10 data files processed. The MFT mirror is different from the MFT. Correcting errors in the Master File Table (MFT) mirror. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 2861586 MB total disk space. 21588 KB in 6 files. 16 KB in 12 indexes. 0 KB in bad sectors. 155371 KB in use by the system. 65536 KB occupied by the log file. 2861414 MB available on disk. 4096 bytes in each allocation unit. 732566271 total allocation units on disk. 732522028 allocation units available on disk. Internal Info: 00 01 00 00 1d 00 00 00 1c 00 00 00 00 00 00 00 ................ 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ _______________________________________________________________________________________ It is not a life or death situation, I have my personal stuff backed up, but a loss of 2.5Tb still stings somewhat :wacko: Any suggestions for software that (doesn't cost a fortune) that could solve this problem? Or any other possible solution? Or should I just suck it up and reformat the drive Appreciate any input from you guys and girls! Hope you all are having a nice weekend!

Hi guys, My pc has been rebooting uncontrollably and it fixed for a few days then came back, I ran a chkdsk and it came up with this "A disk read error occuredc0000185 The disk does not have enough space to replace bad clusters Detected in file 77843 of name /hiberfil.sys." Any ideas? Thanks

So recently I got a blue screen with error Kernel_data_inpage_error. I looked this up and I ran chkdsk (exact command I used was chkdsk c: /f /r). It was going well until I reached 12%. Currently it appears to be stuck at 12% and has been for quite a while now. However the loading wheel animation thing is still moving so the computer itself is still running. Should I wait longer or should I do something? I'm worried to stop it in case of damaged data and such. What should I do? OS: Windows 8.1 FYI: I have never had a bsod before, even with the addition of my new gpu. If you need more info, please say so. EDIT: The session seems to have gone through albeit taking for-fucking-ever. Thanks for your help, those who replied.

A few weeks ago 3 windows updates kept failing. Newer updates installed fine but 3 old ones never worked. I tried lots of things but there is just an error on my drive ( an SSD btw ) somewhere, so CHKDSK sould be the solution. By pure luck, I found the folder with the specific file that's ( most likely ) causing the problem, it can't be deleted because of an drive I/O error. So is there a way to run a chkdsk like thing on that specific file, or some way to fix it now i know where it is. Since CHKDSK is never totally risk free I have been putting it off till now