[khiltd]

Defaults cannot descend into the property list hierarchy, so it probably isn’t ever going to work for anybody. You either have to do it manually through the scripting language of your choice or throw plistbuddy on there and use that.

[khiltd]

Defaults probably isn’t going to be able to get to it very easily, but that’s in com.apple.systemuiserver.plist if you want to muck around with the array. You could also just delete /System/Library/CoreServices/Menu Extras/TimeMachine.menu from the drive.

[khiltd]

Well nobody uses VPNs because they’re speedy; all that security comes at a price.

[khiltd]

Same thing happens to me when accessing public shares over Bonjour, only the delay is not quite as lengthy; maybe 10-20 seconds. I think Leopard’s Finder is simply killing some aspect of the connection when you navigate elsewhere.

[khiltd]

Well if you ordered them from newegg or something they may have been pulling from old stock with a lesser firmware revision, and there are often subtle variations in products over time which may not always be obvious from catalog descriptions (Linksys WRT54G anyone?).

I have a script that will let you check when exactly yours was made here:

http://www.khiltd.com/seagate.html

If the result predates the card, there may be a compatibility issue. Apple’s markup on peripherals is beyond obscene, but if you aren’t positive the cheaper option is going to fly, sometimes your time is worth more than the hundred bucks you’d save buying elsewhere.

[khiltd]

Although there’s a tremendous security hole there, it works perfectly for me on 5.2.4. I’d make sure the query string isn’t getting mangled by something else before finding its way to the command sent by exec.

[khiltd]

I doubt it’s anything more sneaky than requiring ECC DIMMs. Call Apple support and ask what the specific requirements are for that card.

[khiltd]

[QUOTE][u]Quote by: samoir[/u][p]
Im begginning to think there is embeded Apple Hardware on the drives that is required.[/p][/QUOTE]

That’s just ridiculous. Drive manufacturers submit production models to Apple, and Apple engineers then qualify the drives for use with prototype Apple hardware. At the end of this process a list of drives which survived the testing matrices is compiled and passed on to purchasing who then selects the cheapest model which performs as needed. Haggling takes place as the manufacturers strive to win the big contract, and eventually one or two models are selected for a production run. Sometimes, when a minor deviation from a published specification is the only thing keeping an otherwise good (or cheap) drive from qualifying, the manufacturer will alter their firmware in order to correct the problem, but I have never heard of anyone building a custom firmware version specifically for units which are sold to Apple. They simply don’t have the marketshare to make such a demand of any manufacturer. I don’t know of anyone who does.

A very, very long time ago when 30MB hard drives were considered expansive, all drive manufacturers would allow OEM purchasers to poke a custom vendor string into the firmware, so instead of a “SEAGATE” you’d see an “FWB” or “APPLE” if you happened to be a driver engineer, but that’s as far as that ever went. The practice was abandoned completely as specifications stabilized and manufacturers started adhering to them more rigidly. Anyone who puts out an “SATA” drive that does not comply with the SATA spec isn’t going to sell very many drives.

What you’re saying is not impossible, but it is infinitely more likely that the drives you have are simply inadequate or that something is being configured incorrectly. I’m not familiar with Apple’s current RAID driver sources, but mismatched DMA modes is one thing that can definitely cause some problems. I’m sure there are other factors as well.

[khiltd]

When the drive refuses to mount does it have an entry in the IORegistry or is it completely AWOL?

[khiltd]

Again, the return value is largely irrelevant. What is being written to stdout and/or stderr?

This works fine for me:

[code]#! /usr/bin/php

[/code]

Output when invoked:

[code]> ./sipstest.php /Users/nate/samples.jpg

Running sips as uid=502(nate) gid=20(staff) groups=20(staff),98(_lpadmin),80(admin)

[ (kCGColorSpaceDeviceRGB)] ( 0 0 0 1 )
/Users/nate/samples.jpg
/Users/nate/sipsthumb.jpg
[/code]

[khiltd]

“Brand new” isn’t necessarily synonymous with “working.” Have you run any tests on them?

I’d try leaving it alone a little longer, check the connections and also make sure you’re not mixing DMA modes on the bus. Can’t think of anything else off the top of my head. If they really wanted to stop you from using other drives they probably would have just had the driver ignore them altogether.

[khiltd]

I don’t have access to such a machine, but it wouldn’t make much sense for Apple to tether the card to one particular drive since they do not make them and switch models frequently. It’s certainly possible, but not very intelligent on their part. I think they even stopped policing opticals in the DiscRecording framework–just way more trouble than it’s worth.

How long does the array show up as degraded? Are the replacement drives known to be working properly and do they move data fast enough? Seagates are anything but bulletproof, so you might want to try more than one set to narrow it down.

[khiltd]

And what PHP version is running on each? Different versions have different default settings which will be applied regardless of the fact that they are not explicitly defined in php.ini. In particular you’ll want to make sure safe_mode and open_base_dir are off. You should also be certain that /usr/bin/php is in sync with whatever Apache is using; they are frequently two completely different things.

The return value of exec is also not particularly useful. What’s in the output?

And you’ll also want to make sure you’ve read up on all the differences between the execution environments. mod_php runs differently than the command line version: http://www.php.net/manual/en/features.commandline.php

Ultimately, if your application is written in Perl then I think you should probably focus on doing [i]this[/i] in Perl and cut out all this extraneous indirection.

[khiltd]

Again, nobody can really say why it isn’t working until we know what specifically isn’t working. Is it running and generating an error or is nothing happening at all? Are you supplying a full and accurate path to the binary? Is anything in your php.ini file preventing access to that binary? Is PHP being run as an Apache module or as a CGI application, etc etc etc

[khiltd]

To the best of my knowledge, no Apple mass storage driver performs any sort of vendor string based rejection; a drive is a drive.

Step-by-step instructions are in the docs: http://images.apple.com/server/docs/RAIDAdmin1.2_121406.pdf

[Author]

Posts