Topic: I hate hard drives

[devnullius]

FROM: http://scforum.info/index.php/topic,8087.msg20515.html#msg20515

Quote:
"The volume corruption (even if sounds interesting) usually completely independent from the hard disk itself
but can be caused by many other factors (data / power cables, hard disk controller drivers, physical memory problems,
overheat conditions, overclock, non-standard reboot / reset, power loss and so)" (HDS)

Which would mean the people at http://www.hard-data.nl were right after al... :(

STILL I DO NOT UNDERSTAND: REPLACE DISK WITH SAME TYPE/BUILD ON SAME PC AND NO MORE PROBS.

Sigh :s

Karma ;p

devnullius

[devnullius]

SOURCE: http://support.microsoft.com/kb/976329

Download Fix-it / patch: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=976329&kbln=en-us

MIRROR DOWNLOAD KB976329: https://www.box.com/s/3bc40m7tu33r145jav7s

PARTIAL, RAW Copy Paste:
Error message when you run the ChkDsk.exe utility in read-only mode on a Windows-based computer: "The Volume Bitmap is incorrect" or "Error detected in index $I30 for file 5"
Article ID: 976329 Hotfix Download Available

Visit the Windows 8 Solution Center: This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you.

Summary
On a computer running an operating system listed in the Applies To section, you create or extend a volume. The size of the volume is a multiple of 8 gigabytes (GB). For example, the size of the volume is 8,192 megabyte (MB), 16,384 MB, 32,768 MB, etc. (NOTE: 1 GB equals 1,024 MB).

Symptoms
You may experience one or more of the following problems

When you run the ChkDsk.exe utility on the volume in read-only mode (no switches) you receive an error message similar to one of the following:
The Volume Bitmap is incorrect.
Windows found problems with the file system.
Error detected in index $I30 for file 5.
<Number> index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
Restoring computer settings from System Restore point results in an unbootable operating system or corrupt files.
Restoring files from an effected volume using the "Previous Versions" tab may result in restored files being in a corrupted state.
When you use a backup application that leverages the Windows VSS Volume Shadow Copy feature to create snapshots during a backup, one or more files are found to be corrupt after a restore.
Note NTBackup, Windows Server Backup, System Center Data Protection Manager (DPM) or any third-party backup application’s backed-up data can be impacted. Please review the More Information Section on correcting this with Microsoft DPM or contact your third-party backup solution manufacturer to determine if they are using the Windows VSS Volume Shadow Copy feature to create their backups.
Back to the top | Give Feedback
Cause
When a VSS Volume Shadow copy is invoked on an extended volume, the volume bitmap used to track cluster usage may not accurately reflect clusters that are in use by files that fall on an 8GB file system boundary. Consequently, data read or copied from a shadow copy may not accurately represent the file data. When the data is saved to the destination, it is saved in a corrupted state.

Resolution
Microsoft has determined this to be a bug in the product and has corrected the issue in either a service pack or a hotfix depending upon the OS where the volume originated.

A hotfix is available for the following operating systems:

Windows Server 2003 Service Pack 2 (SP2)
Windows Vista Service Pack 1 (SP1)
Windows Vista Service Pack 2 (SP2)
Windows Server 2008
Windows Server 2008 Service Pack 2 (SP2)
Windows 7
Windows Server 2008 R2
The fix is included in the following service packs:

Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2 Service Pack 1 (SP1)
Information about SP1 for the above can be found at: http://support.microsoft.com/kb/976932

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running one of the following Windows operating systems:
Windows Server 2003 Service Pack 2 (SP2)
Windows Vista Service Pack 1 (SP1)
Windows Vista Service Pack 2 (SP2)
Windows Server 2008
Windows Server 2008 Service Pack 2 (SP2)
Windows 7
Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.
Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables.

If you are using System Center Data Protection Manager (DPM) as your backup application, we recommend that you perform a manual RecoveryPoint with IntegrityCheck after the hotfix is applied. This will ensure that any new backups created by DPM will be consistent. See the following Technet article for details on creating a new RecoveryPoint: http://technet.microsoft.com/en-us/library/cc627335.aspx

Note: Any backups created prior to installing the fix and running the manual RecoveryPoint with an IntegrityCheck job may be corrupt if they meet the scenario criteria.

Additional file information? See original Microsoft article for long binary list...

Karma, I guess 

Devvie


~~~ notemail@facebook.com ~~~

Conare nullius momenti videri fortasse missilibus careant
——
All spelling mistakes are my own and may only be distributed under the GNU General Public License! – (© 95-1 by Coredump; 2-013 by DevNullius)

[A41202813GMAIL]

I Do Not Have Many Complaints About HDDs.

I Never Do The Quick Format.

Yes, The Slow One Takes A Long Long Long Time To Complete, But It Is Only Once.

I Stopped Formatting With Compression, Too - No More Problems Since - Fool Me Once...

Cheers.

[herwin94]

yeahh SSD is far better than HDD.. that's why i'm using SSD now rather than HDD

[merlin001]

Something I learned with mechanical hard drives quite a few years back, especially closer to physical failure, is to try to put the failing drive in a freezer for 20 minutes, then try to spin it up. It sounds so against what we're taught, especially with extreme temperatures and moisture, but I've used it 10, maybe 12 times throughout my IT tech career, and it's worked all but twice. Also, don't try it with SSDs.