Windows wants to check D partition at every boot

csabix · Feb 14, 2021

Hi all

My problem started few weeks ago.
At every boot, Windows 10 wants to check drive D and I have to press a key to skip it since the check process doesn't solve anything (although it says it repairs stuff).
My setup:
1. On the SSD
Windows 10 20H2
Debian Linux 10

2. On the HDD
one NTFS partition that can be seen both by Win and Linux.

At first I thought Linux corrupted the NTFS volume. So I let autocheck run and correct things, then restarted and booted again in Windows, to exclude the possibility of another fs corruption. But it kept asking for disk check.

What could I do to solve the issue?

philc43 · Feb 14, 2021

It could be that the D drive is failing and so needs constant checks. Try running a disk diagnostic check on the drive such as HDTune and report back on the results. You can post screen shots of all the HDTune screens to do this.

DTG1 · Feb 14, 2021

When this started what was going on? did just start out of the blue? the MBR might be corrupted

I found this for you, Method 1 is preferred since you dont have to install software you wont use that often.

2 Methods to Fix Master Boot Record (MBR) in Windows 10

Here we gathered 2 different methods to fix MBR in Windows 10 with step-by-step guide. Check them out and learn how to repair or rebuild master boot record.

www.diskpart.com

csabix · Feb 14, 2021

DTG1 said:
When this started what was going on? did just start out of the blue? the MBR might be corrupted

I found this for you, Method 1 is preferred since you dont have to install software you wont use that often.

2 Methods to Fix Master Boot Record (MBR) in Windows 10

Here we gathered 2 different methods to fix MBR in Windows 10 with step-by-step guide. Check them out and learn how to repair or rebuild master boot record.

www.diskpart.com

I suppose it started after an OS update. 99 % of the time I'm on Linux and enter Windows sporadically, to resolve some rare problems that need specific applications. Also, this is hen I update the OS.
MBR is not corrupted but modified by Linux. Windows "corrects" the "issue" by deleting the Linux entries. Anyways, that's not the problem. Drive D is on separate disk. Also, Windows can boot regardless if I skip or let AutoChk do its (useless) job.
At the moment I'm running HDTune just to make sure there aren't issues with the disk itself, as instructed by philc43.

csabix · Feb 14, 2021

philc43 said:
It could be that the D drive is failing and so needs constant checks. Try running a disk diagnostic check on the drive such as HDTune and report back on the results. You can post screen shots of all the HDTune screens to do this.

zbook · Feb 14, 2021

Many drive problems are recorded by Windows in various log files.
Please run V2 and upload results into this thread:

https://www.windowsq.com/resources/v2-log-collector.8/download

csabix · Feb 14, 2021

zbook said:
Many drive problems are recorded by Windows in various log files.
Please run V2 and upload results into this thread:

https://www.windowsq.com/resources/v2-log-collector.8/download

Here you go

zbook · Feb 14, 2021

The logs displayed recurrent drive file system corruption.

Often this can be fixed.

If not, then replace the drive.

First test the hardware.

After completing HD Tune run the Sea Tools long generic test.

1) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread

SeaTools for Windows | Seagate

How to use SeaTools for Windows | Seagate Support US

Tutorial for the use of SeaTools for Windows, explaining the most common features:

knowledge.seagate.com

If the hardware passes testing then run deep Chkdsk scans until all corruption is fixed.
Then an additional scan is ran to make sure that no corruption is detected.

2) Open administrative command prompt and type or copy and paste:
chkdsk /b /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

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)

Type: Y
reboot

3) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

Read Chkdsk Log in Event Viewer in Windows 10

How to Read Event Viewer Log for Chkdsk (Check Disk) in Windows 10

www.tenforums.com

Code:

Event[1828]:
  Log Name: System
  Source: Ntfs
  Date: 2021-02-14T11:48:18.3960000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MunkagepWin
  Description:
A corruption was discovered in the file system structure on volume D:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1000000000026.  The name of the file is "<unable to determine file name>".

zbook · Feb 14, 2021

Other notable findings seen in the logs:

a) insufficient free space on D:
b) absence of a page file
c) BSOD

See these tutorials:

Free Up Drive Space in Windows 10

How to Free Up Drive Space in Windows 10

www.tenforums.com

(1) Manage Virtual Memory Pagefile in Windows 10 | Tutorials (tenforums.com)

Once the drive testing steps are completed steps can be made to troubleshoot the BSOS.

Increase the free space on the Windows drive so that there is > 30 GB free space

Make sure for virtual memory page file:
a) that the page file is on the Windows drive
b) the dot is in system managed
c) the box is checked to automatically manage paging file size for all drives
d) that the computer is rebooted after modifying page file settings

Code:

      Drive: C:
Free Space: 236.8 GB
Total Space: 309.6 GB
File System: NTFS
      Model: KINGSTON SA400S37480G

      Drive: D:
Free Space: 10.5 GB
Total Space: 953.9 GB
File System: NTFS
      Model: WDC WD10EZEX-22MFCA0

Code:

Installed Physical Memory (RAM)    10.0 GB
Total Physical Memory    9.50 GB
Available Physical Memory    1.85 GB
Total Virtual Memory    9.50 GB
Available Virtual Memory    1.00 GB
Page File Space    0 bytes

Code:

Event[1797]:
  Log Name: System
  Source: volmgr
  Date: 2021-02-14T11:47:27.8270000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MunkagepWin
  Description:
Crash dump initialization failed!

Code:

Event[1724]:
  Log Name: System
  Source: volmgr
  Date: 2021-02-14T11:36:28.2060000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MunkagepWin
  Description:
Crash dump initialization failed!

csabix · Feb 14, 2021

Thank you for the effort taken.

Indeed, the pagefile was on drive D: and this prevented checkdisk from completing the repair (Windows automatically locked the fs before chkdsk could be run).
Moved pagefile back to C:, rebooted and completed the repair from GUI.
Did another reboot and everything is fine.
Since I found anomalies in one of the folders (deleted subfolders returning there), I could spot the culprit: the video editor from Linux (KDEnlive) was corrupting the fs when it crashed. Luckily it is cross-platform and the Win version seems more stable. Also, the kernel driver for the filesystem is way better than the open source one since it's native.

As a bonus issue/question: what can I do with the found.000 folders that were created? They contain gigabytes of data with unknown relevance.

zbook · Feb 14, 2021

I've seen reports where end users attempt to recover found.000.

Long ago on one of my drives there was corruption in the EFI partition.
The partition was labeled and fixed with chkdsk.
The found.000 remained in this partition as non usable files.

These files are most often metadata.

I've not seen end users reporting regular success with third party software.
This one has a cost: How to Recover Data from FOUND.000 Folder - Best Three Solutions (systoolsgroup.com)

Please run:

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
LOGS.bat - Click here to go to the BSOD batch repository to download and run this batch file.
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

zbook · Feb 14, 2021

This link has some additional options:
How to Recover Files from Found.000 Folder | EaseUS

csabix · Tuesday at 3:44 PM

Thanks!
Did try UnCHK in the past and it helped on a different computer but not this one. EaseUS is shady business. At least I didn't like something about their policy back in the day.

Windows wants to check D partition at every boot

New Member

My Computer

BSOD Analyst

My Computer

Death to Gnomes!!!

My Computer

New Member

My Computer

New Member

My Computer

Junior Member

My Computer

New Member

Attachments

My Computer

Junior Member

My Computer

Junior Member

My Computer

New Member

My Computer

Junior Member

My Computer

Junior Member

My Computer

New Member

My Computer

Similar threads