US20010010085A1 - Recovering and relocating unreliable disk sectors when encountering disk drive read errors - Google Patents
Recovering and relocating unreliable disk sectors when encountering disk drive read errors Download PDFInfo
- Publication number
- US20010010085A1 US20010010085A1 US09/798,864 US79886401A US2001010085A1 US 20010010085 A1 US20010010085 A1 US 20010010085A1 US 79886401 A US79886401 A US 79886401A US 2001010085 A1 US2001010085 A1 US 2001010085A1
- Authority
- US
- United States
- Prior art keywords
- sector
- data
- read
- data sector
- disk
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/18—Error detection or correction; Testing, e.g. of drop-outs
- G11B20/1883—Methods for assignment of alternate areas for defective areas
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/18—Error detection or correction; Testing, e.g. of drop-outs
- G11B20/1816—Testing
- G11B2020/183—Testing wherein at least one additional attempt is made to read or write the data when a first attempt is unsuccessful
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
- G11B20/10—Digital recording or reproducing
- G11B20/18—Error detection or correction; Testing, e.g. of drop-outs
- G11B20/1883—Methods for assignment of alternate areas for defective areas
- G11B2020/1893—Methods for assignment of alternate areas for defective areas using linear replacement to relocate data from a defective block to a non-contiguous spare area, e.g. with a secondary defect list [SDL]
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B2220/00—Record carriers by type
- G11B2220/20—Disc-shaped record carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1809—Selective-repeat protocols
Definitions
- the present invention relates in general to data storage on disk storage media and in particular to error handling and recovery for disk storage media. Still more particularly, the present invention relates to relocating unreliable disk sectors when read errors are received while reading data.
- a sector for which reads must be retried multiple times is likely to be “failing,” or in the process of becoming unrecoverable.
- disk drives will normally perform relocation of the bad sector to a reserved replacement sector on the drive.
- sectors are generally relocated only after they have become unrecoverable, and typically a sector which may be successfully read is deemed good regardless of the number of attempts required to read the data. This may result in loss of data since the sector was not relocated prior to the sector becoming unrecoverable —that is, prior to the data becoming unreadable and therefore “lost.”
- FIG. 1 depicts a block diagram of a data processing system and network in which a preferred embodiment
- FIG. 2 is a diagram of a mechanism for relocating an unreliable sector in accordance with a preferred embodiment of the present invention
- FIG. 3 depicts a high level flow chart for a process of relocating unreliable disk sectors when encountering disk drive read errors in accordance with a preferred embodiment of the present invention
- FIG. 4 is a high level flow chart for employing relocated, unreliable sectors in accordance with a preferred embodiment of the present invention.
- FIG. 5 depicts a data flow diagram for a process of detecting write errors and preserving user data despite failure of a disk to report write errors in accordance with a preferred embodiment of the present invention.
- Data processing system 100 may be, for example, one of the models of personal computers available from International Business Machines Corporation of Armonk, N.Y.
- Data processing system 100 includes a processor 102 , which in the exemplary embodiment is connected to a level two (L 2 ) cache 104 , connected in turn to a system bus 106 .
- L 2 level two
- data processing system 100 includes graphics adapter 116 also connected to system bus 106 , receiving user interface information for display 120 .
- I/O bus bridge 110 couples I/O bus 112 to system bus 106 , relaying and/or transforming data transactions from one bus to the other.
- Peripheral devices such as nonvolatile storage 114 , which may be a hard disk drive, and keyboard/pointing device 116 , which may include a conventional mouse, a trackball, or the like, are connected to I/O bus 112 .
- data processing system 100 might also include a compact disk read-only memory (CD-ROM) or digital video disk (DVD) drive, a sound card and audio speakers, and numerous other optional components. All such variations are believed to be within the spirit and scope of the present invention.
- data processing system 100 is preferably programmed to provide a mechanism for relocating unreliable disk sectors.
- the mechanism includes a host system 202 , which may be data processing system 100 depicted in FIG. 1, and disk storage 204 , such as nonvolatile storage 114 depicted in FIG. 1.
- Disk storage 204 includes storage media 206 , which is generally several magnetic storage disks spaced apart along a common central axis.
- data is written to and read from storage media 206 by heads (not shown) positioned near storage media 206 as the disks are rotated by a drive motor (also not shown), with a separate head associated with each disk within storage media 206 .
- the heads are moved in tandem over the surface of each respective disk within storage media 206 , with the rotation of the disks and the position of the heads along a radius from the common axis controlled by head position and drive control logic 208 .
- Storage media 206 is logically divided into a number of tracks 210 , which are generally arranged in concentric circles on the surface of the disks forming storage media 206 .
- Each track 210 usually includes servo fields containing positioning information used to locate the head over a specific track, identification and synchronization fields, a data region, and error correcting codes (ECC). Because the servo, identification, synchronization, and ECC fields are not utilized by the present invention, only data regions for tracks 210 are illustrated in FIG. 2 for simplicity.
- each sector 212 typically includes an identification (ID) field and a data field.
- Identification fields generally include a synchronization field required for reading the data, a logical block number (LBN) assigned to the sector and employed by the addressing scheme of host system 202 to identify the sector, flags, and a cyclic redundancy check (CRC) character or similar error correcting codes (ECC)
- LBN logical block number
- CRC cyclic redundancy check
- ECC error correcting codes
- the flags may include a flag (“B”) indicating whether the sector is good or bad, sector servo split flags, and a relocate pointer.
- a defect map table 214 which may be maintained by storage media 204 and/or the operating system for host system 202 , contains entries 216 for each LBN 218 where an error has been detected. Until an unrecoverable sector is identified for storage media 204 , defect map table 214 will contain no entries. As unrecoverable sectors are identified over the life of storage media 204 , entries are added to defect map table 214 . When an unrecoverable sector is identified, the failed sector is mapped within defect map table 214 to a replacement sector previously reserved by the operating system for host system 202 . Each entry 216 thus contains the LBN 220 which addresses a previously reserved replacement sector to which LBN 218 has been relocated, and may also contain a flag as well as other information 222 about the sector identified by LBN 218 within an entry 216 .
- an unreliable sector - a sector for which multiple read attempts are required to successfully read the sector data —such as sector 212 a or 212 b is identified during operation
- the sector is remapped to a reserved spare or replacement sector 212 c or 212 d.
- the LBN 218 corresponding to the unreliable sector 212 a or 212 b is mapped to the LBN 220 of the corresponding replacement sector 212 c or 212 d, which may also be stored in the relocate pointer portion of an ID field for the appropriate unreliable sector 212 a or 212 b.
- All disk drives can detect and report a bad data read from the disk media, typically through CRC errors.
- CRC errors When CRC errors are returned from reading a sector, often the read may be retried successfully, and most file systems simply continue if the data was successfully recovered from the sector.
- a read request being handled by an operating system component 228 for storage disk 204 (often referred to as a “device manager” for disk 204 ) may encounter a CRC error returned from the device driver 230 for storage media 204 , which receives the CRC error from host interface 232 of storage disk 204 .
- the operating system component 228 will then attempt to recover the data within the sector being read by repeatedly retrying the read request.
- Defect map table 214 which is accessible to operating system component 228 , is appropriately updated. “Bad” bit or flag 222 in defect map table 214 , in a defect map within disk 204 (not shown), and/or in failing sector 212 a may be set for failing sector 212 a. An “unusable” flag indicating whether the data within the replacement sector is good or bad (in this case good, since the data was recovered prior to relocation of the failing sector) may also be set.
- the operating system checks the LBNs of the sectors to be read against defect map table 214 . If an entry containing an LBN 216 to be read or written is found, the replacement sector 212 d is read instead of failing sector 212 a. Failing sector 212 a is no longer employed to hold data. Replacement sector 212 d thus becomes a fully functional substitute for failed sector 212 a which it replaced, and the original data is preserved from loss.
- FIG. 3 a high level flow chart for a process of relocating unreliable disk sectors when encountering disk drive read errors in accordance with a preferred embodiment of the present invention is depicted.
- the process begins at step 302 , which depicts a CRC read error being returned by a disk drive to an operating system read request.
- the process first passes to step 304 , which illustrates a retry of the read request by the operating system.
- step 306 depicts a determination of whether the retry request was successful. If not, the process proceeds to step 308 , which illustrates incrementing a retry counter, and then returns to step 304 to again retry the read request.
- step 308 illustrates incrementing a retry counter
- the operating system may simply deem the sector unrecoverable, and relocate the sector with a notification to the user that the sector data was lost.
- step 306 the process proceeds from step 306 to step 310 , which illustrates a determination of whether the number of attempted reads required to successfully read the sector data exceeds a predefined reliability limit.
- the number of retry attempts selected as a threshold for reliability should balance the risk of total loss of the data against the loss of storage space. The number may be variable during the life of a disk storage device, with more retry attempts being tolerated as fewer replacement sectors remain available.
- step 312 depicts relocating the failing sector.
- the failing sector may be remapped to one of the operating system's reserved replacement sectors and written with the recovered data. All future reads and writes to the failing sector number will map to the replacement sector. For this case, the original user data was recovered, a bad sector was removed from use, and a good sector substituted in its place.
- step 314 illustrates the process becoming idle until another read error is received.
- step 402 depicts a read or write to a disk storage device being initiated, with the read or write request being detected by a an operating system device manager component for the disk storage device.
- step 404 illustrates the device manager checking the defect map table maintained for the disk storage device as described above, comparing the LBNs for the target sector(s) to entries, if any, within the defect map table.
- step 406 illustrates a determination of whether any target sectors had previously been relocated, by comparing the target sector LBNs to relocated sector LBNs within the defect map table.
- step 408 which illustrates substituting the replacement sector LBN for the relocated target sector LBN for each target sector which has been relocated. Otherwise, the process proceeds directly to step 410 , which illustrates the process becoming idle until another read or write operating to a disk storage device is detected.
- the present invention allows unreliable sectors to be relocated to spare sectors with preservation of the data which would otherwise be lost when the sector becomes completely unrecoverable.
- An important aspect of the present invention is that it may be implemented within an operating system component, employing replacement sectors reserved by the operating system. This allows consistent handling of unreliable blocks regardless of the disk media or the capabilities of a disk drive which are involved.
- FIG. 5 is a data flow diagram for a process of detecting write errors and preserving user data despite failure of a disk to report write errors in accordance with a preferred embodiment of the present invention is depicted.
- FIG. 5 is a data flow diagram for a process of bad block relocation by an operating system.
- an operating system in accordance with the present invention When an operating system in accordance with the present invention is installed on a data processing system, and also at later times such as when a disk is added to the data processing system, the user is given the opportunity to create new data volumes which reside on disks within the system.
- a utility program allowing the user to enter information about the new volume creates the volumes within one or more partitions on a disk.
- One volume feature which a user may specify is support, within the operating system, for relocation of bad blocks detected on disk media.
- the utility program will create an anchor block on the disk at a known location, such as at the very end of each partition making up the volume.
- the anchor block contains the addresses on the disk for a group of replacement sectors for that partition, reserved by the operating system.
- the replacement sectors reserved by the operating system are invisible to the user, and cannot be utilized directly by the user. Prior to finishing creation of the volume, all replacement sectors are tested by the operating system to insure that, at least initially, these replacement sectors are good. During operation, the reserved replacement sectors are employed by the operating system to relocate failing user sectors.
- FIG. 5 illustrates the flow of data and control for an operating system process of sector replacement on failing disk operations.
- a user program issues a disk access 502 to a sector or block of sectors within the user area of a disk partition.
- the disk drive returns an error 504 to the operating system on the attempted disk access.
- the operating system individually accesses 506 a the sectors which were being accessed when the error was returned, monitoring any errors returned 506 n for individual sectors to identify failing sectors within the group. The operating system thereby identifies failing sectors within the group of sectors. Alternatively, if only one sector was being written when the error was returned, these steps may be skipped.
- the operating system For each failing sector identified, the operating system creates an entry 508 within a mapping table to provide a pretested, reserved replacement sector for subsequent storage of data directed to the failing sector.
- the entry created will include the address of the failing sector, a corresponding address of the replacement sector designated to substitute for the failing sector, and status information regarding the data within the replacement sector.
- Subsequent disk accesses 510 a to the failing sector result in a lookup 510 b in the mapping table and are then directed 510 c to the replacement sector.
- the failing sector is relocated to a reserved replacement sector by the operating system, preferably with no loss of user data. This may be performed on top of, or in addition to, any data relocation performed by a disk drive upon detection of bad sectors.
- marginally bad sectors may finally return the original user data.
- the sector should not be trusted in the future and should be replaced.
- the marginal sector can be remapped to one of the pretested replacement sectors provided by the operating system. In this way, defective sectors can be removed from use before they become totally unusable and the user data is lost.
Abstract
Where a number n of read attempts are required to successfully read a data sector, with the first n-1 attempts returning a disk drive read error, the number of attempts required is compared to a predefined threshold selected to indicate that the sector is unreliable and is in danger of becoming completely unrecoverable. If the threshold number of attempts is not exceeded, the sector is presumed to still be good and no further action need be taken. If the threshold number of attempts was equaled or exceeded, however, the unreliable or failing sector is relocated to a reserved replacement sector, with the recovered data written to the replacement sector. The failing data sector is remapped to the replacement sector, which becomes a fully functional substitute for the failing sector for future reads and writes while preserving the original user data. Data within a failing sector is thus preserved before the sector becomes completely unrecoverable.
Description
- The present invention is related to the subject matter of the following commonly assigned, copending U.S. patent applications: Ser. No.09/______ (Docket No. AT9-98-898) entitled “RELOCATING UNRELIABLE DISK SECTORS WHEN ENCOUNTERING DISK DRIVE READ ERRORS WITH NOTIFICATION TO USER WHEN DATA IS BAD” and filed ______, 1999; Ser. No. 09/______ (Docket No. AT9-98-903) entitled “ABILITY TO DISTINGUISH TRUE DISK WRITE ERRORS” and filed ______, 1999; and Ser. No. 09/______ (Docket No. AT9-98-904) entitled “RELOCATING SECTORS WHEN DISK DRIVE DOES NOT RETURN DISK WRITE ERRORS” and filed ______, 1999. The content of the above-referenced applications is incorporated herein by reference.
- 1. Technical Field
- The present invention relates in general to data storage on disk storage media and in particular to error handling and recovery for disk storage media. Still more particularly, the present invention relates to relocating unreliable disk sectors when read errors are received while reading data.
- 2. Description of the Related Art
- Accurate and prompt reporting of write errors or faults to a disk drive by device drivers, adapters, and/or disk drives when an attempted write to the hard disk drive is unsuccessful represents the ideal situation for data protection. Under these conditions, the system or user application has an opportunity to preserve the data by writing it elsewhere. However, the error may not be detected when the data is written, the error may not be properly reported if detected, or the data may be corrupted after being written to the disk media. The first two circumstances depend on the presence, reliability, and/or thoroughness of error detection, reporting and correction mechanisms for the disk drive, adapter, and device driver. The last circumstance results from failure of the disk media for any one of a number of reasons such as head damage to the disk media, stray magnetic fields, or contaminants finding their way into the disk drive.
- Virtually all contemporary disk drives can detect and report a bad data read from the disk media, typically through CRC errors. When CRC errors are returned from reading a sector, often the read may be retried successfully, and most file systems simply continue if the data was successfully recovered from the sector.
- A sector for which reads must be retried multiple times is likely to be “failing,” or in the process of becoming unrecoverable. Once a sector becomes unrecoverable, disk drives will normally perform relocation of the bad sector to a reserved replacement sector on the drive. However, sectors are generally relocated only after they have become unrecoverable, and typically a sector which may be successfully read is deemed good regardless of the number of attempts required to read the data. This may result in loss of data since the sector was not relocated prior to the sector becoming unrecoverable —that is, prior to the data becoming unreadable and therefore “lost.”
- It would be desirable, therefore, to provide a mechanism for detecting and relocating failing or unreliable disk sectors prior to complete loss of data within the sector.
- It is therefore one object of the present invention to provide improved data storage on disk storage media.
- It is another object of the present invention to provide improved error handling and recovery for disk storage media.
- It is yet another object of the present invention to provide a mechanism for relocating unreliable disk sectors when read errors are received while reading data.
- The foregoing objects are achieved as is now described. Where a number n of read attempts are required to successfully read a data sector, with the first n-1 attempts returning a disk drive read error, the number of attempts required is compared to a predefined threshold selected to indicate that the sector is unreliable and is in danger of imminently becoming completely unrecoverable. If the threshold number of attempts is not exceeded, the sector is presumed to still be good and no further action need be taken. If the threshold number of attempts was equaled or exceeded, however, the unreliable or failing sector is relocated to a reserved replacement sector, with the recovered data written to the replacement sector. The failing data sector is remapped to the replacement sector, which becomes a fully functional substitute for the failing sector for future reads and writes while preserving the original user data. Data within a failing sector is thus preserved before the sector becomes completely unrecoverable.
- The above as well as additional objects, features, and advantages of the present invention will become apparent in the following detailed written description.
- The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself however, as well as a preferred mode of use, further objects and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
- FIG. 1 depicts a block diagram of a data processing system and network in which a preferred embodiment;
- FIG. 2 is a diagram of a mechanism for relocating an unreliable sector in accordance with a preferred embodiment of the present invention;
- FIG. 3 depicts a high level flow chart for a process of relocating unreliable disk sectors when encountering disk drive read errors in accordance with a preferred embodiment of the present invention;
- FIG. 4 is a high level flow chart for employing relocated, unreliable sectors in accordance with a preferred embodiment of the present invention; and
- FIG. 5 depicts a data flow diagram for a process of detecting write errors and preserving user data despite failure of a disk to report write errors in accordance with a preferred embodiment of the present invention.
- With reference now to the figures, and in particular with reference to FIG. 1, a block diagram of a data processing system and network in which a preferred embodiment of the present invention may be implemented is depicted.
Data processing system 100 may be, for example, one of the models of personal computers available from International Business Machines Corporation of Armonk, N.Y.Data processing system 100 includes aprocessor 102, which in the exemplary embodiment is connected to a level two (L2)cache 104, connected in turn to asystem bus 106. In the exemplary embodiment,data processing system 100 includesgraphics adapter 116 also connected tosystem bus 106, receiving user interface information fordisplay 120. - Also connected to
system bus 106 issystem memory 108 and input/output (I/O)bus bridge 110. I/O bus bridge 110 couples I/O bus 112 tosystem bus 106, relaying and/or transforming data transactions from one bus to the other. Peripheral devices such asnonvolatile storage 114, which may be a hard disk drive, and keyboard/pointing device 116, which may include a conventional mouse, a trackball, or the like, are connected to I/O bus 112. - The exemplary embodiment shown in FIG. 1 is provided solely for the purposes of explaining the invention and those skilled in the art will recognize that numerous variations are possible, both in form and function. For instance,
data processing system 100 might also include a compact disk read-only memory (CD-ROM) or digital video disk (DVD) drive, a sound card and audio speakers, and numerous other optional components. All such variations are believed to be within the spirit and scope of the present invention. However,data processing system 100 is preferably programmed to provide a mechanism for relocating unreliable disk sectors. - Referring to FIG. 2, a diagram of a mechanism for relocating an unreliable sector in accordance with a preferred embodiment of the present invention is illustrated. The mechanism includes a
host system 202, which may bedata processing system 100 depicted in FIG. 1, anddisk storage 204, such asnonvolatile storage 114 depicted in FIG. 1. -
Disk storage 204 includesstorage media 206, which is generally several magnetic storage disks spaced apart along a common central axis. In accordance with the known art, data is written to and read fromstorage media 206 by heads (not shown) positioned nearstorage media 206 as the disks are rotated by a drive motor (also not shown), with a separate head associated with each disk withinstorage media 206. The heads are moved in tandem over the surface of each respective disk withinstorage media 206, with the rotation of the disks and the position of the heads along a radius from the common axis controlled by head position and drivecontrol logic 208. -
Storage media 206 is logically divided into a number oftracks 210, which are generally arranged in concentric circles on the surface of the disks formingstorage media 206. Eachtrack 210 usually includes servo fields containing positioning information used to locate the head over a specific track, identification and synchronization fields, a data region, and error correcting codes (ECC). Because the servo, identification, synchronization, and ECC fields are not utilized by the present invention, only data regions fortracks 210 are illustrated in FIG. 2 for simplicity. - The data portion of each track is divided into a number of data sectors212 (also referred to a “blocks”) of a predetermined size and format. In the standard format, each
sector 212 typically includes an identification (ID) field and a data field. Identification fields, in turn, generally include a synchronization field required for reading the data, a logical block number (LBN) assigned to the sector and employed by the addressing scheme ofhost system 202 to identify the sector, flags, and a cyclic redundancy check (CRC) character or similar error correcting codes (ECC) The flags may include a flag (“B”) indicating whether the sector is good or bad, sector servo split flags, and a relocate pointer. - A defect map table214, which may be maintained by
storage media 204 and/or the operating system forhost system 202, containsentries 216 for eachLBN 218 where an error has been detected. Until an unrecoverable sector is identified forstorage media 204, defect map table 214 will contain no entries. As unrecoverable sectors are identified over the life ofstorage media 204, entries are added to defect map table 214. When an unrecoverable sector is identified, the failed sector is mapped within defect map table 214 to a replacement sector previously reserved by the operating system forhost system 202. Eachentry 216 thus contains theLBN 220 which addresses a previously reserved replacement sector to whichLBN 218 has been relocated, and may also contain a flag as well asother information 222 about the sector identified byLBN 218 within anentry 216. - When an unreliable sector - a sector for which multiple read attempts are required to successfully read the sector data —such as
sector replacement sector LBN 218 corresponding to theunreliable sector LBN 220 of thecorresponding replacement sector unreliable sector - All disk drives can detect and report a bad data read from the disk media, typically through CRC errors. When CRC errors are returned from reading a sector, often the read may be retried successfully, and most file systems simply continue if the data was successfully recovered from the sector. Thus, a read request being handled by an
operating system component 228 for storage disk 204 (often referred to as a “device manager” for disk 204) may encounter a CRC error returned from thedevice driver 230 forstorage media 204, which receives the CRC error fromhost interface 232 ofstorage disk 204. Theoperating system component 228 will then attempt to recover the data within the sector being read by repeatedly retrying the read request. - If the data is successfully recovered by repetitively retrying the read request as described above, a determination is made of the number of read attempts required to successfully read the data. If the number of attempts exceeds a predefined limit (e.g., five), the sector is deemed to be unreliable or failing. The failing
sector 212 a is then relocated to areplacement sector 212 d before the data is lost. Defect map table 214, which is accessible tooperating system component 228, is appropriately updated. “Bad” bit orflag 222 in defect map table 214, in a defect map within disk 204 (not shown), and/or in failingsector 212 a may be set for failingsector 212 a. An “unusable” flag indicating whether the data within the replacement sector is good or bad (in this case good, since the data was recovered prior to relocation of the failing sector) may also be set. - When reads or writes are performed to a file containing a sector relocated due to unreliability, the operating system checks the LBNs of the sectors to be read against defect map table214. If an entry containing an
LBN 216 to be read or written is found, thereplacement sector 212 d is read instead of failingsector 212 a. Failingsector 212 a is no longer employed to hold data.Replacement sector 212 d thus becomes a fully functional substitute for failedsector 212 a which it replaced, and the original data is preserved from loss. - With reference now to FIG. 3, a high level flow chart for a process of relocating unreliable disk sectors when encountering disk drive read errors in accordance with a preferred embodiment of the present invention is depicted. The process begins at
step 302, which depicts a CRC read error being returned by a disk drive to an operating system read request. The process first passes to step 304, which illustrates a retry of the read request by the operating system. - The process next passes to step306, which depicts a determination of whether the retry request was successful. If not, the process proceeds to step 308, which illustrates incrementing a retry counter, and then returns to step 304 to again retry the read request. It should be noted that the sector data may not be successfully read after a predetermined number of retry attempts, indicating that the sector is unlikely to be successfully recovered. In this case, the operating system may simply deem the sector unrecoverable, and relocate the sector with a notification to the user that the sector data was lost.
- The present invention, however, presumes that the sector data can be successfully recovered after a number of read attempts. In that circumstance, the process proceeds from
step 306 to step 310, which illustrates a determination of whether the number of attempted reads required to successfully read the sector data exceeds a predefined reliability limit. The number of retry attempts selected as a threshold for reliability should balance the risk of total loss of the data against the loss of storage space. The number may be variable during the life of a disk storage device, with more retry attempts being tolerated as fewer replacement sectors remain available. - If the number of read attempts required to successfully read the data exceeds the reliability limit, the process proceeds to step312, which depicts relocating the failing sector. The failing sector may be remapped to one of the operating system's reserved replacement sectors and written with the recovered data. All future reads and writes to the failing sector number will map to the replacement sector. For this case, the original user data was recovered, a bad sector was removed from use, and a good sector substituted in its place.
- If the number of read attempts required to successfully read the data does not exceed the reliability limit, the sector is presumed to be good and no further action is taken. The process then proceeds to step314, which illustrates the process becoming idle until another read error is received.
- Referring to FIG. 4, a high level flow chart for employing relocated, unreliable sectors in accordance with a preferred embodiment of the present invention is illustrated. The process begins at
step 402, which depicts a read or write to a disk storage device being initiated, with the read or write request being detected by a an operating system device manager component for the disk storage device. - The process first passes to step404, which illustrates the device manager checking the defect map table maintained for the disk storage device as described above, comparing the LBNs for the target sector(s) to entries, if any, within the defect map table. The process then passes to step 406, which illustrates a determination of whether any target sectors had previously been relocated, by comparing the target sector LBNs to relocated sector LBNs within the defect map table.
- If any target sector for the detected disk read or write operation has been relocated, the process proceeds to step408, which illustrates substituting the replacement sector LBN for the relocated target sector LBN for each target sector which has been relocated. Otherwise, the process proceeds directly to step 410, which illustrates the process becoming idle until another read or write operating to a disk storage device is detected.
- The present invention allows unreliable sectors to be relocated to spare sectors with preservation of the data which would otherwise be lost when the sector becomes completely unrecoverable. An important aspect of the present invention is that it may be implemented within an operating system component, employing replacement sectors reserved by the operating system. This allows consistent handling of unreliable blocks regardless of the disk media or the capabilities of a disk drive which are involved.
- With reference now to FIG. 5, a data flow diagram for a process of detecting write errors and preserving user data despite failure of a disk to report write errors in accordance with a preferred embodiment of the present invention is depicted. FIG. 5 is a data flow diagram for a process of bad block relocation by an operating system.
- When an operating system in accordance with the present invention is installed on a data processing system, and also at later times such as when a disk is added to the data processing system, the user is given the opportunity to create new data volumes which reside on disks within the system. A utility program allowing the user to enter information about the new volume creates the volumes within one or more partitions on a disk.
- One volume feature which a user may specify is support, within the operating system, for relocation of bad blocks detected on disk media. When this feature is selected for a volume, the utility program will create an anchor block on the disk at a known location, such as at the very end of each partition making up the volume. The anchor block contains the addresses on the disk for a group of replacement sectors for that partition, reserved by the operating system. A table of addresses or a sized contiguous group of addresses starting at a known location, together with the number of replacement sectors reserved by the operating system, is stored in the anchor block.
- The replacement sectors reserved by the operating system are invisible to the user, and cannot be utilized directly by the user. Prior to finishing creation of the volume, all replacement sectors are tested by the operating system to insure that, at least initially, these replacement sectors are good. During operation, the reserved replacement sectors are employed by the operating system to relocate failing user sectors.
- FIG. 5 illustrates the flow of data and control for an operating system process of sector replacement on failing disk operations. A user program issues a
disk access 502 to a sector or block of sectors within the user area of a disk partition. The disk drive returns anerror 504 to the operating system on the attempted disk access. - If necessary, the operating system individually accesses506 a the sectors which were being accessed when the error was returned, monitoring any errors returned 506 n for individual sectors to identify failing sectors within the group. The operating system thereby identifies failing sectors within the group of sectors. Alternatively, if only one sector was being written when the error was returned, these steps may be skipped.
- For each failing sector identified, the operating system creates an
entry 508 within a mapping table to provide a pretested, reserved replacement sector for subsequent storage of data directed to the failing sector. The entry created will include the address of the failing sector, a corresponding address of the replacement sector designated to substitute for the failing sector, and status information regarding the data within the replacement sector. - Subsequent disk accesses510 a to the failing sector result in a
lookup 510 b in the mapping table and are then directed 510 c to the replacement sector. In this manner, the failing sector is relocated to a reserved replacement sector by the operating system, preferably with no loss of user data. This may be performed on top of, or in addition to, any data relocation performed by a disk drive upon detection of bad sectors. - By retrying a read which previously resulted in a read error some large number of times, marginally bad sectors may finally return the original user data. However, it is obvious that the sector should not be trusted in the future and should be replaced. Once the user data has been recovered, the marginal sector can be remapped to one of the pretested replacement sectors provided by the operating system. In this way, defective sectors can be removed from use before they become totally unusable and the user data is lost.
- It is important to note that while the present invention has been described in the context of a fully functional data processing system and/or network, those skilled in the art will appreciate that the mechanism of the present invention is capable of being distributed in the form of a computer usable medium of instructions in a variety of forms, and that the present invention applies equally regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of computer usable mediums include: nonvolatile, hard-coded type mediums such as read only memories (ROMs) or erasable, electrically programmable read only memories (EEPROMs), recordable type mediums such as floppy disks, hard disk drives and CD-ROMs, and transmission type mediums such as digital and analog communication links.
- While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (33)
1. A method of preserving data in unreliable disk sectors, comprising:
responsive to at least one failed attempt to read a data sector, determining whether the data sector is unreliable; and
responsive to determining that the data sector is unreliable, relocating the data sector to a replacement sector.
2. The method of , wherein the step of determining whether the data sector is unreliable further comprises:
claim 1
determining a number of read attempts required to successfully read the data sector.
3. The method of , wherein the step of determining whether the data sector is unreliable further comprises:
claim 2
determining whether the number of read attempts required to successfully read the data sector exceeds a predetermined number selected as indicating that the data sector is unreliable.
4. The method of , wherein the step of relocating the data sector to a replacement sector further comprises:
claim 1
mapping a logical block number for the data sector to a logical block number for the replacement sector; and
writing data read from the data sector to the replacement sector.
5. The method of , wherein the step of relocating the data sector to a replacement sector is performed by an operating system component for a host system coupled to a disk containing the data sector.
claim 1
6. The method of , further comprising:
claim 1
repeatedly attempting to read the data sector;
detecting a read error returned for each failed attempt at reading the data sector; and
incrementing a counter for failed attempt and reading the data sector.
7. The method of , further comprising:
claim 1
successfully reading the data sector after a number of failed attempts.
8. A method of employing relocated sectors, comprising:
detecting a disk access operation to a disk storage device in an operating system component managing the disk storage device;
checking a defect map table identifying relocated sectors within the disk storage device; and
responsive to determining that a target sector for the detected disk access operation has been relocated, substituting an identifier for a replacement sector to which the target sector was relocated for an identifier for the relocated target sector within the detected disk access operation.
9. The method of , wherein the step of detecting a disk access operation to a disk storage device in an operating system component managing the disk storage device further comprises:
claim 8
detecting a read or write including the identifier for the target sector.
10. The method of , wherein the step of checking a defect map table identifying relocated sectors within the disk storage device further comprises:
claim 9
comparing the identifier for the target sector to identifiers of relocated sectors within entries in the defect map table.
11. The method of , wherein the step of substituting an identifier for a replacement sector to which the target sector was relocated for an identifier for the relocated target sector within the detected disk access operation further comprises:
claim 8
substituting a logical block number for the replacement sector for a logical block number for the target sector within the disk access operation.
12. A system for preserving data in unreliable disk sectors, comprising:
a disk storage device containing a data sector and a replacement sector; and
a processor coupled to the disk storage device and executing a relocation process including:
responsive to at least one failed attempt to read the data sector, determining whether the data sector is unreliable; and
responsive to determining that the data sector is unreliable, relocating the data sector to the replacement sector.
13. The system of , wherein the relocation process determines whether the data sector is unreliable by determining a number of read attempts required to successfully read the data sector.
claim 12
14. The system of , wherein the relocation process determines whether the data sector is unreliable by determining whether the number of read attempts required to successfully read the data sector exceeds a predetermined number selected as indicating that the data sector is unreliable.
claim 13
15. The system of , wherein the relocation process relocates the data sector to the replacement sector by mapping a logical block number for the data sector to a logical block number for the replacement sector and writing data read from the data sector to the replacement sector.
claim 12
16. The system of , wherein the relocation process is performed by an operating system component for a host system coupled to the disk storage device.
claim 12
17. The system of , wherein the processor executes a read process including:
claim 12
repeatedly attempting to read the data sector;
detecting a read error returned for each failed attempt at reading the data sector; and
incrementing a counter for failed attempt and reading the data sector.
18. The system of , wherein the read process successfully reads the data sector after a number of failed attempts.
claim 17
19. A system for employing relocated sectors, comprising:
a disk storage device;
a memory containing a defect map identifying relocated sectors on the disk storage device; and
a processor coupled to the disk storage device and the memory and executing a disk access process including:
detecting a disk access operation to the disk storage device in an operating system component managing the disk storage device;
checking the defect map table; and
responsive to determining that a target sector for the detected disk access operation has been relocated, substituting an identifier for a replacement sector to which the target sector was relocated for an identifier for the relocated target sector within the detected disk access operation.
20. The system of , wherein the disk access process detects a read or write including the identifier for the target sector.
claim 19
21. The system of , wherein the disk access process compares the identifier for the target sector to identifiers of relocated sectors within entries in the defect map table.
claim 20
22. The system of , wherein the disk access process substitutes a logical block number for the replacement sector for a logical block number for the target sector within the disk access operation.
claim 19
23. A computer program product within a computer usable medium for preserving data in unreliable disk sectors, comprising:
instructions, responsive to at least one failed attempt to read a data sector, for determining whether the data sector is unreliable; and
instructions, responsive to determining that the data sector is unreliable, for relocating the data sector to a replacement sector.
24. The computer program product of , wherein the instructions for determining whether the data sector is unreliable further comprise:
claim 23
instructions for determining a number of read attempts required to successfully read the data sector.
25. The computer program product of , wherein the instructions for determining whether the data sector is unreliable further comprise:
claim 24
instructions for determining whether the number of read attempts required to successfully read the data sector exceeds a predetermined number selected as indicating that the data sector is unreliable.
26. The computer program product of , wherein the instructions for relocating the data sector to a replacement sector further comprise:
claim 23
instructions for mapping a logical block number for the data sector to a logical block number for the replacement sector; and
instructions for writing data read from the data sector to the replacement sector.
27. The computer program product of , wherein the instructions for relocating the data sector to a replacement sector form a portion of an operating system component for a host system coupled to a disk containing the data sector.
claim 23
28. The computer program product of , further comprising:
claim 23
instructions for repeatedly attempting to read the data sector;
instructions for detecting a read error returned for each failed attempt at reading the data sector; and
instructions for incrementing a counter for failed attempt and reading the data sector.
29. The computer program product of , further comprising:
claim 23
instructions for successfully reading the data sector after a number of failed attempts.
30. A computer program product within a computer usable medium for employing relocated sectors, comprising:
instructions for detecting a disk access operation to a disk storage device in an operating system component managing the disk storage device;
instructions for checking a defect map table identifying relocated sectors within the disk storage device; and
instructions, responsive to determining that a target sector for the detected disk access operation has been relocated, for redirecting the disk access operation to a replacement sector to which the target sector was relocated.
31. The computer program product of , wherein the instructions for detecting a disk access operation to a disk storage device in an operating system component managing the disk storage device further comprise:
claim 30
instructions for detecting a read or write including the identifier for the target sector.
32. The computer program product of , wherein the instructions for checking a defect map table identifying relocated sectors within the disk storage device further comprise:
claim 31
instructions for comparing the identifier for the target sector to identifiers of relocated sectors within entries in the defect map table.
33. The computer program product of , wherein the instructions for redirecting the disk access operation to a replacement sector to which the target sector was relocated further comprise:
claim 30
instructions for substituting a logical block number for the replacement sector for a logical block number for the target sector within the disk access operation.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/798,864 US6427215B2 (en) | 1999-03-31 | 2001-03-01 | Recovering and relocating unreliable disk sectors when encountering disk drive read errors |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/283,364 US6332204B1 (en) | 1999-03-31 | 1999-03-31 | Recovering and relocating unreliable disk sectors when encountering disk drive read errors |
US09/798,864 US6427215B2 (en) | 1999-03-31 | 2001-03-01 | Recovering and relocating unreliable disk sectors when encountering disk drive read errors |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/283,364 Division US6332204B1 (en) | 1999-03-31 | 1999-03-31 | Recovering and relocating unreliable disk sectors when encountering disk drive read errors |
Publications (2)
Publication Number | Publication Date |
---|---|
US20010010085A1 true US20010010085A1 (en) | 2001-07-26 |
US6427215B2 US6427215B2 (en) | 2002-07-30 |
Family
ID=23085693
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/283,364 Expired - Fee Related US6332204B1 (en) | 1999-03-31 | 1999-03-31 | Recovering and relocating unreliable disk sectors when encountering disk drive read errors |
US09/798,864 Expired - Fee Related US6427215B2 (en) | 1999-03-31 | 2001-03-01 | Recovering and relocating unreliable disk sectors when encountering disk drive read errors |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/283,364 Expired - Fee Related US6332204B1 (en) | 1999-03-31 | 1999-03-31 | Recovering and relocating unreliable disk sectors when encountering disk drive read errors |
Country Status (1)
Country | Link |
---|---|
US (2) | US6332204B1 (en) |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030214744A1 (en) * | 2002-05-20 | 2003-11-20 | Nec Corporation | Information recorder and its control method |
US20040100712A1 (en) * | 2002-11-27 | 2004-05-27 | Riospring, Inc. | Handling data fault and retry in writing/reading data to/from a disk |
US20040133739A1 (en) * | 2002-10-11 | 2004-07-08 | Yoshiyuki Sasaki | Recording of information on recording medium having temporary spare area |
US20040268034A1 (en) * | 2003-06-24 | 2004-12-30 | Seagate Technology Llc | Multi-tiered retry scheme for loading system data |
US6993679B2 (en) | 2002-02-28 | 2006-01-31 | Sun Microsystems, Inc. | System and method for inhibiting reads to non-guaranteed data in remapped portions of a storage medium |
US7032127B1 (en) * | 2000-05-09 | 2006-04-18 | Maxtor Corporation | Method and apparatus for identifying defective areas on a disk surface of a disk drive based on defect density |
US7170703B1 (en) | 2000-05-09 | 2007-01-30 | Maxtor Corporation | Flaw detection in disk drive using significant samples of data pattern stored on disk |
US20100146239A1 (en) * | 2008-12-08 | 2010-06-10 | Infinite Memories Ltd. | Continuous address space in non-volatile-memories (nvm) using efficient embedded management of array deficiencies |
US20100325524A1 (en) * | 2009-06-23 | 2010-12-23 | Phison Electronics Corp. | Control circuit capable of identifying error data in flash memory and storage system and method thereof |
US20110292533A1 (en) * | 2010-05-31 | 2011-12-01 | Kabushiki Kaisha Toshiba | Magnetic disk drive and method for rewriting data block |
JP2012509521A (en) * | 2008-11-18 | 2012-04-19 | エルエスアイ コーポレーション | System and method for recovering solid state drive data |
US8806296B1 (en) | 2012-06-27 | 2014-08-12 | Amazon Technologies, Inc. | Scheduled or gradual redundancy encoding schemes for data storage |
US8850288B1 (en) | 2012-06-27 | 2014-09-30 | Amazon Technologies, Inc. | Throughput-sensitive redundancy encoding schemes for data storage |
US8869001B1 (en) | 2012-06-27 | 2014-10-21 | Amazon Technologies, Inc. | Layered redundancy encoding schemes for data storage |
US9110797B1 (en) * | 2012-06-27 | 2015-08-18 | Amazon Technologies, Inc. | Correlated failure zones for data storage |
CN105808161A (en) * | 2016-02-26 | 2016-07-27 | 四川效率源信息安全技术股份有限公司 | Reading method of bad sector data of hard disk |
US9424141B2 (en) * | 2012-04-28 | 2016-08-23 | Huawei Technologies Co., Ltd. | Hard disk data recovery method, apparatus, and system |
US20170329684A1 (en) * | 2016-05-13 | 2017-11-16 | Synology Incorporated | Method and apparatus for performing data recovery in redundant storage system |
US20180067795A1 (en) * | 2011-11-11 | 2018-03-08 | Level 3 Communications, Llc | Systems and methods for automatic replacement and repair of communications network devices |
US9983963B2 (en) | 2015-11-09 | 2018-05-29 | Alibaba Group Holding Limited | System and method for exploiting hard disk drive capacity reserve and extending operating life thereof |
US20230086852A1 (en) * | 2021-09-17 | 2023-03-23 | EMC IP Holding Company LLC | Method, electronic device, and program product for failure handling |
Families Citing this family (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000137584A (en) * | 1998-10-30 | 2000-05-16 | Nec Software Ltd | Controller for external storage device, method for substituting defective block and storage medium storing defective block substitution control program |
JP3705957B2 (en) * | 1999-06-11 | 2005-10-12 | ヒタチグローバルストレージテクノロジーズネザーランドビーブイ | Bad sector processing method and disk storage device in disk storage device |
US7337360B2 (en) * | 1999-10-19 | 2008-02-26 | Idocrase Investments Llc | Stored memory recovery system |
US6594780B1 (en) * | 1999-10-19 | 2003-07-15 | Inasoft, Inc. | Operating system and data protection |
US6708299B1 (en) * | 1999-11-22 | 2004-03-16 | Thomson Licensing S.A. | BCA data replay |
US6772281B2 (en) * | 2000-02-17 | 2004-08-03 | Western Digital Ventures, Inc. | Disk drive for selectively satisfying a read request from a host computer for a first valid data block with a second valid data block |
US6760869B2 (en) * | 2001-06-29 | 2004-07-06 | Intel Corporation | Reporting hard disk drive failure |
JP2003109328A (en) * | 2001-09-28 | 2003-04-11 | Hitachi Ltd | Storage device and its method for correcting error |
US7050252B1 (en) * | 2002-06-01 | 2006-05-23 | Western Digital Technologies, Inc. | Disk drive employing off-line sector verification and relocation of marginal sectors discovered during read error recovery procedure |
US20040128582A1 (en) * | 2002-11-06 | 2004-07-01 | Ching-Hai Chou | Method and apparatus for dynamic bad disk sector recovery |
US7200771B2 (en) * | 2002-11-15 | 2007-04-03 | Plasmon Lms, Inc. | Relocation batch processing for disk drives |
JP4418286B2 (en) * | 2003-07-14 | 2010-02-17 | 富士通株式会社 | Distributed storage system |
US20050028030A1 (en) * | 2003-07-31 | 2005-02-03 | International Business Machines Corporation | Method, system, and product for improved storage device media verification |
US7490261B2 (en) * | 2003-12-18 | 2009-02-10 | Seagate Technology Llc | Background media scan for recovery of data errors |
JP3953036B2 (en) * | 2004-02-24 | 2007-08-01 | ソニー株式会社 | Optical disc apparatus and photographing apparatus having the same |
JP2005326935A (en) * | 2004-05-12 | 2005-11-24 | Hitachi Ltd | Management server for computer system equipped with virtualization storage and failure preventing/restoring method |
US7870464B2 (en) * | 2004-11-02 | 2011-01-11 | International Business Machines Corporation | System and method for recovery of data for a lost sector in a storage system |
US20060123321A1 (en) * | 2004-11-22 | 2006-06-08 | International Business Machines Corporation | System and method for reconstructing lost data in a storage system |
JP2007188463A (en) * | 2005-12-13 | 2007-07-26 | Fujitsu Ltd | Failure recovering method and recording apparatus |
US7574621B2 (en) * | 2006-03-14 | 2009-08-11 | Lenovo (Singapore) Pte Ltd. | Method and system for identifying and recovering a file damaged by a hard drive failure |
JP2007317283A (en) * | 2006-05-24 | 2007-12-06 | Fujitsu Ltd | Storage device, controller, and failure report method |
JP2008077783A (en) * | 2006-09-22 | 2008-04-03 | Fujitsu Ltd | Memory data processor, memory, and memory data processing program |
US9042045B1 (en) | 2007-11-01 | 2015-05-26 | Western Digital Technologies, Inc. | Disk drive adjusting a defect threshold when scanning for defective sectors |
US7962739B2 (en) * | 2008-02-25 | 2011-06-14 | Lenovo (Singapore) Pte. Ltd. | Recovering from hard disk errors that corrupt one or more critical system boot files |
JP2010044814A (en) * | 2008-08-11 | 2010-02-25 | Toshiba Storage Device Corp | Method for controlling storage apparatus and storage apparatus |
US7923874B2 (en) * | 2009-06-17 | 2011-04-12 | Hamilton Sundstrand Corporation | Nested torsional damper for an electric machine |
US20110006545A1 (en) * | 2009-07-08 | 2011-01-13 | Hamilton Sundstrand Corporation | Nested exciter and main generator stages for a wound field generator |
US8207644B2 (en) | 2009-07-14 | 2012-06-26 | Hamilton Sundstrand Corporation | Hybrid cascading lubrication and cooling system |
US8014094B1 (en) | 2009-08-31 | 2011-09-06 | Western Digital Technologies, Inc. | Disk drive expediting defect scan when quality metric exceeds a more stringent threshold |
US8140890B2 (en) * | 2009-12-29 | 2012-03-20 | International Business Machines Corporation | Relocating bad block relocation (BBR) directory upon encountering physical media defect on a disk |
CN104572374B (en) * | 2015-01-13 | 2018-02-13 | 华为技术有限公司 | Processing method, device and the storage device of storage |
US9208817B1 (en) | 2015-03-10 | 2015-12-08 | Alibaba Group Holding Limited | System and method for determination and reallocation of pending sectors caused by media fatigue |
US9536563B1 (en) * | 2016-02-16 | 2017-01-03 | Seagate Technology Llc | Detecting shingled overwrite errors |
CN114721585A (en) * | 2021-01-06 | 2022-07-08 | 伊姆西Ip控股有限责任公司 | Storage management method, apparatus and computer program product |
Family Cites Families (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3771143A (en) | 1972-06-01 | 1973-11-06 | Burroughs Corp | Method and apparatus for providing alternate storage areas on a magnetic disk pack |
US4434487A (en) | 1981-10-05 | 1984-02-28 | Digital Equipment Corporation | Disk format for secondary storage system |
JPS5877034A (en) | 1981-10-30 | 1983-05-10 | Hitachi Ltd | Controlling system for unrewritable storage device |
US4656532A (en) | 1985-07-29 | 1987-04-07 | International Business Machines Corporation | Sector identification method for hard sectored hard files |
JPS6364678A (en) | 1986-09-05 | 1988-03-23 | Mitsubishi Electric Corp | Write error recovery system for disk |
JPH01231122A (en) | 1988-03-11 | 1989-09-14 | Hitachi Ltd | Data storage device |
US5075804A (en) | 1989-03-31 | 1991-12-24 | Alps Electric Co., Ltd. | Management of defect areas in recording media |
JPH03222167A (en) | 1990-01-26 | 1991-10-01 | Matsushita Electric Ind Co Ltd | Optical information recording and reproducing device and optical disk |
JPH0786810B2 (en) | 1990-02-16 | 1995-09-20 | 富士通株式会社 | Array disk device |
US5189566A (en) | 1990-03-15 | 1993-02-23 | International Business Machines Corporation | Method and apparatus for recovering data |
US5088081A (en) | 1990-03-28 | 1992-02-11 | Prime Computer, Inc. | Method and apparatus for improved disk access |
US5166936A (en) | 1990-07-20 | 1992-11-24 | Compaq Computer Corporation | Automatic hard disk bad sector remapping |
US5420730A (en) | 1990-08-17 | 1995-05-30 | Moon; Ronald R. | Servo data recovery circuit for disk drive having digital embedded sector servo |
US5287363A (en) | 1991-07-01 | 1994-02-15 | Disk Technician Corporation | System for locating and anticipating data storage media failures |
JP2625609B2 (en) * | 1991-07-10 | 1997-07-02 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Disk storage device |
GB2260004B (en) * | 1991-09-30 | 1995-02-08 | Apple Computer | Memory management unit for a computer system |
US5422890A (en) * | 1991-11-19 | 1995-06-06 | Compaq Computer Corporation | Method for dynamically measuring computer disk error rates |
US5313626A (en) | 1991-12-17 | 1994-05-17 | Jones Craig S | Disk drive array with efficient background rebuilding |
US5483641A (en) | 1991-12-17 | 1996-01-09 | Dell Usa, L.P. | System for scheduling readahead operations if new request is within a proximity of N last read requests wherein N is dependent on independent activities |
US5506977A (en) | 1991-12-17 | 1996-04-09 | Dell Usa, L.P. | Method and controller for minimizing reads during partial stripe write operations to a disk drive |
JPH05174508A (en) | 1991-12-20 | 1993-07-13 | Nec Corp | Magnetic disc unit |
US5452147A (en) | 1992-09-28 | 1995-09-19 | Nec Corporation | Data reading mechanism for disk apparatuses for reproducing data and serum information recorded on a recording medium by a multi-zone recording method |
US5437020A (en) * | 1992-10-03 | 1995-07-25 | Intel Corporation | Method and circuitry for detecting lost sectors of data in a solid state memory disk |
US5473753A (en) | 1992-10-30 | 1995-12-05 | Intel Corporation | Method of managing defects in flash disk memories |
US5740349A (en) | 1993-02-19 | 1998-04-14 | Intel Corporation | Method and apparatus for reliably storing defect information in flash disk memories |
JP3078946B2 (en) | 1993-03-11 | 2000-08-21 | インターナショナル・ビジネス・マシーンズ・コーポレ−ション | Managing method of batch erase nonvolatile memory and semiconductor disk device |
JPH0773602A (en) | 1993-09-02 | 1995-03-17 | Fujitsu Ltd | Optical disk device |
US5602857A (en) | 1993-09-21 | 1997-02-11 | Cirrus Logic, Inc. | Error correction method and apparatus |
US5632012A (en) | 1993-11-24 | 1997-05-20 | Storage Technology Corporation | Disk scrubbing system |
MY112118A (en) * | 1993-12-23 | 2001-04-30 | Hitachi Global Storage Tech Netherlands B V | System and method for skip-sector mapping in a data recording disk drive. |
US5778167A (en) | 1994-06-14 | 1998-07-07 | Emc Corporation | System and method for reassigning a storage location for reconstructed data on a persistent medium storage system |
JP3322768B2 (en) * | 1994-12-21 | 2002-09-09 | 富士通株式会社 | Recording / reproducing apparatus and recording medium alternation processing method |
JPH08255432A (en) | 1995-03-20 | 1996-10-01 | Fujitsu Ltd | Recording/reproducing apparatus and alternate processing method |
JPH08297928A (en) | 1995-04-26 | 1996-11-12 | Toshiba Corp | Magnetic disk device with recording medium inspecting function |
US5633767A (en) | 1995-06-06 | 1997-05-27 | International Business Machines Corporation | Adaptive and in-situ load/unload damage estimation and compensation |
JP3604466B2 (en) * | 1995-09-13 | 2004-12-22 | 株式会社ルネサステクノロジ | Flash disk card |
US5841600A (en) | 1996-01-11 | 1998-11-24 | Quantum Corporation | Randomly ordered data block envelope tape format |
US5793559A (en) | 1996-02-27 | 1998-08-11 | Quantum Corporation | In drive correction of servo pattern errors |
JPH09259537A (en) | 1996-03-25 | 1997-10-03 | Toshiba Corp | Information record disk having alternate area |
US5828511A (en) | 1996-04-22 | 1998-10-27 | Iomega Corporation | Writing and reading high density magnetic tapes |
US5751733A (en) | 1996-09-16 | 1998-05-12 | Cirrus Logic, Inc. | Interleaved redundancy sector for correcting an unrecoverable sector in a disc storage device |
KR100228795B1 (en) * | 1996-12-31 | 1999-11-01 | 윤종용 | Method for improving the function of read/write of track |
US6034831A (en) | 1997-05-09 | 2000-03-07 | International Business Machines Corporation | Dynamic reverse reassign apparatus and method for a data recording disk drive |
-
1999
- 1999-03-31 US US09/283,364 patent/US6332204B1/en not_active Expired - Fee Related
-
2001
- 2001-03-01 US US09/798,864 patent/US6427215B2/en not_active Expired - Fee Related
Cited By (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7032127B1 (en) * | 2000-05-09 | 2006-04-18 | Maxtor Corporation | Method and apparatus for identifying defective areas on a disk surface of a disk drive based on defect density |
US7170703B1 (en) | 2000-05-09 | 2007-01-30 | Maxtor Corporation | Flaw detection in disk drive using significant samples of data pattern stored on disk |
US6993679B2 (en) | 2002-02-28 | 2006-01-31 | Sun Microsystems, Inc. | System and method for inhibiting reads to non-guaranteed data in remapped portions of a storage medium |
US20030214744A1 (en) * | 2002-05-20 | 2003-11-20 | Nec Corporation | Information recorder and its control method |
US7191365B2 (en) * | 2002-05-20 | 2007-03-13 | Nec Corporation | Information recorder and its control method |
US7228376B2 (en) | 2002-10-11 | 2007-06-05 | Ricoh Company, Ltd. | Recording of information on recording medium having temporary space area |
US20040133739A1 (en) * | 2002-10-11 | 2004-07-08 | Yoshiyuki Sasaki | Recording of information on recording medium having temporary spare area |
US20040100712A1 (en) * | 2002-11-27 | 2004-05-27 | Riospring, Inc. | Handling data fault and retry in writing/reading data to/from a disk |
US20040268034A1 (en) * | 2003-06-24 | 2004-12-30 | Seagate Technology Llc | Multi-tiered retry scheme for loading system data |
US7296142B2 (en) * | 2003-06-24 | 2007-11-13 | Seagate Technology Llc | Multi-tiered retry scheme for reading copies of information from a storage medium |
JP2012509521A (en) * | 2008-11-18 | 2012-04-19 | エルエスアイ コーポレーション | System and method for recovering solid state drive data |
US20100146239A1 (en) * | 2008-12-08 | 2010-06-10 | Infinite Memories Ltd. | Continuous address space in non-volatile-memories (nvm) using efficient embedded management of array deficiencies |
US20100325524A1 (en) * | 2009-06-23 | 2010-12-23 | Phison Electronics Corp. | Control circuit capable of identifying error data in flash memory and storage system and method thereof |
US8607123B2 (en) * | 2009-06-23 | 2013-12-10 | Phison Electronics Corp. | Control circuit capable of identifying error data in flash memory and storage system and method thereof |
US8416518B2 (en) * | 2010-05-31 | 2013-04-09 | Kabushiki Kaisha Toshiba | Magnetic disk drive and method for rewriting data block |
US20110292533A1 (en) * | 2010-05-31 | 2011-12-01 | Kabushiki Kaisha Toshiba | Magnetic disk drive and method for rewriting data block |
US10592330B2 (en) * | 2011-11-11 | 2020-03-17 | Level 3 Communications, Llc | Systems and methods for automatic replacement and repair of communications network devices |
US20180067795A1 (en) * | 2011-11-11 | 2018-03-08 | Level 3 Communications, Llc | Systems and methods for automatic replacement and repair of communications network devices |
US9424141B2 (en) * | 2012-04-28 | 2016-08-23 | Huawei Technologies Co., Ltd. | Hard disk data recovery method, apparatus, and system |
US9281845B1 (en) | 2012-06-27 | 2016-03-08 | Amazon Technologies, Inc. | Layered redundancy encoding schemes for data storage |
US9110797B1 (en) * | 2012-06-27 | 2015-08-18 | Amazon Technologies, Inc. | Correlated failure zones for data storage |
US9098433B1 (en) | 2012-06-27 | 2015-08-04 | Amazon Technologies, Inc. | Throughput-sensitive redundancy encoding schemes for data storage |
US8869001B1 (en) | 2012-06-27 | 2014-10-21 | Amazon Technologies, Inc. | Layered redundancy encoding schemes for data storage |
US8850288B1 (en) | 2012-06-27 | 2014-09-30 | Amazon Technologies, Inc. | Throughput-sensitive redundancy encoding schemes for data storage |
US8806296B1 (en) | 2012-06-27 | 2014-08-12 | Amazon Technologies, Inc. | Scheduled or gradual redundancy encoding schemes for data storage |
US9983963B2 (en) | 2015-11-09 | 2018-05-29 | Alibaba Group Holding Limited | System and method for exploiting hard disk drive capacity reserve and extending operating life thereof |
CN105808161A (en) * | 2016-02-26 | 2016-07-27 | 四川效率源信息安全技术股份有限公司 | Reading method of bad sector data of hard disk |
US20170329684A1 (en) * | 2016-05-13 | 2017-11-16 | Synology Incorporated | Method and apparatus for performing data recovery in redundant storage system |
US20230086852A1 (en) * | 2021-09-17 | 2023-03-23 | EMC IP Holding Company LLC | Method, electronic device, and program product for failure handling |
US11892920B2 (en) * | 2021-09-17 | 2024-02-06 | EMC IP Holding Company LLC | Method, electronic device, and program product for failure handling |
Also Published As
Publication number | Publication date |
---|---|
US6427215B2 (en) | 2002-07-30 |
US6332204B1 (en) | 2001-12-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6427215B2 (en) | Recovering and relocating unreliable disk sectors when encountering disk drive read errors | |
US6247152B1 (en) | Relocating unreliable disk sectors when encountering disk drive read errors with notification to user when data is bad | |
US6295619B1 (en) | Method and apparatus for error management in a solid state disk drive | |
US7490263B2 (en) | Apparatus, system, and method for a storage device's enforcing write recovery of erroneous data | |
US6513135B2 (en) | Automatic read reassignment method and a magnetic disk drive | |
US6993679B2 (en) | System and method for inhibiting reads to non-guaranteed data in remapped portions of a storage medium | |
US8661193B1 (en) | Disk drive with partial sector management | |
US7274639B1 (en) | Disk drive performing multi-level prioritization of entries in a suspect sector list to identify and relocate defective data sectors | |
US10120769B2 (en) | Raid rebuild algorithm with low I/O impact | |
US8289641B1 (en) | Partial data storage device failures and improved storage resiliency | |
US6408406B1 (en) | Hard disk drive infant mortality test | |
US6625096B1 (en) | Optical disk recording and reproduction method and apparatus as well as medium on which optical disk recording and reproduction program is recorded | |
US5572661A (en) | Methods and system for detecting data loss in a hierarchic data storage system | |
US7664981B2 (en) | Method of restoring source data of hard disk drive and method of reading system information thereof | |
US6360293B1 (en) | Solid state disk system having electrically erasable and programmable read only memory | |
US20070174678A1 (en) | Apparatus, system, and method for a storage device's enforcing write recovery of erroneous data | |
US5467361A (en) | Method and system for separate data and media maintenance within direct access storage devices | |
US6842867B2 (en) | System and method for identifying memory modules having a failing or defective address | |
US6426928B1 (en) | Ability to distinguish true disk write errors | |
US7389466B1 (en) | ECC in computer system with associated mass storage device, and method for operating same | |
US6393580B1 (en) | Automatic read reassignment method and a magnetic disk drive | |
US20070250757A1 (en) | Method and data storage devices for a RAID system | |
US6079044A (en) | Method and error correcting code (ECC) apparatus for storing predefined information with ECC in a direct access storage device | |
US20090241011A1 (en) | Memory device | |
CN113190179B (en) | Method for prolonging service life of mechanical hard disk, storage device and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees | ||
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20100730 |