This command runs the DOS version of GDisk and wipes the first drive using the DoD standards.
Instructs GDisk to perform the required wipes meeting the DoD standards. Replace disk with a number between 1 and 128. The Gdisk executable used, such as GDisk.exe (for DOS) or GDisk32.exe (for WinPE). The following table explains the GDisk command-line elements. GDisk can be run from a DOS (GDisk.exe), WinPE (GDisk32.exe or GDisk64.exe), or Linux (Gdisk) pre-boot operating system using the following syntax: All addressable locations on the hard disk are verified in hardware using the Verify Sectors command to the disk.All addressable locations on the hard disk are overwritten with a pseudorandom character.All addressable locations on the hard disk are overwritten with 0xCA.All addressable locations on the hard disk are overwritten with 0x35.According to this standard, the following group of operations is performed six times: Department of Defense (DoD) 5220.22-M standard.
GDisk’s secure disk wiping feature wipes data according to the U.S. The GDisk utility (one of the Ghost tools included with Deployment Solution 6.9 SP1 - Ghost Solution Suite 3.0) is a multipurpose disk management utility that includes a secure disk wiping feature. When reallocating hardware from one person to another, it is often important to ensure that none of the old data from the hard disk can be retrieved, even after deploying a new imaging to the computer. “ĭisk density is also a factor.How to preform a hard disk wipe using the Ghost utility called GDisk. This was true in 1996, and is still true now.
As the paper says, “ A good scrubbing with random data will do about as well as can be expected“. For any modern PRML/EPRML drive, a few passes of random scrubbing is the best you can do. If you’re using a drive which uses encoding technology X, you only need to perform the passes specific to X, and you never need to perform all 35 passes. “In the time since this paper was published, some people have treated the 35-pass overwrite technique described in it more as a kind of voodoo incantation to banish evil spirits than the result of a technical analysis of drive encoding techniques… In fact performing the full 35-pass overwrite is pointless for any drive since it targets a blend of scenarios involving all types of (normally-used) encoding technology, which covers everything back to 30+-year-old MFM methods (if you don’t understand that statement, re-read the paper).
0 kommentar(er)
