Home  ›  Is It Ok if Chkdsk Runs in Read-only Mode on Win Xp 32

Is It Ok if Chkdsk Runs in Read-only Mode on Win Xp 32

Written By mercredi 9 mars 2022 Add Comment Edit

Organisation tool in DOS, OS/2 and Windows

chkdsk
CHKDSK WIN10.PNG

chkdsk.exe in action on drive C: in Windows 10
Original author(s) Tim Paterson
Developer(s) SCP, Microsoft, IBM, DR, Datalight, Novell, Toshiba, PhysTechSoft, ReactOS Contributors
Initial release 1980; 42 years ago  (1980)
Written in MS-DOS: x86 associates language
FreeDOS, ReactOS: C
Operating system 86-DOS, MS-DOS, PC DOS, MSX-DOS, SISNE plus, OS/ii, eComStation, ArcaOS, FlexOS, DR-DOS, ROM-DOS, 4690 OS, PTS-DOS, Windows, FreeDOS, ReactOS
Platform Cross-platform
Type Command
License MS-DOS: MIT
FreeDOS, ReactOS: GPLv2

In computing, CHKDSK (short for "check disk") is a system tool and command in DOS, Digital Research FlexOS,[1] IBM/Toshiba 4690 Os,[two] IBM Bone/2,[3] Microsoft Windows and related operating systems. It verifies the file system integrity of a volume and attempts to set logical file arrangement errors. Information technology is similar to the fsck command in Unix and similar to Microsoft ScanDisk which co-existed with CHKDSK in Windows 9x and MS-DOS half dozen.x.

Implementations [edit]

An early implementation of a 'CheckDisk' was the CHECKDSK that was a part of Digital Equipment Corporation hardware's diagnostics, running on early 1970s TENEX and TOPS-xx.[iv] [5]

SCP 86-DOS [edit]

The CHKDSK command was offset implemented in 1980 by Tim Paterson and included in Seattle Reckoner Products 86-DOS.[6]

MS-DOS / IBM PC DOS [edit]

CHKDSK.COM (among several other COM files) in IBM PC DOS 1.0.

The control is available in MS-DOS versions 1 and afterward.[seven] CHKDSK is implemented as an external command. MS-DOS versions ii.ten - 4.x use chkdsk.com as the executable file. MS-DOS versions five.x and later utilize chkdsk.exe as the executable file.[eight]

MS-DOS 5.0 bug [edit]

CHKDSK and UNDELETE in MS-DOS 5.0 have a bug which tin can corrupt data: If the file allocation tabular array of a disk uses 256 sectors, running CHKDSK /F can cause data loss and running UNDELETE tin cause unpredictable results. This commonly affects disks with a capacity of approximately a multiple of 128 MB. This applies to CHKDSK.EXE and UNDELETE.EXE begetting a datestamp of April 9, 1991. This bug was fixed in MS-DOS 5.0a.[nine]

Microsoft Windows [edit]

CHKDSK can exist run from DOS prompt, Windows Explorer, Windows Command Prompt, Windows PowerShell or Recovery Console.[x]

On Windows NT operating systems, CHKDSK can likewise check the disk surface for bad sectors and marking them (in MS-DOS 6.x and Windows 9x, this is a task done by Microsoft ScanDisk). The Windows Server version of CHKDSK is RAID-aware and tin fully recover data in bad sectors of a disk in a RAID-one or RAID-5 assortment if other disks in the set are intact.[11]

Fragments of files and directories accounted as corrupt as a outcome of, for case, power outages while writing, file proper noun overlength, and/or invalid characters in file proper noun, are moved into a directory under the segmentation's root, named found.000, and renamed into generic hexadecimally numbered files and directories starting with file00000000.chk and dir_00000000.chk respectively.[12] [13]

On Windows NT family, a standard CHKDSK browse consists of three phases of testing file metadata. Information technology looks for errors but does not prepare them unless it is explicitly ordered to do so. The same applies to surface scan—this test, which could exist extremely time-consuming on large or low-performance disks, is non carried out unless explicitly requested. CHKDSK requires exclusive write admission to the volume to perform repairs.[fourteen] [fifteen]

