JP2001189055A - Removable memory and removable memory drive - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a disk-like recording medium keeping the whole data in a sector even when an error exists in the ID data. SOLUTION: The ID data is incorporated in a data part so that an error correction code is applied to the ID data. Further, a re-synchronization part is provided, and even when the error exists in the data, an error detection code and an error connection code are made accessible.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention generally relates to an information record carrier and a driving device thereof, and more particularly to a removable memory having a predetermined format and a removable memory drive for recording and / or reproducing the removable memory. The disk-shaped recording medium of the present invention includes both a removable memory and a fixed disk, and is suitable as a sector format of, for example, current and next-generation magnetic disks, optical disks, and floppy (registered trademark) disks using an optical servo system. . Further, the removable memory of the present invention can store data such as video information, audio information, text information, and software, and security information for accessing these data. The present invention also relates to a security management method using the removable memory and the removable memory drive. Such a security management method includes a method of generating, storing, and using the security information.

[0002]

2. Description of the Related Art In recent years, optical disks and magnetic disks (hereinafter simply referred to as "disks") are required to have a large capacity for storing image files and moving image files, and data loss is prevented as much as possible. There is a demand for improved reliability. The disk is divided into a plurality of tracks in the circumferential direction, and each track is divided into a plurality of sectors. CLV (Constant Linear Ve) is used to arrange the sectors (physical format).
location, CAV (Constant An)
Gullar Velocity) system and ZCAV (Z
one Constant Angular Veloc
Ity) method is known. For example, CAV method and Z
In the CAV method, the rotation speed (angular speed) is substantially constant at the inner and outer circumferences, and the synchronous clock frequency for recording and reproduction is changed.
In the LV system, the clock frequency between bands is made the same by changing the rotation speed.

[0003] Each sector (or sometimes referred to as a "block") has an ID portion, a gap, a data portion, and a gap in this order. The ID portion is an area that can be written only by the media manufacturer, and is formed only at the time of physical formatting. The ID section identifies the ID section and stores ID data. ID data is generally
It stores information such as a synchronization unit (Sync), a track number, a sector number, and an (operation) bad sector (that is, defective sector) flag. Note that, in the present application, such an ID part existing as a pair with a data part may be referred to as an “independent ID part”. The conventional independent ID portion has a size of, for example, about 28 bytes, and the ID data is assigned, for example, a size of about 7 bytes.

The data section identifies the data section and stores predetermined data (user data).
Therefore, the ID part and the data part have a one-to-one correspondence. The data section has an error detection code (EDC) and an error correction code (ECC). The EDC detects whether the data in the data section is correct, but does not correct the error. The EDC (or an alternative functionally similar cyclic redundancy check code (CRCC)) is
It is also included in the D section and detects whether the ID data is correct but does not correct the error. The ECC can restore the original data by performing error correction on the data in the data section.

[0005] The gap is inserted for adjusting the length as a kind of buffer for absorbing the buffer between sectors. In addition,
The magnetic disk having a high storage capacity further has a sector mark for identifying a sector before the ID portion.

[0006] Disk drives use logical block addresses (or sometimes referred to as "user serial numbers") for their sectors (Logical Block Address:
By allocating an LBA), data at an arbitrary position can be directly read and written regardless of the order in which the data is stored. Such an access scheme is known as random access or direct access. In the random access method, for example, if all the data in the block 2 among the data recorded in the sectors (blocks) 1 to 3 are erased, the next new data is recorded in the block 2 instead of the block 4. As a result, there is a case where the order in which the data recorded in the block 2 is stored after the data recorded in the block 3.

A disk typically has a recording management area (disk management area) provided at the innermost and / or outermost circumference in the disk radial direction (track direction).
(Mental Area: DMA) and a plurality of bands interposed therebetween. The recording management area may be called a disk management information area, a disk mapping area, or the like. The DMA includes a disk management table (Disk Management Table) in all or a part of the DMA.
e: DMT) is formed. Therefore, DMA and DM
T may be used synonymously. The DMT may also be called a disk management (or mapping) track (or table). Note that the DMA is sometimes called a lead-in area and / or a lead-out area, but which of the outer circumference and the inner circumference is the lead-in area is a matter of specifications and is optional.

[0008] The DMA is formed when the disk is formatted and is an area used by manufacturers and drive systems that cannot be accessed by the user. The DMT includes a recording / reproducing method for the entire disc, a position of a data area (for example, replacement information), and other management information (for example, security data).
And other information are stored. The DMT is redundantly recorded in two areas on the inner and outer circumferences. Further, there is a case where the DMT is typically recorded twice in one DMA. This is to prevent all DMTs from becoming unrecognizable even when the disk is eroded by rust.

On the other hand, each band is an area that can be accessed by a user, and typically includes one data area and a corresponding spare area. The data area is an area for storing predetermined data to be recorded by the user.
BA will be attached. The replacement area stores a replacement block (replacement block) for the defective block existing in the user area. Therefore, if there is no defect in the data area, no data is written in the replacement area. The address of the replacement area is written in the DMT. The reason why the band is divided into the data area and the replacement area in this manner is that if a replacement block is provided in the data area,
This is because the LBA already attached is out of order.

Generally, two types of replacement management systems are adopted for disks. If the manufacturer finds a defective block in the data area at the time of the initial inspection performed before shipping the disc, the block having the next address to the defective block is replaced with the defective block because no data is stored in the data area yet. The replacement information is stored in the DMT. This replacement method does not involve a replacement area, and a primary defect list (primary defect list) is used.
Fact List (PDL). On the other hand, if a defective block occurs in the data area while the user is using the disk, the replacement area provides a replacement block. This replacement method uses a secondary defect list (Second defect list).
It is generally known as a "dary Defect List (SDL)".

[0011] The disk is typically managed by an operation system (OS) of an external device (for example, a personal computer) to which the disk drive is connected. To access predetermined data on the disk, the OS notifies the control unit of the disk drive of the LBA, and based on this, the control unit moves the head to the sector having the LBA and performs a recording / reproducing operation.

[0012]

In view of the recent demand for increasing the capacity of a disk and improving reliability, the present inventor has reviewed the currently used disk format and drafted a simpler format. It has been conceived to increase the capacity of the disk, increase the capacity by further storing user data in the increased portion, and / or improve the reliability by storing data redundantly. Therefore,
As a result of intensive studies on the conventional format system, the present inventors have found that the identification of the data portion does not necessarily require the ID portion and the ID data having the above-described size. The inventor has also found that DMT has room for improvement in order to realize a simpler format.

When a data error occurs in a conventional disk, if the error is a data portion, the ECC can correct the error and restore the original data.
However, since the ECC is configured not to operate on the ID section, if there is an error in the ID data, it cannot be corrected, and the ID information of the sector cannot be read, so that the data in the sector cannot be read. The whole is lost. Further, since the ID data is as short as several bytes, there is a technical problem that even if the ECC is provided in the ID section, the ID data does not operate smoothly. Alternatively, as disclosed in Japanese Patent Laid-Open Publication No.
No. 712 discloses a technique in which the ECC operates on the ID section. However, in the configuration of the publication, the data amount of the ID section on which the ECC operates is unnecessarily large and high-speed processing (for example, real-time processing) is not possible. Will be possible. In connection with this, EC
The capacity of C must be increased, and the capacity is increased as a whole, and the processing speed is further reduced.

At present, there is a demand for storing and selling software on a rewritable disk such as an optical servo type floppy disk having a high storage capacity. In this case, if functions that do not exist in the conventional media can be realized in the copy product, it can help increase orders. On the other hand, if the user can freely rewrite such new information added to the disc, it is not preferable because it causes problems such as illegal copying. It is also preferable that the user can be prevented from erroneously erasing the software. Furthermore, it is preferable to adopt a configuration that does not infect such software with a computer virus. For example, conventionally, an operation system (OS) also has attribute information on a file basis.
This was modifiable on the OS and was not an effective countermeasure against computer viruses.

[0015]

SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to provide a new and useful removable memory and a removable memory drive which solve such conventional problems.

More specifically, it is an exemplary object of the present invention to provide a removable memory having a format that is simpler than a conventional one and a removable memory drive for driving such a removable memory.

In order to achieve the above object, a removable memory according to an exemplary aspect of the present invention has a plurality of sectors each having a data section, and the data section has an ID representing the ID of the corresponding sector. It has data, user data that can be recorded and reproduced by the user, and an error correction code that can correct errors in both the ID data and the user data. According to such a removable memory, the data in the sector is maintained because the error correction code extends to the ID data which did not work on the conventional magnetic disk.

According to another aspect of the present invention, there is provided a removable memory including a plurality of sectors each having a data portion, wherein the data portion includes user data recordable and reproducible by a user and an error in the user data. An error detection code, an error correction code arranged in a predetermined positional relationship from the error detection code and capable of correcting the data error, and a resynchronization functioning as a trigger for reading the error detection code. And a part. According to such a removable memory, the resynchronization unit
It is possible to prevent a reading position of an error detection code from being shifted due to an error existing in a data portion, and to enable reading of an error detection code. Further, the error correction code is determined from the error detection code in a predetermined positional relationship (for example, adjacent).
Since it is known that the error detection code is arranged, if the error detection code can be detected, the error correction code can also be detected. As a result, the reading of the user data can be secured by the error detection code and the error correction code.

According to another aspect of the present invention, there is provided a removable memory having a plurality of sectors each having an ID portion and a data portion, wherein the ID portion identifies an ID of the corresponding sector, The data section includes ID data representing the ID of the corresponding sector, user data that can be recorded and reproduced by a user, and an error correction code that can correct errors in both the ID data and the user data. Have. According to such a removable memory, the user data can be written immediately if the first ID part can be detected, so that the writing speed is high.

According to another aspect of the present invention, there is provided a removable memory having a plurality of sectors each having a data portion, wherein the data portion includes user data that can be recorded and reproduced by a user, and an error in the user data. And an error correction code that is arranged in a predetermined positional relationship from the error detection code and that can correct the error of the data. And a post-synchronization unit that functions as a trigger. According to such a removable memory, the post-synchronization section prevents a signal read position of a desired field from being shifted due to an error existing in the data section, and allows a desired field (for example, an error correction code or the like) to be read in the backward direction. As a result, reading of user data can be ensured by the error correction code.

