HRT硬盘固件修复软件使用教程.doc

1、转载注明出处：倚浪电脑网程序菜单概述转自：倚浪电脑网 程序菜单如图1所示， HRT就是由这些常用的菜单组成的。一些菜单项（如Test, Info等）在综合工具里有详细的描述，这里只对Maxtor硬盘驱动器的特征作一些必要的补充及说明。如图1. 主程序基本菜单结构图驱动器转储的特性与综合工具里的其它修复程序相比较而言，考虑到当前程序分为两种ATA转储方式，第一种是Reset- ATA，这种方式较为常见，控制驱动器的转储并定义其参数。这种方式也可以在改变驱动器任何特性后再使用等等。同样地相对于其他应用程序, ATA信息转存比较有效的方式有两种.第一种

2、是 (Reset- ATA),如果执行这项操作,程序会对储存器发出一组信息,通过转存结构信息程序可以准确地辨认存储器的缓存和定位储存器的参数.如果转换成功以后就可以针对Maxtor储存器进行其他的测试操作了.无论如何在进行其他测试操作的前提下,读出和定位储存器的详细信息是必需的.如果储存器信息转存操作失败. (描述如下),在任何情况下程序读取存储器细节结构文件的前提都不允许这种错误出现的.然而它是必要的,调和过程是在和之间的.如果要在菜单上进行新的操作就必需执行(Reset- Universal) .如果选择了这项操作程序就会向储存器发出一个简单的复位信号,在这种复位状态下程序是不会读取储存器

3、的详细参数的.版本的一些组成特征Maxtor公司生产的储存器里面有很重要的微程序版本信息, 而且它们之间都有一些相同的代码.因此我们可以通过这些代码把他们的微程序版本信息分成两部分. 第一部分是在一定条件下控制和管理只读存储器(ROM)芯片工作的程序.第二部分是微程序识别储存器型号和版本信息的程序.,在工作窗口里我们将看到储存器的重要信息.例如, 主窗口如下：如图2. 系列代码由两部分组成如果查看只读存储器（其内容保存于CP00）并在它的末尾就会看到有两个字节为CF E7: 如图3. 红色部分是储存器设定在某些条件下唯一读取的代码因此在微代码中它的值及储存器代码总是固定的，而不需要修改的。这样

4、就可以利用这个值来判断微代码版本、资源文件是否兼容。固件概念只读存储器作为只读存储器，它很是令人惊讶，共由四个部分组成，两个是真正的物理存储器，另两个只是只读存储器镜像文件，它们是用来替代基本的只读存储器。第一部分只读存储器被固化在微处理器内部，第二部分是FLASH或NVRAM被焊接在驱动器的PCB电路板上，第三部分及第四部分是基本模块保存在驱动器的伺服区，它们的作用就是在驱动器初始时取代物理识读存储器。如图4. 各种微代码资源从下面内容可以知道，当您对驱动器的只读存储器操作时，您应当对驱动器的只读存储器的工作原理有一个充分的了解。如果NVRAM没有焊接在PCB电路板上，那么可直接对它进行访问

5、，虽然有时它直接固化在封装的微处理器内部。第二部分物理只读存储器是安全模式只读存储器，只有当您对驱动器将要替换不同版本的固件时才需要用着，这种镜只读存储器只是用来做工厂测试用的。如果对只读存储器执行不正确的写操作，驱动器就会不能撤消这种操作了，而进入了一种“挂”的状态。因此在对只读存储器进行写操作时，要用permanent模式才是最恰当的。配置页根据Maxtor驱动器伺服区的一些特征，固件只有三种形式：伺服区、 配置页、只读存储器。 它们本身不是这么划分的，但是为了操作方便，HRT程序将它们进行了单独的分类，而不只是伺服模块部分了，您可以通过CP操作对话框对它们进行操作。有关CP00 驱动器只

6、读存储器模块就是基本这种思想而设计的，它在Temp及Perm模式，仅仅是用来进行读取操作的，为了使ROM在储存器工作时不受损害的基础上，专门设定的一种模式。它只能在Unlock模式，可能才会写入，在对cp操作中cp00是为了让你能够读取储存器后面的程序.其他的 配置页 是覆盖的. 我们都可以对它们执行读出和写入的操作.CP00是特意放在列表的末端，原因是对它的处理很特殊.见图. 5. CP00位于列表的末端，它的操作方法不是两个而是三个伺服模块对于模板的特性服务区域Maxtor硬盘列入某种程度同样的结构中，某些模板是含有标题的，而有些是没有的。还有一些模板的检测数据被看作是所有的，还有一些是没