Due to the requirement of the monopolized access to the drive, the CHKDSK cannot check the system disk in the normal organization mode. Instead, the system sets a dirty bit to the disk volume and then reboots the computer. During the Windows start-upward, a special version of CHKDSK called Autochk (a native mode application) is started past the SMSS.EXE and checks and attempts repairing the file system if the dirty bit is set up.

Because of the exclusive access requirement and the time-consuming nature of CHKDSK functioning, Windows Vista implemented a new file arrangement health model in which the operating system fixes errors on the volumes as it encounters them. In the event that the problem is grave and a total scan is required, Action Centre notifies the user to take the volume offline at the first convenience.[16]

Windows Vista and Windows Server 2008 added self-healing ability, turned on by default, in addition to providing the CHKDSK command. It detects concrete file system errors and silently fixes them on the fly. Thus, many problems previously discovered on running CHKDSK never appear. It is administered by fsutil repair control.[17] [18]

Criticism has been aimed at the tendency of AUTOCHK to automatically modify the file organization when not explicitly solicited past the user who may wish to support their data in prior, equally an attempted repair may scramble, undermine and disown file and directory paths, especially on a multiboot installation where multiple operating systems may have interferingly written to the same partition.[xix] [20] [21]

The alleged Windows 7 bug [edit]

Before the release of Windows 7, InfoWorld reported an alleged memory leak in CHKDSK; according to the report, the chkdsk /r command would cause the retentivity consumption to achieve the maximum and the arrangement to crash. Randall C. Kennedy of InfoWorld attributed the original study to "various Web sources" and said that in his tests, the memory consumption reached higher up xc%, although he did not experience a crash. Even so, Kennedy took the retention consumption for a critical bug that would derail Windows seven's launch and chastised Microsoft.[22] Tom Warren of Neowin dismissed Kennedy'due south assessment of the declared leak's significance.[23] Steven Sinofsky of Microsoft as well responded that Microsoft could not reproduce a crash either but that the massive memory consumption was by design, to ameliorate functioning, and not a leak. Ed Bott of ZDNet as well reviewed the claim with his own tests and observed that no crash would occur. Noting that chkdsk /r, past design, does not work on the system drive while Windows is online, Bott concluded "information technology's arguably a feature, not a bug, and the likelihood that you lot'll always crash a arrangement this mode is very, very pocket-size and completely avoidable."[24]

DR/Novell DOS [edit]

DR DOS 6.0 also includes an implementation of the CHKDSK command.[25]

FreeDOS [edit]

The FreeDOS version was developed by Imre Leber and is licensed under the GNU GPL 2.[26]

ReactOS [edit]

The ReactOS implementation is based on a free clone developed by Mark Russinovich for Sysinternals in 1998.[27] Information technology was adapted to ReactOS by Emanuele Aliberti in 1999 and supports volumes using the FAT32 filesystem. The command does not back up volumes using the Btrfs filesystem, although ReactOS supports it since version 0.4.1.

See also [edit]

  • Defragmentation
  • Data scrubbing
  • List of file systems
  • e2fsprogs

