API tools faq
paste
Advertisement
genBTC

Seagate Barracuda Terminal Firmware Information BrainDump

genBTC
Jul 3rd, 2018
126
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 35.10 KB | None | 0 0
raw download clone embed print report
  1. F0A2,00,22 -- disables read and write sparing, and enables correction.
  2. F0A2,01,22 -- disables read and write sparing, and disables correction.
  3. F"RWRecoveryFlags",00,22 - @Byte:00A2 disables read sparing, write sparing, and correction.
  4. F"ReadRetries",00,22 - @Byte:00A3 disabling read retries.
  5. F"BGMSFlags",00,22 - @ Byte:011C disables Background Media Scan.
  6. F"PerformanceFlags",043C,22 - @ Byte:056C disables offline sparing and sets DAR_ENABLED = 0.
  7.  
  8.  
  9.  
  10. Regenerated translator (like lba0 bsy fix , m0,2,2,0,0,0,0,22)
  11. V10 will display the P-LIST. (permanent)
  12.  
  13.  
  14. Managed to get the format pass the 000FFF00 sector . Is now at LBA :00149E43 after 1444mins. Command used F3 T>m0,9,2,,,,,22 , works very slow
  15.  
  16. Drives that are from the F3 Arch will not have Self-Scan code on them, like older Seagate drives used to have, so the best that you can do is, using the terminal :
  17.  
  18. 1 - Clear the G-List with F3 T>i4,1,22 command.
  19.  
  20. 2 - Do a full media scan with the F3 T>m0,8,2,,,,,22 command.
  21.  
  22. It will take some hours and this will move the bad sectors into the P-List.
  23.  
  24. 3 - Do a SMART reset under level 1 with F3 1>N1 command.
  25.  
  26. 4 - Then do a full erase and a sector scan under Windows/DOS. You can use MHDD for this.
  27. All data will be lost.
  28.  
  29. with m0,8 it would hang at 5% LBA: 000FFF00
  30. with m0,9 goes past that sector , but didn`t see the format finished cuz AC power went off in the meantime and the UPS gone empty after 20mins :roll:
  31.  
  32. before m0,9 second time i set from Set Retries - DERP (Level 2, 7, A, F 'Y') to 5
  33. Code:
  34. "SetDerpRetries, Y[Mode],[MaxRdRetries],[MaxWrtRetries],[OtcTLevel],[Options]";
  35.  
  36. Code:
  37. 0 - Error Recovery Mode.
  38.  
  39. This parameter specifies the error recovery mode to be used. The following
  40. error recovery modes are available:
  41.  
  42. 0 = Maximum Normal
  43. 1 = Maximum Full
  44. 2 = Default Normal
  45. 3 = Default Full
  46. 4 = Minimum Normal
  47. 5 = Minimum Full
  48. 6 = Simple
  49.  
  50. The Maximum Error Recovery Modes (0 and 1) are typically used for system
  51. information recovery.
  52.  
  53. The Default Error Recovery Modes (2 and 3) are typically used by the native
  54. interface.
  55.  
  56. The Minimum Error Recovery Modes (4 and 5) are typically used for diagnostic
  57. and media certification operations.
  58.  
  59. Level T 'm': Rev 0012.0019, Flash, FormatPartition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],
  60. [MaxEccTLevel],[MaxCertifyTrkRewrites],[ValidKey],[DataPattern]
  61. 1 - Format Options.
  62.  
  63. This parameter is a bit significant value that selects the following options:
  64.  
  65. Bits 31-6: not used
  66.  
  67. Bit 5: Enable SeaCOS XF Space Format. 32
  68.  
  69. Bit 4: Enable Zone Re-format Skipping. 16
  70.  
  71. Bit 3: Enable Event-based Format Logging. 8
  72.  
  73. Bit 2: Disable User Partition Certify. 4
  74.  
  75. Bit 1: Disable User Partition Format. 2
  76.  
  77. Bit 0: Corrupt User Partition Primary Defects. 1
  78.  
  79. This bit is only valid when the User Partition is selected. If this
  80. bit is equal to 1, the primary defective sectors will be corrupted.
  81.  
  82. Type: Unsigned 32-bit value
  83.  
  84. Range: 0 or 0xFFFFFFFF
  85.  
  86. Default: 0 (Enable User partition Certify,
  87. Enable User Partition Format,
  88. Don't Corrupt Primary Defects)
  89. ormat Partition
  90. Availability:
  91. Level T , 'm'
  92.  
  93. Quick Help:
  94. Format Partition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertifyTrkRewrites],[ValidKey],[DataPattern]
  95.  
  96. Description:
  97. This command formats the specified partition.
  98.  
  99.  
  100. Input Parameters:
  101.  
  102. 0 - Partition Number.
  103.  
  104. This parameter specifies the media partition to be formatted.
  105.  
  106. 0 = User Partition
  107. 1 = System Partition
  108. 99 = Set format corrupt state
  109. Type: Unsigned 8-bit value
  110.  
  111. Range: 0 or 1
  112.  
  113. Default: 0
  114.  
  115. 1 - Format Options.
  116.  
  117. This parameter is a bit significant value that selects the following options:
  118.  
  119. Bits 31-5: not used
  120.  
  121. Bit 6: Disable Track Re-write for Data Sync Time-out Errors.
  122.  
  123. If this bit is equal to 1, the the Format Partition command will
  124. not perform track re-write operations for an unrecovered
  125. data sync time-out error.
  126. NOTE: This feature can be enabled or disabled at compile-time. Use
  127. the quick help to determine whether your code supports this feature.
  128.  
  129. Bit 5: Enable SeaCOS XF Space Format.
  130.  
  131. This bit is only valid when the User Partition is selected. If this
  132. bit is equal to 1, the the Format Partition command will only format
  133. SeaCOS Extended File (XF) space.
  134. NOTE: This feature can be enabled or disabled at compile-time. Use
  135. the quick help to determine whether your code supports this feature.
  136.  
  137. Bit 4: Enable Zone Re-format Skipping.
  138.  
  139. If this bit is equal to 1, then the Format Partition command will
  140. enable the zone re-format skipping mode during the format operation.
  141. With this mode enabled, the format operation will not re-format
  142. a zone if grown defects were found in the zone.
  143. NOTE: This feature can be enabled or disabled at compile-time. Use
  144. the quick help to determine whether your code supports this feature.
  145.  
  146. Bit 3: Enable Event-based Format Logging.
  147.  
  148. If this bit is equal to 1, then the Format Partition command will
  149. display information about error events that occur during the format
  150. operation. This information will be displayed as interim status as
  151. these events occur.
  152. NOTE: This feature can be enabled or disabled at compile-time. Use
  153. the quick help to determine whether your code supports this feature.
  154.  
  155. Bit 2: Disable User Partition Certify.
  156.  
  157. This bit is only valid when the User Partition is selected. If this
  158. bit is equal to 1, media certification and defect deallocation will
  159. be disabled.
  160.  
  161. Bit 1: Disable User Partition Format.
  162.  
  163. This bit is only valid when the User Partition is selected. If this
  164. bit is equal to 1, the User Partition sectors will not be written
  165. with a constant data pattern.
  166.  
  167. Bit 0: Corrupt User Partition Primary Defects.
  168.  
  169. This bit is only valid when the User Partition is selected. If this
  170. bit is equal to 1, the primary defective sectors will be corrupted.
  171.  
  172. Type: Unsigned 32-bit value
  173.  
  174. Range: 0 or 0xFFFFFFFF
  175.  
  176. Default: 0 (Enable User partition Certify,
  177. Enable User Partition Format,
  178. Don't Corrupt Primary Defects)
  179.  
  180. 2 - Defect List Options.
  181.  
  182. This parameter is a bit significant value that selects the following options:
  183.  
  184. Bits 31-3: not used
  185.  
  186. Bit 2: Process the Active Error Log.
  187.  
  188. This bit is only valid when the User Partition is selected. If this
  189. bit is equal to 1, the Format Client Defect List will be written with
  190. contents of the Active Error Log and the option to process the Client
  191. Defect List will be enabled. If there is no Active Error Log or there
  192. are no R/W-related entries in the Active Error Log, then this bit will
  193. be ignored.
  194.  
  195. Bit 1: Process Primary Defect Lists.
  196.  
  197. This bit is only valid when the User Partition is selected. If this
  198. bit is equal to 1, the the Primary Defect Lists will be used when
  199. creating the defect list to be used by the format operation.
  200.  
  201. Bit 0: Process Grown Defect Lists.
  202.  
  203. This bit is only valid when the User Partition is selected. If this
  204. bit is equal to 1, the the Grown Defect Lists will be used when
  205. creating the defect list to be used by the format operation.
  206.  
  207. Type: Unsigned 32-bit value
  208.  
  209. Range: 0 or 0xFFFFFFFF
  210.  
  211. Default: 0x00000003 (Process Grown Defect Lists,
  212. Process Primary Defect Lists,
  213. Do not process the Active Error Log)
  214.  
  215. 3 - Maximum Write Retry Count.
  216.  
  217. If this parameter is entered, the maximum write retry count will be set to the
  218. specified value. This parameter is only valid when the User Partition is being
  219. formatted (Parameter 0 is equal to 0). If this parameter is not entered, the
  220. maximum write retry count will not be changed.
  221.  
  222. Type: Unsigned 16-bit value
  223.  
  224. Range: 0 or 0xFFFF
  225.  
  226. Default: None.
  227.  
  228. 4 - Maximum Read Retry Count.
  229.  
  230. If this paremeter is entered, the maximum read retry count will be set to the
  231. specified value. This parameter is only valid when the User Partition is being
  232. formatted (Parameter 0 is equal to 0). If this parameter is not entered, the
  233. maximum read retry count will not be changed.
  234.  
  235. Type: Unsigned 16-bit value
  236.  
  237. Range: 0 or 0xFFFF
  238.  
  239. Default: None.
  240.  
  241. 5 - Max iteration count
  242. If this paremeter is entered, the iteration count will be set to the specified
  243. value. This parameter is only valid when the User Partition is being formatted
  244. (Parameter 0 is equal to 0). If this parameter is not entered, the iteration
  245. count will not be changed.
  246. 5 - Maximum ECC T-Level.
  247.  
  248. If this paremeter is entered, the maximum ECC T-Level will be set to the specified
  249. value. This parameter is only valid when the User Partition is being formatted
  250. (Parameter 0 is equal to 0). If this parameter is not entered, the ECC T-Level
  251. will not be changed.
  252.  
  253. Type: Unsigned 16-bit value
  254.  
  255. Range: 0 or 0xFFFF
  256.  
  257. Default: None.
  258.  
  259. 6 - Track Rewrite During Certify Retry Threshold.
  260.  
  261. If this parameter is entered, it specifies the maximum number of rewrite retries
  262. to be performed during the user partition certification pass.
  263.  
  264. Type: Unsigned 16-bit value
  265.  
  266. Range: 0 or 0xFFFF
  267.  
  268. Default: None. If this parameter is not entered, the default value recommended
  269. by the R/W Firmware will be used.
  270.  
  271. 7 - Valid Command Key.
  272.  
  273. For a User Partition format, this parameter must be equal to 22 Hex. If this
  274. parameter is not equal to 22 Hex, the command will not be executed.
  275.  
  276. For a System Partition format, this parameter must be equal to DD Hex. If this
  277. parameter is not equal to DD Hex, the command will not be executed.
  278.  
  279. Type: Unsigned 8-bit value
  280.  
  281. Range: 0x22 or 0xDD
  282.  
  283. Default: None
  284.  
  285. 8 - Data Pattern For Format.
  286.  
  287. This parameter specifies the data pattern to be used when formatting the specified
  288. partition. If this parameter is not entered, the specified partition will be
  289. formatted with a 0x00000000 data pattern.
  290.  
  291. Type: Unsigned 32-bit value
  292.  
  293. Range: 0 or 0xFFFFFFFF
  294.  
  295. Default: 0x00000000.
  296.  
  297. 9 - Secondary Maximum Write Retry Count.
  298.  
  299. If this parameter is entered, the secondary maximum write retry count will be set
  300. to the specified value. This parameter is only valid if all secondary ER mode
  301. parameters (parameter 9, 10 and 11) are entered. If any of the 3 parameters is
  302. not entered, the secondary ER mode feature is disabled. Note that this usage is
  303. only available if RW_FORMAT_APPLY_SECONDARY_ER_MODE is enabled.
  304.  
  305. Type: Unsigned 16-bit value
  306.  
  307. Range: 0 or 0xFFFF
  308.  
  309. Default: None.
  310.  
  311. 10 - Secondary Maximum Read Retry Count.
  312.  
  313. If this paremeter is entered, the secondary maximum read retry count will be set
  314. to the specified value. This parameter is only valid if all secondary ER mode
  315. parameters (parameter 9, 10 and 11) are entered. If any of the 3 parameters is
  316. not entered, the secondary ER mode feature is disabled. Note that this usage is
  317. only available if RW_FORMAT_APPLY_SECONDARY_ER_MODE is enabled.
  318.  
  319. Type: Unsigned 16-bit value
  320.  
  321. Range: 0 or 0xFFFF
  322.  
  323. Default: None.
  324.  
  325. 11 - Secondary Maximum ECC T-Level.
  326.  
  327. If this paremeter is entered, the secondary maximum ECC T-Level will be set to the
  328. specified value. This parameter is only valid if all secondary ER mode
  329. parameters (parameter 9, 10 and 11) are entered. If any of the 3 parameters is
  330. not entered, the secondary ER mode feature is disabled. Note that this usage is
  331. only available if RW_FORMAT_APPLY_SECONDARY_ER_MODE is enabled.
  332.  
  333. Type: Unsigned 16-bit value
  334.  
  335. Range: 0 or 0xFFFF
  336.  
  337. Default: None.
  338.  
  339.  
  340. Output Data:
  341.  
  342.  
  343. If an error occurred, the following information will be displayed.
  344.  
  345. "DiagError aaaaaaaa"
  346.  
  347. where
  348.  
  349. aaaaaaaa is the Diagnostic Error Code
  350.  
  351. If the error occurred while processing the defect lists, the following additional
  352. information will be displayed.
  353.  
  354. "Process Defect List Error"
  355. "R/W Sense cccccccc, R/W Error dddddddd, List Offset eeeeeeee, List Index ffffffff File Error gggggggg"
  356.  
  357. where
  358.  
  359. cccccccc is the sense status that was returned by the R/W subsystem
  360.  
  361. dddddddd is the error code that was returned by the R/W subsystem
  362.  
  363. eeeeeeee is the byte offset of the defect list entry at which the error occurred
  364.  
  365. ffffffff is the index of the defect list entry at which the error occurred
  366.  
  367. gggggggg is the error code that was returned by the system information manager (SIM)
  368.  
  369. If the error occurred during the format operation, the following additional information
  370. will be displayed.
  371.  
  372. "User Partition Format Failed - Elapsed Time c"
  373. "R/W Sense dddddddd, R/W Error eeeeeeee, File Error ffffffff"
  374. "LBA gggggggg, Cyl iiiiiiii Hd jj, Phy Sec kkk, Wedge llll"
  375.  
  376. where
  377.  
  378. c is the amount of time that has elapsed since the format operation was started
  379.  
  380. dddddddd is the sense status that was returned by the R/W subsystem
  381.  
  382. eeeeeeee is the error code that was returned by the R/W subsystem
  383.  
  384. ffffffff is the error code that was returned by the system information manager (SIM)
  385.  
  386. gggggggg is the R/W block address at which the error occurred
  387.  
  388. iiiiiiii is the R/W cylinder address at which the error occurred
  389.  
  390. jj is the R/W head address at which the error occurred
  391.  
  392. kkk is the physical sector at which the error occurred
  393.  
  394. llll is the wedge no at which the error occurred
  395.  
  396. If no error occurred and the format operation is still in progress, the following
  397. information will be displayed.
  398.  
  399. "Max Wr Retries = cc, Max Rd Retries = dd, Max ECC T-Level = ee, Max Certify Rewrite Retries = ffff"
  400. "User Partition Format gg% complete, Zone hh, Pass ii, LBA jjjjjjjj, ErrCode kkkkkkkk, Elapsed Time l"
  401.  
  402. where
  403.  
  404. cc is the maximum write retry count to be used
  405.  
  406. dd is the maximum read retry count to be used
  407.  
  408. ee is the maximum ECC T-Level to be used
  409.  
  410. ffff is the certify rewrite rety threshold
  411.  
  412. gg is the percent of the format operation that has been completed
  413.  
  414. hh is the data zone that is currently being formatted
  415.  
  416. ii is the number of the current pass through the data zone
  417.  
  418. jjjjjjjj is the last LBA that was formatted
  419.  
  420. kkkkkkkk is the error code that was reported by the R/W subsystem
  421.  
  422. l is the amount of time that has elapsed since the format operation was started
  423.  
  424. If no error occurred and the format operation is still in progress, and the secondary ER mode feature is
  425. enabled, the following information will be displayed.
  426.  
  427. "Secondary ER mode Enabled: 2nd Max Wr Retries = cc, 2nd Max Rd Retries = dd, 2nd Max ECC T-Level = ee"
  428.  
  429. where
  430.  
  431. cc is the secondary maximum write retry count to be used
  432.  
  433. dd is the secondary maximum read retry count to be used
  434.  
  435. ee is the secondary maximum ECC T-Level to be used
  436.  
  437. If no error occurred, the format operation is still in progress, a format event occurs,
  438. and format event reporting is enabled, the following information will be displayed.
  439.  
  440. "Event: Media Write Start, aaa Format, Zone bb, Start Blk cccccccc, Num Sectors dddddddd"
  441.  
  442. or
  443.  
  444. "Event: Write Xfer, Start Blk cccccccc, Len eeeeeeee, Next Blk ffffffff, Erc gggggggg, Stat hh"
  445.  
  446. or
  447.  
  448. "Event: Media Certify Start, New Format, Zone bb, Start Blk cccccccc, Num Sectors dddddddd"
  449.  
  450. or
  451.  
  452. "Event: Certify Xfer, Start Blk cccccccc, Len eeeeeeee, Next Blk ffffffff, Erc gggggggg, Stat hh"
  453.  
  454. or
  455.  
  456. "Event: Unrec Err, LBA iiiiiiii, PBA jjjjjjjj, Erc gggggggg, Trk llll, Hd mm, Sctr nn, Wdg oo, ZnGrp pp, Zn qq, DOS: rr/ss/tt"
  457. "Event: Unrec Err, LBA iiiiiiii, PBA jjjjjjjj, Erc gggggggg, Trk llll, Hd mm, Sctr nn, Wdg oo, Zn qq, DOS: rr/ss/tt"
  458. "Event: Unrec Err, LBA iiiiiiii, PBA jjjjjjjj, Erc gggggggg, Trk llll, Hd mm, Sctr nn, Wdg oo, ZnGrp pp, Zn qq"
  459. "Event: Unrec Err, LBA iiiiiiii, PBA jjjjjjjj, Erc gggggggg, Trk llll, Hd mm, Sctr nn, Wdg oo, Zn qq"
  460.  
  461. NOTES: ZnGrp information is only available on drives supporting VBAR
  462. DOS information is only available on drives supporting Directed Offline Scan
  463.  
  464. or
  465.  
  466. "Event: Cert Trk Rewrite, Retry Blk kkkkkkkk, Len eeeeeeee, Next Blk ffffffff, Erc gggggggg, Stat hh"
  467.  
  468. or
  469.  
  470. "Event: Cert Trk Rewrite Cntr Update, Cnt 0001"
  471.  
  472. where
  473.  
  474. aaa indicates whether this is a "New Format" or a "Reformat"
  475.  
  476. bb is the zone
  477.  
  478. cccccccc is the starting block
  479.  
  480. dddddddd is the number of blocks to be formatted
  481.  
  482. eeeeeeee is the length of the transfer
  483.  
  484. ffffffff is the next starting block
  485.  
  486. gggggggg is the error code that was reported by the R/W subsystem
  487.  
  488. hh is the read/write status
  489.  
  490. iiiiiiii is the logical block address (LBA)
  491.  
  492. jjjjjjjj is the physical block address (PBA)
  493.  
  494. kkkkkkkk is the block which causes the rewrite retry
  495.  
  496. llll is the track on which the error occurred
  497.  
  498. mm is the head on which the error occurred
  499.  
  500. nn is the sector on which the error occurred
  501.  
  502. oo is the wedge on which the error occurred
  503.  
  504. pp is the zone group in which the error occurred
  505.  
  506. qq is the zone in which the error occurred
  507.  
  508. rr is the DOS scan unit associated with the error
  509.  
  510. ss is the DOS relative cylinder in scan unit associated with the error
  511.  
  512. tt is the DOS surface cylinder unit associated with the error
  513.  
  514. If no error occurred, the format operation is still in progress, a format event occurs,
  515. and brief format event reporting is enabled, the following information will be displayed.
  516.  
  517. "Ev LBA/Soft XferLen Zn Trk Hd Sct Wdg PBA ErrCode"
  518.  
  519. NOTES: This is the header for the tabulated output below.
  520.  
  521. "ZW iiiiiii eeeeeeee qq"
  522.  
  523. NOTES: This is zone write start message.
  524.  
  525. "ZR iiiiiii eeeeeeee qq"
  526.  
  527. NOTES: This is zone read start message.
  528.  
  529. "WX iiiiiii eeeeeeee"
  530.  
  531. NOTES: This is write transfer message.
  532.  
  533. "RX iiiiiii eeeeeeee"
  534.  
  535. NOTES: This is read transfer message.
  536.  
  537. "ER iiiiiii eeeeeeee qq llll mm nn oo jjjjjjjj gggggggg"
  538.  
  539. NOTES: This is error details message.
  540.  
  541. "SE uuuuuuu"
  542.  
  543. NOTES: This is soft error message when a read is recovered by track-rewrite.
  544.  
  545. "HE"
  546.  
  547. NOTES: This is hard error message when a sector is deallocated.
  548.  
  549. where
  550.  
  551. iiiiiiii is the logical block address (LBA)
  552.  
  553. eeeeeeee is the length of the transfer
  554.  
  555. qq is the zone number
  556.  
  557. gggggggg is the error code that was reported by the R/W subsystem
  558.  
  559. jjjjjjjj is the physical block address (PBA)
  560.  
  561. llll is the track on which the error occurred
  562.  
  563. mm is the head on which the error occurred
  564.  
  565. nn is the sector on which the error occurred
  566.  
  567. oo is the wedge on which the error occurred
  568.  
  569. uuuuuuuu is the total number of soft errors recovered by track-rewrite
  570.  
  571. If no error occurred and the format operation has successfully completed, the following
  572. information will be displayed.
  573.  
  574.  
  575. " User Partition Format Successful - Elapsed Time m"
  576.  
  577. where
  578.  
  579. m is the amount of time that has elapsed since the format operation was started
  580.  
  581. If at least one zone re-format was skipped then the following will also be
  582. displayed upon successful completion of the format:
  583.  
  584. "Zone re-format was skipped."
  585.  
  586.  
  587. Examples:
  588.  
  589. Example #1:
  590. Perform a "quick format" (process defect lists, clear format corrupt, do not write
  591. or certify the drive)
  592.  
  593. F3 T>m0,6,,,,,,22
  594.  
  595. Example #2:
  596. Perform a "quick format" (don't process defect lists i.e. unslip and unalt, do not
  597. write or certify the drive)
  598.  
  599. F3 T>m0,6,0,,,,,22
  600.  
  601. Example #3:
  602. Perform a format with the default data pattern 0x00000000 and certify with event
  603. reporting enabled:
  604.  
  605. F3 T>m0,8,,,,,,22
  606.  
  607. Example #4:
  608. Perform a format and certify with event reporting enabled, set max write retries
  609. to 16, set max read retry count to 8, max ECC T-Level to 0, and track rewrite
  610. during certify retry threshold to 20:
  611.  
  612. F3 T>m0,8,,10,8,0,14,22
  613.  
  614. Example #5:
  615. Perform a format with user input data pattern 0xFFFFFFFF and certify with event
  616. reporting enabled:
  617.  
  618. F3 T>m0,8,,,,,,22,ffffffff
  619.  
  620. Example #6:
  621. Perform a format with secondary ER mode feature. Two sets of ER mode parameters are
  622. entered. First set is used in the first pass of format/certify, set max write retry
  623. to 15, max read retry to 5 and max ECC T-Level to 6. Second set is used in the rest
  624. passes, set max write retry to 17, max read retry to 7 and max ECC T-Level to 14.
  625. Note that this usage is only available if RW_FORMAT_APPLY_SECONDARY_ER_MODE is enabled.
  626.  
  627. F3 T>m0,1,2,15,5,6,,22,,17,7,14
  628.  
  629. Example #7:
  630. Determine the current format state and set format corrupt:
  631.  
  632. F3 T>m99
  633.  
  634. Revision History:
  635.  
  636. 0001.0000 Initial revision.
  637. 0001.000X Added ability to enable and display event-based output.
  638. 0011.000X Combined the PSG Diagnostic Error Codes (PSGDEC) and the Diagnostic External
  639. Test Service Error Codes (DETSEC) into a single set of Diagnostic Error Codes
  640. (DiagError).
  641. 0012.000X Added additional parameter 8 for users to input data pattern for format. The
  642. default data pattern is 0x00000000 instead of the 0x77777777 for the User
  643. Partition and 0xFFFFFFFF for the System Partition.
  644. 0012.001X Added option to process the Active Error Log.
  645. 0012.01XX Added brief event reporting (see bit 4 of the minor revision history below).
  646. 0012.02XX Added support for reporting the index of the defect list entry at which defect
  647. list processing error occurred.
  648. 0012.03XX Added support for skipping track re-write operation on data sync time-out errors.
  649. 0012.04XX Added support for displaying error location for failing LBA ( wedge no and physical sector no )
  650. 0012.05XX Corrected output for iterative channels
  651.  
  652. Note on Minor Rev:
  653. ----.ZZXX ZZ represents the minor rev base value.
  654. XX represents set of conditional feature supported by the command.
  655. - If bit 0 of X is set, then the ability to enable and display
  656. event-based output is supported.
  657. - If bit 1 of X is set, then the ability to enable zone re-format
  658. skipping and output command result information if at least one
  659. zone re-format was skipped is supported.
  660. - If bit 2 of X is set, then the ability to format only SeaCOS
  661. Extended File (XF) space is supported.
  662. - If bit 3 of X is set, then the ability to use secondary ER mode
  663. to format/certify is supported.
  664. - If bit 4 of X is set, then the command supports brief event
  665. reporting.
  666. - If bit 5 of X is set, then the command supports skipping of
  667. track re-write operation on data sync time-out errors.
  668.  
  669.  
  670. start by checking Heads resistance, this will provide a hint about possible fault with the heads.
  671.  
  672. F3 T>/7
  673. F3 7>X
  674.  
  675.  
  676. If you do a check on the re-assigned sector list and User Slip Defect list you might have more clues regarding how many defects were re-assigned on a specific head :
  677.  
  678. F3 T>V4
  679. F3 T>V1
  680.  
  681. even if you fix a drive from the BSY/LBA 0 bug you shouldn't re-use the drive (at least for important data). The fix should be used only to take the data from the drive.
  682.  
  683.  
  684. Also I truly think that it's a head issue, because even if the drive were to have some sort of translator problem (like on 0-LBA bug, preventing sector access by LBA), the m0,8,2,,,,,22 command shouldn't get stuck and should be able to complete
  685.  
  686. When the firmware is running "normally", it checks the presence of heads and motors and if it can't find them goes in an "isolation" mode, i.e. if any of heads or motor is not found an instruction is executed that shuts off the serial interface.
  687. When a BSY (but not as seen a LBA0) occurs, the firmware "loops" in a more restricted set of instruction that do not comprehend the check for heads and motor, and thus though still running, the procesor never reaches the instructon "shut off the serial".
  688.  
  689.  
  690. If your drive stops running after 5 seconds then it has a different problem. The most likely cause is the fact that it is not able to read the SA (Service Area) which means you either have a damaged head or platter, or both
  691.  
  692. Also a question was raised as how to get the defects onto the G-list.
  693. It is my understanding that if the drive cannot read a sector it is placed on the pending list.
  694. If at a later point the drive can read or if the sector is written to the drive will remap the sector to a new 'pool' sector.
  695. When this occurs the drive places it on the ALT-LIST which contains an entry to map the old sector LBA/CHS -> new sector LBA/CHS. An entry for the old sector is also made in the G-LIST.
  696. The P-LIST or (permanent list is not touched) nor is the slip list.
  697. Also the i4,1,22 command DOES NOT delete the NRG, or P-LIST.
  698. It deletes the G-LIST, ALT-LIST and SLIP lists.
  699. Also the Alt-LIST is not the SAME as the G-LIST.
  700. The ALT-LIST contains mappings from old to new sectors.
  701. The G-LIST contains entires of old bad sectors only.
  702. You cannot add to glist as entries here do not form basis for translator, wheras NRG defects do. Need to add defects to slip list directly, but also you need to be careful as the HDD can have non NRG defects that are interpreted wrong.
  703.  
  704.  
  705. The System Partition (sometimes called the System Area) is an area on the drive that is used for internal drive operation and contains
  706. firmware, code, modules, tables, adaptives, etc
  707. And duplicate copies of many important areas
  708.  
  709. There is NO standard layout for the SA and its contents are specific to the model of the drive and even to the specific disk itself (eg adaptives, defect lists)
  710.  
  711. It is totally separate from any user data area
  712.  
  713. see
  714. Newbie info, from and for newbies :) About firmware, SA, etc
  715. http://forum.hddguru.com/viewtopic.php?f=16&t=6562&start=20
  716.  
  717.  
  718. Older drives / other manufacturers sometimes use the concept of negative cylinders for the SA
  719.  
  720. Modules Seagate F3 (probably .11, not .12)
  721.  
  722. Module Sys. file Description
  723. 00 Defect list of SA
  724. 01 0x001A Drive information file
  725. 02 0x0019 Performance parameter file
  726. 03 0x001B P-List
  727. 04 0x003F SAP (Servo Adaptive FParameters)
  728. 05 0x0300 Manufacturin information file
  729. 06 0x0001 RAP (Read Adaptives Parameters)
  730. 07 0x0208 CAP (Controller Adaptives Parameters)
  731. 09 0x0133 SMART config (filling by pattern)
  732. 0A 0x0134 SMART Frame
  733. 0C 0x0139 Self scan log
  734. 0E DIC (Data integrity check), Head 0
  735. 0F DIC Dummy file
  736. 13 0x030A Disk reestr (Security settings)
  737. 15 0x0306 Offline selfscan of surface (DOS)
  738. 1D 0x0100 Overlay 0
  739. 1E 0x0101 Overlay 1
  740. 22 File selfscan surface, head 0
  741. 23 File selfscan surface, head 1
  742. 24 File selfscan surface, head 2
  743. 25 File selfscan surface, head 3
  744. 26 File selfscan surface, head 4
  745. 27 File selfscan surface, head 5
  746. 28 File selfscan surface, head 6
  747. 29 File selfscan surface, head 7
  748. 2A 0x0093 Saved Mode pages (Edit HDD ID)
  749. 2B 0x0028 RW operations, (Translator)
  750. 2C DIC (Data Integrity Check), Head 1, pattern
  751. 2D DIC (Data Integrity Check), Head 2, pattern
  752. 2E DIC (Data Integrity Check), Head 3, pattern
  753. 2F DIC (Data Integrity Check), Head 4, pattern
  754. 30 DIC (Data Integrity Check), Head 5, pattern
  755. 31 DIC (Data Integrity Check), Head 6, pattern
  756. 32 DIC (Data Integrity Check), Head 7, pattern
  757. 33 Service file FDE
  758. 34 0x032C Packed structure descriptor CONGEN
  759. 35 0x0135 SMART
  760.  
  761.  
  762. 7.4 Background Media Scan
  763.  
  764. Background Media Scan (BMS) is a self-initiated media scan. BMS is defined in the T10 document SPC-4 available from the T10 committee. BMS performs sequential reads across the entire pack of the media while the drive is idle. In RAID arrays, BMS allows hot spare drives to be scanned for defects prior to being put into service by the host system. On regular duty drives, if the host system makes use of the BMS Log Page, it can avoid placing data in suspect locations on the media. Unreadable and recovered error sites will be logged or reallocated per ARRE/AWRE settings.
  765.  
  766. With BMS, the host system can consume less power and system overhead by only checking BMS status and results rather than tying up the bus and consuming power in the process of host-initiated media scanning activity.
  767.  
  768. Since the background scan functions are only done during idle periods, BMS causes a negligible impact to system performance. The first BMS scan for a newly manufactured drive is performed as quickly as possible to verify the media and protect data by setting the “Start time after idle” to 5ms, all subsequent scans begin after 500ms of idle time. Other features that normally use idle time to function will function normally because BMS functions for bursts of 800ms and then suspends activity for 100ms to allow other background functions to operate.
  769.  
  770. BMS interrupts immediately to service host commands from the interface bus while performing reads. BMS will complete any BMS-initiated error recovery prior to returning to service host-initiated commands. Overhead associated with a return to host-servicing activity from BMS only impacts the first command that interrupted BMS, this results in a typical delay of about 1 ms.
  771.  
  772. 7.5 Media Pre-Scan
  773.  
  774. Media Pre-Scan is a feature that allows the drive to repair media errors that would otherwise have been found by the host system during critical data accesses early in the drive’s life. The default setting for Media Pre-Scan is enabled on standard products. Media Pre-Scan checks each write command to determine if the destination LBAs have been scanned by BMS. If the LBAs have been verified, the drive proceeds with the normal write command. If the LBAs have not been verified by BMS, Pre-Scan will convert the write to a write verify to certify that the data was properly written to the disc.
  775.  
  776. Note. During Pre-Scan write verify commands, write performance may decrease by 50% until Pre-Scan completes. Write performance testing should be performed after Pre-Scan is complete. This may be checked by reading the BMS status.
  777.  
  778. To expedite the scan of the full pack and subsequently exit from the Pre-Scan period, BMS will begin scanning immediately when the drive goes to idle during the Pre-Scan period. In the event that the drive is in a high transaction traffic environment and is unable to complete a BMS scan within 24 power on hours BMS will disable Pre-Scan to restore full performance to the system.
  779.  
  780. 7.6 Deferred Auto-Reallocation
  781.  
  782. Deferred Auto-Reallocation (DAR) simplifies reallocation algorithms at the system level by allowing the drive to reallocate unreadable locations on a subsequent write command. Sites are marked for DAR during read operations performed by the drive. When a write command is received for an LBA marked for DAR, the auto-reallocation process is invoked and attempts to rewrite the data to the original location. If a verification of this rewrite fails, the sector is re-mapped to a spare location.
  783.  
  784. This is in contrast to the system having to use the Reassign Command to reassign a location that was unreadable and then generate a write command to rewrite the data. DAR is most effective when AWRE and ARRE are enabled — this is the default setting from the Seagate factory. With AWRE and ARRE disabled DAR is unable to reallocate the failing location and will report an error sense code indicating that a write command is being attempted to a previously failing location.
  785.  
  786. 7.7 Idle Read After Write
  787.  
  788. Idle Read After Write (IRAW) utilizes idle time to verify the integrity of recently written data.
  789. During idle periods, no active system requests, the drive reads recently written data from the media and compares it to valid write command data resident in the drives data buffer. Any sectors that fail the comparison result in the invocation of a rewrite and auto-reallocation process. The process attempts to rewrite the data to the original location. If a verification of this rewrite fails, the sector is re-mapped to a spare location.
  790.  
  791.  
  792.  
  793. It might be worth disabling READ_CACHING and READ_LOOKAHEAD in DIY cloning cases, and perhaps setting DISABLE_ADAPTIVE_READ_AHEAD = 1 might have benefits also.
  794. http://malthus.mooo.com/viewtopic.php?f=59&t=694
  795. CacheControl Mode Page
  796. CacheControl Group
  797.  
  798. Byte:00EA: CacheFlags = 14
  799. Byte:00EA: Bit:0, READ_CACHING_DISABLED_ON_POWER_UP = 0
  800. Byte:00EA: Bit:1, MULTIPLICATION_FACTOR = 0
  801. Byte:00EA: Bit:2, WRITE_CACHING_ENABLED_ON_POWER_UP = 1
  802. Byte:00EA: Bit:4, DISCONTINUITY = 1
  803. Byte:00EA: Bit:5, CACHING_ANALYSIS_PERMITTED = 0
  804. Byte:00EA: Bit:6, ABORT_PREFETCH = 0
  805. Byte:00EA: Bit:7, DISABLE_ADAPTIVE_READ_AHEAD = 0
  806.  
  807. Byte:00F4: Bit:5, READ_LOOKAHEAD_DISABLED_ON_POWER_UP = 0
  808. Byte:00F4: Bit:7, FORCE_SEQUENTIAL_WRITE = 1
  809.  
  810.  
  811. m0,2,1,,,,,22 ( To rebuilt slip list, V1 )
  812. m0,2,2,,,,,22 ( To rebuilt G list, V2 )
  813. m0,2,3,,,,,22 ( To rebuilt P list, V3 )
  814.  
  815. m0,5,1,10,3,,,22 ( To zero fill with slip list )
  816. m0,5,2,10,3,,,22 ( To zero fill with G list )
  817. m0,5,3,10,3,,,22 ( To zero fill with P list )
  818.  
  819. m0,8,1,10,3,,,22 ( To format with slip list )
  820. m0,8,2,10,3,,,22 ( To format with G list )
  821. m0,8,3,10,3,,,22 ( To format with P list )
  822.  
  823. m0,D,1,,,,,22 ( To repair bad sector by Slip list )
  824. m0,D,2,,,,,22 ( To repair bad sector by G list )
  825. m0,D,3,,,,,22 ( To repair bad sector by P list )
  826.  
  827. m0,20,1,,,,,22 ( To format (seacos XF) by Slip list )
  828. m0,20,2,,,,,22 ( To format (seacos XF) by G list )
  829. m0,20,3,,,,,22 ( To format (seacos XF) by P list, most powerfull to repair bad sectors, red and green blocks )
  830.  
  831. m0,2,2,,,,,22 ( Format user area partition without certifying defects and relocate defects. not effect Data in a drive ) LIES - actually erased my ALT-List. and i think G_liSt
  832. m0,2,1,,,,,22 ( Format user area partition with user slip list with certify defects. DATA WILL BE LOSS )
  833. m0,D,3,,,,,22 ( Format user area partition with repairing of bad sector, auto add bad sector into G list and in the last it will be shifted to P list )
  834.  
  835. m0,5,1,,,,,22 ( it used for erasing of all sector )
  836. m0,8,2,,,,,22 ( it is used for formatting hard disk sectors )
  837.  
  838. The i4,2,22 command deletes the Alt-list and G-list. Contrary to some statements by so called GURUS on HDD GURU forum, the G-list and alt are NOT the same thing. The alt list is used to remap bad sectors to the new ones, in other words it remaps the LBA to the new PBA and CHS, the G-list hold the location of the BAD sector in PBA and CHS format.
  839.  
  840. Modify Track Defect List (Level 2 'F')
  841.  
  842.  
  843. Description:
  844. The Modify Track Defect List command modifies the defect list for the specified
  845. sector(s).
  846.  
  847. Quick Help:
  848.  
  849. "ModTrkDfctLst, F[PSctr/LBA],[Action]";
  850.  
  851. Input Parameters:
  852.  
  853.  
  854. 0 - Physical Sector or LBA to Modify.
  855.  
  856. If Parameter 1 is A1, B1, C1, or F1, this value is an LBA.
  857. If parameter 1 is some other value, this parameter is the physical sector number
  858. of the block to be affected. The cylinder and head come from the current address.
  859.  
  860. Type: Unsigned 32-bit value
  861.  
  862. Range: 0 to 0xFFFFFFFF
  863.  
  864. Default: 0
  865.  
  866. Note: The track and head used are the current track. When working with sectors
  867. that are already alted, it is best to use the LBA mode actions (B1 and C1
  868. below) .
  869.  
  870.  
  871. 1 - Defect List Action.
  872.  
  873. Parameter 1 specifies the format action to be taken. The valid choices are:
  874. A - Add Sector to Alternated Sector List
  875. A1 - Add LBA to Alternated Sector List
  876. B - Add Sector to Pending Sector List
  877. B1 - Add LBA to Pending Sector List
  878. C1 - Remove LBA from Alternated Sector List
  879. F1 - Remove LBA from Alternated Sector List ( same as C1 above )
  880.  
  881. Type: Unsigned 32-bit value
  882.  
  883. Range: 0 to 0xFFFFFFFF
  884.  
  885. Default: 0x0C1
  886.  
  887.  
  888. Output Data:
  889.  
  890. If an error occurred, the following information will be displayed.
  891.  
  892. "DiagError aaaaaaaa "
  893.  
  894. where
  895.  
  896. aaaaaaaa is the Diagnostic Error Code
  897.  
  898.  
  899. Examples:
  900.  
  901. Example #1:
  902. To remove LBA 1234 from the alt list:
  903.  
  904. F3 2>F1234,f1
  905.  
  906. Revision History:
  907.  
  908. 0001.0000 Initial Revision.
  909. 0002.0000 Remove 2>Fx,F; add Fx,F1 to unalt by sector.
  910. 0011.0000 Combined the PSG Diagnostic Error Codes (PSGDEC) and the Diagnostic External
  911. Test Service Error Codes (DETSEC) into a single set of Diagnostic Error Codes
  912. (DiagError).
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!