7、有意义的部分。在单独的模板中，总得来说有一些检测数据。但是特殊的话是没有的。搜索一下模板的数据就可以得出，整个服务区或者没有，或者是不允的。浏览标题的规则/模板检测数据参考DMP8(N40P)硬盘,如下:CRCB BLOCK-1 CRC -1 NON ZERO PARTSM SMART, 1-BYTES STANDARD CRC=N40P=37 U_LIST B1F GMAP B78 RZ_TBL B18 AT_PDL -121 RCT B1E SRV B1A SECU B2F SMART SM30 SMART SM63 SMART SM41 SMART SM22 ATAF B34 ARREH

8、 1ST SECTOR = B, OTHERS - B-PER-EACH-SECTOR1D DMCS B1B AT_POL B64 MAXATG SM5E EVTLG 1ST SECTOR = NO CRC, OTHERS - B-PER-EACH-SECTOR7B FW B39 DISKWARE 0 CODE, B38 OVERLAY 0 CODE, EACH PART = B4F OVERLAY 1 CODE, EACH PART = B97 DISKWARE 1 CODE, B96 OVERLAY 2 CODE, EACH PART = B98 OVERLAY 3 CODE, EACH

9、PART = B图. 6. 是储存器的结构表But fortunately, typical malfunction of stores Maxtor - operatively enough to reveal and remove rather simply. It is enough to sort modules by name and to thumb through them up to the letter N. All modules, as a rule, begin with NO. If she is - means it is necessary to make aut

10、omatic, or manual . If is not present - to understand with the list of modules all details. Some words about modules of defects - sheetsMaxtor驱动器缺陷表基本模块是HLUTL/HUSR，以编译器模块为基础，像AT_PDL、 AT_POL、DMCS、ULIST、ULIST 伺服缺陷表、AT_PDL 服务区和工作区的缺陷列表, 它是通过工厂测试后生成的(P-list),但是也可以通过模块AT_POL把缺陷转换进去. AT_POL 缺陷增长表(G-list),

11、 当储存器出现缺陷扇区的时候可以通过普通软件把缺陷加进缺陷增长表. 因此HRT可以对HUSR进行操作, and all other modules can be received at submission of a command of recalculation of the compiler. At Maxtor corrects contents of modules of the compiler, sometimes spoiling it. Therefore at it is possible to copy all modules AT_PDL, AT_POL, DMCS,

12、RZTBL, ULIST, and then to execute a command of recalculation of the compiler.Distinction of the same modules on different Copies on different are not identical. Therefore in the program for the modules laying on different it will be compulsorily modified ID. For example, different copies of the same

13、 module can have ID0044, ID4044, ID8044, IDC044. The given fact creates problems for display of the name of modules in a field what is it which easily are solved through commenting of modules not on their identifier, and on coordinates on which the given modules settle down. More in detail about dif

14、ferences of the mechanism of commenting of modules it will be told in the section devoted to files.非常重要的提示注意! COPY MODULES OF SERVICE AREA FROM RESOURCES ONLY AS A LAST RESORT! FIRST TRY TO COLLECT THE NATIVE MODULE FROM SEVERAL COPIES AND APPLY OTHER REGENERATIVE MEASURES AND ONLY AT EXTREME NEED,

15、USE FILES WITH RESOURCES! RECORD OF ANOTHERS MODULES OF SERVICE AREA CAN IRREVOCABLY DESTROY THE STORE!全部伺服区伺服区完全的操作是使用UBA方式进行的， In the program the following assumption is accepted：如果在读取/写入 record on physics the cylinder is equal a minus to one number of sector sets number UBA. 磁头号就会显示真正的物理磁头，相对对的驱动

16、器操作概念假物理磁头（它的起始编号总是0），stores Maxtor work with truly physical . And it means, that the card in dialogue for work on physical parameters ceases to be simple formality and starts to work on the direct purpose（由下图结果可以发现，在0位置显示有一个3号磁头），磁头分布表在具体驱动器在初始化时，程序自动定义的。如图7. 柱面总是等于-1，磁头分布表不只是一种形式Alternative servic

17、e areaFeature of stores Maxtor on Poker/Ardent the processor is that at them is present two service areas. The first is basic area which is used at work of the store, the second, is initially latent from the user and used only at creation of the store at a factory.If the store does not have problems

18、 in the basic service area alternative thus it is inaccessible, but here if suddenly in the basic area have been spoiled - modules the store itself is thrown out in alternative area. Thus it will work completely in a service mode, i.e. with service area, but to not work at all “ on logic ”. such sto

19、res it is identical , stores, but it is necessary to be made from Safe Mode. Thus it is necessary to use that way at which the store will not be anything from disks.Mach FirmwareAt modern stores, it is important to guess the correct version of service area. As against old stores ATHENA, it to make n

20、ot so it is simple. However, it is possible to not guess the version, and to pick up her, touching all possible variants. For this purpose item Service- Mach Firmware is entered. After his choice, on the screen the following dialogue will appear:如图8. Dialogue Mach FirmwareChoose subdirectory in whic

21、h touched resources in format CPS are located and press the button start. In a grey line touched files will start to be displayed. If after the termination burns light-emitting diode ERR, the store means has rejected all variants offered to it. If the message submitted below has appeared, the store

22、that resource which name is displayed in a grey line means has accepted. Remember it. Resources of this version can be used for work with the given concrete store.如图 9. An attribute of successfully picked up version更新 FlashFunction Update Flash causes a standard ATA-command of updating of a microcod

23、e. According to the standard, updating with a code 1 - time (in the RAM), with a code 7 - constant (with record on disks). As the store will process inquiry with a code 7 - depends on circuitry of the store (depending on a version, -memory can be stitched, it can not be stitched, and can be - in the

24、 store is used not -memory, and the READ-ONLY STORAGE). First of all, item Actions- Update Flash- With code 1 is used for operation the store.然而需要考虑的是，现代Maxtor驱动器有一个奇怪的现象：需要了解作为微代码称之为DISKWARE - the module pseudo the READ-ONLY STORAGE which is stored on a surface of a disk in a service zone (对于N40P系列

25、，例如它将会是ID39) and after start of the store in memory and management is transferred it. Actually, primary initialization of the store, start, base service modules and loading diskware in memory is carried out -. It is a small code on the size which is stored either in a flash-microcircuit, or in inter

26、nal flash-rom the processor. It as can be updated and rewritten, but in 99 % of cases in it there is no necessity.In practice a great variety of versions - on modern families of stores Maxtor has been established and looked through implicit while dependence in compatibility of various versions - and

27、 a base microcode on a disk.如图10. Typical codes of an insertion of the READ-ONLY STORAGE初始化系统变量 stores Maxtor it is necessary to attribute that strange fact to features, that the ambassador all necessary , they start to read service area without any problems, and here write - with displacement. Disp

28、lacement - not constant. For different UBA it variously. Therefore if the store, having filled it and there and then to rush to restore service area anything good from this will not leave. You can jam either restored modules, or their neighbours. To result displacement of record in norm, it is neces

29、sary to choose item of menu Actions- Reinit Variables. If the store will not give out a mistake, all means has passed successfully, and it it will be fine to read and write. If light-emitting diode ERR has lit up, means, most likely, you have filled or an image of the READ-ONLY STORAGE, or , incompa

30、tible with the microprogram of the current payment.重运算地址译码器To count the compiler (to take into account the defects brought both in P, and in G-LIST, having united them only in P-List), choose item of menu Actions- Misc- Merge G- P. At successful performance of a command, the store will independently

31、 clear module AT_POL.Change of a configuration of the storeTo change the current adjustments of the store, choose item of menu Actions- Misc- Configuration. Thus, on the screen the following dialogue will be given:如图11. Change of a configuration of the storeThe special attention should be turned on

32、item Security Set Supported. If the given tag is reset, the store will reject operation Actions- Quick Clear as she is carried out just on the basis of subsystem Security. But no mean virus can your store.Clearing SMARTTo clear attributes SMART, choose item Actions- Misc- Clear SMART and EL. Thus, t

33、he store will execute clearing not only clearing of attributes and threshold values, but also will clear sector of magazine of mistakes (module EVTLG_00).Record on one sectorSome stores after operation start to hang at work with modules of service area if to read them entirely. If reading and record

34、 go on one sector no problems arise. For such stores in the program it is possible to include mode Options- Write Spec Area by 1 sec. If about the given item there is a tick, the mode means is included.Ignoring of single mistakes of modulesFrequently there is a necessity to subtract the module entir

35、ely, despite of defective sectors contained in it. For this purpose it is possible to take advantage of item Options- Ignore single errors. Thus, sectors of the module which did not manage to be read, will be filled in the final buffer with the signature “ BAD! ”. From the point of view of the user