A removable memory according to another exemplary embodiment of the present invention is a magnetic disk having a plurality of sectors each having an ID section and a data section,
The unit comprises: ID data representing an ID of the corresponding sector;
An ID error detection code for detecting an error in the ID data, and a post-synchronization unit functioning as a trigger for reading a desired field of the ID unit in a backward direction,
The data section has user data that can be recorded and reproduced by a user. According to such a removable memory, the post-synchronization section prevents the signal readout position of the desired field from being shifted due to an error existing in the ID section, and the desired field (for example, ID data or ID error detection code) is prevented.
In the reverse direction. As a result, the ID data can be read again in the reverse direction.

According to another embodiment of the present invention, there is provided a removable memory including a plurality of sectors each including a sector mark for identifying a sector and a data portion, wherein the data portion stores an ID of the corresponding sector. ID data to be recorded and user data that can be recorded and reproduced by the user.
According to such a removable memory, each sector does not have an independent ID part, unlike the related art, so that the storage capacity can be increased. In the expanded capacity, further user data may be stored to achieve a large capacity, or management information may be redundantly stored to improve reliability. Further, the removable memory drive as an exemplary embodiment of the present invention capable of driving such a removable memory has the same effect.

According to another exemplary aspect of the present invention, there is provided a method for storing a plurality of sectors, a management area capable of storing management data related to the sectors and not being rewritten by a user, and at least a part of the management data. Forming an area different from the management area in the removable memory; and, when the management area becomes unreadable, referencing the defective sector information stored in an area different from the management area. Repairing. According to this method, it is possible to restore a management area that could not be restored conventionally.

A method of calculating a sector address according to another exemplary embodiment of the present invention includes a plurality of tracks each having a plurality of sectors, a number of operable sectors included in each track, and a reference for each sector included in each track. Referring to an area in which an offset number from an address can be stored, forming ID data for storing the ID of the sector in a removable memory, and accessing the area when accessing a predetermined sector among the plurality of sectors. The address of the predetermined sector, the total number of operable sectors included from the first track to the track immediately before the predetermined track including the predetermined sector, and the predetermined sector from the start address of the predetermined track. And calculating the total number of offsets. In this method, the sector address is calculated more easily than in the past by using the total number of operable sectors and the total number of offsets.

A read method according to another exemplary aspect of the present invention includes a step of receiving a predetermined address to be accessed, a plurality of tracks each having a plurality of sectors, and an operable operation included in each track. In a removable memory capable of storing the number of sectors, the number of offsets of each sector included in each track from a reference address, and ID data for storing the ID of the sector, a predetermined sector having the predetermined address from a first track is provided. The predetermined track is specified by calculating the sum of the total number of operable sectors included up to the track immediately before the predetermined track to which the track belongs and the offset number of the predetermined sector from the start address of the predetermined track. The head at the start address of the predetermined track specified in the specifying step. Moving the head, reading the ID of the sector on the predetermined track while moving the head, and determining whether or not the sector is located immediately before the predetermined sector. Reading data stored in a predetermined sector. In this method as well, the sector address is calculated more easily than in the past by using the total number of operable sectors and the total number of offsets. In addition, the removable memory drive according to an exemplary embodiment of the present invention, which has such a method in a memory as firmware, has a similar effect.

A write method according to another exemplary aspect of the present invention includes a step of receiving a predetermined address to be accessed and a plurality of tracks each having a plurality of sectors, each of which includes an operable operation included in each track. In a removable memory capable of storing the number of sectors, the number of offsets of each sector included in each track from a reference address, the operability of each sector, and ID data for storing the ID of the sector, Calculating a total of a total number of operable sectors included up to a track immediately before a predetermined track to which a predetermined sector having a predetermined address belongs and an offset number of the predetermined sector from a start address of the predetermined track; Identifying the predetermined track and confirming the operability of each sector of the predetermined track And mapping process that includes the steps of moving the head to the start address of the given track calculated by the identifying step, while moving the head,
Reading the ID of a sector on the predetermined track to determine whether the sector is located immediately before the predetermined sector; and determining whether the predetermined sector is an operable sector from the predetermined sector. Writing the predetermined data by the head from the first operable sector after the predetermined sector if the predetermined sector is a defective sector. In this method as well, the sector address is calculated more easily than in the past by using the total number of operable sectors and the total number of offsets. A removable memory drive according to an exemplary embodiment of the present invention, which has such a method as firmware in a memory, performs the same operation.

[0027] Other objects and further features of the present invention will become apparent from the embodiments described below with reference to the accompanying drawings.

[0028]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A format structure of a sector 1 of a magnetic disk which is a removable memory according to an exemplary embodiment of the present invention will be described below with reference to FIG.
The magnetic disk has a plurality of sectors, and FIG. 1 is a schematic block diagram of one sector. The sector 1 of the present invention includes a data (Data) section 100 and a gap (Ga).
p) 200. The data section 100
It has an ID ′ section 110 and a Data ′ section 120.
The data section corresponds to a conventional data section in that it is a field in which the ECC 128 described later functions. ID '
The section 110 has ID data 112 and the Data 'section 12
0 is the user data 122, the resynchronization unit (Resync B)
te), an error detection code (EDC) 126, and an error correction code (ECC) 128. The magnetic head (not shown) reads the sectors in FIG. 1 and other figures from left to right.

The ID 'section 110 includes ID data 112. However, like the conventional ID section, an ID synchronization section (ID S
nc) and the ID mark (ID Mark) are not included. Here, the ID synchronization unit is a read trigger for hardware (for example, a PLL circuit) for finding an ID mark, and has a function of identifying that the ID mark is an ID unit. The ID 'part does not include the ID synchronizing part and the ID mark because the ID' part 110 is arranged not in the ID part but in the data part 100. However, the ID 'part may have EDC or a cyclic redundancy check code (CRCC) functionally similar to this. The ID data 112 represents the ID of the corresponding sector 1 and has a size of, for example, 7 bytes. A drive device (not shown) of the magnetic disk having the sector 1 recognizes in advance by a software program that the first few bytes of the sector 1 are the ID 'part 110. The “first few bytes of sector 1” is generally determined if the maximum number of sectors is determined.

The user data 122 is predetermined data that can be recorded and reproduced by the user. The resynchronization unit 124 functions as an EDC read trigger as described later. ED
C126 detects whether the user data 122 is correct, but does not correct the error. The ECC 128 can restore the original data by performing error correction on the ID data 112 and the user data 122 as described later.
The gap 200 is inserted for adjusting the length as a kind of buffer for absorbing a buffer between sectors.

In sector 1, the ID section provided independently in the conventional magnetic disk is removed, and instead,
By providing an ID 'unit 110 including data 112 in the data unit 100, the ECC1
28 are configured to operate. That is, the sector 1 applies the ECC 128 to the ID 'unit 110 by regarding the data from the ID' unit 110 to the Data 'unit 120 as the data unit. Since the ECC 128 extends to the ID data 112 which did not work on the conventional magnetic disk, any error can be corrected by the ECC 128. Conventionally, if there is an error in the ID section, it cannot be corrected, and as a result, all data in the sector cannot be used because the ID information cannot be read.
In the sector 1 of the present embodiment, if there is an error in the ID '
By generating the C128, the user data 122 is maintained, and the reliability is improved. Further, unlike the related art, an independent ID section is not required, so that the storage capacity can be expanded. In the expanded capacity, further user data may be stored to achieve a large capacity, or management information may be redundantly stored to improve reliability.

Preferably, sector 1 includes data section 100
Before the data synchronization unit (Data Sync) shown in FIG.
130 and a data mark 132. The data synchronizer 130 is provided with hardware (for example, P
LL circuit). The data mark 132 identifies the data part 100. In the case of a floppy disk using the optical servo method, a sector synchronization and a sector mark will be further provided before the data synchronization unit 130 and the data mark 132 shown in FIG.

