10-13-2009 09:39 AM
I bought the BlackArmor 440 based on years' satisfaction with Seagate's hard drives, their speed, reliability and Seagate's outstanding replacement policy. The 440 was to be a destination for critical file backups, primarily from a MacPro workstation running OS 10.6.1. After the initial problems with the setup wizard freezes (see other post), I began to experience problems, from the Mac platform, with the backup software being unable to write to a mounted BA share with full write privileges. I tried some straight Finder drag and drops on the desktop, and found that some folders and files within folders that were dragged and dropped to the BA share would become inaccessible, i.e., would not allow me, with admin privileges on the Mac to subsequently delete the files or folders once they were copied to the BA share. I got a consistent error -8072 message. A little red no access / no write symbol would sometimes appear on folder icons copied to the BA share, indicating that the current user (me with admin privileges) had no write privileges to the folder, even though I had just copied it to the BA. (Yes, I performed the 'repair permissions' routine - w/o finding any that needed repaired). Sometimes the folders would not contain the files they contained on the source drive. I checked, double-checked and re-created users, volumes and shares on the BA, hoping I was missing something with user privileges or access settings on that end. Still random problems occurred. I contacted Seagate and after forwarding my problem to a 2nd tier tech person, I was informed on 10-13-209,
"I researched your case further, and wanted to share with you that at this point in time the drive isn't supported with the new MacOS 10.6.1.
The only aspect of it that is supported is mapping the drive, anything else will take a few more weeks, until our design team will release any additional information for using the drive with the new MacOS, as well as any possible software updates."
I'm hesitant to carry out the same copy / delete tests on the one Windows machine in the office. Anyone have any strange read/write/privileges problems in particular on Macs, or in general?
It's hard to be critical of a company that's been around for so long, and actually has English speaking fairly knowledgeable techs available at toll free numbers on weekends and holidays, but one would think marketing would place a little more priority on end-users' ability to actually use their product, and less on selling what is for now a useless warm brick sitting in an office. It's not like Seagate's 'design team' didn't have access to Apple's software developer's kit for months prior to the release of Snow Leopard, eh?
Any comments or work-arounds would be appreciated. And Seagate, please announce the release of a fix when it's finished, instead of just posting it and hoping it gets disseminated by word of mouth.
10-15-2009 09:54 PM
How are you mounting your NAS, smb or nfs? I've had different kinds of problems with both. I know that this doesn't answer any of your questions, but I'll share my experience since I'm also having problems using this thing on my mac and have yet to find a suitable workaround via either protocol. To start, I'm running 10.6.1 on a dual quad core with 8GB ram. here goes:
I'm able to mount it either as a startup item or by hitting command+k manually. I can access it from the finder and create and delete files, but the perfromance is ABYSMAL. I'm moving a 180GB iTunes library to it via smb and it's probably not going to complete until sometime tomorrow, and I started the consolidation yesterday around this time. It only seems to write in bursts and I'm getting an average of about 30kb/sec throughput. That's kilobytes, folks. Just terrible. My system log is also full of these types of errors, to which there is little information via google:
Oct 15 21:13:01: --- last message repeated 5 times ---
On the command line it works fine, much faster than SMB (though I need to wait for my iTunes library to finish consolidating before running any performance tests to get actual numbers), however when I access the share via Finder it doesn't work at all. It just spins forever trying to open the folder. For some godforsaken reason that I can't uderstand, this thing defaults to all_squash on nfs mounts and you can't change it. I can't really fathom why seagate decided this was the way to go. I hope there is some technical reason but I can't think of a good one. I have a centos box and set up an nfs server on it and was able to mount it up on my mac no problem, until I enabled all_squash. Then all kinds of stupid things started happening so I can only assume the problems with the Blackarmor are related to this ridiculous, unchangeable option.
I would honestly prefer to use nfs, but if it's not going to let me write files & folders to the thing with my uid/gid then it's kind of pointless.
I also have a windows box on my network that I'm going to try this on to see if it's a mac specific issue or not, but like I said I want to wait for my iTunes to finish copying over. The last thing I want is for that copy to crud out 75% of the way through a 2 day process, though to be honest if I don't find a solution I'll probably end up returning the device. I will post again when my iTunes is complete and I've tried varoius scenarios, but so far this device has been very disappointing.
11-16-2009 02:52 PM
11-07-2010 06:17 AM
What an frustrating experience. The BA110 will not allow me to drag & drop any data files via the Mac OS 10.5.8 and 10.6.4. I installed their latest firmware and still no success. I gave up and bought a similar product from a company starting with a "W". Way to go.
When does Seagate recognize that there are many Mac users out there.