References [edit]

  1. ^ "FlexOS User's Guide" (PDF). www.bitsavers.org. 1986. Retrieved 2020-09-14 .
  2. ^ [1] [ expressionless link ]
  3. ^ "Archived copy". Archived from the original on 2019-04-14. Retrieved 2019-07-twenty . {{cite web}}: CS1 maint: archived copy every bit championship (link)
  4. ^ "134-TENEX JOBZRO.MAC". BitSavers. 1979-09-sixteen. Archived from the original on 2019-01-27. Retrieved 2020-08-14 .
  5. ^ "Xerox Palo Alto Inquiry Center" (PDF). Under Tenex .. Hardware Maintenance Procedures .. Recovery from Checkdsk Errors
  6. ^ "86-DOS User'south Manual - Version 0.iii" (PDF). Archived from the original (PDF) on 2019-07-fourteen. Retrieved 2019-06-09 .
  7. ^ Wolverton, Van (2003). Running MS-DOS Version 6.22 (20th Anniversary Edition), 6th Revised edition. Microsoft Press. ISBN0-7356-1812-7.
  8. ^ "MS-DOS and Windows command line chkdsk control". world wide web.computerhope.com.
  9. ^ "When Not to Use MS-DOS v.0 CHKDSK and UNDELETE Commands". Back up (1.i ed.). Microsoft. 16 Nov 2006.
  10. ^ "Description of the Windows XP Recovery Console for avant-garde users". Back up (8.0 ed.). Microsoft. 11 July 2013. Retrieved 4 September 2014.
  11. ^ Holm, Dan; Thomas, Orin (2003). "11-three: Maintaining Disk Storage Volumes". Managing and Maintaining a Microsoft Windows Server 2003 Environment. Microsoft Press. p. 11.25. ISBN9780735614376.
  12. ^ "What Are the FOUND.000 Folder and FILE0000.CHK File in Windows?".
  13. ^ "Delete File when Path Too Long or Name Ends with Dots or Infinite".
  14. ^ "An explanation of the new /C and /I Switches that are available to use with Chkdsk.exe". Microsoft Support. Microsoft. ane Dec 2007. Archived from the original on 24 October 2014. Retrieved 25 Jan 2019.
  15. ^ "Troubleshooting Disks and File Systems". Windows XP Professional Resource Kit. Microsoft. 3 Nov 2005. Retrieved iv September 2014.
  16. ^ Bangalore, Kiran (10 May 2012). Sinofsky, Steven (ed.). "Redesigning chkdsk and the new NTFS health model". Edifice Windows eight. Microsoft.
  17. ^ Chen, Ken (4 Baronial 2014). "NTFS Self-Healing is An Overlooked but Useful Feature in Windows 7". Adjacent of Windows.
  18. ^ Pawar, Amit (13 February 2008). "Self-healing NTFS in Windows Server 2008 and Windows Vista". Amit Pawar - Infrastructure web log. Microsoft.
  19. ^ "Will Scandisk or CHKDSK Cause Calculator Information Loss?". Data Recovery Blog. 8 February 2017.
  20. ^ "Disable or Terminate Auto CHKDSK During Windows Startup • Raymond.CC". Raymond.CC. 23 Feb 2008.
  21. ^ "How to Fix a Corrupted Windows NTFS Filesystem With Ubuntu". MakeUseOf. 22 September 2010.
  22. ^ Kennedy, Randall C. (5 Baronial 2009). "Critical Windows 7 problems risks derailing product launch". InfoWorld. IDG. Retrieved 19 Feb 2015.
  23. ^ Warren, Tom (v August 2009). "Windows 7 RTM contains a rather nasty chkdsk bug". Neowin . Retrieved xix February 2015.
  24. ^ Bott, Ed (5 August 2009). "A killer Windows 7 problems? Sorry, no". ZDNet. CBS Interactive.
  25. ^ "DR DOS 6.0 User Guide Optimisation and Configuration Tips" (PDF). Archived from the original (PDF) on 2019-09-xxx. Retrieved 2019-08-thirteen .
  26. ^ "ibiblio.org FreeDOS Bundle -- chkdsk (FreeDOS Base)". www.ibiblio.org.
  27. ^ "reactos/reactos". GitHub. 3 Jan 2022.

Farther reading [edit]

  • Wolverton, Van (1990). MS-DOS Commands: Microsoft Quick Reference, 4th Revised edition. Microsoft Press. ISBN978-1556152894.
  • Kathy Ivens; Brian Proffit (1993). Os/ii Inside & Out. Osborne McGraw-Hill. ISBN978-0078818714.
  • Frisch, Æleen (2001). Windows 2000 Commands Pocket Reference. O'Reilly. ISBN978-0-596-00148-iii.

External links [edit]

  • Official documentation well-nigh Microsoft CHKDSK
  • Open source CHKDSK implementation that comes with MS-DOS v2.0

duttonextration.blogspot.com

Source: https://en.wikipedia.org/wiki/CHKDSK

0 Response to "Is It Ok if Chkdsk Runs in Read-only Mode on Win Xp 32"

Enregistrer un commentaire

Inscription à : Publier les commentaires (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel