Jesse Schluntz
Forum Replies Created
-
THE END OF THE TROUBLESHOOTING ROAD…
Today was D Day for troubleshooting. At this point I have tried:
– reinstalling the OS
– changing out the graphics card
– swapping out the ram
– having ram board replaced
– swapping out the ATTO raid card
– swapping out the raid
– swapping out the cableAll with the same error code -36 resulting in the same, predictable way during the final hours of copying footage back onto the raid late last night. The only thing left to do is replace the computer. I’m on hold with Apple waiting for a senior advisor right now…
-
What version of OSX ?
10.7.5
All these externals FW800 ? Always using the same FW800 port on ya macpro ?
YES AND YES.
If you can get 500Gig onto the Raid I’d try duplicating that 500Gig. Then dupe the 1TB..
See if that balks it.
Also
https://blogs.discovermagazine.com/badastronomy/2008/03/30/mac-os-tip-for-er...INTERESTING LINK. I APPRECIATE IT, BUT MUST ADD ONE MORE PART OF THE STORY:
MY COMPUTER HAS LOST COMMUNICATION WITH THE RAID IN THE PAST WHEN COPYING FILES WAS NOT EVEN PART OF THE EQUATION. I WAS HAVING BOOT ISSUES, WHICH I TOOK MY COMPUTER IN FOR REPAIR AT THE APPLE STORE 3 TIMES, AND SOMETIMES WHEN THE COMPUTER WOULD REBOOT, MY RAID WOULD BE GONE FROM THE FINDER AND I’D HAVE TO RE-INITIALIZE.
JESSE
-
I’d suggest 2 things.
But 1st. Have you ever successfully dragged and dropped 10TB via finder onto this raid?
NO. TYPICALLY I COPY IT OVER 1 OR 2 OF THE BACKUP DRIVES AT A TIME. USUALLY IT’S 2 FIREWIRE 800 DRIVES AT A TIME (OVERNIGHT), EACH WITH ABOUT 2 TB OF MEDIA.
To copy that amount of data you should be verifying and I wouldn’t use finder to do 10TB :-/
Try Chronosync
https://www.econtechnologies.com/pages/cs/chrono_overview.html
..and turn verification on.That way hopefully CS will flag an issue not the OS panics..
I’LL LOOK INTO THIS. BUT AGAIN, I’M NOT COPYING 10 TB AT ONCE. I HAVE 5 BACKUP DRIVES THAT I HOOK UP IN NO PARTICULAR ORDER AND COPY THEM OVER.
THE ISSUE NEVER OCCURS WHEN I HAVE THE SAME DRIVE OR FOLDER COPYING OVER, NOR DOES IT ALWAYS OCCUR WHEN I HAVE, SAY, 2 HOURS OF COPYING LEFT. LAST WEEK WHEN THIS ISSUE HAPPENED, THE FINDER SOMEHOW WENT FROM NEEDING A FEW HOURS TO FINISH COPYING TO “2 DAYS”, THE DATA TRANSFER SPEED CRAWLED, AND THE “STOP COPYING” OPTION WOULD NOT WORK.
JESSE
-
Are you sure you don’t have a corrupt file in your backup your copying across ?
YES. THE -36 ERROR HAPPENS ON RANDOM FILES, AND ALWAYS DURING THE FINAL STRETCH OF FILE COPYING.
How are you restoring your media ? Not just drag n drop in Finder?
YES. DRAG FROM EXTERNAL BACKUP DRIVES TO THE RAID. WORKED PERFECTLY FOR ABOUT 9 MONTHS. ISSUE STARTED A COUPLE MONTHS AGO.
-
Screen shots from this latest issue:
-
OH MY GOSH… IT HAPPENED AGIAN!
After swapping out the ATTO card with a new one and having the same issue, I purchased a new MINI SAS cable and received a replacement RAID from G Technology. These were my last two possible causes of the problem.
Since the RAID always seemed to vanish off my computer during the home stretch of file copying (final few hours of 10 TB), I reasoned it must have had something to do with my original RAID. I skipped swapping out the new cable and went for the newer RAID.
This morning, after two days of restoring the files, I came into the office and found the same error code (-36), followed by the standard clicking of “OK”, then opening the raid to find zero files on it.
The strange thing is that when the -36 error code appears, the files disappear off the RAID, but the RAID reads out as being mostly full (which it should). It’s when I restart that the OS (not the config tool, the OS) loses communication with the RAID and forces me to re-initialize it.
I restarted and got the usual “disk not readable” drive warning, and had to re-initialize the new raid again on disk utility.
I am not onto the final step, swapping the mini SAS cable. If this doesn’t fix the problem, I’m going to have to demand a new computer from Apple.
UNBELIEVABLE…
jesse
-
Sorry Simon I misread your post. Here is my correct question:
Why is diskwarror bad to use on a raid?
thanks
jesse -
I agree Simon. Would’ve been far easier to diagnose the issue if the same company was responsible for everything that’s connected to my computer rather than ATTO for the card, G drive for the raid and another company for the cable. Is there any company who sells complete setups?
Why is diskwarrior bad for raids & external HD’s in your opinion?
thanks
jesse -
PROBLEM SOLVED???
I installed the new ATTO raid card in my tower, hooked up the original raid & cable, and began copying data back over from the backups.
After the standard, 2 days of copying multiple TB’s over, the transfer speed slowed to a crawl (suddenly 7 hours of data was supposed to take 2 days). I was unable to get the finder to stop copying or to log out, so I did the usual last resort, forced shutdown.
Sure enough, the raid icon had disappeared from the desktop again, and the familiar “can’t recognize the disk” message was on my desktop.
My only 2 remaining troubleshoot options after this new ATTO card were replacing the mini SAS cable or the raid itself. At this point I firmly believe it’s the raid. Why else would the raid go offline whenever I’m on my final day of file copying? My rationale is if the raid always vanishes once I’m almost finished rebuilding, it must be failing hardware.
Is there anyone out there who thinks this could somehow be the mini SAS cable?
I’ll confirm this whether this works next week once the new raid is up and I’m able to work on it with no issues.
jesse
-
Unfortunately it takes several days for the Raid issue to manifest, so each of these three troubleshoot steps will take a while.
I’m in the process of reloading all 10TB of data now via the new ATTO card. If I do this and can edit for a couple of days, it’s probably fixed. If not, I test the cable, then the new raid itself. Its so frustrating not knowing which part it is!
thanks
jesse
