# Windows 7 chkdsk running for hours.  Problem?

**URL:** <https://boards.straightdope.com/t/windows-7-chkdsk-running-for-hours-problem/625785>\
**Category:** Factual Questions\
**Created:** [June 20, 2012, 9:02pm UTC](https://boards.straightdope.com/t/windows-7-chkdsk-running-for-hours-problem/625785 "2012-06-20T21:02:26Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![Nobody](https://avatars.discourse-cdn.com/v4/letter/n/94ad74/32.png) [@Nobody](https://boards.straightdope.com/u/Nobody)\
**Post date:** [June 21, 2012, 11:50pm UTC](https://boards.straightdope.com/t/windows-7-chkdsk-running-for-hours-problem/625785/21 "2012-06-21T23:50:08Z")

</div>

> [@yoyodyne](#):
>
> Scandisk moves the data it can from bad sectors to good sectors, then marks the bad sectors in a table so that they’re not accessed again. If you do a sector-by-sector clone it won’t even see the bad sectors so they aren’t copied. If any data got corrupted it’s copied, but from good-to-good sectors.

I used a third party partition manager and I think it copied everything as/is, including the list of bad sectors because after chkdsk on the new partition it listed the same bad sectors, so I’ll have to use **AHarris** ’s suggestion and use chkdsk /b.

[Previous page](https://boards.straightdope.com/t/windows-7-chkdsk-running-for-hours-problem/625785.md?page=1)