The sector 1 has a resynchronization unit 124. The resynchronizing unit 124 has not been provided in the conventional magnetic disk. The resynchronization unit 124 is configured with a single frequency that returns to the original pattern because the same frequency is repeated. The re-synchronization unit 124 is a read trigger for hardware (for example, a PLL circuit) that notifies that the EDC 126 is to be read after synchronization in response to a specific signal when an error occurs in the user data 122. The magnetic head of the driving device (not shown) moves forward (ie, from left to right in FIG.
To read 126, the resynchronization unit 124
It is arranged at a stage earlier than 6. When the EDC 126 is read by reading the magnetic head in the reverse direction, a post-synchronizing unit, which will be described later, disposed after the EDC 126 can be used.

The specific signal is, for example, E
512 bytes excluding DC126 and ECC128
If it is not a byte, it can be automatically generated in a magnetic disk drive (not shown) so that it is automatically generated. In this embodiment, the resynchronization unit 1
24 are arranged immediately before the EDC 126,
A plurality of data may be provided inside the ata 'section 120. Further, the resynchronization unit 124 includes the ID 'unit 110 and the Data' unit 1
20 (the EDC 126 thereof).

Here, the errors occurring in the user data 122 are (1) that the signal cannot be read from the user data 122 (that is, the signal is broken), and (2) the read position of the signal is shifted. At least two things are included. If the signal cannot be read, the ECC 128 corrects the signal. That is, EDC12
6 and the address of the ECC 128 are designated and operated to correct an error in the user data 122.

On the other hand, the resynchronization unit 124 operates when the signal position is shifted, and an error in the user data 122 (ie, a shift in the signal reading position) is detected by the EDC 126 and the EC.
Propagation to C128 is prevented, and EDC 126 can be read reliably. More specifically, when the position of the signal is shifted by, for example, 20 bytes, the shift in the user data 122 is determined by the subsequent resynchronization unit 124 from the EC.
Since the position of the EDC 126 and the ECC 128 is shifted to reach the C128, even if the address is specified in order to operate the EDC or the ECC, it does not correspond to the actual EDC 126 or the EC.
It may not be the address of C128. Therefore, the resynchronization unit 124 clarifies the position of the EDC 126 and
26 and ECC128. ECC128
1 is adjacent to the EDC 126 as shown in FIG. 1 or separated from the EDC 126 by a predetermined distance.
8 can also be read.

More specifically, EDC 126 and EDC
CC128 has a signal reading position slightly (for example, 20
Even if it is shifted (within bytes), error calculation can be performed. Therefore, the resynchronization unit 124 operates only when the EDC
It will be the case that the deviation of the signal from the error calculation of 126 or ECC 128 exceeds the allowable value.

The operation when the magnetic head (not shown) of the sector 1 shown in FIG. 1 writes information to the user data 122 will be described. First, as described above, the magnetic head recognizes in advance that the first few bytes of the sector 1 are the ID 'part 110 by the software program. I
If the D ′ unit 112 can read the data, and if the Data ′ unit 120 can be read without any problem (that is, if the read information can be understood), the magnetic head writes the information in the user data 122 and proceeds to the next sector via the gap 200. move on.

On the other hand, the magnetic head uses the I '
If there is an error in the D data 112 and / or the user data 122 of the Data 'unit 120, the E
Access DC126 and ECC128 or EDC12
6 and the address of the ECC 128 are designated and operated. As a result, the ECC 128 performs error correction. Note that once the ECC 128 operates, error correction is performed on the entire ID 'unit 110 and Data' unit 120 (excluding the ECC 128 itself). afterwards,
The magnetic head performs the write operation as described above. As a result, the ECC 128 can correct ID data that could not be corrected if there was an error in the related art, thereby improving data reliability. Note that reading of the user data 122 is the same, and a description thereof will be omitted.

Next, with reference to FIG. 3, a description will be given of a format structure of sector 2 of a magnetic disk which is a removable memory as another exemplary embodiment of the present invention. The magnetic disk has a plurality of sectors, and FIG. 3 is a schematic block diagram of one of the sectors. Note that, in FIG. 3, the same elements as those shown in FIG. 1 are denoted by the same reference numerals, and redundant description will be omitted.

The sector 2 of the present invention includes a data section 100a
The point that a gap 200 is added after the data section 100 (ie, the data synchronization section 130 and the data mark 132 shown in FIG. 2 are added to the data section 100 in FIG. 1) is the same as the sector described with reference to FIGS. However, this is different from the sector 1 in that the ID section 300 is arranged via the gap 200 in front of the data section 100a. That is, sector 2 is independent I
It has a D section 300.

The ID section 300 includes an ID synchronization section (ID Sy).
nc) 310 and ID mark (IDMark) 320
, ID data 330 and an ID error detection code (ID
EDC) 340. ID synchronization section 310
Hardware to find mark 320 (eg,
This is a read trigger for the PLL circuit, and has a function of identifying that the ID mark 320 is the ID section 300. The ID data 330 may store the same information as the ID data 112, or the ID data 112 may be a part of the ID data 330. For example, the ID data may be only the sector address. ID data 330 is read I
D and track start logical address (TSL)
BA) information. The TSLA is the first OS or command-based logical address information of the track on the concentric circle, and the current LBA is TSLBA + sector address. The ID EDC 340 is the ID data 33
Detects whether 0 is correct, but does not correct the error.

The sector 2 has a feature that the recording / reproducing speed by the magnetic head can be higher than that of the sector 1 if the ID section 300 operates normally. Because the magnetic head is the ID data 330 of the ID section 300
Is ready for recording / reproduction as soon as it can be read. On the other hand, in the sector 1, the magnetic head starts reading and writing to the user data 122 after reading up to the gap 200 (the reading of the data section 100 cannot be interrupted halfway). Most ID part 300
It should be noted that, when is broken, sector 2 may have a lower recording / reproducing speed than sector 1. In FIG. 3, the number of bytes of the ID part 300 appears to be long, but is actually as short as several bytes.

In the case where a magnetic head (not shown) reads the sector 2 shown in FIG.
The ID data 330 of 0 is read. If the ID data 330 can be read properly, the magnetic head starts writing to the user data 122 in the data section 100a. Note that the magnetic head recognizes in advance that the first few bytes after reading the data mark 132 are the ID 'part 110.

On the other hand, if the ID data 330 of the ID section 300 cannot be read due to an error, the I
The ID data 112 in the D ′ section is read. ID data 11
2 may be present before or after the user data 122 or randomly between the data mark 132 and the resynchronization unit 124. If the magnetic head can read the ID data 112, it similarly starts writing to the user data 122.

If there is an error in the ID data 112 of the ID 'section 110 and / or the user data 122 of the Data' section 120, the magnetic head passes through the resynchronization section 124 to the EDC 1
26 and ECC 128 or EDC 126 and E
These are operated by designating the address of CC128.
As a result, the ECC 128 performs error correction. Note that E
Once the CC 128 operates, the ID 'section 110 and the Dat
The entire a 'section 120 (excluding the ECC 128 itself)
Will be corrected. Thereafter, the magnetic head starts writing to the user data 122 in the same manner. As a result, the ECC 128 can correct ID data that could not be corrected if there was an error in the related art, thereby improving data reliability. Note that user data 1
The reading of 22 is exactly the same, and the description is omitted.

The resynchronization unit 124 used in this embodiment
Indicates that the EDC 126 is used when an error occurs, regardless of whether the ID 'section 110 is a part of the data section 100 (or 100a) in the sectors 1 and 2.
It can be understood that the present invention can also be applied to a conventional sector structure in that access to the ECC 128 is ensured. The resynchronizing unit 124 facilitates the forward reading of the EDC 126 by the magnetic head. Hereinafter, a post synchronization unit (Post Sync) 140 that facilitates the backward reading of the EDC 126 will be described.

For example, sector 3 of a magnetic disk which is a removable memory according to another exemplary embodiment of the present invention
Represents the data part 100b and the gap 2 as shown in FIG.
00. In FIG. 4, the same elements as those shown in the other figures are denoted by the same reference numerals, and the duplicate description will be omitted. The data section 100b has two post-synchronization sections 140 unlike the data section 100a. The post-synchronizer 140 enables the magnetic head to read the desired field in the reverse direction.

The post-synchronizer 140 has not been provided on a conventional magnetic disk. The post synchronizer 140 is configured with a single frequency that returns to the original pattern because the same frequency is repeated. The post synchronization unit 140 has an ID
When an error occurs in the data 112 or the user data 122, a hardware (for example, P) that indicates that a desired field such as the ID data 112 or the ECC 128 is to be read in the reverse direction in response to a specific signal in synchronization.
LL circuit). Since the magnetic head of the drive unit (not shown) reads the post-synchronizer 140 in the reverse direction (ie, from right to left in FIG. 4), the desired field is located on the left side of the post-synchronizer 140 (before the forward read). You.

In FIG. 4, the post synchronization section 140
There are two places. For example, when the ID data 112 has an error, the post-
Is used to correct the ID data 112. The post synchronization unit 140 on the left side is used, for example, when the read position of the ID data 112 is shifted and is corrected and read again. This is because even if the user data 122 can be accessed, the information cannot be substantially reproduced and recorded without knowing which sector. It is needless to say that the positions and the numbers of the post-synchronizers 140 shown in FIG. 4 are merely examples.

Similarly, the ID section 300 shown in FIG.
Can be replaced with the ID part 300a shown in FIG. The ID section 300a has a post-synchronizer 350 identical to the post-synchronizer 140 arranged downstream of the ID EDC 340.
It is used, for example, when the readout position of 00 is shifted and is corrected and read out again. This is because even if the user data 122 can be accessed, the information cannot be substantially reproduced and recorded without knowing which sector.

The post-synchronizer 14 described with reference to FIGS. 4 and 5
0 and 350 ensure that the magnetic head accesses the desired field in the event of an error, completely independent of whether the ID 'section 110 is part of the data section 100 (or 100a). It will be appreciated that it can be applied to conventional sector structures.

Next, a floppy disk (magnetic disk) using an optical servo system as another embodiment of the removable memory according to the present invention will be described with reference to FIGS. Needless to say, the removable memory widely includes an optical disk, a magneto-optical disk, and the like. Here, FIG. 6 is a plan view of the removable memory 400 of the present invention embodied as a magnetic disk employing the optical servo method. FIG. 7 is a schematic block diagram showing the configuration of the management areas (DMA) 410a and 410b shown in FIG. FIG. 8 is a schematic plan view for explaining the zone structure of the removable memory 400 shown in FIG.

First, referring to FIG.
00 has management areas 410a and 410b, a data area 440 and a groove 480 existing therebetween. The disk 400 characteristically employs laser servo, irradiates the groove 480 with laser light, detects the intensity of reflected light that changes depending on the presence or absence of the groove 480, and performs tracking servo, for example, 2,490 tpi.
Optical track density. The number of the grooves 480 is, for example, 1666 / circumference, 930 grooves / surface, and a duty ratio of 50%.

In the management area 410a, for example, the head of a removable memory drive, which
00 is an area to be accessed, and the management area 410b is
For example, the buffer area indicates the end of reading, and is provided at the innermost circumference or the outermost circumference facing the management area 410a. The management area may be only one of the management areas 410a and 410b, or may be provided more. The management area 410 is an area that the user cannot access. "Inaccessible" means that access is not possible when the user uses a normal removable memory drive, for example, when the user modifies the drive or uses the same equipment as the manufacturer It should be noted that this does not always mean that rewriting is impossible.

As shown in FIG. 7, each of the management areas 410a and 410b (hereinafter, unless otherwise specified, the reference number 410 is to be summarized)
Two DMTs 420a and 420b (hereinafter, unless otherwise specified, the reference numeral 420 is a general description thereof) and, optionally, one security table (S
T) 430a and 430b (hereinafter, unless otherwise specified,
Reference number 430 is intended to summarize these. ) Are redundantly provided. However, the present invention relates to the management area 41.
This does not prevent Oa and 410b from having zero or a different number of DMTs 20. DMT 420 stores management data, and ST 430 stores security data. In the present embodiment, the same management data is redundantly stored in the four DMTs 420.
T420 may store different management data. Further, in FIG. 7, ST 430 is located at the top in management area 410, but it is needless to say that the present invention is not limited to this.

