Question on G-Raid + Disk Utility + El Capitan

[AdiosVista]

Hello, I'm having issues with a G-Raid drive on El Capitan and any feedback would be greatly appreciated. Here's what happened:

I have a new 5K iMac with a new 8TB G-Raid Thunderbolt external drive (two 4TB drives in raid 0). I was in the process of erasing the drive through Disk Utility and lost power half way through When I booted the computer again, it said the G-Raid was unmountable.

Eventually (and I wish I remember how but I don't) I was able to get the two separate 4TB drives to become visible again but the raid was lost. After some Googling, I read that El Capitan has done away with the simple raid options in Disk Utility so I resorted to Terminal and used this line:

diskutil appleRAID create stripe G-RAID JHFS+ disk1 disk2

Voila, my 8TB raid was back but there are a couple concerns I have:

1. When I start Disk Utility now, I see a couple HGST drives, a few Untitled drives, and then my G-RAID I created. The number of drives looks odd. Furthermore, when I select the first Untitled drive, Disk Utility just says "Loading Disks" and never changes (screenshot below). I have a sinking feeling that something still is not right.
2. I also lost my Thunderbolt G-Raid icon and just see the plain icon on the desktop now. Again, not sure if there were more steps I needed to take in restoring this drive to factory specs. I did contact G-Tech directly and they were not exactly helpful (they told me to find an older Mac with previous Disk Utility version and create a new raid).

My main question is did I permanently screw something up with this drive and is it fixable? Thanks for your time.

 

[treekram]

I have 2 internal SSD's using RAID 0 in my 2012 MBP. Your command was the same one I used (different names and disks obviously). Your Disk Utility screenshot looks similar to mine, I have the same "Untitled" set with 3 entries (interestingly, mine is also under the "External" heading). The dual manufacturer listing is the same and the name of the volume (in your case, "G-RAID") appears as well, mine listed under Internal rather than External. My setup has been working without a problem since I set it up about 2 weeks ago.

 

[AdiosVista]

I have 2 internal SSD's using RAID 0 in my 2012 MBP. Your command was the same one I used (different names and disks obviously). Your Disk Utility screenshot looks similar to mine, I have the same "Untitled" set with 3 entries (interestingly, mine is also under the "External" heading). The dual manufacturer listing is the same and the name of the volume (in your case, "G-RAID") appears as well, mine listed under Internal rather than External. My setup has been working without a problem since I set it up about 2 weeks ago.

Thank you for the info! I'm curious, do you also see the never-ending "loading disk" when you select the first Untitled drive? I feel like that only started for me after the drive was improperly disconnected during the power outage.

 

[treekram]

Yes, I get "loading disk" with the first Untitled drive. I figured since it was grayed-out, anything Disk Utility told me about the "Untitled" drives were liable to be wonky.

 

[AdiosVista]

Yes, I get "loading disk" with the first Untitled drive. I figured since it was grayed-out, anything Disk Utility told me about the "Untitled" drives were liable to be wonky.

That is reassuring to hear, glad I'm not the only one seeing that. Thanks again for the insight!

 

[m4v3r1ck]

I had the exact reading in DU in my clean installed OS X 10.11.3 (the very first release of El Cap that I installed) for my MAC_SCRATCH RAID 0 disk. Trying to mount the "Untitled" RAID slices in El Cap, but no luck. After rebooting into OS X 10.10.5 (main OS) again, I stumbled onto a crippled RAID 0 / 2 SSD's in a USB 3.0 / eSATA external enclosure!

I forgot to make my own DU screen-cap in El Cap...

I know a RAID 0 needs a very strict back-up scheme, so using Carbon Copy Cloner daily on all drives I can easily restore the data. Nevertheless I want to troubleshoot this and share the results here. Any directions how to start to troubleshoot (perhaps with terminal commands) of this issue?

Here the both SSD's output in DU:

Verifying partition map for “Samsung SSD 840 EVO 500GB Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitionsChecking booter partition disk8s3
Verifying file system.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Boot OS X appears to be OK.
File system check exit code is 0.
Checking Core Storage Physical Volume partitions
The partition map appears to be OK

Verifying partition map for “Samsung SSD 840 EVO 500GB Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitionsChecking booter partition disk10s3
Verifying file system.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Boot OS X appears to be OK.
File system check exit code is 0.
Checking Core Storage Physical Volume partitions
The partition map appears to be OK

Using DU in OS X 10.11.3 to check my disks, I'm now left with my FIRST Apple Software Raid (RAID 0 or 1) slice failure EVER!!!!!.

Cheers

 

[m4v3r1ck]

[RESOLVED] I set up a new RAID0 and cloned my CCC data back to it!

I had the exact reading in DU in my clean installed OS X 10.11.3 (the very first release of El Cap that I installed) for my MAC_SCRATCH RAID 0 disk. Trying to mount the "Untitled" RAID slices in El Cap, but no luck. After rebooting into OS X 10.10.5 (main OS) again, I stumbled onto a crippled RAID 0 / 2 SSD's in a USB 3.0 / eSATA external enclosure!

I forgot to make my own DU screen-cap in El Cap...

I know a RAID 0 needs a very strict back-up scheme, so using Carbon Copy Cloner daily on all drives I can easily restore the data. Nevertheless I want to troubleshoot this and share the results here. Any directions how to start to troubleshoot (perhaps with terminal commands) of this issue?

Here the both SSD's output in DU:

Verifying partition map for “Samsung SSD 840 EVO 500GB Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitionsChecking booter partition disk8s3
Verifying file system.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Boot OS X appears to be OK.
File system check exit code is 0.
Checking Core Storage Physical Volume partitions
The partition map appears to be OK

Verifying partition map for “Samsung SSD 840 EVO 500GB Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitionsChecking booter partition disk10s3
Verifying file system.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Boot OS X appears to be OK.
File system check exit code is 0.
Checking Core Storage Physical Volume partitions
The partition map appears to be OK

Using DU in OS X 10.11.3 to check my disks, I'm now left with my FIRST Apple Software Raid (RAID 0 or 1) slice failure EVER!!!!!.

Cheers