【REGZA HDD修復５】REGZA修復ツールを使った成功例

別のHDDでREGZA修復ツールの成功例が見れたのでメモしておく。

マウントできるような状態の機器では下記のように「（３）修復する録画機器」と「（４）修復する記憶領域」が選択できる状態となる。
これが、前記事などであたっている「見えてはいるがマウントできない」ような機器の場合、「（４）修復する記憶領域」が選択できないような状態となる。

ちなみに正常機器で実行した結果のlogは以下のようなもの。

Phase 1 – find and verify superblock…
– reporting progress in intervals of 15 minutes
– block cache size set to 330256 entries
Phase 2 – using internal log
– zero log…
zero_log: head block 785 tail block 785
– scan filesystem freespace and inode maps…
– 09:56:39: scanning filesystem freespace – 32 of 32 allocation groups done
– found root inode chunk
Phase 3 – for each AG…
– scan and clear agi unlinked lists…
– 09:56:39: scanning agi unlinked lists – 32 of 32 allocation groups done
– process known inodes and perform inode discovery…
– agno = 0
– agno = 15
– agno = 16
– agno = 17
– agno = 18
– agno = 19
– agno = 20
– agno = 21
– agno = 22
– agno = 23
– agno = 24
– agno = 25
– agno = 26
– agno = 27
– agno = 28
– agno = 29
– agno = 30
– agno = 31
– agno = 1
– agno = 2
– agno = 3
– agno = 4
– agno = 5
– agno = 6
– agno = 7
– agno = 8
– agno = 9
– agno = 10
– agno = 11
– agno = 12
– agno = 13
– agno = 14
– 09:56:39: process known inodes and inode discovery – 192 of 192 inodes done
– process newly discovered inodes…
– 09:56:39: process newly discovered inodes – 32 of 32 allocation groups done
Phase 4 – check for duplicate blocks…
– setting up duplicate extent list…
– 09:56:39: setting up duplicate extent list – 32 of 32 allocation groups done
– check for inodes claiming duplicate blocks…
– agno = 0
– agno = 1
– agno = 2
– agno = 3
– agno = 4
– agno = 5
– agno = 6
– agno = 7
– agno = 8
– agno = 9
– agno = 10
– agno = 11
– agno = 12
– agno = 13
– agno = 14
– agno = 15
– agno = 16
– agno = 17
– agno = 18
– agno = 19
– agno = 20
– agno = 21
– agno = 22
– agno = 23
– agno = 24
– agno = 25
– agno = 26
– agno = 27
– agno = 28
– agno = 29
– agno = 30
– agno = 31
– 09:56:39: check for inodes claiming duplicate blocks – 192 of 192 inodes done
Phase 5 – rebuild AG headers and trees…
– agno = 0
– agno = 1
– agno = 2
– agno = 3
– agno = 4
– agno = 5
– agno = 6
– agno = 7
– agno = 8
– agno = 9
– agno = 10
– agno = 11
– agno = 12
– agno = 13
– agno = 14
– agno = 15
– agno = 16
– agno = 17
– agno = 18
– agno = 19
– agno = 20
– agno = 21
– agno = 22
– agno = 23
– agno = 24
– agno = 25
– agno = 26
– agno = 27
– agno = 28
– agno = 29
– agno = 30
– agno = 31
– 09:56:39: rebuild AG headers and trees – 32 of 32 allocation groups done
– reset superblock…
Phase 6 – check inode connectivity…
– resetting contents of realtime bitmap and summary inodes
– traversing filesystem …
– agno = 0
– agno = 1
– agno = 2
– agno = 3
– agno = 4
– agno = 5
– agno = 6
– agno = 7
– agno = 8
– agno = 9
– agno = 10
– agno = 11
– agno = 12
– agno = 13
– agno = 14
– agno = 15
– agno = 16
– agno = 17
– agno = 18
– agno = 19
– agno = 20
– agno = 21
– agno = 22
– agno = 23
– agno = 24
– agno = 25
– agno = 26
– agno = 27
– agno = 28
– agno = 29
– agno = 30
– agno = 31
– traversal finished …
– moving disconnected inodes to lost+found …
Phase 7 – verify and correct link counts…
– 09:56:39: verify and correct link counts – 32 of 32 allocation groups done

XFS_REPAIR Summary Sat Feb 5 09:56:40 2022

Phase Start End Duration
Phase 1: 02/05 09:56:35 02/05 09:56:36 1 second
Phase 2: 02/05 09:56:36 02/05 09:56:39 3 seconds
Phase 3: 02/05 09:56:39 02/05 09:56:39
Phase 4: 02/05 09:56:39 02/05 09:56:39
Phase 5: 02/05 09:56:39 02/05 09:56:39
Phase 6: 02/05 09:56:39 02/05 09:56:39
Phase 7: 02/05 09:56:39 02/05 09:56:39

Total run time: 4 seconds
done
DO_REPAIR_SUCCESS