36、of the utility, the similar opportunity allows to restore in most cases in part damaged module with the minimal expenses on time.储存器典型的故障Typical malfunction of stores Maxtor - . If the store feels, that at him something not so (the defect - sheet, repeated mistakes in the same place was overflew and

37、 .), it automatically modifies heading of one of modules of service area. At the following start, store ATHENA it will not be simple to be defined, at more modern stores - at the end of the version of the microprogram the symbol Z will appear. Presumably, developers have deliberately made this featu

38、re whenever possible to keep the information on the store leaving out of operation. Means of OS with such disk already to make nothing, so, the information will be kept with the greater probability. the store it is possible to count more serious case a condition when - the store it was not possible

39、to execute correct start and-or initialization of the service modules necessary for the further work, and start diskware. Such mode can be named safe-mode and, usually, his opportunities of the store by way of work on the ATA-interface are very strongly limited. In this case, the store will be defin

40、ed with a name of family instead of model and the version - as the version . For example, for store N40P it will look so:In this case it is possible to recommend some times to make the store a feed since at Maxtor there is a specific feature periodically astably to read service area, or to try loadi

41、ng flash (cp0) in mode TEMP with the subsequent loading other pages (cpXX) and the store through ATA- Reset.Unfortunately, in most cases, start of the store at unsuccessful start in safe-mode speaks that the service area is strongly damaged. Restoration of such store probably in rare cases also dema

42、nds an individual approach.储存器ATHENA and Romulus的操作步骤对于ATHENA储存器来说,典型的操作可以表示为如下步骤:1) 将驱动器的跳线模式设置为下列位置：如图12. ATHENA, Romulus驱动器系列安全模式跳线设置在修复过程中不是100%一定需要跳安全模式的.有时候没有他也可以的。但是还有一种情况就是，在储存器排斥所有的基本操作的情况下.那怎么办呢?储存器的初始化与磁盘的什么地方有关联，是我们难以估计的.但是如果存储器一开始就调用安全跳线模式的话。那么以上的问题就不会发生了,在存储器开始工作，又停止转动的情况下.(附带的端口在表面)，调

43、用安全跳线的模式，就可以对它进行有效的操作2) 给储存器提供电源3) 选择菜单项 Actions- Update Flash- With Code 14) (作为文件)在电脑找出任意微程序版本，此微程序的程序版本是和硬盘驱动器表面上所标示的版本是一致的。5) 选择菜单项 Reset- Universal6) 选择菜单上的按钮Service-CP Operations，把startup ROM以及这个文件里面的所有tag file页都roll in。把所有的页面都移进Temp里.7) 选择菜单项 Reset- ATA8) 选择菜单上的按钮Actions-Reinit Variables.如果在这

44、个过程中，没有出现错误，意味着你成功地选择了匹配的程序，步骤就可以忽略了。9) 选择菜单项 Service- CP Operations10) 选择 CPO，进入dump，来到dump的结尾，检查符合条件的KC的程序。11) 选择 Reset- Power Click12) 选择菜单项 Actions- Update Flash- With Code 113) (作为文件)在电脑找出weaving，此weaving是和startup ROM里符合条件的KC相匹配的。(看选项“verson”).14) 选择菜单项 Reset- Universal15) 选择菜单项service-CP Opera

45、tions,装载配置参照成套的装置,及ROM，将所有的页面转到temp状态。16) 选择菜单项 Reset- ATA17) 选择菜单项 Actions- Reinit Variables.至此应该不会有错误.重点注意 通过执行actions-reinit Variables ，是对于存储器必须的。如果没有选择他的话，刚才所有操作都有可能读与写在两个完全不同的扇区上。After performance of the specified actions, the store also can be passed to editing the service area described below

46、.储存器 FB3, DMP8, DMP9 的操作步骤For given stores SAFE position of the crosspiece the following:如图13. FB3, DMP8, DMP9驱动器系列安全模式跳线设置通常, Flash for the given stores it is not necessary. It is possible even to try to take advantage of function Service-described earlier Mach Firmware. In some cases, after this o

47、peration, the store will leave for an operating condition and will allow to carry out editing of modules.However, some stores after such operation will hang. In this case, it is possible to try to make the following sequence of actions:1)在CP操作对话框中选择载入CPS文件2)选择最下面的Unlock模式3)按send All按钮，在Unlock模式下将会只剩

