Installation of Win7 performs a Disk Check?

[BTRY B 529th FA BN]

So this is my second time reinstalling Win 7. Going to upgrade to 10 immediately after. Upon the install windows rebooted and did a disk check. This is the second time this has happened. In the past 3 days my long time Win7 install corrupted, then the next install and upgrade to X might have gotten corrupted cause it showed the same symptoms but eventually was able to boot. I can't remember if a disk check was normal ever. This doesn't seem right and I'm hoping the Samsung 840 Pro 128Gb drive isn't dying. Magician checked it and it got a "Good" report so I am stumped

:hmm:

 

[MustISO]

Does the Samsung tool have a consistency checker for the drive? Sounds to me like a failing disk or controller.

 

[BTRY B 529th FA BN]

Does the Samsung tool have a consistency checker for the drive? Sounds to me like a failing disk or controller.

I normally don't even install it so i'm not too familiar with it but the S.M.A.R.T. test came back good.

Controller: are you referring to the motherboard controller? It's possible too much was going on for it. Is there specific voltage i can increase to maybe help stabilize it? Is it the IOH, or ICH?

 

[Bubbaleone]

If the Windows installer needs to run chkdsk prior to the start of the installation but the SMART test shows OK, that indicates a serious file system error/s, such as free space being incorrectly reported or errors in the volume bitmap, rather than your 840 failing. I've been runnning the same drives 24/7 for the past three years and find them to be extremely reliable. Boot your installation media into the Windows recovery environment, open the CMD prompt and run chkdsk on each volume with these switches:

>chkdsk X: /x /v /r /b

(where "X:" is your actual drive letter).

The verbose (/v) switch enables you to read a detailed summary of any errors that were corrected.

.

 

[BTRY B 529th FA BN]

If the Windows installer needs to run chkdsk prior to the start of the installation but the SMART test shows OK, that indicates a serious file system error/s, such as free space being incorrectly reported or errors in the volume bitmap, rather than your 840 failing. I've been runnning the same drives 24/7 for the past three years and find them to be extremely reliable. Boot your installation media into the Windows recovery environment, open the CMD prompt and run chkdsk on each volume with these switches:

>chkdsk X: /x /v /r /b

(where "X:" is your actual drive letter).

The verbose (/v) switch enables you to read a detailed summary of any errors that were corrected.

.

I am just personalizing the Windows X install right now. Can I just do the chkdsk X: /x /v /r /b from an elevated command prompt in windows?

 

[Bubbaleone]

I am just personalizing the Windows X install right now. Can I just do the chkdsk X: /x /v /r /b from an elevated command prompt in windows?

IMHO it's best practice to run chkdsk from the recovery environment because when run from the desktop with these switches, chkdsk will still have to reboot the computer in order to close all open handles but when it completes, chkdsk immediately reboots to the desktop leaving you no time to read the summary report of corrected errors.

When run from the recovery environment, chkdsk stops when it's finished which gives you all the time you need to review the entire log. That information can often prove vital in assessing whether you merely have a corrupt file system or there actually is a problem with the drive itself.

.

 

[BTRY B 529th FA BN]

IMHO it's best practice to run chkdsk from the recovery environment because when run from the desktop with these switches, chkdsk will still have to reboot the computer in order to close all open handles but when it completes, chkdsk immediately reboots to the desktop leaving you no time to read the summary report of corrected errors.

When run from the recovery environment, chkdsk stops when it's finished which gives you all the time you need to review the entire log. That information can often prove vital in assessing whether you merely have a corrupt file system or there actually is a problem with the drive itself.

.

Thanks again for the reply.

How do I get to the recovery environment?


EDIT1: F8 I see. Which environment do I choose? Safe Mode with command prompt?

 

[Bubbaleone]

Thanks again for the reply.

How do I get to the recovery environment?


EDIT1: F8 I see. Which environment do I choose? Safe Mode with command prompt?

