Welcome, Guest
Username: Password: Remember me

Search Micromat Forum

Keyword

TOPIC: Volume Rebuild errors and spontaneous quits

Volume Rebuild errors and spontaneous quits 27 Jun 2013 20:26 #4241

Hi,
I have a volume on a Promise RAID5 fibre-attached to an Xserve. There are a number os slices and volumes, but this one in particular is giving me a lot of grief. It will no longer mount in the Finder and is "accessible" only through diagnostic tools, such as TTP, that can 'see' it. However, TTP cannot repair this volume with Volume rebuild errors. Moreover, when I run Volume Structures check, it spontaneously quits TTP altogether. Here is some of the Console data on the quit (more available):

Process: TechTool Pro 6 [51756]
Path: /Applications/TechTool Pro 6.app/Contents/MacOS/TechTool Pro 6
Identifier: com.micromat.techtoolpro6
Version: 6.0.6 (7347)
Code Type: X86 (Native)
Parent Process: launchd [241]
User ID: 501

Date/Time: 2013-06-27 16:20:02.456 -0400
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10

Interval Since Last Report: 1799796 sec
Crashes Since Last Report: 92
Per-App Interval Since Last Report: 5985 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: EABD0A20-548C-3D40-6789-EC6E168857EB

Crashed Thread: 7

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayI objectAtIndex:]: index 4294967295 beyond bounds [0 .. 0]'

Application Specific Backtrace 1:
0 CoreFoundation 0x94f4be8b __raiseError + 219
1 libobjc.A.dylib 0x9a09152e objc_exception_throw + 230
2 CoreFoundation 0x94e59b4e -[__NSArrayI objectAtIndex:] + 190
3 TechTool Pro 6 0x00065fd1 -[MMVolumeStructuresAgent executeVolumeStructuresTest:devicePath:] + 4187
4 TechTool Pro 6 0x00064e01 -[MMVolumeStructuresAgent runThreadWithArguments:] + 383
5 TechTool Pro 6 0x0004b4fc -[MMThreadAgent threadEntry:] + 121
6 TechTool Pro 6 0x0004b764 -[MMDevThreadAgent threadEntry:] + 215
7 Foundation 0x92574448 -[NSThread main] + 45
8 Foundation 0x925743cb __NSThread__main__ + 1396
9 libsystem_c.dylib 0x946b45b7 _pthread_start + 344
10 libsystem_c.dylib 0x9469ed4e thread_start + 34

FWIW, Disk Utility barber-poles endlessly just after "Updating boot partitions…" and DiskWarrior won't touch the volume due to "Disk Hardware failure".

Given that the volume is on a RAID5 array, how could I ascertain which physical drives the volume might be spanned across? And why would TTP v6 be unable to handle this issue? I could try a Surface Scan, but TTP shows me the actual volumes of the RAID and there's no way for me to match up my unmounting volume ("Outtakes3") with any of the various "2.2 TB Promise vTrak E610f" I see as available for surface scanning in TTP.

Thanks for any ideas...
Attachments:
The administrator has disabled public write access.

Volume Rebuild errors and spontaneous quits 27 Jun 2013 22:15 #4242

TechTool Pro has been reported to work with some RAID arrays, but we develop and test it only with RAIDs created by Apple’s Disk Utility. There are too many variations on proprietary RAID arrays for us to be able to properly test the application with them.

Please send a message to This email address is being protected from spambots. You need JavaScript enabled to view it. , including a link to this thread. The programmer will have to take a look at the log file. I hope that some suggestion or at least an understanding of what the problem is will be forthcoming.

I suggest that that you run the Surface Scan test to check the drive, to see if the crash is being caused by unremapped bad blocks. The Surface Scan is a read-only test, and will not make matters worse. It is unfortunate that S.M.A.R.T. data is not available for the drive. Please let us know what happens.
MicroMat Inc
Makers of TechTool
Last Edit: 27 Jun 2013 22:18 by micromattech3.
The administrator has disabled public write access.

Volume Rebuild errors and spontaneous quits 27 Jun 2013 22:33 #4243

See if Disk Utility displays the drive mechanisms and what volumes are on them in a way that is helpful. The Surface Scan checks physical drives, not volumes, but of course with the RAID it may be difficult to associate the drives and their volumes.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Volume Rebuild errors and spontaneous quits 27 Jun 2013 22:49 #4244