48、下CP27、CP28及CP00.4) 储存器执行 (Reset- Usual)5)在Temp模式下载入所有配置页， 在这个状态下加载所有CP, 除CP00以外.If also it will not help, it is necessary to connect intuition and to try to pick up any working combination from earlier described methods.内存，复位驱动器的资源对于DMP8及DMP9驱动器的其它固件资源，建议保存它的内存镜像。例如当驱动器的所有配置页（事实上它是一个微程序，and program

49、），command Rein it Variables is sent, but nevertheless, the store instead of a card 2, 3 gives a card 3, 255. Besides, attempts of work with the head 2 lead to to a mistake. 这样, will help before the kept image of the RAM with subsequent submission ATA Reset. To keep the area of memory from 0 address

50、in length 0x 1D8000 byte follows.如图14. 内存镜像 重要的资源文件编辑模块After the store , it is necessary to remove the reason . For this purpose it is necessary enter dialogue Service- Special Area- Structure and in it to choose I/O- Read All Blocks.常常需要对以下部分模块进行编辑：模块 a nameATPDL 0NO_PLISTATPOL 1NO_GLISTULIST00NO_U

51、LISTULIST00 (in the beginning of the list)ULIST01DMCS 1NO_DMCS显然，大多数模块开始都处于NO状态，可以通过选择ID下面的复选框来选它们 Service- Special Area.有两种方式可以对它们进行编辑：手工和自动。手工编辑时，需要对它们有一定的了解；在自动编辑时 是利用了一个INI初始化文件。对于自动编辑，在work with service area对话框中，选择菜单Maxtor- Repair All Headers。这样就会检查所有的模块头，如果在If the heading is found in section U

52、NLOCK a file Maxtor.ini it will be modified, according to a rule from given a file then for him the control sum will be automatically counted. At those modules which have undergone to automatic editing, allocation remain, at other - will disappear. You can keep on a disk or all modified modules, or

53、what will consider necessary.如图15. After automatic editing modules, are allocated only modified伺服缺陷在伺服区(SA)存储着驱动器许多重要的代码程序及模块，如果伺服区出现了一些未能读取的坏扇区（缺陷），那么驱动将可能不能正常工作，多数情况下是根本不能工作的。为了对伺服区进行存取，Maxtor驱动器对其采取了一种逻辑块寻址方式。这种寻址方式与LBA寻址方式很相似，但能适用于伺服区，且对每个磁头都单独运用这种UBA（UNIT BLOCK ADDRESSING）寻址方式。因此对于UBA寻址方式有一种特性可

54、以参考，那就是它的第一伺服柱面是一个负值。与LBA寻址方式一样， in UBA the miss of defective sectors which for 动力 will be worn out in the table of defects of the service area, located in module HLUTL is used. 但是这里有一个很重要的问题在添加缺陷后，对于UBA寻址方式而言，所有的伺服模块都发生了偏移，从而导致驱动器进入了一种非工作状态（不能正常工作）。为了将这些伺服区存储块转换到一种工作状态，这就需要对伺服区的所有与缺陷相关联的模块进行重运算，在此过

55、程中可以返回所有模块记录并查看这种消除偏移的过程。HRT综合工具可以自动对必要的模块及这些模块的记录进行重运算。如前所述可知，在对伺服区进行操作时，这种操作要求很严格，要求计算很精确，一个错误的操作将会导致驱动器立刻进入一种禁止状态。在对伺服区缺陷进行操作之前，有必要对所有伺服模块进行保存操作, 在进入伺服缺陷表时需要等待程序进入就绪状态才能进行操作.如果驱动器的伺服区已经含有缺陷，那么可以这些缺陷添加到伺服缺陷表中。在对伺服缺陷进行操作时，就需要进入这个专门的伺服缺陷表，所有的原缺陷记录及后来发现的缺陷就会记录在这个缺陷表中。在伺服缺陷表中添加缺陷记录时，对保存在P-list 及G-list

56、缺陷表不会有任何的影响。这就像如果对P-list及G-list缺陷表进行操作时，伺服缺陷也是一样没有任何改变。对伺服缺陷的操作可以看作为在对驱动器维修时的最基本的操作，这是因为驱动器在初始化过程中首先要读取这些伺服信息的。因此查找及隐藏伺服缺陷，可以选择菜单 Test- Special Area. 将会出现下列对话框窗口：如图16.伺服区测试首先，需要查找缺陷，可以点击 Test 测试按钮。程序就会UBA方式来查找Search of defects will be carried out with UBA which number is registered in field From sec