Boot your Windows installation media and when you get to the "Install Windows" screen, look in the lower-left corner of that dialog box and click "Repair" to enter the recovery environment. You'll have administrator access to CMD prompt and other useful diagnostic and repair tools.

.

 

[BTRY B 529th FA BN]

Boot your Windows installation media and when you get to the "Install Windows" screen, look in the lower-left corner of that dialog box and click "Repair" to enter the recovery environment. You'll have administrator access to CMD prompt and other useful diagnostic and repair tools.

.

Great Thanks!

p.s. tried the F8 key upon boot and couldn't get to the menu

 

[BTRY B 529th FA BN]

Not sure if I'm doing it correctly still.

I installed my Windows 7 media disc in an booted up, it went straight to the installation (naturally) I then rebooted again and hit the F8 key and it brought me to the advanced boot options and I chose Safe Mode with Command Prompt it booted into safe mode asking to install Windows. I currently have Windows X installed. Do I go through the sys prep of the windows install to get to the repair part? This Win X install seems fine so far. Is there anything I can do while having Win X installed, or is your method safe and not going to reinstall windows 7 over this Win X install?

Also I've ran sfc /scannow and the file integrity checked out ok

:hmm:

 

[Bubbaleone]

Not sure if I'm doing it correctly still.

I installed my Windows 7 media disc in an booted up, it went straight to the installation (naturally) I then rebooted again and hit the F8 key and it brought me to the advanced boot options and I chose Safe Mode with Command Prompt it booted into safe mode asking to install Windows. I currently have Windows X installed. Do I go through the sys prep of the windows install to get to the repair part? This Win X install seems fine so far. Is there anything I can do while having Win X installed, or is your method safe and not going to reinstall windows 7 over this Win X install?

Also I've ran sfc /scannow and the file integrity checked out ok

:hmm:

The Windows 10 installer apparently ran chkdsk and corrected any existing file system errors prior to starting the actual installation. Since you've successfully installed 10 and sfc shows good, go ahead and open an elevated cmd prompt from the desktop and run chkdsk with the previously mentioned switches. If you get a clean bill of health you're good to go with 10.

You can't access the Windows 10 recovery environment using Windows 7 installation media but this short and concise tutorial will get you started on the multiple options for accessing the Windows 10 recovery environment: How to Boot to Advanced Startup Options in Windows 10.

.

 

[ninaholic37]

I currently have Windows X installed. Do I go through the sys prep of the windows install to get to the repair part? This Win X install seems fine so far. Is there anything I can do while having Win X installed, or is your method safe and not going to reinstall windows 7 over this Win X install?

Why are you switching between numbers and roman numerals? I don't believe even Microsoft calls it Win X (prove me wrong). If you call it "Win X" you should call 7 "Win VII" for consistency. Pretty sure this "WinX" trend started at Anand forums and you guys are inaccurately trying to spread this silly unofficial name like a disease. This is the only thing I get when I search WinX on Google btw (zero Windows 10 images):

/rant




Really? You want to threadcrap and troll?



Stay on topic and give help or stay out of future threads if you have nothing to add.


esquared
Anandtech Forum Director

 

[BTRY B 529th FA BN]

The Windows 10 installer apparently ran chkdsk and corrected any existing file system errors prior to starting the actual installation. Since you've successfully installed 10 and sfc shows good, go ahead and open an elevated cmd prompt from the desktop and run chkdsk with the previously mentioned switches. If you get a clean bill of health you're good to go with 10.

You can't access the Windows 10 recovery environment using Windows 7 installation media but this short and concise tutorial will get you started on the multiple options for accessing the Windows 10 recovery environment: How to Boot to Advanced Startup Options in Windows 10.

.

Ran the chkdsk with the mentioned switches and it completed but I didn't get a look at the results as it hung up on 12% and I stepped out of the room to watch some football but I hope it did it's thing as I feel a little bit better now.