Table 1 shows an example of the management data and the security data. In FIG. 7 and Table 1, ST43
0 is located at the beginning of the DMA 410,
The 30 pieces of information are divided into pieces or collectively
It is needless to say that the present invention is not limited to this, such as being arranged in one place or a plurality of places in T420.

[Table 1]

The management data generally includes control information of the disk 400, test information, replacement block information, bad sector flag information, and the like. In Table 1, USN is an update serial number (Update Serial Number).
r), DSC is the data sector count, RSC is the re-allocation sector count (Reasin Sector Co.)
unt), TSA zone X is track start address in zone X, RSA is reallocation sector address, L
BA indicates a logical block address. In the present invention, as will be described in detail in another embodiment described later, management data different from the conventional one can be constructed at the time of formatting.

ST43 in which security data is stored
0 can be considered to be arranged in the security area in a broad sense. In this embodiment, the security area is provided in the management area 10. As described above, it is preferable that the security area is provided in an area that cannot be accessed by the user. This is because (1) if the security area is provided in the data area 440 if the removable memory 400 of the present embodiment is of a rewritable type, it may be erroneously used for writing user data. (2) It can function as a confidentiality-dedicated area if it is not an area normally accessed by the user. However, the area that the user cannot access is not limited to the management area 410. For example, even in the data area 440, a reserved area reserved for a predetermined purpose that is not used for recording and reproducing user data can be allocated to the security area. Therefore, the security area is the management area 410
It is not limited to a part.

ST30 has a security write count, which is the number of rewrites in ST30, a security flag for displaying the presence or absence of a security area, and a security drive S / N for displaying the serial number of the drive 800 to which the last security has been added. The password length indicates the length of the password to be stored in the security code. The security code has 36 bytes and can be written using any cryptographic method, including simple ASCII codes. The security data ends at the 165th byte, but it goes without saying that the security data is not limited to this byte.

Various security levels can be set for the security 1 to 9. In the security level 1, for example, the disk 400 is ejected from the drive 800 when the number of comparison tests between the password input by the user and the password stored in the disk in advance exceeds a predetermined number. Security level 2 defines, for example, the number of password entry failures by the user,
When the number of times exceeds a specified number, the DMT 420 is deleted. The security level 3 prohibits, for example, reading from a drive other than a drive with security. Other security levels may require additional information (user name, company name, phone number, biometric data, external institution authentication code, etc.).

The security data is recorded at a plurality of locations according to the number of DMTs 420 with a physical distance therebetween. The contents of the management data recorded in a plurality of locations can be the same and / or different. Recording the same security data redundantly at a plurality of locations avoids data loss due to security data defects and increases reliability. For example, the security data stored in the second DMT 20a in the management area 410a shown in FIG. 7 may be redundant with the security data stored in the first DMT 420a. In particular, since there is a high risk that data is lost due to erosion of the disk medium from the outer circumference or the inner circumference due to rust, it is preferable to record security data redundantly in both the management areas 410a and 410b.

In this embodiment, the security area is formed as a result of the user selecting the security format when formatting the disk. Since only the physical format is changed instead of the disk structure, the present invention can use a conventional removable memory, or can use a unique removable memory 400 shown in FIG.

As described above, the information of ST 430 may be divided or collectively arranged in DMT 420 at one location or at multiple locations. Recording security data having different contents in a plurality of locations increases the reliability of data because meaningful security data cannot be obtained unless all security data is found. If necessary, the method of combining the data segments of each security data may be characterized. For example, in the management area 410a, the security data in the two DMTs 420a shown in FIG. 7 are combined from left to right, and in the management area 410b, two security data are written from right to left.
Security data in two DMTs 420b are combined, and so on. Optionally, any data segment may define how other management data segments are combined.

The security data manages access to the user data, and thus has an effect of maintaining the confidentiality of the user data. In general, the level of confidentiality (security) depends on the existence of security data and the difficulty in determining security data. The level of confidentiality generally increases with the complexity of the system, but complex systems increase costs and reduce reliability. The level of reliability and cost generally increases with the simplicity of the system.

In order to solve such a problem, the security data of this embodiment basically includes only a security flag and a password as essential components. As a result,
It is possible to reduce the information amount of the security data so that the existence of the security data itself is not found. If no security data is found, no security data is determined, and if the amount of information is small, simplification can be achieved. Considering the security data function, the security data of this embodiment
The information amount of the conventional management area such as the control track of the O standard magneto-optical disk is unnecessary. However, the present invention does not exclude increasing the amount of security data.

In this embodiment, since the recording area of the security data is limited to a part of the track, it is effective to make the existence of the security data inconspicuous.
Therefore, the security area does not need to cover the entire circumference (circumference) of the disk 400, and it is sufficient to secure only an area necessary and sufficient for recording ST430. As a result, when the removable memory 400 is an optical disk, a Service-to-Self examines with a microscope or the like in an attempt to determine the existence of security data for each track by looking at only a part of the track of the disk 400 of the present embodiment and there is no security data. Or give up examining security data.

On the other hand, the data area 440 is an area which can be used by the user, and the recordable / reproducible disk 400 uses this area to record video information, audio information, text information, software and other information (user data). be able to. Each data area 440 may have the sector structure shown in FIGS. 1 to 5, but is not limited thereto. Hereinafter, modifications of the sector structure applicable to the data area 440 will be described with reference to FIGS.
This will be described in detail with reference to FIG. Here, FIG. 9 is a block diagram showing the structure of the zone management sector 500 shown in FIG. FIG. 10 is a block diagram showing the structure of data sector 600 shown in FIG.

The data area 440 has a plurality (for example, 11
0), each zone illustratively has 32 tracks, and each track has 256 sectors. Therefore, the removable memory has 3520 tracks. As shown in FIG.
0 is a zone management sector (Zone Managementme).
nt Sector: ZMS) 500, data sector (Data Sector: DS) 600, and gap (GAP) 700. Note that a desired number of gaps 700 are provided at desired positions regardless of FIG.

The ZMS 500 and DS 600 have the same sector structure as shown in FIG. 9 (second from the top) and FIG. Characteristically, like the sector structure shown in FIG. 1, they do not include an independent ID part. The removable memory 400 of this embodiment has a storage capacity after formatting (that is, the total capacity of all data areas 640 described later) that is 90% or more of the storage capacity before formatting, and has a conventional magnetic capacity having an independent ID section. Compared to the disk, the storage capacity can be increased by about + 5%.
According to the conventional format having an independent ID part,
The actually usable capacity is smaller than the original storage capacity of the removable memory. The inventor of the present invention considers that the cause is to provide an independent ID section on which information cannot be recorded, and achieves the efficiency and reliability of the format by the removable memory 400. Further data may be stored in the expanded capacity to increase the capacity, or management information, ZMS, EDC and / or
Alternatively, ECC may be stored to improve reliability. Also,
Since they have the same structure, even if an error occurs in the ZMS 500, it is possible to save information to the DS 600, thereby improving reliability.

Each ZMS 500 manages one track included in the corresponding zone. In this embodiment, since 32 tracks are provided in one zone, 32 ZMSs 500 of ZMS0 to ZMS31 are provided. For example, ZMS0 manages a track having a track number 0 included in the zone. In other words, ZMS5
The number 00 indicates the track number included in the zone. Further, in the present embodiment, as shown in the uppermost diagram of FIG.
600 are provided adjacent to each other (but via the gap 700). Here, the uppermost diagram in FIG. 9 is a schematic block diagram in which the ZMS 500 and the data sector 600 shown in FIG. 8 are arranged in a line. Such a ZMS arrangement has the advantage that by reading the first 32 ZMSs 500, 32 tracks included in the zone can be managed.

As shown in FIG. 9, the ZMS 500 has a sector mark (Sector Mark) 510 and a data (Data) section 520, and does not include an independent ID section. The sector mark 510 indicates the data part 52
This is a trigger for hardware (for example, a PLL circuit) included in the drive 800 for recognizing 0.

The data section 520 has a data preamble (Data Pr) as shown in the second diagram from the top in FIG.
eamble) 522, the data synchronization unit 524, and the ZM
S field type code (Field Type Code)
e: FTC) 526, ID data 528, resynchronization unit 530, data area 540, data EDC 580
And data ECC590. Here, the second diagram from the top in FIG. 9 is a schematic block diagram showing the structure of the ZMS 500.

The data preamble 522 is a trigger for detecting the data synchronization section 524 by a hardware (for example, PLL circuit) PLL circuit included in the drive 800. In this embodiment, the size of the data preamble 522 can be reduced as much as possible (for example, 8 bytes). The data synchronization unit 524 uses the ZMS
This is a read trigger for hardware (for example, a PLL circuit) for detecting the field type code 526. The ZMS FTC 526 is a code for identifying that the information currently read by the head is that of the ZMS 500.

The ID data 528 includes a zone number for identifying a zone number, a track number in a zone for identifying a track in a zone (that is, a ZMS number), and a reference address in a track (that is, the sector to which the sector belongs). It consists of a sector number for identifying the number of offsets from the track start address (LBA). The present inventor has found that these three data are substantially sufficient to calculate the position of a sector. The method of calculating the sector address will be described later. Since each of these is sufficient for 1 byte, ID data 5
28 is sufficient for 3 bytes in total. Therefore, the present inventor has succeeded in expressing the information that has been consumed in the ID part of the conventional sector structure in 28 bytes substantially in 3 bytes. Therefore, the ID data 528 further improves the ID data 112.

The ID data 528 also holds the advantages of the ID data 112. That is, the ECC is added to the ID data 528.
590 is configured to operate. Since the ECC 590 extends to the ID data 528 which did not work on the conventional magnetic disk, any error can be corrected by the ECC 590, thereby improving the reliability.

