API tools faq
paste
Advertisement
grahamperrin

preparing to reinstall 10.7 (Build 11A511) — step 001

grahamperrin
Jul 24th, 2011
147
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.96 KB | None | 0 0
raw download clone embed print report
  1. Verifying and repairing partition map for “TOSHIBA MK1234GSX Media”
  2. Checking prerequisites
  3. Checking the partition list
  4. Checking for an EFI system partition
  5. Checking the EFI system partition’s size
  6. Checking the EFI system partition’s file system
  7. Checking all HFS data partition loader spaces
  8. Reviewing boot support loaders
  9. Checking Core Storage Physical Volume partitions
  10. Checking storage system
  11. Checking volume.
  12. disk0s2: Scan for Volume Headers
  13. disk0s2: Scan for Disk Labels
  14. Logical Volume Group 27B49546-1916-4231-B567-2F138A39B95E spans 1 device
  15. Logical Volume Group has a 16 MB Metadata Volume with double redundancy
  16. Start scanning metadata for a valid checkpoint
  17. Load and verify Segment Headers
  18. Load and verify Checkpoint Payload
  19. Load and verify Transaction Segment
  20. Load and verify Transaction Segment
  21. Incorporate 1 newer non-checkpoint transactions
  22. Load and verify Virtual Address Table
  23. Load and verify Segment Usage Table
  24. Load and verify Metadata Superblock
  25. Load and verify Logical Volumes B-Trees
  26. Logical Volume Group contains 1 Logical Volumes
  27. Load and verify BE41A217-AA91-4433-A4E6-B168E9670B06
  28. Load and verify E6F22C10-C8CB-45C7-B9B9-2A97746A6001
  29. Load and verify Freespace Summary
  30. Load and verify Block Accounting
  31. Load and verify Segment Cleaning
  32. Newest transaction commit checkpoint is valid
  33. The volume 27B49546-1916-4231-B567-2F138A39B95E appears to be OK.
  34. Checking storage system
  35. Checking volume.
  36. disk0s4: Scan for Volume Headers
  37. disk0s4: Scan for Disk Labels
  38. Logical Volume Group 85784E02-E96E-43B3-8545-2765F7EB6F73 spans 1 device
  39. Logical Volume Group has a 16 MB Metadata Volume with double redundancy
  40. Start scanning metadata for a valid checkpoint
  41. Load and verify Segment Headers
  42. Load and verify Checkpoint Payload
  43. Load and verify Transaction Segment
  44. Incorporate 0 newer non-checkpoint transactions
  45. Load and verify Virtual Address Table
  46. Load and verify Segment Usage Table
  47. Load and verify Metadata Superblock
  48. Load and verify Logical Volumes B-Trees
  49. Logical Volume Group contains 1 Logical Volumes
  50. Load and verify 6DE77C6D-CD94-4CD8-90F0-3EA8045EBF2F
  51. Load and verify 8BF1ECCF-2BBE-49BB-8F96-2ACE073D31C5
  52. Load and verify Freespace Summary
  53. Load and verify Block Accounting
  54. Load and verify Segment Cleaning
  55. Newest transaction commit checkpoint is valid
  56. The volume 85784E02-E96E-43B3-8545-2765F7EB6F73 appears to be OK.
  57. Updating Windows boot.ini files as required
  58. The partition map appears to be OK
  59.  
  60. Verify and Repair volume “a”
  61. Checking storage systemChecking volume.
  62. disk0s2: Scan for Volume Headers
  63. disk0s2: Scan for Disk Labels
  64. Logical Volume Group 27B49546-1916-4231-B567-2F138A39B95E spans 1 device
  65. Logical Volume Group has a 16 MB Metadata Volume with double redundancy
  66. Start scanning metadata for a valid checkpoint
  67. Load and verify Segment Headers
  68. Load and verify Checkpoint Payload
  69. Load and verify Transaction Segment
  70. Load and verify Transaction Segment
  71. Incorporate 1 newer non-checkpoint transactions
  72. Load and verify Virtual Address Table
  73. Load and verify Segment Usage Table
  74. Load and verify Metadata Superblock
  75. Load and verify Logical Volumes B-Trees
  76. Logical Volume Group contains 1 Logical Volumes
  77. Load and verify BE41A217-AA91-4433-A4E6-B168E9670B06
  78. Load and verify E6F22C10-C8CB-45C7-B9B9-2A97746A6001
  79. Load and verify Freespace Summary
  80. Load and verify Block Accounting
  81. Load and verify Segment Cleaning
  82. Newest transaction commit checkpoint is valid
  83. The volume 27B49546-1916-4231-B567-2F138A39B95E appears to be OK.
  84. Checking file systemChecking Journaled HFS Plus volume.
  85. Checking extents overflow file.
  86. Checking catalog file.
  87. Checking multi-linked files.
  88. Checking catalog hierarchy.
  89. Checking extended attributes file.
  90. Checking volume bitmap.
  91. Checking volume information.
  92. The volume a appears to be OK.
  93. Volume repair complete.Updating boot support partitions for the volume as required.
  94. Verify and Repair volume “b”
  95. Checking storage systemChecking volume.
  96. disk0s4: Scan for Volume Headers
  97. disk0s4: Scan for Disk Labels
  98. Logical Volume Group 85784E02-E96E-43B3-8545-2765F7EB6F73 spans 1 device
  99. Logical Volume Group has a 16 MB Metadata Volume with double redundancy
  100. Start scanning metadata for a valid checkpoint
  101. Load and verify Segment Headers
  102. Load and verify Checkpoint Payload
  103. Load and verify Transaction Segment
  104. Incorporate 0 newer non-checkpoint transactions
  105. Load and verify Virtual Address Table
  106. Load and verify Segment Usage Table
  107. Load and verify Metadata Superblock
  108. Load and verify Logical Volumes B-Trees
  109. Logical Volume Group contains 1 Logical Volumes
  110. Load and verify 6DE77C6D-CD94-4CD8-90F0-3EA8045EBF2F
  111. Load and verify 8BF1ECCF-2BBE-49BB-8F96-2ACE073D31C5
  112. Load and verify Freespace Summary
  113. Load and verify Block Accounting
  114. Load and verify Segment Cleaning
  115. Newest transaction commit checkpoint is valid
  116. The volume 85784E02-E96E-43B3-8545-2765F7EB6F73 appears to be OK.
  117. Checking file systemChecking Journaled HFS Plus volume.
  118. Checking extents overflow file.
  119. Checking catalog file.
  120. Checking multi-linked files.
  121. Checking catalog hierarchy.
  122. Checking extended attributes file.
  123. Checking volume bitmap.
  124. Checking volume information.
  125. The volume b appears to be OK.
  126. Volume repair complete.Updating boot support partitions for the volume as required.
  127. Verify and Repair volume “a”
  128. Checking storage systemChecking volume.
  129. disk0s2: Scan for Volume Headers
  130. disk0s2: Scan for Disk Labels
  131. Logical Volume Group 27B49546-1916-4231-B567-2F138A39B95E spans 1 device
  132. Logical Volume Group has a 16 MB Metadata Volume with double redundancy
  133. Start scanning metadata for a valid checkpoint
  134. Load and verify Segment Headers
  135. Load and verify Checkpoint Payload
  136. Load and verify Transaction Segment
  137. Load and verify Transaction Segment
  138. Incorporate 1 newer non-checkpoint transactions
  139. Load and verify Virtual Address Table
  140. Load and verify Segment Usage Table
  141. Load and verify Metadata Superblock
  142. Load and verify Logical Volumes B-Trees
  143. Logical Volume Group contains 1 Logical Volumes
  144. Load and verify BE41A217-AA91-4433-A4E6-B168E9670B06
  145. Load and verify E6F22C10-C8CB-45C7-B9B9-2A97746A6001
  146. Load and verify Freespace Summary
  147. Load and verify Block Accounting
  148. Load and verify Segment Cleaning
  149. Newest transaction commit checkpoint is valid
  150. The volume 27B49546-1916-4231-B567-2F138A39B95E appears to be OK.
  151. Checking file systemChecking Journaled HFS Plus volume.
  152. Checking extents overflow file.
  153. Checking catalog file.
  154. Checking multi-linked files.
  155. Checking catalog hierarchy.
  156. Checking extended attributes file.
  157. Checking volume bitmap.
  158. Checking volume information.
  159. The volume a appears to be OK.
  160. Volume repair complete.Updating boot support partitions for the volume as required.
  161. Verify and Repair volume “b”
  162. Checking storage systemChecking volume.
  163. disk0s4: Scan for Volume Headers
  164. disk0s4: Scan for Disk Labels
  165. Logical Volume Group 85784E02-E96E-43B3-8545-2765F7EB6F73 spans 1 device
  166. Logical Volume Group has a 16 MB Metadata Volume with double redundancy
  167. Start scanning metadata for a valid checkpoint
  168. Load and verify Segment Headers
  169. Load and verify Checkpoint Payload
  170. Load and verify Transaction Segment
  171. Incorporate 0 newer non-checkpoint transactions
  172. Load and verify Virtual Address Table
  173. Load and verify Segment Usage Table
  174. Load and verify Metadata Superblock
  175. Load and verify Logical Volumes B-Trees
  176. Logical Volume Group contains 1 Logical Volumes
  177. Load and verify 6DE77C6D-CD94-4CD8-90F0-3EA8045EBF2F
  178. Load and verify 8BF1ECCF-2BBE-49BB-8F96-2ACE073D31C5
  179. Load and verify Freespace Summary
  180. Load and verify Block Accounting
  181. Load and verify Segment Cleaning
  182. Newest transaction commit checkpoint is valid
  183. The volume 85784E02-E96E-43B3-8545-2765F7EB6F73 appears to be OK.
  184. Checking file systemChecking Journaled HFS Plus volume.
  185. Checking extents overflow file.
  186. Checking catalog file.
  187. Checking multi-linked files.
  188. Checking catalog hierarchy.
  189. Checking extended attributes file.
  190. Checking volume bitmap.
  191. Checking volume information.
  192. The volume b appears to be OK.
  193. Volume repair complete.Updating boot support partitions for the volume as required.
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!