Kevin Remde's IT Pro Weblog
IT Pro Resources
TechNet EventsMicrosoft Security Response CenterMicrosoft Virtual AcademyKevin’s Evaluation Download Center
IT Pro Evangelist Blogs
Blain Barton Blain Barton's Blog@BlainBar
Brian LewisMy Thoughts on IT...@BrianLewis_
Dan Stolts IT Pro Guru Blog@ITProGuru
Jennelle Crothers TechBunny@jkc137
Kevin RemdeFull of I.T.@KevinRemde
Tommy PattersonVirtually Cloud 9@Tommy_Patterson
Yung Chou Yung Chou on Hybrid Cloud@YungChou
Yes, you read that subject line correctly. We’ve actually improved the volume error detection so much in Windows Server 2012 that you’ll rarely if ever have to run a CHKDSK command to fix it. And if you do, it will run fast and get out of your way.
In our 29th installment of “31 Days of our Favorite Things”, Matt Hester does an excellent job of summarizing how the new CHKDSK works so much better than in the past; even on very large volumes.
And he also describes the equivalent method of doing a CHKDSK using PowerShell. Do you want to take a guess at what the PowerShell cmdlet is?
Nope. That would be a very good guess, though. However, I think because it’s really more of a repair than a simple check, and that we’re talking about volumes rather than disks.. the actual PowerShell cmdlet is “Repair-Volume”.
“Hey Kevin.. why do you have a photo of road construction barriers here?”
Matt shares an interesting analogy of disk repairs and road construction in his article. For all of the details on the new CHKDSK, as well as the road construction analogy, READ MATT’S EXCELLENT ARTICLE HERE.
Have you always wanted a faster way to repair a disk? Or wished that errors would happen less frequently? Me too.