-
Gspeed ES Pro RAID keeps disappearing from Mac, have to re-initialize!
-
Now Jesse,
you have had the right thought. Get a new raid system! And for heavens sake run it on Raid 5 and not 0. Alex has given you his recommondations. I recommend a Sonnet R800 SAS with Hitachi HUA’s in it. It takes 8 Harddiscs, so you end up with enough storage to cover your 10 TB on Raid 5!
Cheers
Rainer
factstory
Rainer Wirth
phone_0049-177-2156086
Mac pro 8core
Adobe,FCP,Avid
several raid systems -
Thanks for the recommendations. Unfortunately I don’t have thousands of dollars to drop on a new raid. I need my G Tech gear to work now, so I’m more interested in solutions to my problem that can be achieved this week.
jesse
-
Spent a while on the phone with G Tech today. The AJA system test says the raid is working perfectly, and the ATTO config tool says the same. We are left with one theoretical answer & workaround:
Since my data was filling up just over 90% of the raid, this must be what causes the glitch. Why this happens, no company involved can say. I am currently shuffling data around, and will be housing my media on the raid – plus one additional G Drive via Esata (I can afford an Esata card, not a new raid setup). This will hopefully keep my system from no recognizing the raid.
jesse
-
[Jesse Schluntz] “This is strange because I had 2.68 TB left on the raid, and was copying 2.45 TB over to it.”
The file system has an overhead which varies depending on block size, number of files, their sizes. E.g. it’s theoretically possible for 1TB of data to take 16TB of disk space (or more) if the volume isn’t formatted properly for the application.
Do you have the stats for the data you’re copying – number of files, total size, total size on disk? (Two last numbers are never the same – at best, the last is just slightly larger than the 2nd.)
Also, how is the RAID (and volume) formatted? RAID level, stripe size, any other parameters? Next time you re-initialize it, re-format it as well. Volume: block size, file system type? Is journaling on?
Possibly it’s a FS glitch that you are running into, where the OS just can’t handle when the volume gets too close to being full.
Possibly something else is going on – but for now, it’s clearly the problem between the FS (OS) and RAID brain. Someone, somewhere, is not reporting the capacity correctly to the OS, and the OS flakes out and marks the whole volume offline.
So for now, I’d just leave a 500GB headroom on the array and consider it full when you get half a terabyte close to the limit.
Alex Gerulaitis
Systems Engineer
DV411 – Los Angeles, CA -
Hello, I just had the same problem and its the third time it happens, it always happen when is am copying files.
-
Congratulations. You’re the 2nd person G Technology has ever even heard of having this issue. Here’s what I can tell you for now:
If you’re configured at RAID 0, do not fill the raid up to within 3.2 TB of filling it. I had to sacrifice that much space to get my setup functional. Right now I have about 3.8 TB empty, and will have to work off both the raid and an external esata drive in order to not crash the raid again.
Totally sucks, I know, but if this works for you thank the good Lord you asked me because I spent weeks and weeks figuring this out. I literally swapped out every major component from my computer itself to the raid itself.
jesse
-
I am having exactly the same problem, what i do is i don’t le the raid pass the 8 tb marker because it always fail with this amount of data.
G speed es pro is the worst purchase i have ever made, novody knows what is the issue and GTech Atto and apple just throw away the ball.
My advice is don’t G-SPEED eS PRO, go with the promise 16 TB thunderbolt Raid,
-
Jesse,
Thank you for all your hard work, time and effort that went into trying to solve this problem. I too had a raid config of (RAID 0) which worked great for 2 months until one fine day i had run into your exact problem while copying data from day 6 of this feature film.
I am in no position to be purchasing new raids like those above have recommended. I was prompted with the exact same (error -36) and just like you, had the raid disconnect upon start-up. I was once however able to re-mount it by clicking (auto-map) however once i restarted my mac pro tower, that option no longer worked no matter how many times i restarted, force shutdown, re initialize etc. So once again, I reconfigure to a new (raid 0) setups and yet without even any data on the raid – The problem persists.
And now.. I sit here in moments of pain, having to re-transcode 2 weeks of shooting (thank god I have a red rocket) and I’ll be reconnecting all my media to my auto-saves. I’m now rebuilding on a (raid5) configuration and hoping to god that this new raid configuration will do the trick.
Sorry to hear about your troubles.. i sympathize with you…
-
I’m happy you won’t be going through all the same troubleshooting steps my friend! Automap didn’t help me much either, and when it did most of the data didn’t register anyway.
I wound up finishing my last feature using the raid plus one additional external drive to compensate for the needed space, renders, etc.
jesse
-
Hi Jesse and all others coping with such a nightmare.
At least Jesse, you are not alone with your problem. What do we learn? The G-tech hardware sometimes has its Monday productions.
Personally I wouldn’t touch this hardware – even if you can save some bucks, go for better hardware. We’ve got a Sonnet SAS R800 working for years flawlessly. There are a lot of other brands out there as good and reliable as Sonnet, but definitely not G-tech. If you scroll in this forum you will find a lot of threads with problems with G-tech products.
Throw it away and buy a decent piece of hardware – with no hustles for the future – in the end it’s cheaper.
The best raid is one you forget about that its there – A Raid has just to work, work, work.cheers
Rainer
factstory
Rainer Wirth
phone_0049-177-2156086
Mac pro 8core
Adobe,FCP,Avid
several raid systems
Reply to this Discussion! Login or Sign Up