Author Topic: preventing repair files by chkdsk at boot  (Read 10828 times)

0 Members and 1 Guest are viewing this topic.

makinero

  • Guest
preventing repair files by chkdsk at boot
« on: January 18, 2016, 07:10:16 am »
Issue 1: preventing repair files by chkdsk at boot

May you need to modify the registry it?
Always check only (with the /V [Verbose])without repairing /F, if any error Occurs on the drive.

Issue 2:

Immediately inform the (balloon  / beep etc. ) for possible file corruption.
Windows inform only in the event log (NTFS), but I can not know this until eg. In the morning do not run my PC. I mean something like this: Live Update / Real Time / (error occurred disk)

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: preventing repair files by chkdsk at boot
« Reply #1 on: January 18, 2016, 07:43:56 am »
This article may help with that http://www.thewindowsclub.com/check-disk-runs-at-every-startup-windows but the trial version of HDSentinel will give you a written report on the status of all HDDs/SSDs connected to the computer.

http://www.hdsentinel.com/ (green download button)

makinero

  • Guest
Re: preventing repair files by chkdsk at boot
« Reply #2 on: January 18, 2016, 08:42:57 am »
This article may help with that http://www.thewindowsclub.com/check-disk-runs-at-every-startup-windows but the trial version of HDSentinel will give you a written report on the status of all HDDs/SSDs connected to the computer.

http://www.hdsentinel.com/ (green download button)

I am in constant contact with the support and got a private message.


"( . . . ) Hard Disk Sentinel now does not check / report it, as it focuses on real, actual physical drive problems.
I'm still researching about the possibilities and verify when / how problems related to the logical drives could and should be reported, so this may be available in a later version."

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: preventing repair files by chkdsk at boot
« Reply #3 on: January 18, 2016, 08:49:13 am »
I've had HDSentinel saved in my Downloads folder for a while now so will stay with that version.

Was that article any good for stopping the chkdsk on boot ?

I used to know that fix but had forgotten it - hence the Googled link.

makinero

  • Guest
Re: preventing repair files by chkdsk at boot
« Reply #4 on: January 18, 2016, 09:02:12 am »
You can stop CHKDSK (during boot), you can also modify the time needed to run ... (in the registry), but it still remain a problem that an error will occur and I will not know about it and contribute to data loss.I receive up to date to be informed. The sooner the better.
I have a tool to check the ID of the directory and file and can quickly make a copy of the directory and files (if possible) and then perform the CHKDSK repair.
My hard working non-stop (all time record and automatically defragments) and errors may occur reading / writing or modification. The old file system - NTFS - (1993 Years). New REFS, provides greater security to store data on more capacious and faster drives. The weakness of file systems to process changes, both to modify the file name and backup set. NTFS uses the diary - kind registry that records all changes. This solution negatively affect the performance of the file system and in extreme cases leads to loss of data when an error occurs during recording, since all the information about the file is overwritten. Just as the NTFS file system distinguishes REFS file information (metadata), and the contents of the set (user data), but in the case of both types of information used are the same protection. Metadata standard are protected by checksums. Upon request, we provide the same protection for the utility. REFS saves checksums on disk is always at a safe distance so that in the event of an error the data can be reconstructed. By default, the refs creates metadata located as close to the area of ​​the disk, so they can be quickly read.

Windows 7 not support REFS.

Windows 8 or higher OS - support
« Last Edit: January 18, 2016, 09:04:22 am by makinero »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: preventing repair files by chkdsk at boot
« Reply #5 on: January 18, 2016, 09:10:08 am »
So why were you asking about preventing chkdsk on boot ?

makinero

  • Guest
Re: preventing repair files by chkdsk at boot
« Reply #6 on: January 18, 2016, 09:27:26 am »
I want to check the disk, but without repair (as in this topic)

but I do not know how modified switches (in the Windows system registry)
/v /f, etc.


CMD: Help CHKNTFS
CHKNTFS /D /T: /X /C
« Last Edit: January 18, 2016, 09:31:56 am by makinero »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: preventing repair files by chkdsk at boot
« Reply #7 on: January 18, 2016, 09:36:29 am »
If you can't find the answer on Google then just do it manually.

makinero

  • Guest
Re: preventing repair files by chkdsk at boot
« Reply #8 on: January 18, 2016, 09:47:39 am »

May I ask a question on another forum and get an answer helpful.

makinero

  • Guest
Re: preventing repair files by chkdsk at boot
« Reply #9 on: January 18, 2016, 09:58:08 am »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: preventing repair files by chkdsk at boot
« Reply #10 on: January 18, 2016, 01:13:55 pm »
If you can't get an answer on one forum then there's nothing to stop you looking elsewhere, but one thing that comes to mind.

Going back to that Google link to stop chkdsk from starting on boot -  http://www.thewindowsclub.com/check-disk-runs-at-every-startup-windows

Did you have it set as autocheck autock * /. to get it to run on boot as I see you now have it set so that it doesn't auto run ?

If you did, then after the / try putting f instead of the dot

It's only a guess but the / and . must be significant.