I do not see any familiar Terminal command that helps to associate drive mechanisms with the volumes on them, and Apple System Information does not seem to have it. If you enable the debug menu in Disk Utility, and then launch Disk Utility, you get more detailed information.

The Terminal command to enable the debug menu is:

sudo defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

(taken from sysblog.sund.org/category/apple/ )

There are some variations on the command for different versions of system software:

Manage all partitions with Disk Utility in OS X, by Topher Kessler.






6/27/13 3:40:32.141 PM Disk Utility: **********
6/27/13 3:40:32.145 PM Disk Utility: Disk Utility started.
6/27/13 3:40:32.452 PM Disk Utility: module: Restore - loaded
6/27/13 3:40:32.471 PM Disk Utility: module: First Aid - loaded
6/27/13 3:40:32.493 PM Disk Utility: module: Erase - loaded
6/27/13 3:40:32.510 PM Disk Utility: module: Information - loaded
6/27/13 3:40:32.534 PM Disk Utility: DUDiskController needed [DMManager sharedManager], thread = 0x7ff043c19690
6/27/13 3:40:32.575 PM Disk Utility: preBootEnvironmentFlag: DMPreBootEnvironmentEFI
6/27/13 3:40:32.576 PM Disk Utility: module: Partition - loaded
6/27/13 3:40:32.589 PM Disk Utility: module: RAID - loaded
6/27/13 3:40:32.593 PM Disk Utility: ## rebuildMasterList ##
6/27/13 3:40:33.940 PM Disk Utility: **********
6/27/13 3:40:34.036 PM Disk Utility: Disk: disk0 (WDC WD1001FALS-40Y6A0 Media) - 0x7ff0451639d0
6/27/13 3:40:34.036 PM Disk Utility: Optical Device: SuperDrive - 0x7ff043cc4bb0
6/27/13 3:40:34.037 PM Disk Utility: =============================
6/27/13 3:40:34.038 PM Disk Utility: Unattached Disk Image: SATSMARTDriver-0.6.dmg - 0x7ff045166280
6/27/13 3:40:34.038 PM Disk Utility: Unattached Disk Image: ttp606_7347.dmg - 0x7ff04507ec50
6/27/13 3:40:34.039 PM Disk Utility: Unattached Disk Image: java jre-7u25-macosx-x64.dmg - 0x7ff0450537f0
6/27/13 3:40:34.039 PM Disk Utility: Disk: disk0 (WDC WD1001FALS-40Y6A0 Media) - 0x7ff0451639d0
6/27/13 3:40:34.047 PM Disk Utility: Partition: disk0s1 (disk0s1) - 0x7ff045444350
6/27/13 3:40:34.054 PM Disk Utility: Partition: disk0s2 (Macintosh HD) [* boot volume] - 0x7ff045449080
6/27/13 3:40:34.061 PM Disk Utility: Partition: disk0s3 (Recovery HD) - 0x7ff0454461b0
6/27/13 3:40:34.064 PM Disk Utility: Disk: disk1 (G-TECH) - 0x7ff045164040
6/27/13 3:40:34.072 PM Disk Utility: Partition: disk1s1 (disk1s1) - 0x7ff045446510
6/27/13 3:40:34.080 PM Disk Utility: Partition: disk1s2 (G-Drive_Q_232) - 0x7ff045449e20
6/27/13 3:40:34.087 PM Disk Utility: Partition: disk1s3 (eDrive) - 0x7ff043c6ce70
6/27/13 3:40:34.094 PM Disk Utility: Partition: disk1s4 (Recovery) - 0x7ff04544a7b0
6/27/13 3:40:34.097 PM Disk Utility: Disk: disk2 (G-TECH) - 0x7ff0451649c0
6/27/13 3:40:34.104 PM Disk Utility: Partition: disk2s1 (disk2s1) - 0x7ff043cc6a30
6/27/13 3:40:34.111 PM Disk Utility: Partition: disk2s2 (H_G_Wells) - 0x7ff0450eedd0
6/27/13 3:40:34.112 PM Disk Utility: Optical Device: SuperDrive - 0x7ff043cc4bb0
6/27/13 3:40:34.112 PM Disk Utility: =============================
MicroMat Inc
Makers of TechTool
Last Edit: 27 Jun 2013 22:54 by micromattech3.
The administrator has disabled public write access.
The following user(s) said Thank You: thellum
Time to create page: 0.386 seconds