Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Chkdsk Program Download
19 views
Skip to first unread message
Janae Nowinski
Dec 30, 2023, 3:44:55 PM12/30/23
to
Checks the file system and file system metadata of a volume for logical and physical errors. If used without parameters, chkdsk displays only the status of the volume and does not fix any errors. If used with the /f, /r, /x, or /b parameters, it fixes errors on the volume.
Membership in the local Administrators group, or equivalent, is the minimum required to run chkdsk. To open a command prompt window as an administrator, right-click Command prompt in the Start menu, and then click Run as administrator.
chkdsk program download
DOWNLOAD https://t.co/KqTv4KFoUP
Interrupting chkdsk is not recommended. However, canceling or interrupting chkdsk should not leave the volume any more corrupt than it was before chkdsk was run. Running chkdsk again checks and should repair any remaining corruption on the volume.
If you choose to check the drive the next time you restart the computer, chkdsk checks the drive and corrects errors automatically when you restart the computer. If the drive partition is a boot partition, chkdsk automatically restarts the computer after it checks the drive.
You can also use the chkntfs /c command to schedule the volume to be checked the next time the computer is restarted. Use the fsutil dirty set command to set the volume's dirty bit (indicating corruption), so that Windows runs chkdsk when the computer is restarted.
You should use chkdsk occasionally on FAT and NTFS file systems to check for disk errors. Chkdsk examines disk space and disk use and provides a status report specific to each file system. The status report shows errors found in the file system. If you run chkdsk without the /f parameter on an active partition, it might report spurious errors because it cannot lock the drive.
Because repairs on FAT file systems usually change a disk's file allocation table and sometimes cause a loss of data, chkdsk might display a confirmation message similar to the following:
If you press Y, Windows saves each lost chain in the root directory as a file with a name in the format File.chk. When chkdsk finishes, you can check these files to see if they contain any data you need.
If you specify the /f parameter, chkdsk displays an error message if there are open files on the disk. If you do not specify the /f parameter and open files exist, chkdsk might report lost allocation units on the disk. This could happen if open files have not yet been recorded in the file allocation table. If chkdsk reports the loss of a large number of allocation units, consider repairing the disk.
Because the Shadow Copies for Shared Folders source volume cannot be locked while Shadow Copies for Shared Folders is enabled, running chkdsk against the source volume might report false errors or cause chkdsk to unexpectedly quit. You can, however, check shadow copies for errors by running chkdsk in Read-only mode (without parameters) to check the Shadow Copies for Shared Folders storage volume.
On servers that are infrequently restarted, you may want to use the chkntfs or the fsutil dirty query commands to determine whether the volume's dirty bit is already set before running chkdsk.
If it encounters errors, chkdsk pauses and displays messages. Chkdsk finishes by displaying a report that lists the status of the disk. You cannot open any files on the specified drive until chkdsk finishes.
It wanted to check my harddrive for consistency. I would've said no but the time expired before I could press a key so it ran. Luckily it wasn't ransomware. Still not convinced it wasn't a virus but if it isn't I would like to know why this program ran and what it is for.
Windows provides a utility tool known as chkdsk that can correct most errors on a storage disk. The chkdsk utility must be run from an administrator command prompt to perform its work. In this How To article, we will learn what chkdsk does and how to use it to overcome the issues above, as well as others not listed in the intro here.
How does a hard disk become corrupted? Another good question. Anytime Windows shuts down abnormally or has a system crash, it can cause corruption. Over time, you can expect that you will experience such corruption. Running chkdsk as part of a normal maintenance routine is good practice if you wish to do so.
The above screenshot shows the result of chkdsk with /f option used on the C: partition. As you can see the command resulted in not being run because of the disk being used by another process. It offers to run on the next restart if desired, typing y allows for the scan to take place. This is common when running chkdsk while booted to Windows.
When chkdsk is run without options, it runs in Read Only mode and reports on the overall health of the filesystem on the specified partition. This is a good scan to run on your disk partitions as a routine maintenance of your disks. If the scan check results in finding an issue with the filesystem, then running or scheduling a run of chkdsk /f will then attempt to fix the found error(s).
Now that we have covered the primary usage of the chkdsk utility, it is time to delve into using the utility on a Windows System OS disk. We have already discovered that chkdsk will not run on a booted Windows System C: partition/volume unless/until a restart of the computer occurs. You may have noticed at this point that chkdsk works on individual partitions on a disk. A Windows System OS disk formatted as a GPT disk, as most modern Windows installs are, may have several partitions on a disk. The fact is that disk corruption may exist on any partition on a disk. Corruption may exist on more than one partition on a single disk as well. Additionally, Windows System disks will have partitions on a disk that are not assigned drive letters which makes using the chkdsk utility on them a more challenging task.
As you can see in the screenshot above, this disk has four partitions. They are a Recovery (450 MB), EFI (99 MB), Windows 10 PRO (237.08 GB), and OEM (861 MB). Take note that only one partition has a drive letter assigned, which is the Windows 10 partition having the letter (C:) assigned as you would expect. The other three partitions have no letter assignment. In order to use the chkdsk utility to look for and fix disk errors the utility must be run on each partition of the disk, one at a time. It is necessary then to temporarily assign drive letters to the partitions not having letter assignments to perform a chkdsk scan on them.
Notice that all volumes installed on the computer are displayed using this command including those on other disks. You should note here that we only need to assign letters to those partitions that do not have existing letter assignments so that chkdsk can be run on them. In the screenshot above these partitions/volumes are Volumes 1, 3, and 4.
Now, to run the chkdsk command, it is necessary to leave the diskpart utility. At the prompt type exit. This will end the utility returning your command prompt to read C:\\WINDOWS\\system32>. At this prompt you can now run the chkdsk utility scans desired. Have a look at the screenshot below for running the command chkdsk x:/f to illustrate.
It is recommended when disk corruption is suspected that you forego use of the /f option of the chkdsk command and instead use the /r option. Using the /r option includes /f in the scan so you will be doing both using the /r option.
Once your chkdsk scan completes you can now use the diskpart utility again to remove the drive letter you assigned to the volume/partition so that all is back to normal. At the Windows command prompt type
You can follow these steps to assign drive letters to the other non-lettered partitions on disk so that chkdsk scans can be performed on them. Chances are that you will find errors on one or more of these partitions. Once the chkdsk scans and error corrections are applied you should then be able to backup or restore your disk.
Important note: If the output of badblocks is going to be fed to the e2fsck or mke2fs programs, it is important that the block size is properly specified, since the block numbers which are generated are very dependent on the block size in use by the filesystem. For this reason, it is strongly recommended that users not run badblocks directly, but rather use the -c option of the e2fsck and mke2fs programs.
The command is available in MS-DOS versions 1 and later.[7]CHKDSK is implemented as an external command. MS-DOS versions 2.x - 4.x use chkdsk.com as the executable file. MS-DOS versions 5.x and later use chkdsk.exe as the executable file.[8]
Can I recover from chkdsk d: /x /f ?
Page 1 of 1
[ 11 posts ] Previous topic Next topic AuthorMessageDriver-21 Post subject: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 17:00
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeI have an Elements external USB drive that was corrupted. I ran this command to fix it. The problem is it deleted the index entry files I needed. Is there a way to recover the data from these two files below? I have not written to the HD since.
C:\Users\user>chkdsk d: /x /f
The type of the file system is NTFS.
Deleting index entry filename-here.txt in index $I30 of file 452.
Deleting index entry filename-2-here.txt in index $I30 of file 452.
Any suggestions would be greatly appreciated.
Thanks.
S
Top rogfanther Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 17:28
Joined: October 16th, 2013, 13:21
Posts: 717
Location: BrazilTry with Recuva, GetDataBack or R-Studio.
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 18:50
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeI tried Recuva in the past and it didn't bring up the file I'm looking for. Maybe I'll try again with the latest version if R-studio doesn't work.
Currently scanning using R-studio which looks a bit more robust. Should I scan for all files or can I focus in on just the .txt files which I am after?
Since I'm after the data in "$I30 of file 452", how does that translate to the hex editor so I can see the data in that space? Or it doesn't work that way?
Deleting index entry filename-here.txt in index $I30 of file 452.
Deleting index entry filename-2-here.txt in index $I30 of file 452.
Thanks.
S
Top Alexey Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 23:08
Joined: June 17th, 2017, 18:30
Posts: 37
Location: RussiaDeleting index entries is a consequence of the problem, not the problem itself.
NTFS has an MFT entry for a file, and then in every directory containing that file (which may be more than one) it will store the index entry. If the file ceases to exist, index entries should be removed. This normally happens as a part of file deletion, but if there is a power failure or somethnig, or if the file is damaged instead of deleted, there is a stale index entry pointing to the file which does not exist any longer. These index entries are cleaned up during checkdisk.
Deleting index entry filename-here.txt in index $I30 of file 452.
translates into
Deleting index entry (a pointer to) filename-here.txt in index $I30 (normal directory index) of file 452 (of a directory which has MFT ID 452), because the file no longer exists.
You should look earlier in the log to see what happens with the file itself.
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 14:09
Joined: February 6th, 2018, 16:28
Posts: 5
Location: Europe"You should look earlier in the log to see what happens with the file itself."
There is nothing in the chkdsk log file with this filename before this entry. Just before the lines with the two files I'm trying to recover it displayed the following lines below. $130 matches but the file number is different.:
"Correcting error in index $I30 for file 441.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 441.
Sorting index $I30 in file 441."
I've finished the scan. There are a bunch of .txt files with numbers for filenames. Is there a way to search for the old file name or contents of these files in R-studio?
Thanks.
S
Top lcoughey Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 14:30
Joined: February 9th, 2009, 16:13
Posts: 2540
Location: Ontario, CanadaGenerally speaking, chkdsk causes irreversible damage and should never be run on a drive that isn't backed up.
_________________
Luke
Recovery Force Data Recovery
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 17:02
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeNow the external drive is not booting and I'm getting a denied error. This is why I originally ran the chkdsk program to begin with so I could access the drive. I'm not going to do the chkdsk again. This occurred on Windows. I switched to the Linux computer and the drive shows up normally again. Now I have to re-install R-studio and run a scan again.
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 17:04
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeThis external WD Elements drive was supposed to be the main backup drive. My 2nd backup was a USB flash drive and that died too as well as the original SSD drive in my laptop which died first.
Top mr_spokk Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 17:49
Joined: May 21st, 2007, 16:10
Posts: 1593
Location: Gothenburg/ SwedenDriver-21 wrote:Now the external drive is not booting and I'm getting a denied error. This is why I originally ran the chkdsk program to begin with so I could access the drive. I'm not going to do the chkdsk again. This occurred on Windows. I switched to the Linux computer and the drive shows up normally again. Now I have to re-install R-studio and run a scan again.
First option should be to make a clone and work with that...not with the original drive.
_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
-it.se
Top Spildit Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 10th, 2018, 15:47
Joined: December 19th, 2006, 8:49
Posts: 11048
Location: Portugallcoughey wrote:Generally speaking, chkdsk causes irreversible damage and should never be run on a drive that isn't backed up.
FULLY AGREEE !!!!
I did have a HUGE problem myself with my MAIN system last week !!!
Was running just fine and did never had a single problem for almost 10 years now.
It's running XP on a old 80 GB 7200.10 drive with 3 partitions. One for the OS and 2 for tools. Then i have other drives plugged for data.
It was raining allot here and thundering and while the computer was running and writting stuff the power went down. No UPS. So when the system re-started there was a message complaining about missing windows .dll.
I boot from the 1TB SATA drive that i have on the same system and chose Hirens mini xp. Tryed to replace the damaged file on C: of the main 7200.10 drive and it didn't allow me to write. Complained about damaged file and couldn't write at all. Power off the system and run MHDD on the drive. S.M.A.R.T. checked ok. Full surface scan checked ok, neither a single bad sector (or slow for that matter) all grey blocks (fast) and G-List was empty. Ok, disk was fine. Loaded min-xp again and run checkdisk with option to fix errors.
It created a found.000 folder or whatever on c: and now i was able to copy the missing .dll (damaged) back to the drive. Power off/on and booted from the main drive .... guess what ?
When window booted up there was no longer desktop background image and my documents, etc were gone ... I found most of the stuff inside sub-folders of found.000 that checkdisk created .... BIG MESS !!!!
That chkdsk is just BAD !!!! It's only good to diagnose problems with the file system and be sure that all is still in order. Example - you create a full backup and then you run chkdsk on the main drive to see if it have problems. If not you are good to go !!!
On my case i don't think i would be able to recover the damage done by chkdsk myself even with my collection of tools like R-Studio, GetDataBack, etc ....
The sollution that i did use to "solve" my issue was to restore the backup (full clone) of the drive. I'm using this 80 GB drive mainly for OS and to test firmware tools so it doesn't change much over time. Even so i do have a full clone done from 2 in 2 weeks with "savepart". I use sector by sector clone.
I did restore the clone to the 7200.10 power off/on and run chkdsk on it. All fine without a single error. Just to be sure i did left prime95 running for a day and memtest running for an entire night to test for hardware problems. Looks good to me now. Re-run the chkdsk no found.000 so far !
If you run chkdsk and you see something like found.000 on the drive letter you run the command you are in for pain ... oh and make sure you have option to show hidden files enabled as well !!
_________________
Donations (if my help/knowledge was of use to you) : -
Top Spildit Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 10th, 2018, 15:52
Joined: December 19th, 2006, 8:49
Posts: 11048
Location: PortugalDriver-21 wrote:This external WD Elements drive was supposed to be the main backup drive. My 2nd backup was a USB flash drive and that died too as well as the original SSD drive in my laptop which died first.
Flash have re-write cycles limits meaning that flash memory will die if you write to it more then it can take. Also its based on electrical charges that might dis-charge over time. Conventional HDD are based on magnetic storage ....
I'm not the best person in the world to talk about this but for me flash looks way less reliable for long term storage / backup ....
Even to move files around i only use conventional 2.5 HDDs now. For some reason i don't like "flash" as all the experiences that i had with it were not the best ...
Flash pen drives are only of use to move data that you don't mind to loose like i use that to copy movies/series from the PC main drive to watch on the television. I do have a big TV set that can read MPG, MKV, etc from the USB drives so you can use pen drives for that kind of stuff but NEVER to store important data that you want to keep over the years ....
_________________
Donations (if my help/knowledge was of use to you) : -
Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject AscendingDescending Page 1 of 1
[ 11 posts ] Main Forums home Conventional hard drives
35fe9a5643
Membership in the local Administrators group, or equivalent, is the minimum required to run chkdsk. To open a command prompt window as an administrator, right-click Command prompt in the Start menu, and then click Run as administrator.
chkdsk program download
DOWNLOAD https://t.co/KqTv4KFoUP
Interrupting chkdsk is not recommended. However, canceling or interrupting chkdsk should not leave the volume any more corrupt than it was before chkdsk was run. Running chkdsk again checks and should repair any remaining corruption on the volume.
If you choose to check the drive the next time you restart the computer, chkdsk checks the drive and corrects errors automatically when you restart the computer. If the drive partition is a boot partition, chkdsk automatically restarts the computer after it checks the drive.
You can also use the chkntfs /c command to schedule the volume to be checked the next time the computer is restarted. Use the fsutil dirty set command to set the volume's dirty bit (indicating corruption), so that Windows runs chkdsk when the computer is restarted.
You should use chkdsk occasionally on FAT and NTFS file systems to check for disk errors. Chkdsk examines disk space and disk use and provides a status report specific to each file system. The status report shows errors found in the file system. If you run chkdsk without the /f parameter on an active partition, it might report spurious errors because it cannot lock the drive.
Because repairs on FAT file systems usually change a disk's file allocation table and sometimes cause a loss of data, chkdsk might display a confirmation message similar to the following:
If you press Y, Windows saves each lost chain in the root directory as a file with a name in the format File.chk. When chkdsk finishes, you can check these files to see if they contain any data you need.
If you specify the /f parameter, chkdsk displays an error message if there are open files on the disk. If you do not specify the /f parameter and open files exist, chkdsk might report lost allocation units on the disk. This could happen if open files have not yet been recorded in the file allocation table. If chkdsk reports the loss of a large number of allocation units, consider repairing the disk.
Because the Shadow Copies for Shared Folders source volume cannot be locked while Shadow Copies for Shared Folders is enabled, running chkdsk against the source volume might report false errors or cause chkdsk to unexpectedly quit. You can, however, check shadow copies for errors by running chkdsk in Read-only mode (without parameters) to check the Shadow Copies for Shared Folders storage volume.
On servers that are infrequently restarted, you may want to use the chkntfs or the fsutil dirty query commands to determine whether the volume's dirty bit is already set before running chkdsk.
If it encounters errors, chkdsk pauses and displays messages. Chkdsk finishes by displaying a report that lists the status of the disk. You cannot open any files on the specified drive until chkdsk finishes.
It wanted to check my harddrive for consistency. I would've said no but the time expired before I could press a key so it ran. Luckily it wasn't ransomware. Still not convinced it wasn't a virus but if it isn't I would like to know why this program ran and what it is for.
Windows provides a utility tool known as chkdsk that can correct most errors on a storage disk. The chkdsk utility must be run from an administrator command prompt to perform its work. In this How To article, we will learn what chkdsk does and how to use it to overcome the issues above, as well as others not listed in the intro here.
How does a hard disk become corrupted? Another good question. Anytime Windows shuts down abnormally or has a system crash, it can cause corruption. Over time, you can expect that you will experience such corruption. Running chkdsk as part of a normal maintenance routine is good practice if you wish to do so.
The above screenshot shows the result of chkdsk with /f option used on the C: partition. As you can see the command resulted in not being run because of the disk being used by another process. It offers to run on the next restart if desired, typing y allows for the scan to take place. This is common when running chkdsk while booted to Windows.
When chkdsk is run without options, it runs in Read Only mode and reports on the overall health of the filesystem on the specified partition. This is a good scan to run on your disk partitions as a routine maintenance of your disks. If the scan check results in finding an issue with the filesystem, then running or scheduling a run of chkdsk /f will then attempt to fix the found error(s).
Now that we have covered the primary usage of the chkdsk utility, it is time to delve into using the utility on a Windows System OS disk. We have already discovered that chkdsk will not run on a booted Windows System C: partition/volume unless/until a restart of the computer occurs. You may have noticed at this point that chkdsk works on individual partitions on a disk. A Windows System OS disk formatted as a GPT disk, as most modern Windows installs are, may have several partitions on a disk. The fact is that disk corruption may exist on any partition on a disk. Corruption may exist on more than one partition on a single disk as well. Additionally, Windows System disks will have partitions on a disk that are not assigned drive letters which makes using the chkdsk utility on them a more challenging task.
As you can see in the screenshot above, this disk has four partitions. They are a Recovery (450 MB), EFI (99 MB), Windows 10 PRO (237.08 GB), and OEM (861 MB). Take note that only one partition has a drive letter assigned, which is the Windows 10 partition having the letter (C:) assigned as you would expect. The other three partitions have no letter assignment. In order to use the chkdsk utility to look for and fix disk errors the utility must be run on each partition of the disk, one at a time. It is necessary then to temporarily assign drive letters to the partitions not having letter assignments to perform a chkdsk scan on them.
Notice that all volumes installed on the computer are displayed using this command including those on other disks. You should note here that we only need to assign letters to those partitions that do not have existing letter assignments so that chkdsk can be run on them. In the screenshot above these partitions/volumes are Volumes 1, 3, and 4.
Now, to run the chkdsk command, it is necessary to leave the diskpart utility. At the prompt type exit. This will end the utility returning your command prompt to read C:\\WINDOWS\\system32>. At this prompt you can now run the chkdsk utility scans desired. Have a look at the screenshot below for running the command chkdsk x:/f to illustrate.
It is recommended when disk corruption is suspected that you forego use of the /f option of the chkdsk command and instead use the /r option. Using the /r option includes /f in the scan so you will be doing both using the /r option.
Once your chkdsk scan completes you can now use the diskpart utility again to remove the drive letter you assigned to the volume/partition so that all is back to normal. At the Windows command prompt type
You can follow these steps to assign drive letters to the other non-lettered partitions on disk so that chkdsk scans can be performed on them. Chances are that you will find errors on one or more of these partitions. Once the chkdsk scans and error corrections are applied you should then be able to backup or restore your disk.
Important note: If the output of badblocks is going to be fed to the e2fsck or mke2fs programs, it is important that the block size is properly specified, since the block numbers which are generated are very dependent on the block size in use by the filesystem. For this reason, it is strongly recommended that users not run badblocks directly, but rather use the -c option of the e2fsck and mke2fs programs.
The command is available in MS-DOS versions 1 and later.[7]CHKDSK is implemented as an external command. MS-DOS versions 2.x - 4.x use chkdsk.com as the executable file. MS-DOS versions 5.x and later use chkdsk.exe as the executable file.[8]
Can I recover from chkdsk d: /x /f ?
Page 1 of 1
[ 11 posts ] Previous topic Next topic AuthorMessageDriver-21 Post subject: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 17:00
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeI have an Elements external USB drive that was corrupted. I ran this command to fix it. The problem is it deleted the index entry files I needed. Is there a way to recover the data from these two files below? I have not written to the HD since.
C:\Users\user>chkdsk d: /x /f
The type of the file system is NTFS.
Deleting index entry filename-here.txt in index $I30 of file 452.
Deleting index entry filename-2-here.txt in index $I30 of file 452.
Any suggestions would be greatly appreciated.
Thanks.
S
Top rogfanther Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 17:28
Joined: October 16th, 2013, 13:21
Posts: 717
Location: BrazilTry with Recuva, GetDataBack or R-Studio.
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 18:50
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeI tried Recuva in the past and it didn't bring up the file I'm looking for. Maybe I'll try again with the latest version if R-studio doesn't work.
Currently scanning using R-studio which looks a bit more robust. Should I scan for all files or can I focus in on just the .txt files which I am after?
Since I'm after the data in "$I30 of file 452", how does that translate to the hex editor so I can see the data in that space? Or it doesn't work that way?
Deleting index entry filename-here.txt in index $I30 of file 452.
Deleting index entry filename-2-here.txt in index $I30 of file 452.
Thanks.
S
Top Alexey Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 6th, 2018, 23:08
Joined: June 17th, 2017, 18:30
Posts: 37
Location: RussiaDeleting index entries is a consequence of the problem, not the problem itself.
NTFS has an MFT entry for a file, and then in every directory containing that file (which may be more than one) it will store the index entry. If the file ceases to exist, index entries should be removed. This normally happens as a part of file deletion, but if there is a power failure or somethnig, or if the file is damaged instead of deleted, there is a stale index entry pointing to the file which does not exist any longer. These index entries are cleaned up during checkdisk.
Deleting index entry filename-here.txt in index $I30 of file 452.
translates into
Deleting index entry (a pointer to) filename-here.txt in index $I30 (normal directory index) of file 452 (of a directory which has MFT ID 452), because the file no longer exists.
You should look earlier in the log to see what happens with the file itself.
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 14:09
Joined: February 6th, 2018, 16:28
Posts: 5
Location: Europe"You should look earlier in the log to see what happens with the file itself."
There is nothing in the chkdsk log file with this filename before this entry. Just before the lines with the two files I'm trying to recover it displayed the following lines below. $130 matches but the file number is different.:
"Correcting error in index $I30 for file 441.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 441.
Sorting index $I30 in file 441."
I've finished the scan. There are a bunch of .txt files with numbers for filenames. Is there a way to search for the old file name or contents of these files in R-studio?
Thanks.
S
Top lcoughey Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 14:30
Joined: February 9th, 2009, 16:13
Posts: 2540
Location: Ontario, CanadaGenerally speaking, chkdsk causes irreversible damage and should never be run on a drive that isn't backed up.
_________________
Luke
Recovery Force Data Recovery
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 17:02
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeNow the external drive is not booting and I'm getting a denied error. This is why I originally ran the chkdsk program to begin with so I could access the drive. I'm not going to do the chkdsk again. This occurred on Windows. I switched to the Linux computer and the drive shows up normally again. Now I have to re-install R-studio and run a scan again.
Top Driver-21 Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 17:04
Joined: February 6th, 2018, 16:28
Posts: 5
Location: EuropeThis external WD Elements drive was supposed to be the main backup drive. My 2nd backup was a USB flash drive and that died too as well as the original SSD drive in my laptop which died first.
Top mr_spokk Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 7th, 2018, 17:49
Joined: May 21st, 2007, 16:10
Posts: 1593
Location: Gothenburg/ SwedenDriver-21 wrote:Now the external drive is not booting and I'm getting a denied error. This is why I originally ran the chkdsk program to begin with so I could access the drive. I'm not going to do the chkdsk again. This occurred on Windows. I switched to the Linux computer and the drive shows up normally again. Now I have to re-install R-studio and run a scan again.
First option should be to make a clone and work with that...not with the original drive.
_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
-it.se
Top Spildit Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 10th, 2018, 15:47
Joined: December 19th, 2006, 8:49
Posts: 11048
Location: Portugallcoughey wrote:Generally speaking, chkdsk causes irreversible damage and should never be run on a drive that isn't backed up.
FULLY AGREEE !!!!
I did have a HUGE problem myself with my MAIN system last week !!!
Was running just fine and did never had a single problem for almost 10 years now.
It's running XP on a old 80 GB 7200.10 drive with 3 partitions. One for the OS and 2 for tools. Then i have other drives plugged for data.
It was raining allot here and thundering and while the computer was running and writting stuff the power went down. No UPS. So when the system re-started there was a message complaining about missing windows .dll.
I boot from the 1TB SATA drive that i have on the same system and chose Hirens mini xp. Tryed to replace the damaged file on C: of the main 7200.10 drive and it didn't allow me to write. Complained about damaged file and couldn't write at all. Power off the system and run MHDD on the drive. S.M.A.R.T. checked ok. Full surface scan checked ok, neither a single bad sector (or slow for that matter) all grey blocks (fast) and G-List was empty. Ok, disk was fine. Loaded min-xp again and run checkdisk with option to fix errors.
It created a found.000 folder or whatever on c: and now i was able to copy the missing .dll (damaged) back to the drive. Power off/on and booted from the main drive .... guess what ?
When window booted up there was no longer desktop background image and my documents, etc were gone ... I found most of the stuff inside sub-folders of found.000 that checkdisk created .... BIG MESS !!!!
That chkdsk is just BAD !!!! It's only good to diagnose problems with the file system and be sure that all is still in order. Example - you create a full backup and then you run chkdsk on the main drive to see if it have problems. If not you are good to go !!!
On my case i don't think i would be able to recover the damage done by chkdsk myself even with my collection of tools like R-Studio, GetDataBack, etc ....
The sollution that i did use to "solve" my issue was to restore the backup (full clone) of the drive. I'm using this 80 GB drive mainly for OS and to test firmware tools so it doesn't change much over time. Even so i do have a full clone done from 2 in 2 weeks with "savepart". I use sector by sector clone.
I did restore the clone to the 7200.10 power off/on and run chkdsk on it. All fine without a single error. Just to be sure i did left prime95 running for a day and memtest running for an entire night to test for hardware problems. Looks good to me now. Re-run the chkdsk no found.000 so far !
If you run chkdsk and you see something like found.000 on the drive letter you run the command you are in for pain ... oh and make sure you have option to show hidden files enabled as well !!
_________________
Donations (if my help/knowledge was of use to you) : -
Top Spildit Post subject: Re: Can I recover from chkdsk d: /x /f ?Posted: February 10th, 2018, 15:52
Joined: December 19th, 2006, 8:49
Posts: 11048
Location: PortugalDriver-21 wrote:This external WD Elements drive was supposed to be the main backup drive. My 2nd backup was a USB flash drive and that died too as well as the original SSD drive in my laptop which died first.
Flash have re-write cycles limits meaning that flash memory will die if you write to it more then it can take. Also its based on electrical charges that might dis-charge over time. Conventional HDD are based on magnetic storage ....
I'm not the best person in the world to talk about this but for me flash looks way less reliable for long term storage / backup ....
Even to move files around i only use conventional 2.5 HDDs now. For some reason i don't like "flash" as all the experiences that i had with it were not the best ...
Flash pen drives are only of use to move data that you don't mind to loose like i use that to copy movies/series from the PC main drive to watch on the television. I do have a big TV set that can read MPG, MKV, etc from the USB drives so you can use pen drives for that kind of stuff but NEVER to store important data that you want to keep over the years ....
_________________
Donations (if my help/knowledge was of use to you) : -
Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject AscendingDescending Page 1 of 1
[ 11 posts ] Main Forums home Conventional hard drives
35fe9a5643
0 new messages