The resynchronization unit 530 is a read trigger for hardware (for example, a PLL circuit) for detecting the data area 540. The data area 540 is shown in FIG.
The resynchronization unit is included like the user data 122 including the resynchronization unit 124 shown in FIG. The layout 541 of the data area 540 is shown third from the top in FIG. As shown in the figure, the data area 540 includes the side track code 54
2, track start LBA 542, operable sector number 546, and sector 0 to sector x + n information 550a to 550x + n (hereinafter, unless otherwise specified, reference numeral "55"
"0". ) And a reserved area 578. In this embodiment, the EC
Error correction by C590 has been extended.

The side track code 542 identifies whether it is the front surface or the back surface of the removable memory 400. The track start LBA 542 and the start address of the track managed by the ZMS 500 are identified. The number of operable sectors 546 identifies an operable sector (that is, a sector that is not a defective sector) included in a track managed by the ZMS 500. The sector information 550 stores information for managing each sector included in the corresponding track. The layout 551 of the sector information 550 is shown fourth from the top in FIG. As shown in the figure, a sector number 552, a reserved area 554, an operable / defect flag 562, and a replacement information (PD / SD) flag 564
And a write attribute (WRT) flag 566 and a read attribute (RD) flag 568. In this embodiment,
These fields are subject to error correction by the ECC 590.

The sector number 552 is the number of the sector (for example, “0” for the sector 0 information 550a).
Identify. In the present embodiment, the reserved area 554 is
This area is reserved for future use. The operable / defect flag 562 identifies whether the sector is an operable sector or a defective sector. For example, if the flag 562 identifies the sector as an operable sector, in a write operation described later, a head 830 described later will write data to the sector. If the flag 562 identifies the sector as a defective sector, a write operation to be described later is performed in a head 8 to be described later.
30 will write data to the next operational sector after that sector.

The replacement information flag 564 identifies replacement information (ie, PDL and SDL) of the sector. For example, the operable / defect flag 562 identifies a defect, and if a substitute sector exists, identifies the address of that sector. Such a replacement method is generally called DMT420 as SDL.
Is stored in However, in the present embodiment, the replacement information 56
4 is used to repair any DMT 420 that has been destroyed (e.g., scratched across a track). The replacement information flag 564 indicates that the E
Although formed in the data section 520 to which the CC 590 extends,
DMT 420 is not as good as ECC 590. For this reason,
This embodiment enables error correction for information of the DMT 420, which could not be corrected before because of the ECC 590. Of course, it goes without saying that the reserved area 554 may be selectively covered by the ECC 590 including other management data of the DMT 420.

The write attribute (WRT) flag 566 is
It identifies whether the corresponding sector is read-only (read only) or rewritable. The write attribute flag 566 has a size of about several bits. On the other hand, the conventional ID data has a size of 7 bytes, but about 20 bits thereof are not used.
66 can also be provided in a conventional structure using such unused portions. The write attribute flag 566 is
If it is identified as read-only, data 640 described later of the corresponding sector becomes read-only and cannot be rewritten. Here, "cannot be rewritten" means that rewriting is not possible when the user uses a normal removable memory drive.For example, the user modifies the removable memory drive, or the same as the manufacturer. It should be noted that rewriting is not always possible even when equipment is used. If the write attribute flag 566 identifies that the sector is rewritable, data 640 described later of the sector is provided to the user in a rewritable manner.

The read attribute (RD) flag 568 identifies whether reading to the corresponding sector is restricted for security. For example, when the read attribute flag 568 is set, the user needs to input security data such as a password and / or a user name to read the data 640 of the corresponding sector.

In the present embodiment, the reserved area 578 is
This area is reserved for future use. EDC
580 and ECC 590 are the same as EDC 126 and ECC 590, respectively, and a description thereof will be omitted.

According to the removable memory 400 of this embodiment, by providing the ZMS 500 instead of the conventional independent ID section, the capacity related to the ID can be reduced by 26%. When the ZMS 500 is redundantly provided for the expanded capacity because it does not have an independent ID section, for example, the data area 540 is configured to have the sector information of the tracks before and after the corresponding track in the sector information 550. be able to. Such a triple structure not only greatly improves reliability but also contributes to securing high-speed access.

The DS 600, like the ZMS 500, has a sector mark (Sector Mark) 610 and a data (Data) section 620, and has an independent ID.
Parts are not included. The sector mark 610 indicates the data part 6
20 is a trigger for hardware (for example, a PLL circuit) included in the drive 800 for recognizing 20.

[0086] The data section 620 includes, as shown in FIG.
Data preamble (Data Preamble) 6
22, a data synchronizing unit 624, a field type code (Field Type Code: FTC) 626,
ID data 628, resynchronization unit 630, data area 6
40, a data EDC 650, and a data ECC 660. The data preamble 622 is the same as the data preamble 522, and the data synchronization unit 624 is the same as the data synchronization unit 524. FTC
626 indicates that the information to be read is DS600.
This is a code for identifying that the ID
The data 628 and the resynchronization unit 630
The description is omitted because it is the same as that of the resynchronization unit 530.
Since the data area 640 is the same as the user data 122 and 124, the description is omitted. EDC650 and EC
C660 is the same as EDC580 and ECC590, and a description thereof will be omitted.

Instead of the ZMS 500 of the present invention, ZMS
Track management sector (Track Management sector) provided for each track having the same information as
t Sector (TMS) may be provided. Also, D
A part or all of the information of the ZMS 500 may be stored in the MT 420. The case where a part of the information of the ZMS 500 is stored in the DMT 420 is, for example, the case where the DMT 420 stores the information on the number of operable sectors of each track and the number of offsets from the reference address of each sector. In this case, when calculating the address of the target sector described later, the DMT
Both 420 and ZMS 500 will be referenced.
When all information of the ZMS 500 is stored in the DMT 420, only the DMT 420 is referred to when calculating the address of a target sector described later. In this case, since information of all tracks and sectors must be stored in the memory, a large-capacity memory is required, but high-speed access to the target sector can be expected.

Next, a description will be given of a sector address calculation method as an exemplary embodiment of the present invention. According to the method of the present invention, the address (LBA) of the target sector is A for the start address of the track to which the target sector belongs, B for the number of offsets from the start address, and the removable memory 4.
Assuming that the total number of operable sectors included from the first track of 00 to the track immediately before the track to which the target sector belongs is C, A and C are equal, so LBA is calculated by the following equation.

(Equation 1)

Instead of storing the start address of each track, the method of the present invention calculates the total number of operable sectors included from the first track of the removable memory 400 to the track immediately before the track to which the target sector belongs. By doing so, the amount of information to be stored is reduced.

Here, the number of operable sectors can be considered as the number of sectors to which an LBA is attached in each track. Hereinafter, a DMT using the conventional PDL method with respect to the number of operating sectors and a DMT as one exemplary embodiment of the present invention storing all or a part of ZMS information
Consider the processing performed by For example, if the total number of sectors included in each track is 100 and the sector 10 included in the track 0 is a primary defective sector, the conventional D
MT writes sector 10 as PDL, but DMT 420 of the present invention writes 99 to track 0. Therefore, it is understood that the number of operable sectors is not displayed in the case of the conventional DMT. DMT42
If 0 stores a part of the information of ZMS 500, ZMS
The 500 operable / defect flag 562 indicates "F" indicating a defect.
F ”is displayed, and the DMT 420 displays the ZMS 50
If all the information of 0 is stored, the sector 10 and the FF are stored in the DMT 420 in association with each other.

Hereinafter, a schematic configuration of a removable memory drive 800 as an exemplary embodiment of the present invention which is compatible with the removable memory 400 will be described with reference to FIG. Here, FIG. 11 is a schematic block diagram of the removable memory drive 800. In this embodiment, the removable memory drive 800 is configured as a magnetic disk drive connected to an external device 900 embodied as a personal computer.
10, a memory 820, a head 830, and a signal processing device 840. In addition, the drive 800
Input means such as buttons and a keyboard (not shown) and display means such as a liquid crystal display can be provided.

The control section 810 controls the operation of the head 830 and the signal processing device 840 under the control of the firmware stored in the memory 820. Here, “firmware” refers to software stored in the memory 820 regardless of the name. The firmware includes a utility program for formatting the disk 400, a utility program for reading the disk 400, a utility program for writing on the disk 400, and a security program for performing security management.

The utility program and the security program are programs supplied from the manufacturer of the drive 800 or a company entrusted by the manufacturer. According to this embodiment, the user can use the normal format and the security format. The purpose of the security program is to prevent a user who does not have a proper authority from accessing not only the user data but also the disk 100. Details of the firmware processing will be described later.

The head 830 reads out management data, security data and user data of the disk 400 and sends them to the signal processing device 840. However, as will be described later, when the security data is present on the disk 400, the head
Under the control of the control unit 810 according to the firmware stored in the storage unit 0, security data or management data is first extracted, and after performing predetermined processing, access to the user data by the external device 900 is permitted. The security data and the user data are not supplied to the signal processing device 840 at the same time. The signal processing device 840 is connected to the SCSI interface 912 of the external device 900, and can demodulate management data, security data, and user data to extract original information.

The external device 300 includes a PCI bus 310,
SCSI interface 912 and IDE bus 914
, A main memory 920, a control unit 930, a hard disk drive 940, a removable memory drive 950, a removable memory 952, and a display 960. Note that the removable memory 95
2 and 400, removable memory drives 950 and 80
0 may be the same.

The PCI bus 910, the SCSI interface 912, and the IDE interface 914 are well known in the art, so that detailed description is omitted here. The main memory 920 includes, for example, a RAM and a ROM, and a program necessary for the operation of the control unit 930 is temporarily loaded from the hard disk 940 or an input from an input unit (not shown) such as a keyboard, a mouse, and a joystick is provided. It is temporarily stored or stores information necessary for system operation. The control unit 930 controls the operation of each unit, and the hard disk 940 stores an OS such as Windows 98 and other programs (various drivers and the like) necessary for the operation of each unit. The removable memory drive 950 and the removable memory 952 can be used for recording and reproducing user data. The display is composed of, for example, a CRT display. 1 Security management

The security management of the removable memory drive 200 will be described below with reference to FIGS. Here, FIG. 12 is a flowchart illustrating an example of security management of the removable memory drive 800, and FIG. 13 is a flowchart illustrating another example of security management of the removable memory drive 800.

Referring to FIG. 12, when disk 400 is inserted into drive 800, first, control unit 810 causes head 830 to control SMT of DMT 420 according to firmware.
Command to read T430 (step 100)
2) It is determined whether or not the security flag is set (on or not). The control unit 810 controls the disk 40
0 is inserted into the drive 800 to determine whether the disk 400 has been inserted.
The determination can be made by communicating with a detection unit that detects by optical means using D or the like. In the present embodiment, it is assumed that a security flag is set on the disk 400. However, the drive 800 can be used on a disk with no security flag set even after a security format described later and a disk with a normal format set. Can be configured to be compatible. In such a case, control section 810 can execute step 1008, which will be described later, if the security flag is not set (off) or if it is determined that ST430 does not exist.

When the control unit 810 determines that the security flag is set, the control unit 810 shifts to a process called “Check Condition”. The check condition is an error code from the drive 800 when there is a flag. When this error occurs, the drive 800 itself or in cooperation with the external device 900 requests the user to input a password (step 1004). The password request to the user can be displayed on the display 960 or by using a liquid crystal display, a speaker, or other output means provided in the drive 800. Further, it is not necessary to directly express such a fact such as a red lamp or a warning sound. In response, the user inputs a password using an input device such as a button provided on the drive 800 or an input unit (keyboard, mouse, etc.) (not shown) connected to the external device 900. The control unit 810 may prompt input of additional data together with a password according to the security level. At this time, even if a malicious person with specialized knowledge attempts to release security by accessing the disk 400 using a command or the like, if the correct password cannot be input by the mode sense, mode selector, etc., the disk 400 itself can be accessed as described later. become unable.

Next, control section 810 determines whether or not the security data stored in advance in the security code of ST430 matches the password input by the user (step 1006). Note that “match” does not require that the password and the security code be completely the same. For example, security codes may be a list of allowed passwords. In that case, it is sufficient to enter one of the passwords listed in the table. If necessary, the security level may be changed for each user data, and a plurality of passwords may be requested for data having a high security level. If the control unit 810 determines that the security data and the password match, the DMT4 of the DMA 410
20 is read out, the management data is reproduced by the signal processing device 840, and then transmitted to the external device 900 via the SCSI interface 912 (step 1008). As a result, the external device 900 can access the disk 400 to record and reproduce user data.

On the other hand, if the control unit 810 determines that there is a mismatch, it prompts the user to re-enter the password, and if the password does not match within the predetermined number of times, or if it determines that there is a mismatch, the disc 400 is automatically ejected. (Step 10
10). More specifically, when the head 830 fails to read the security data successfully, when the read security data cannot be understood, and when the password input by the user is incorrect, error processing is performed. In the case of error processing, the fact is displayed on the display 960 to retry, but in any case, the signal processing device 940 cannot reproduce the user data in the error processing. Thus, it is possible to prevent the user data from leaking to the outside.

If the error is determined, the control unit 810 ejects the disk 400. The control unit 810 can immediately determine the error and eject the disk 400 even if the disk 400 for which the password has failed to be input a predetermined number of times is input to the drive 800 again. As a result, no information about the disk 400 is transmitted from the drive 800 to the external device 900.
Even the existence of 0 cannot be recognized.

Alternatively, as shown in FIG. 13, the management area may be read first (step 1012), and then steps 1002 to 1004 may be performed. After that, if the control unit 810 determines that they match, the control unit 810 reproduces the management data already read out by the signal processing device 840 and then controls the external device 900.
Via the SCSI interface 912 (step 1014). As a result, the external device 900 can access the disk 400 to record and reproduce user data. When the steps 1012 and 1014 are adopted, the read management data is stored in the memory 820.
It will be temporarily stored in other storage units.

According to the security management method as an exemplary aspect of the present invention, the security data is stored in the external device 9.
00 is managed by the firmware of the drive 800, not by the OS stored in the hard disk 940.
That is, the external device 900 cannot access the removable memory 400 unless the control unit 810 determines that the security data and the password match. Accessibility of the external device 900 to the removable memory 400 is determined without intervention of the OS of the external device 900. Since the firmware of the removable memory drive 800 can only be understood by a person who has expert knowledge unless it is a designer of the drive 800, the confidentiality of the user data can be enhanced as compared with the security management method using the conventional OS. . 2 Security format

Next, with reference to FIG. 14, a security formatting method as an exemplary embodiment of the present invention will be described. Here, FIG. 14 shows the removable memory drive 8
00 performs the security formatting method (ie,
21 is a flowchart showing a format method for forming ST430). First, the user drives 800
Insert an unformatted or already formatted disc 400 into the disc. In response, control unit 810 prompts the user to select a format format in the same manner as in step 1004 (step 1102).

When a disk that has already been formatted is inserted, the user can use an input device such as a button provided on the drive 800 or an external device 900.
A format process is selected using input means (keyboard, mouse, etc.) (not shown) connected to. A normal OS (for example, Windows (registered trademark) 9)
If the data is formatted according to 8), the user will desire a security format in step 1104 described later. If the security format has already been performed, step 1
At 104, the user will want the normal format. If the security format has already been done, the user executes the processing shown in FIG. 12 or FIG.
It is necessary to secure access to the removable memory 400 by the external device 900. Changing the format usually involves erasing the user data. For example, it can be used as a normal non-security disk by converting it to meaningless data such as EE. However, alternatively, only DMT 420 could be changed without erasing the user data.

Next, control unit 810 determines whether the format input by the user is a normal format or a security format (step 1104). Here, the “security format” refers to the S format shown in FIG.
It refers to a physical format that forms T430. If the user selects a normal format (including the quick format) (step 1104), a management area and a data area are set by a known format method, and a DMT not including ST430 is formed in the management area 410 (step 1104). 1106).

On the other hand, if the user selects a security format (step 1104), control unit 810 sets
The management area 410 and the data area 440 are set, and the DMT 420 including the ST 430 is formed in the management area 410 (step 1108). As a result, the disk 400 becomes a logical security disk. It should be noted that ST 430 may be formed in data area 440 as described above. Next, the control unit 8
10 sets a security flag (step 111)
0). More specifically, even if the security format is selected, the user can enter the password in step 111 described later.
If no input is made in step 2, it is possible to consider that the format is substantially the same as a normal format and not to set a security flag. The fact that the user did not enter the password can be determined by the password length. Alternatively, the security flag may be set in any case, requiring a password in the security format.

Next, the control unit 810 inputs a password and other optional data required for the user (for example, setting of security level, necessity of encryption, type of encryption to be used, necessity of biometric data, etc.). Is required (step 1112), and when there is an input, the additional data (user name, company name, telephone number, etc.) and the necessity of authentication from an external certification organization are prompted. For example, well-known cryptographic protocols can be involved in security data. For example, data stored in a removable memory drive is transmitted online (eg, via the Internet or a commercial online line), and a digital signature and a public / private key are used.

The removable memory 400 having been subjected to the security format as described above can be driven only by the dedicated removable memory drive 800 which can support the security format. Therefore, even if the removable memory 400 is stolen, the stealer cannot obtain the data stored in the stealer unless the stealer has the dedicated removable memory drive 800, so that the confidentiality of the user data is improved.

Although not shown in FIG. 14, the user can change the password once set. Further, when a password has been forgotten, it is also possible to invalidate a previously input password under predetermined conditions.

The drive 800 can perform not only reproduction of the disk 400 but also recording. If the disk 400 is of a rewritable type, the user can add desired data to previous user data. The disc 400 and the drive 800 may selectively input and collate additional information during recording to increase the confidentiality compared to when reproducing. Thus, for example, it is possible to prevent the distribution of the disc 400 in which part of the information has been rewritten to incorrect information. Since only the user whose access is permitted and authenticated can record the user data, it is possible to prevent the previously recorded user data from being changed unprotected. The removable memory 400 can be used for, for example, an electronic medical record for each patient in a hospital, insured data of an insurance company, business activity data of a company, a management ledger of a public organization, and the like. 3 Selection of ID format

Next, the present invention provides, as an exemplary embodiment,
D format method can be selected. The selection of the ID format method includes forming a format having the ZMS 500, forming a format having a DMT storing all or a part of the information, forming a format having a TMS, or using a conventional independent ID.
Means that a format having a section is formed.

This can be considered similarly to the security format shown in FIG. In addition, since the selection of the ID format can be performed independently of the security format, it can be considered that the selection follows the steps 1106 and 1112, and can be performed in a format having no selection of the security format. In these cases, similarly,
The control unit 810 prompts the user to select an ID format format, and the user uses an input device such as a button provided on the drive 800 or an input unit (keyboard, mouse, etc.) (not shown) connected to the external device 900. And select the format process. 4 Reading method

Next, referring to FIG. 15, the TM of the present invention will be described.
A method for reading the removable memory 400 having S, ZMS, and / or DMT will be described. Here, FIG. 15 is a flowchart showing a reading method executed by the removable memory drive 800. The reading method according to an exemplary embodiment of the present invention is stored in the memory 820 of the drive 800 as firmware.

First, the drive 800 receives the address LBA of the target sector from the OS of the external device 900 (Step 1202). Now, assume that the address is 903. Next, the control unit 810 of the drive 800 calculates which track of which zone the address belongs to (step 1204). The control unit 810 includes:
Based on the number of operable sectors and the number of offsets of each track stored in the TMS, ZMS 500 and / or DMT 420, the zone number and the track number are calculated according to the above-described sector address calculation method. For example, if each zone is 3
If there are two tracks and each track has 100 sectors, track number 0 of zone number 0
If there are no defective sectors in the control units 810 to 8, the control unit 810
Recognizes that the target sector (target address) is located at track number 9 in zone 0, and that the target sector has an offset number of 3 from the start address of track 9.

Note that when the DMT 420 inserts the removable memory 400 into the drive 800, the DMT 420 first
Since 0 is a place to be read, ZMS5 is added to DMT420.
When all of the information of 00 are stored, the control unit 81
In the case of 0, the zone number and the track number can be calculated immediately in step 1204. However, in that case, the drive 800 will need a large-capacity RAM for temporarily storing the contents of the DMT 420. But T
If the MS, the ZMS 500, or the DMT storing a part of the information of the ZMS 500 is provided, step 12 is executed.
At 04, the head 830 must access the TMS or ZMS 500. This is the same in a writing method described later.

Next, the controller 810 moves the head 830 to the start address (start sector) of the track (target track) to which the target sector belongs (step 1206).
It should be noted that the head 8 is assigned to the zone and track to which the target sector belongs.
Whether or not there is 30 is determined by reading the zone number and the track number included in the ID data 528 of the sector read by the head 830. Then, the head 83
0 is the header of the sector (ie,
By reading the offset number of the sector included in the ID data 628), it is determined whether the current sector is the target sector. For example, if the start sector of the target track, the second, third, and fourth sectors from the start sector are operable sectors, defective sectors, operable sectors, and operable sectors, the sector with LBA = 903 is from the start sector. This is the fourth sector. That is, in this embodiment, the offset number is the offset number from the start sector when the defective sector is excluded from the start sector. (If the start sector is a defective sector, the immediately operable sector may be the start sector. Needless to say). Alternatively, however, the offset number including the defective sector may be used.

When the step 1208 is completed, the head 8
It can be seen that 30 is actually on the sector with LBA = 902, just before reading the sector mark of sector 903. Therefore, when the head 830 reads the sector mark 610 of the sector 903, the user data stored in the data area 640 is read (step 1210). The read user data is reproduced via the signal processing device 840, transmitted to the external device 900 via the SCSI interface 912, and is stored in the removable memory 952.
And so on. 5 Writing method

Next, referring to FIG. 16, the TM of the present invention will be described.
A writing method of the removable memory 400 having S, ZMS, and / or DMT will be described. Here, FIG. 16 is a flowchart showing a writing method executed by the removable memory drive 800. The writing method according to an exemplary embodiment of the present invention is stored in the memory 820 of the drive 800 as firmware.

First, the drive 800 receives, from the OS of the external device 900, the address LBA of the target sector to which predetermined data is to be written (step 1202). Now, assume that the address is 903. Next, the control unit 81
0 calculates the zone number and the track number as described above (step 1204).

Next, the control unit 810 determines the Z of the target track.
MS 500 (or TMS) is mapped. The mapping step is a step of confirming the operability of each sector of the target track. Thereby, the control unit 810 recognizes that, for example, the start sector of the target track, and the second, third, and fourth sectors from the start sector are the operable sector, the operable sector, the defective sector, and the operable sector. . In a write operation, it is necessary to perform a read operation in order to check the operability of each sector in order to write data in an operable sector.

If the operable state of each sector is not known, the head 830 tries to write data to the third sector from the start sector of the target track, and an error operation occurs. On the other hand, in order to avoid this, as a write preparation operation, it is also conceivable to read all the sectors of the target sector once before writing data, confirm the operability thereof, and then start the write operation after returning to the start sector. Can be However, in this case, it is necessary to always read the target track as a preparatory operation during the write operation, and it takes a long time to write.

In order to avoid such a problem, in this embodiment, the ZMS 500 has the sector information 550, and eliminates the need to read all the sectors of the target track by reading the ZMS 500 that manages the target track.

Next, the control unit 810 sets the head 830 to the start address (start sector) of the track to which the target sector belongs.
(Step 1206), and it is determined whether or not the currently accessed sector matches the offset number (step 1208).

When Step 1208 is completed, the head 8
It can be seen that 30 is actually on the sector with LBA = 902, just before reading the sector mark of sector 903. Therefore, when the head 830 reads the sector mark 610 of the sector 903, it writes predetermined user data transmitted from the external device 900 via the SCSI interface 912 into the data area 640 (step 1224).

The preferred embodiments of the present invention have been described above. However, the present invention is not limited to these embodiments, and various modifications and changes can be made without departing from the gist of the present invention.

[0128]

The removable memory according to the present invention can achieve various effects. An exemplary effect of the present invention is that since the ID portion including the ID data is included in the data portion to perform error correction by applying ECC to the ID data, the ID data is lost due to the error and all users in the sector are lost. Prevents data from becoming unavailable. Thereby, the reliability of data is improved.
Also, the resynchronization unit clarifies the position of the error detection code,
This prevents a signal reading position due to an error from reaching an error detection code (and an error correction code).
As a result, the error detection codes (and the error correction codes) can always be operable unless they are broken, thereby improving data reliability. Further, by providing a post-synchronization unit instead of or together with the resynchronization unit, the desired field (for example, I
D field, error detection code and error correction code).

In the present invention, the storage capacity is increased by removing the independent ID section. Further user data may be stored in the expanded capacity to achieve a large capacity, or an error detection code, an error correction code, a ZM
The reliability may be improved by storing S, TMS, or the like.

[Brief description of the drawings]

FIG. 1 is a schematic block diagram showing the format of a sector as a first exemplary aspect of the present invention.

FIG. 2 is a schematic block diagram of an exemplary format structure that can be added to the sector shown in FIG.

FIG. 3 is a schematic block diagram showing a format of a sector as a second exemplary aspect of the present invention.

FIG. 4 is a schematic block diagram showing a format of a sector as a third exemplary aspect of the present invention.

FIG. 5 is a schematic block diagram showing a modification of the ID part of the sector shown in FIG. 3;

FIG. 6 is a plan view of a removable memory as an exemplary embodiment of the present invention embodied as a floppy disk employing an optical servo method.

FIG. 7 is a schematic plan view illustrating a zone structure of the removable memory shown in FIG. 6;

FIG. 8 is a schematic plan view for explaining a zone structure of the removable memory shown in FIG. 6;

FIG. 9 is a block diagram showing a structure of a zone management sector shown in FIG.

FIG. 10 is a block diagram showing a structure of a data sector shown in FIG.

FIG. 11 is a schematic block diagram of a removable memory drive as an exemplary aspect of the present invention.

12 is a flowchart illustrating an example of security management executed by the removable memory drive shown in FIG.

13 is a flowchart illustrating another example of security management performed by the removable memory drive illustrated in FIG.

FIG. 14 is a flowchart illustrating a security formatting method performed by the removable memory drive shown in FIG. 11;

FIG. 15 is a flowchart illustrating a reading method executed by the removable memory drive.

FIG. 16 is a flowchart showing a writing method executed by the removable memory drive.

[Explanation of symbols]

 1 sector 2 sector 3 sector 100 data section 100a data section 100b data section 110 ID 'section 112 ID data 120 Data' section 122 user data 124 resynchronization section 126 error detection code 128 error correction code 130 data synchronization section 132 data mark 140 post Synchronization section 200 Gap 300 ID section 310 ID synchronization section 320 ID mark 330 ID data 340 ID error detection code

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G11B 20/18 570 G11B 20/18 570G 574 574H 21/08 21/08 F F term (Reference) 5D044 AB01 AB05 AB07 BC01 BC02 CC04 DE03 DE12 DE33 DE38 DE48 DE50 DE52 DE64 DE69 DE70 GM03 GM23 HL02 HL08 5D088 PP01 SS14

Claims (57)

