Disk formatting process Disk formatting

1 disk formatting process

1.1 low-level formatting of floppy disks
1.2 low-level formatting (llf) of hard disks

1.2.1 transition away llf
1.2.2 disk reinitialization


1.3 partitioning
1.4 high-level formatting

disk formatting process

formatting disk use operating system , applications typically involves 3 different processes.

low-level formatting of floppy disks

the low-level format of floppy disks (and hard disks) performed disk drive s controller.

consider standard 1.44 mb floppy disk. low-level formatting of floppy disk, writes 18 sectors of 512 bytes each of 160 tracks (80 on each side) of floppy disk, providing 1,474,560 bytes of storage on disk.

physical sectors larger 512 bytes, in addition 512 byte data field include sector identifier field, crc bytes (in cases error correction bytes) , gaps between fields. these additional bytes not included in quoted figure overall storage capacity of disk.

different low-level formats can used on same media; example, large records can used cut down on inter-record gap size.

several freeware, shareware , free software programs (e.g. gparted, fdformat, nformat , 2m) allowed considerably more control on formatting, allowing formatting of high-density 3.5 disks capacity 2 mb.

techniques used include:

head/track sector skew (moving sector numbering forward @ side change , track stepping reduce mechanical delay),
interleaving sectors (to boost throughput organizing sectors on track),
increasing number of sectors per track (while normal 1.44 mb format uses 18 sectors per track, possible increase maximum of 21), and
increasing number of tracks (most drives tolerate extension 82 tracks: though handle more, others jam).

linux supports variety of sector sizes, , dos , windows support large-record-size dmf-formatted floppy format.

low-level formatting (llf) of hard disks

low-level format of 10-megabyte ibm pc xt hard drive

hard disk drives prior 1990s typically had separate disk controller defined how data encoded on media. media, drive and/or controller possibly procured separate vendors, users able perform low-level formatting. separate procurement had potential of incompatibility between separate components such subsystem not reliably store data.

user instigated low-level formatting (llf) of hard disk drives common minicomputer , personal computer systems until 1990s. ibm , other mainframe system vendors typically supplied hard disk drives (or media in case of removable media hdds) low-level format. typically involved subdividing each track on disk 1 or more blocks contain user data , associated control information. different computers used different block sizes , ibm notably used variable block sizes popularity of ibm pc caused industry adopt standard of 512 user data bytes per block middle 1980s.

depending upon system, low-level formatting done operating system utility. ibm compatible pcs used bios, invoked using ms-dos debug program, transfer control routine hidden @ different addresses in different bioses.

transition away llf

starting in late 1980s, driven volume of ibm compatible pcs, hdds became routinely available pre-formatted compatible low-level format. @ same time, industry moved historical (dumb) bit serial interfaces modern (intelligent) bit serial interfaces , word serial interfaces wherein low level format performed @ factory.

today, end-user, in cases, should never perform low-level formatting of ide or ata hard drive, , in fact not possible on modern hard drives because formatting done on servowriter before disk assembled drive in factory.

disk reinitialization

while impossible perform complete llf on modern hard drives (since mid-1990s) outside factory, term low-level format still used called reinitialization of hard drive factory configuration (and these terms may misunderstood).

the present ambiguity in term low-level format seems due both inconsistent documentation on web sites , belief many users process below high-level (file system) format must called low-level format. since of low level formatting process can today performed @ factory, various drive manufacturers describe reinitialization software llf utilities on web sites. since users have no way determine difference between complete llf , reinitialization (they observe running software results in hard disk must high-level formatted), both misinformed user , mixed signals various drive manufacturers have perpetuated error. note: whatever possible misuse of such terms may exist (search hard drive manufacturers web sites these terms), many sites make such reinitialization utilities available (possibly bootable floppy diskette or cd image files), both overwrite every byte , check damaged sectors on hard disk.

reinitialization should include identifying (and sparing out if possible) sectors cannot written , read drive, correctly. term has, however, been used refer portion of process, in every sector of drive written to; writing specific value every addressable location on disk.

traditionally, physical sectors initialized fill value of 0xf6 per int 1eh s disk parameter table (dpt) during format on ibm compatible machines. value used on atari portfolio. 8-inch cp/m floppies typically came pre-formatted value of 0xe5, , way of digital research value used on atari st , amstrad formatted floppies. amstrad otherwise used 0xf4 fill value. modern formatters wipe hard disks value of 0x00 instead, called zero-filling, whereas value of 0xff used on flash disks reduce wear. latter value typically default value used on rom disks (which cannot reformatted). advanced formatting tools allow configuring fill value.

one popular method performing zero-fill operation on hard disk writing zero-value bytes drive using unix dd utility /dev/zero stream input file , drive (or specific partition) output file. command may take many hours complete, , can erase files , file systems.

another method scsi disks may use sg_format command issue low-level scsi format unit command.

zero-filling drive not secure method of erasing sensitive data, or of preparing drive use encrypted filesystem.

partitioning

partitioning process of writing information blocks of storage device or medium allows access operating system. operating systems allow device (or medium) appear multiple devices; i.e. partitioned multiple devices.

on ms-dos, microsoft windows, , unix-based operating systems (such bsd, linux , mac os x) done partition editor, such fdisk, gnu parted, aomei partition assistant or disk utility. these operating systems support multiple partitions.

in current ibm mainframe oss derived os/360 , dos/360, such z/os , z/vse, done init command of ickdsf utility. these oss support single partition per device, called volume. ickdsf functions include creating volume label , writing record 0 on every track.

floppy disks not partitioned; depending upon os may require volume information in order accessed os.

partition editors , ickdsf today not handle low level functions hdds , optical disc drives such writing timing marks, , cannot reinitialize modern disk has been degaussed or otherwise lost factory formatting.

high-level formatting

high-level formatting process of setting empty file system on disk partition or logical volume and, pcs, installing boot sector. fast operation, , referred quick formatting.

the entire logical drive or partition may optionally scanned defects, may take considerable time.

in case of floppy disks, both high- , low-level formatting customarily performed in 1 pass disk formatting software. 8-inch floppies typically came low-level formatted , filled format filler value of 0xe5. since 1990s, 5.25-inch , 3.5-inch floppies have been shipped pre-formatted factory dos fat12 floppies.

in current ibm mainframe operating systems derived os/360 or dos/360, may done part of allocating file, utility specific file system or, in older access methods, on fly new data written.

cite error: there <ref group=nb> tags on page, references not show without {{reflist|group=nb}} template (see page).