[Claims] 1. A removable memory having a plurality of sectors each having a data section, wherein the data section has an ID representing an ID of the corresponding sector.
A removable memory including data, user data that can be recorded and reproduced by a user, and an error correction code capable of correcting both the ID data and the user data. 2. The data section according to claim 1, further comprising: an error detection code for detecting an error in the user data; and an error detection code disposed between the ID data and the error detection code, and functioning as a trigger for reading the error detection code. The removable memory according to claim 1, further comprising a synchronization unit. 3. A removable memory having a plurality of sectors each having a data part, the data part comprising: user data recordable and reproducible by a user; an error detection code for detecting an error in the user data; A removable memory, comprising: an error correction code that is arranged in a predetermined positional relationship from an error detection code to correct an error in the data; and a resynchronizing unit that functions as a trigger for reading the error detection code. 4. A removable memory having a plurality of sectors each having an ID section and a data section, wherein the ID section identifies an ID of the corresponding sector, and wherein the data section stores the ID of the corresponding sector. A removable memory having ID data representing the ID, user data that can be recorded and reproduced by a user, and an error correction code capable of correcting errors in both the ID data and the user data. 5. The removable memory according to claim 4, wherein the ID of the sector is an ID commonly used for reading and writing of the sector. 6. A removable memory having a plurality of sectors each having an ID part and a data part, wherein the ID part identifies an ID of the corresponding sector, and the data part identifies the corresponding sector. A removable memory having a sector address to be represented, user data that can be recorded and reproduced by a user, and an error correction code capable of correcting errors in both the sector address and the user data. 7. The removable memory according to claim 4, wherein said removable memory is a magnetic disk. 8. The removable memory according to claim 4, wherein the data unit further includes an error detection code for detecting an error in the user data, and a resynchronization unit functioning as a trigger for reading the error detection code. 9. The removable memory according to claim 4, wherein the data section further includes a post-synchronization section that functions as a trigger for reading ID data of the data section in the backward direction. 10. The removable memory according to claim 2, wherein the resynchronization unit has a single frequency. 11. A removable memory having a plurality of sectors each having a data portion, the data portion comprising: user data recordable and reproducible by a user; an error detection code for detecting an error in the user data; An error correction code that is arranged in a predetermined positional relationship from the error detection code and that can correct the error of the data, and a post-synchronization unit that functions as a trigger for reading a desired field of the data unit in the reverse direction. Having removable memory. 12. A removable memory having a plurality of sectors each having an ID section and a data section, wherein the ID section detects ID data representing an ID of the corresponding sector, and detects an error in the ID data. A removable memory having an ID error detection code and a post-synchronization unit functioning as a trigger for reading out a desired field of the ID unit in a backward direction, wherein the data unit has user data that can be recorded and reproduced by a user. 13. The removable memory according to claim 9, wherein the post synchronization unit has a single frequency. 14. A removable memory having a plurality of sectors each including a sector mark for identifying a sector and a data portion, wherein the data portion includes ID data for storing an ID of the corresponding sector, and recording and reproduction by a user. Removable memory with possible user data. 15. The removable memory is divided into a plurality of zones each storing the plurality of sectors, each zone has a plurality of tracks, each track has a plurality of sectors, and the ID data is 15. The removable memory according to claim 14, which is provided for each zone. 16. The removable memory is divided into a plurality of zones each storing the plurality of sectors, each zone has a plurality of tracks, each track has a plurality of sectors, and the data section has 17. The removable memory according to claim 16, comprising: a plurality of zone management sectors each managing one track; and a plurality of data sectors each storing the user data. 17. The data section further includes a code for identifying a zone management sector and a data sector.
4. The removable memory according to 4. 18. The removable memory according to claim 16, wherein the plurality of zone management sectors are provided adjacent to each other, and thereafter, the data sectors are provided adjacent to each other. 19. The removable memory according to claim 16, wherein said zone management sector stores front and back information of said removable memory. 20. The removable memory according to claim 16, wherein said zone management sector stores a start address of a corresponding track. 21. The zone management sector stores the number of operable sectors included in a corresponding track.
6. The removable memory according to 6. 22. The removable memory according to claim 16, wherein said zone management sector stores information for managing each sector included in a corresponding track. 23. The removable memory according to claim 14, wherein the removable memory is divided into a plurality of tracks each storing the plurality of sectors, and information for managing the track is provided for each track. 24. The removable memory according to claim 23, wherein the information includes front and back information of the removable memory. 25. The removable memory according to claim 23, wherein said information includes a start address of a corresponding track. 26. The removable memory according to claim 25, wherein the information includes the number of operable sectors included in a corresponding track. 27. The removable memory according to claim 23, wherein the information includes an offset number from a reference address of the sector. 28. The removable memory according to claim 23, wherein said information includes information for managing each sector included in a corresponding track. 29. The removable memory according to claim 14, wherein the removable memory further has a management area inaccessible to a user, and the management area stores front and back information of the removable memory. 30. The removable memory according to claim 14, wherein the removable memory further has a management area inaccessible to a user, and the management area stores a start address of a corresponding track. 31. The removable memory according to claim 14, wherein the removable memory further has a management area inaccessible to a user, and the management area stores the number of operable sectors included in a corresponding track. 32. The removable memory according to claim 16, wherein the removable memory further has a management area inaccessible to a user, and the management area stores an offset number from a reference address of the sector. 33. The removable memory according to claim 14, wherein said removable memory further has a management area inaccessible to a user, and said management area stores information for managing each sector included in a corresponding track. 34. The information for managing the sector,
24. A system according to claim 22, including a sector number of said sector.
4. The removable memory according to claim 3, wherein 35. The information for managing the sector,
34. The removable memory according to any one of claims 22, 28 and 33, wherein the removable memory includes whether the sector is an operable sector or a defective sector. 36. The information for managing the sector,
34. The system according to claim 22, further comprising replacement information of the sector.
The removable memory according to any one of the above. 37. The information for managing the sector,
Further comprising an attribute identifier for identifying whether the corresponding sector is read-only or rewritable; if the attribute identifier identifies read-only, the corresponding user data can be read but cannot be rewritten; 34. The removable memory according to claim 22, wherein the corresponding user data can be rewritten when the attribute identifier identifies that rewriting is possible. 38. The information for managing the sector,
Further including an attribute identifier for identifying whether reading of the corresponding sector is restricted, and inputting predetermined security data for reading the corresponding user data when the attribute identifier identifies that the reading is restricted. 22, 28 and 3 which require
4. The removable memory according to claim 3, wherein 39. The removable memory according to claim 16, wherein said zone management sector is provided redundantly in said removable memory. 40. The removable memory according to claim 16, wherein said zone management sector and said data sector have the same form. 41. The removable memory according to claim 18, wherein said zone management sector also redundantly stores contents of preceding and succeeding zone management sectors. 42. The ID data comprises: a zone number for identifying a zone number; a track number in a zone for identifying a track in the zone; and a sector number for identifying an offset number from a reference address in the track. 17. The removable memory according to claim 16, wherein: 43. The removable memory according to claim 14, further comprising a resynchronization unit as a trigger for identifying user data between the ID data and the user data. 44. The removable memory according to claim 1, wherein the removable memory is a disk-shaped medium. 45. The removable memory according to claim 1, wherein the removable memory is a magnetic disk using an optical servo system. 46. The data section has redundantly an error correction code and / or an error detection code.
The removable memory described. 47. A removable memory, comprising: a plurality of sectors; a management area capable of storing management data relating to the sector and not being rewritable by a user; and an area different from the management area storing at least a part of the management data. Forming the management area, and repairing the management area with reference to the defective sector information stored in an area different from the management area when the management area becomes unreadable. 48. The method according to claim 47, wherein the removable memory further has an error correction code, and wherein the forming step provides an area different from the management area in an area covered by the error correction code. 49. A plurality of tracks each having a plurality of sectors, an area capable of storing the number of operable sectors included in each track and the number of offsets of each sector included in each track from a reference address, Forming ID data for storing an ID in a removable memory, referring to the area when accessing a predetermined sector among the plurality of sectors, and setting an address of the predetermined sector as:
Calculated by the sum of the total number of operable sectors included from the first track to the track immediately before the predetermined track including the predetermined sector, and the offset number of the predetermined sector from the start address of the predetermined track. Address calculation method comprising the steps of: 50. Receiving a predetermined address to be accessed, comprising a plurality of tracks each having a plurality of sectors, the number of operable sectors included in each track, and a reference for each sector included in each track. The number of offsets from the address,
In a removable memory capable of storing ID data for storing the ID of the sector, the total number of operable sectors included from a first track to a track immediately before a predetermined track to which a predetermined sector having the predetermined address belongs is included. A step of specifying the predetermined track by calculating the sum of the predetermined track and the offset number of the predetermined sector from the start address of the predetermined track; and setting a head at the start address of the predetermined track specified by the specifying step. Moving the head; reading the ID of a sector on the predetermined track while moving the head to determine whether the sector is located immediately before the predetermined sector; Reading data stored in the predetermined sector. 51. The removable memory is divided into a plurality of zones each storing the plurality of sectors, each zone has a plurality of tracks, each track has a plurality of sectors, and the specifying step includes: The reading method according to claim 50, wherein a predetermined zone to which the predetermined sector belongs and the predetermined track are specified. 52. Receiving a predetermined address to be accessed, comprising a plurality of tracks each having a plurality of sectors, the number of operable sectors included in each track, and a reference for each sector included in each track. The number of offsets from the address,
In a removable memory capable of storing operability of each sector and ID data for storing the ID of the sector,
A total number of operable sectors included from a first track to a track immediately before a predetermined track to which a predetermined sector having the predetermined address belongs, and an offset number of the predetermined sector from a start address of the predetermined track. Calculating the sum to specify the predetermined track; a mapping step for confirming the operability of each sector of the predetermined track; and a start address of the predetermined track calculated by the specifying step. Moving the head; reading the ID of a sector on the predetermined track while moving the head to determine whether or not the sector is located immediately before the predetermined sector; If the sector is an operable sector, start from the predetermined sector; if the predetermined sector is a defective sector, start from the predetermined sector. Writing predetermined data from the first operable sector after a predetermined sector by the head. 53. The removable memory is divided into a plurality of zones each storing the plurality of sectors, each zone has a plurality of tracks, and each track has a plurality of sectors. 53. The writing method according to claim 52, wherein a predetermined zone to which the predetermined sector belongs and the predetermined track are specified. 54. A plurality of tracks each having a plurality of sectors each including a sector mark for identifying a sector and a data portion, wherein the data portion has an ID of the corresponding sector.
A method of formatting a removable memory so as to have ID data for storing user data and user data recordable and reproducible by a user, comprising: information for managing each of the track and the sector; A step of allowing the user to select whether to divide into a plurality of zones having the same track, to manage each zone, to manage each track, or to manage them collectively; and the management method selected in the selecting step Formatting the removable memory based on the data. 55. A plurality of sectors each including a sector mark for identifying a sector and a data portion, wherein the data portion includes ID data for storing an ID of the corresponding sector, and user data that can be recorded and reproduced by a user. And a removable memory drive for driving the removable memory. 56. It has a plurality of tracks each having a plurality of sectors, and includes the number of operable sectors included in each track, the number of offsets of each sector included in each track from a reference address, and the ID of the sector. A removable memory drive for driving a removable memory capable of storing ID data to be stored, a communication unit with an external device, a head capable of reproducing the removable memory, a head connected to the head and processing an output of the head. And a memory storing firmware for managing a read operation. When a predetermined address to be accessed by the communication unit is received from the external device, the predetermined track is read from the first track of the removable memory. By the track immediately before the predetermined track to which the predetermined sector having the address belongs The signal processing device calculates the total of the total number of operable sectors to be included and the number of offsets of the predetermined sector from the start address of the predetermined track to identify the predetermined track, and The signal processing device reads the ID of a sector on the predetermined track to determine whether or not the head is located in the sector immediately before the predetermined sector, and The removable memory drive, wherein the firmware is designed so that the signal processing device reads data stored in the predetermined sector. 57. A plurality of tracks each having a plurality of sectors, the number of operable sectors included in each track, the number of offsets of each sector included in each track from a reference address, and the ID of the sector. A removable memory drive for driving a removable memory capable of storing ID data to be stored, a communication unit with an external device, a head capable of reproducing the removable memory, and connected to the head to process an output of the head. And a memory storing firmware for managing a write operation. When a predetermined address to be accessed by the communication unit is received from the external device, the predetermined track is read from the first track of the removable memory. By the track immediately before the predetermined track to which the predetermined sector having the address belongs The signal processing device calculates the sum of the total number of operable sectors to be included and the offset number of the predetermined sector from the start address of the predetermined track to identify the predetermined track, and the signal processing device The operability of each sector of the predetermined track is checked, the head moves to the specified start address of the predetermined track, the ID of the sector on the predetermined track is read, and the ID of the predetermined sector is read. The signal processing device determines whether the current sector is in the immediately preceding sector, and starts from the predetermined sector if the predetermined sector is an operable sector, and after the predetermined sector if the predetermined sector is a defective sector. The firmware is designed so that the signal processing device writes predetermined data by the head from the first operable sector of the driver. .