HT2497 apple software won't mount on an apple computer

Airport Utility 5.6 for Lion won't install on Lion (oh, yeah, Apple makes it a challenge to figure out what 'Lion' means: computer only says 10.7.x; web only refers to 'Lion' without numbers; sorry, I don't memorize how all cats map to all numbers). Is it 1997 all over again? I hear Steve Jobs rolling over in his grave.
file://localhost/Users/marrett/Desktop/AppleSoftware.tiff

Ironically AU 5.6 for lion will not install in Lion after about .2.. so 10.7.5 you are already out of luck.. Apple decided you no longer should have such a useful utility.. but it is easy to fix.
Here is one method.. just search there are many people who have listed it.
How to load 5.6 into later Lion & ML
1. Download 5.6 for Lion.
http://support.apple.com/kb/DL1482
Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
Leave the package open on the desktop so you can see the file. AirportUtility56.pkg
2. Download and install unpkg.
http://www.timdoug.com/unpkg/
Run unpkg on the desktop.. If your Mac refuses to run the software, because it wasn’t downloaded from the Apple store, go to security in preferences and allow other software to work.. this is limitation of trade methinks. You can set back later if you like.
Now drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. in finder, open the new directory, drill down.. applications, utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
You cannot uninstall version 6 (now 6.3 if you updated) so don't try.. and you cannot or should not run them both at the same time.. although I have had no problems when doing so.

Similar Messages

External drive won't mount- which software is best for data recovery?

Hi,
My external OWC drive won't mount to the desktop. It is visible in Disc Utility, but can't be manually mounted from there. Verify and Repair disk functions state that the disk appears ok (log below):
Verify and Repair volume “OWC Mercury Elite AL Pro mini”
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 OWC Mercury Elite AL Pro mini appears to be OK.
Drive lights up and spins. No weird sounds, just won't mount.
Not everything on the disc was backed up before the problem occurred. It's still under warranty with OWC, but I'd like to attempt to recover the data before sending it in for repair/replacement. The OWC tech on the phone said he's never seen this specific problem with this drive.
I'm thinking Data Rescue 3 would be the best software to try, but does anyone know of any other options to try first?
Thanks!

JohnDoe2009
I concur with the previous poster that if Disk Utility found no problems running TechTool Pro, Drive Genius or Disk Warrior might get it going. If you don't have any of those you could try
• Download and install Applejack
• Restart computer holding down Command + S
• When Command line comes up type in
+applejack AUTO+
Let is run all five functions.
In terms of Data Recovery
DataRescue 3
Virtual Lab
FileSalvage
are all excellent tools, and all offer a demo version.
Dr. Smoke's FAQ Data Recovery offers excellent tips on how to do it.
Good luck.
cornelius

My WD hard drive won't "mount" it shows in disk utility but can't be repaired. I'm thinking this is a software issue since the disk is being recognized.

I
I have a WD drive that won't "mount". Tried repairing, turning off and back on, unplugging and nothing has worked. Can anyone help?

The WD Passport has no independent power supply, relying instead on getting power from a USB port on the computer. AS the drive ages it can need more power to spin the platter and many USB ports on notebook cannot provid that much.
Anther issue is the WD drive itself. WD uses an odd proproprietary formatting scheme that makes the drive not always behave like typical Mac drives.
If the drive contains nothing you need to access, use Disk Utility to reformat it to "Macintosh Extended (Journalled)"
If the drive contains important data, there are a couple of inexpensive ways to get more power to it:
1) Get a "Y" conenctor cable like this:
http://eshop.macsales.com/item/OWC/USB2AYMBPB/
It draws power from two USB ports and ofter that is enough to make the drive work.
2) Get a powered USB Hub:
http://eshop.macsales.com/item/NewerTech/USB2HB7PRO/
It has its own power brick and that is usually enough to get an older USB external drive recognized.

WD Portable Hard Drive Won't Mount

This is the second time I have had a portable hard drive that suddenly quits mounting on the mac. First, a Lacie, and now a WD. After working with apple support and trying everything I could never get the problem fixed with the Lacie. Luckly, when I plugged it into a dell PC it came up and I was able to recover all data.
I then purchased the new drive, the WD, and copied the information over. Today, the WD quit working. It will not mount on either of my Macs, IMAC G5 and a powerbook G4. It also unfortunately will not show up on a PC either. It is a combo, firewire/usb drive. It does show up in Disk Utility but will not let you select "mount" only "info" and "eject".
Long story short....anyone have any ideas. I read some posts about data recovery with "data rescue" and other products. If I can't get it to mount, can I still get the data off?
Help!!

If software won't do it - you'll try it all if it's important enough - there's the costly way; disk recovery specialists.
It's a cruel lesson, but I'm sure you'll have a better back up system / procedure in the future. Ideally save to two disks and keep a third set of (important) back ups off site.

External HD won't mount (plus other problems now)

I have a LaCie 1TB that stores my Time Machine backups that now won't mount.
I actually have had a litany of issues since yesterday afternoon, which I'll list here - - perhaps all just coincidence?
iTunes offered to update our iPad 2 to iOS 5.
     Did that fine.
iTunes then offered to update my iPhone 4 (Verizon version; 3G network) - - which surprised me as I thought it wouldn't be compatible with iOS 5
     The download of the iPhone iOS 5 indicated it was over 750mb in size and took an hour or two just to download the iOS.
     Software extract failed and iTunes indicated it couldn't verify my iPhone with Apple - try later. Got same results several times, leaving my iPhone apparently in a 'new' pristine, empty state.
     iTunes no longer recognized my iPhone and offered to restore it, but it wouldn't restore as Apple couldn't verifty it.
     As far as I knew, I now had a new(ish) empty iPhone after 10 months of app downloading etc (though I hoped my backups were still on my iMac
Then I noticed shortly after all of the above that my wireless router (Cisco Linksys E1000) had suddenly failed - - its bank of lights were blinking and I had no wi-fi.
     I wired direct between the iMac and cable modem which at least got the iMac on the internet.
Then I tried following suggested steps at Apple.com support to restore/repair iPhone issues, one of which included ensuring all iMac software wals up to date
     Sure enough, it wasn't - there was a new Security Update 2011-006 plus iPhoto update and 1 other I don't recall
     It was a 569mb download in all which took 5-6 hours to download (THAT seemed awful slow as did the earlier iOS 5 download - and this was direct throught the cable modem).
     The iPhoto update failed but apparently the other two updates were installed successfully
Re-started iMac and noticed my external 1TB LaCie was not mounting
In the midst of all of the above - at one point I'd had my iPhone connected by USB and using the direct cable internet access I thought I'd try iTunes again to restore the iPhone - - no luck again.   HOWEVER, letting the iPhone sit there in its blank state for several minutes, it suddenly came to life on its own with no software interaction. Up popped the password screen on the iPhone, I entetered my PIN and there was my iPhone in its normal state (what the ?????)
So I have my iPhone back in its normal state under iOS 4.2.10 with apparently every app still on it - - this without a backup restore. Why it was dead - with only the iTunes + USB connector picture on its window before - I have no idea.
But - -I'm without my external HD. Disk Utility won't give me an option to mount it.
Any thoughts? (and sorry for the long post - - this has been a frustrating 16 hours so far)

Hi whatstin
See the lower part of > http://support.apple.com/kb/HT1317
+1. Shut down the computer.+
+2. Disconnect all devices and all other cables, except the keyboard and mouse cable(s).+
+3. Disconnect the computer from the power outlet and wait for 3 to 5 minutes.+
+4. Plug the computer back in and turn it on.+
+5. Reconnect the device(s) (one at a time if there is more than one) and test. Test with each port if you have more than one.+
If nothing then try a different USB cable.
If still nothing contact WD support @ http://support.wdc.com/?wdc_lang=en
Dennis

Two seperate external hard drives won't mount

HELP!
Neither of my external hard drives, both AC powered, suddenly won't mount. I've swapped all the cables and ports but no joy - it can only be the mac. Any idea?! Maybe I haven't mounted them since the last software/ security update, I can't remember...
I feel like everything is breaking down one by one and it always seems to be the result of an update.

Ok, a small amount of success.... I've figured out that it's the USB adapter (Apple - The one I got with my ipod). So I changed the fuse in the actual plug, and that works fine with the laptop charger connected but not the USB part of the adapter plug - the actual square adapter than hooks onto the plug... So what can I do about that? is there another fuse inside that? I can't seem to get it open - Do I just need to buy a new one?

Volume won't mount - xsanctl returns error 5

Dear List,
One of our Volumes has failed to remount following scheduled software updates and cvfsck disk utility run. PromiseGroups, the problem volume starts, shows up in cvadmin and the GUI but won't mount either through the GUI or CLI.
Recent filtered fsmpm Log displays the following:
713 17:37:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:38:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:39:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:40:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:41:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:42:40] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:43:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:44:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:45:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:46:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:47:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:48:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:49:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:50:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:51:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:52:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:53:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:54:11] 0xa033f720 (debug) NSS: FSS mount list for client 10.0.0.8 (id 129.11.67.18) - Promise1, XRAIDScratch, Promise2, PromiseGroups
[0713 17:54:13] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:54:19] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups' disconnected.
[0713 17:54:19] 0xa033f720 (debug) FSS 'PromiseGroups' REGISTERED -> DYING, next event in 60s
[0713 17:54:19] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:54:19] 0xb040f000 (debug) Portmapper: FSS 'PromiseGroups' (pid 6192) exited with status 18 (transient error)
[0713 17:54:19] 0xb040f000 (debug) FSS 'PromiseGroups' DYING -> RELAUNCH, next event in 10s
[0713 17:54:19] 0xa033f720 INFO NSS: Active FSS 'PromiseGroups[1]' at 129.11.67.19:55742 (pid 6192) - dropped.
[0713 17:54:19] 0xa033f720 (debug) NSS: removing vote inhibitor for FSS 'PromiseGroups'.
[0713 17:54:23] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:54:28] 0xb040f000 (debug) FSS 'PromiseGroups' RELAUNCH -> LAUNCHED, next event in 60s
[0713 17:54:28] 0xb040f000 NOTICE PortMapper: RESTART FSS service 'PromiseGroups[1]' on host xsanmdp.leeds.ac.uk.
[0713 17:54:28] 0xb040f000 NOTICE PortMapper: Starting FSS service 'PromiseGroups[1]' on xsanmdp.leeds.ac.uk.
[0713 17:54:28] 0xa033f720 (debug) FSS 'PromiseGroups' LAUNCHED -> REGISTERED
[0713 17:54:28] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups'[1] (pid 7545) at port 63518 is registered.
[0713 17:54:29] 0xa033f720 INFO NSS: Standby FSS 'PromiseGroups[1]' at id 129.11.67.19 port 63518 (pid 7545) - registered.
[0713 17:54:29] 0xa033f720 (debug) Heartbeat from ID 129.11.67.19 updating LOCAL PromiseGroups to 10.0.0.9:63518
[0713 17:54:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:55:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:56:16] 0xa033f720 INFO NSS: Starting vote for FSS PromiseGroups using 1 voting member: 129.11.67.19.
[0713 17:56:18] 0xa033f720 (debug) localfssvote: WINNER PromiseGroups at 10.0.0.9:63518.
[0713 17:56:18] 0xa033f720 (debug) tally_member:FSS/PromiseGroups COUNTED 0 vote for 10.0.0.8:60597 from member 129.11.67.19:49153
[0713 17:56:18] 0xa033f720 (debug) tally_member:FSS/PromiseGroups COUNTED 1 vote for 10.0.0.9:63518 from member 129.11.67.19:49153
[0713 17:56:18] 0xa033f720 INFO NSS: Vote selected FSS 'PromiseGroups[1]' at 10.0.0.9:63518 (pid 7545) - attempting activation.
[0713 17:56:18] 0xa033f720 INFO NSS: Vote call for FSS PromiseGroups is inhibited - vote dis-allowed.
[0713 17:56:23] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups' disconnected.
[0713 17:56:23] 0xa033f720 (debug) FSS 'PromiseGroups' REGISTERED -> DYING, next event in 60s
[0713 17:56:23] 0xb040f000 (debug) Portmapper: FSS 'PromiseGroups' (pid 7545) exited with status 18 (transient error)
[0713 17:56:23] 0xb040f000 (debug) FSS 'PromiseGroups' DYING -> RELAUNCH, next event in 10s
[0713 17:56:24] 0xa033f720 INFO NSS: Active FSS 'PromiseGroups[1]' at 129.11.67.19:63518 (pid 7545) - dropped.
[0713 17:56:24] 0xa033f720 (debug) NSS: removing vote inhibitor for FSS 'PromiseGroups'.
[0713 17:56:33] 0xb040f000 (debug) FSS 'PromiseGroups' RELAUNCH -> LAUNCHED, next event in 60s
[0713 17:56:33] 0xb040f000 NOTICE PortMapper: RESTART FSS service 'PromiseGroups[1]' on host xsanmdp.leeds.ac.uk.
[0713 17:56:33] 0xb040f000 NOTICE PortMapper: Starting FSS service 'PromiseGroups[1]' on xsanmdp.leeds.ac.uk.
[0713 17:56:33] 0xa033f720 (debug) FSS 'PromiseGroups' LAUNCHED -> REGISTERED
[0713 17:56:33] 0xa033f720 NOTICE PortMapper: FSS 'PromiseGroups'[1] (pid 7563) at port 63713 is registered.
[0713 17:56:34] 0xa033f720 INFO NSS: Standby FSS 'PromiseGroups[1]' at id 129.11.67.19 port 63713 (pid 7563) - registered.
[0713 17:56:34] 0xa033f720 (debug) Heartbeat from ID 129.11.67.19 updating LOCAL PromiseGroups to 10.0.0.9:63713
[0713 17:56:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:57:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:58:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 17:59:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:00:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:01:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:02:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:03:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:04:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:05:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:06:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:07:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:08:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:09:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:10:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:11:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:12:40] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:13:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:14:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:15:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:16:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:17:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:18:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:19:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:20:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:21:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:22:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:23:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:24:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:25:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:26:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:27:36] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
[0713 18:28:35] 0xa033f720 (debug) find_fsm fsm PromiseGroups ipaddr 10.0.0.8 port 60597 TestLink failed: Connect timed out
Does anyone have a fix for this problem?
Geoff Cross - Systems Administrator (Macintosh)
 Apple Certified XSAN 2 Administrator • BakBone NetVault Certified Administrator
 ACTC 10.6  ACSP 10.6  ACS Deployment, Security & Mobility
Sections of Oncology and Biostatistics and Epidemiology
Leeds Institute of Molecular Medicine, Cancer Research UK Centre
Wellcome Trust Brenner Building, St James's University Hospital
Beckett Street, Leeds LS9 7TF

Here is system.log:
(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:38:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:38:42: --- last message repeated 1 time ---
Jul 30 09:38:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:39:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:39:43: --- last message repeated 1 time ---
Jul 30 09:39:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:40:12 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:40:42: --- last message repeated 8 times ---
Jul 30 09:40:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:40:42: --- last message repeated 1 time ---
Jul 30 09:40:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:40:48 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:41:18: --- last message repeated 11 times ---
Jul 30 09:41:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:41:42: --- last message repeated 1 time ---
Jul 30 09:41:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:42:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:42:42: --- last message repeated 1 time ---
Jul 30 09:42:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:43:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:43:42: --- last message repeated 1 time ---
Jul 30 09:43:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:44:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:44:42: --- last message repeated 1 time ---
Jul 30 09:44:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:45:47 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:45:47: --- last message repeated 1 time ---
Jul 30 09:45:47 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:46:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:46:43: --- last message repeated 1 time ---
Jul 30 09:46:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:47:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:47:42: --- last message repeated 1 time ---
Jul 30 09:47:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:48:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:48:43: --- last message repeated 1 time ---
Jul 30 09:48:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:49:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:49:42: --- last message repeated 1 time ---
Jul 30 09:49:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:50:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:50:43: --- last message repeated 1 time ---
Jul 30 09:50:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:51:02 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:51:32: --- last message repeated 19 times ---
Jul 30 09:51:32 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:51:42: --- last message repeated 2 times ---
Jul 30 09:51:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:51:42: --- last message repeated 1 time ---
Jul 30 09:51:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:51:43 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:52:13: --- last message repeated 2 times ---
Jul 30 09:52:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:52:43: --- last message repeated 1 time ---
Jul 30 09:52:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:53:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:53:42: --- last message repeated 1 time ---
Jul 30 09:53:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:54:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:54:42: --- last message repeated 1 time ---
Jul 30 09:54:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:55:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:55:42: --- last message repeated 1 time ---
Jul 30 09:55:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:56:23 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:56:42: --- last message repeated 6 times ---
Jul 30 09:56:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:56:42: --- last message repeated 1 time ---
Jul 30 09:56:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:56:53 xsanmdp mDNSResponder[31]: ERROR: getOptRdata - unknown opt 4
Jul 30 09:57:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:57:43: --- last message repeated 1 time ---
Jul 30 09:57:43 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:58:35 xsanmdp servermgrd[99274]: xsan: [99274/2425EA0] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:58:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Jul 30 09:58:42: --- last message repeated 1 time ---
Jul 30 09:58:42 xsanmdp servermgrd[99274]: xsan: [99274/103B90] ERROR: getquotas_for_fsmvolnamed(PromiseGroups): Could not connect to FSM because File System Manager "PromiseGroups" on 10.0.0.9 is on standby.
Cheers, Geoff

Help! My externals won't mount!

HELP!
Neither of my external hard drives, both AC powered, suddenly won't mount. I've swapped all the cables and ports but no joy - it can only be the mac. Any idea?! Maybe I haven't mounted them since the last software/ security update, I can't remember...
They don't show up in disk utility, so I can't do it that way either.
I feel like everything is breaking down one by one and it always seems to be the result of an update.

You don't say how the HDs are connected - USB or Firewire? If USB, will your mouse work in the USB port(s)?
Look at these links.
USB and FireWire Quick Assist
http://support.apple.com/kb/HT1151?viewlocale=en_US
What to do if your computer won't recognize a FireWire device
http://docs.info.apple.com/article.html?artnum=88338
Dealing with FireWire problems (drives not mounting, devices unrecognized, etc.)
http://www.macfixit.com/article.php?story=20041221081432908
Common fixes for USB device issues (unrecognized, etc.)
http://www.macfixit.com/article.php?story=20070824012114701
 Cheers, Tom

IPod won't mount in iTunes

Hello there,
I have a 20gb iPod that's nearly 3 years old & my PC is running Windows XP Professional with SP2. And I've got the latest version of iTunes (7.4.3).
Recently my iPod started behaving strangely, skipping during songs sometimes, and sometimes hanging for several seconds whilst playing.
Anyway, my big problem now is that the iPod won't mount in iTunes & iTunes hangs for ages when the iPod is connected.
The iPod comes up in Windows Explorer as a Removeable Drive called "Apple iPod". This leads me to believe that I may have accidentally put it into disc mode?
All the troubleshooting advice I've read suggests that if I can only get iTunes to recognise it, then iTunes should then automatically load the required software on to the iPod & everything will be hunky dory. That sounds all very well & good but iTunes is not currently seeing the iPod so it's not doing that.
As I've said, the iPod comes up in Windows Explorer, but if I do anything with it, even just right-clicking on it for example, Windows Explorer hangs as well.
Grrrrrrrr!!
I know it is not a cable problem or a PC problem as I have tried several different cables & 3 different PCs, all with the same results.
Please help!

I'm having a similar problem with my sons 3 generation Ipod Nano.
When I plug in my sons Ipod into my Apple G5 running OS X Version 10.4.11 and Apple Itunes 9.0.2... I too can't mount the Ipod on to Itunes.
What I found is that my son plugged his Ipod into a Windows laptop and reformatted his Ipod by accident for MS Windows... now my son is only 10 and didn't know what he was doing and would admit he did it.
How I found out was when I plugged in the two Ipods and hit Get Info
His Ipod Nano had: FORMAT: MS-DOS File System (FAT32)
and my Ipod Nano had: FORMAT: Mac OS Extended (Journaled)
I asked him and he admitted that... that's what he did... this is after 5 hours of trying to mount his Ipod.
Now here's the problem: His music and my music is all in the same account on the same computer (That being my G5)
My G5 running the most recent version of Itunes 9.0.2 recognizes all of our other Ipods except his which just shows up on the desktop of my computer... BUT DOES NOT DOW UP IN ITUNES UNDER DEVICES like all the other Ipods.
What I think I need to do is re format his Ipod Nano for Mac... Only problem is Itunes 9.0.2 doesn't allow that to happen.
Can someone point me in the right direction?
Thanks

IPod Photo 30G won't mount

My iPod won't mount. I visited the Apple Store in London to see what software I needed to access RAW photos I downloaded from Canon 20D while in Africa. The helpful person there attached my iPod to a powerbook and it mounted fine and we opened one of the photos to see that everything was okay. I bought OS 10.4 and iLife '05 and downloaded all the updates. The system profiler sees that I have the iPod attached and shows its title and info but it won't mount; doesn't open iTunes or show up in iTunes or on the desktop. I took the iPod to a local retailer and they attached it to a new Mac with a different Firewire cable and also a USB cable, didn't mount but was seen by system profiler. The photos are from two months in Africa and the thought of losing them makes me sick. Any ideas?

Try Putting iPod into Disk Mode
If that does not help, have a browse through the iPod Troubleshooting FAQ
Good luck.

Disk Image Won't Mount - Reason: Device Not Recognized

As I've searched the discussion forums, I've seen plenty of postings for "Disk Image Won't Mount" and for "Device Not Recognized" but not the way I'm seeing it on my laptop.
After a backup and restore, my mac will no longer mount any... and I mean any images. I have downloaded several security or software updates from different vendors and each .dmg file will not mount. I still have the .dmg files in hopes that after I get this problem solved, I'll be able to install them, but...
It always gives the same reason for not mounting and I'm at a loss on what to do next. I've run Software Update hoping it will be a quick fix, but have had no success.
Any suggestions?

I have a similar problem. Using FireWire disk mode, I put a disk image of my entire iBook onto my iMac as a back-up. (For an unrelated problem, Apple told me I needed to erase my iBook completely and do a clean install of the system.) Well, I screwed something up. I don't know what exactly--maybe I didn't "put away" the device correctly, but the next day when I flipped on my iMac, the disk image of my iBook was just gone, and not to be found anywhere. I finally succeeded in restoring the image using TechTool, which scanned the entire volume of the iMac for directory information. And it's all there, because the img file is more than 10GB. But when I double-click on it, I get the following error msg: "The following disk images failed to mount...reason--not recognized." I've checked the app it's supposed to open with, permissions, and run Disk Utility volume repair. No dice. Any ideas??? Did I mention that this is EVERYTHING I had on my iBook???

External Firewire drives power up, but won't mount.

I wanted to see if anyone else is having this problem. I recently upgraded my mom's laptop to OSX Lion after she experienced a lot of problems with Snow Leopard. All updates available from Software Update have been installed. Now 2 issues have arisen after the new install: 1) the FW 800 and 400 ports appear to be non-functional, and 2) the OS takes about 10 minutes to boot up to the desktop.
1) Regarding the FW ports: I have a couple external Firewire 800 hard drives that I use on other Macs so I know they're fully operational and mount without any issues. They're both 5400RPM drives that have been inserted into Macally external enclosures, and are of different capacities - one is 320GB and the other is 500GB. The enclosures offer FW 800, 400, USB 2.0 and mini-USB connectivity. But after upgrading the laptop I mentioned, neither of the drives will mount when using the FW 800 or 400 cables. They power up but won't mount, and they don't show up in the list in Disk Utility. However, the drives will power up and mount via USB.
I realize the laptop may have a hardware/port problem - but both 800 and 400 ports? Seems unlikely.
2) Any idea why it's taking the OS 10 minutes to boot up? I've shut down the laptop and rebooted it twice since the OS install, and both times took 10 minutes.
I may just install Lion on one of the hard drives, pull it and then pop it into the laptop to see if that makes any difference. Before I do that, can anyone recommend a hardware utility that can check the ports?
I welcome your suggestions.
Thank you.

Thanks for responding. Here's the info you requested. I'm not a systems guy so hopefully I've pasted in something that helps.
system.log report, after searching BOOT_TIME, here's one of the timestamps:
May 25 22:04:58 localhost bootlog[0]: BOOT_TIME 1337997898 0
Here's a chunk of the log after that timestamp:
May 25 22:05:00 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
May 25 22:05:13 localhost com.apple.launchd[1] (com.apple.powerd): Unknown value for key POSIXSpawnType: Interactive
May 25 22:05:13 localhost com.apple.launchd[1] (com.apple.sandboxd): Unknown value for key POSIXSpawnType: Interactive
May 25 22:05:18 localhost com.apple.pfctl[34]: No ALTQ support in kernel
May 25 22:05:18 localhost com.apple.pfctl[34]: ALTQ related functions disabled
May 25 22:05:18 localhost UserEventAgent[11]: starting CaptiveNetworkSupport as SystemEventAgent built May 25 2011 12:27:35
May 25 22:05:18 localhost UserEventAgent[11]: CaptiveNetworkSupport:CaptiveSCCopyWiFiDevices:388 WiFi Device Name == NULL
May 25 22:05:19 localhost com.apple.ucupdate.plist[28]: ucupdate: Checked 1 update, no match found.
May 25 22:06:14 localhost configd[14]: InterfaceNamer: timed out waiting for IOKit to quiesce
May 25 22:06:14 localhost configd[14]: Busy services :
May 25 22:06:14 localhost configd[14]:   MacBookPro3,1 [76967, 4375662836 ms]
May 25 22:06:15 localhost mDNSResponder[37]: mDNSResponder mDNSResponder-320.16 (Mar 17 2012 21:31:16) starting OSXVers 11
May 25 22:06:15 localhost com.apple.locationd[40]: ERROR,Time,359690775.485,Function,"_Apple80211* CLWifiService::createApple80211()",Apple80211GetIfListCopy failed, error -3903 (Unknown error: -3903)
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,1   locationd                           0x00000001077fe583 locationd + 624003
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,2   locationd                           0x00000001077fe719 locationd + 624409
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,3   libdispatch.dylib                   0x00007fff85f46c79 _dispatch_barrier_sync_f_invoke + 33
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,4   locationd                           0x00000001077fe9b0 locationd + 625072
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,5   locationd                           0x00000001077fea10 locationd + 625168
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,6   libsystem_c.dylib                   0x00007fff85e96e06 pthread_once + 86
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,7   locationd                           0x00000001077fea47 locationd + 625223
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,8   locationd                           0x00000001077f33ac locationd + 578476
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,9   locationd                           0x00000001077f353f locationd + 578879
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,10 libsystem_c.dylib                   0x00007fff85e96e06 pthread_once + 86
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,11 locationd                           0x00000001077f3509 locationd + 578825
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,12 locationd                           0x00000001077b052a locationd + 304426
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,13 locationd                           0x0000000107791653 locationd + 177747
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,14 locationd                           0x0000000107791a08 locationd + 178696
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,15 locationd                           0x00000001077921b2 locationd + 180658
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,16 locationd                           0x00000001077c332c locationd + 381740
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,17 locationd                           0x0000000107767fd8 locationd + 8152
May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,18 ???                                 0x0000000000000001 0x0 + 1
May 25 22:06:15 localhost com.apple.usbmuxd[27]: usbmuxd-268.5 on Jan 5 2012 at 03:34:01, running 64 bit
May 25 22:06:15 localhost UserEventAgent[11]: CaptiveNetworkSupport:CaptiveSCCopyWiFiDevices:388 WiFi Device Name == NULL
May 25 22:06:15 localhost UserEventAgent[11]: ServermgrdRegistration cannot load config data
May 25 22:06:15 localhost UserEventAgent[11]: get_backup_share_points no AFP
May 25 22:06:15 localhost systemkeychain[59]: done file: /var/run/systemkeychaincheck.done
May 25 22:06:15 localhost configd[14]: ioctl(SIOCGIFCAP) failed: Device not configured
May 25 22:06:16: --- last message repeated 1 time ---
May 25 22:06:16 localhost mDNSResponder[37]: D2D_IPC: Loaded
May 25 22:06:16 localhost mDNSResponder[37]: D2DInitialize succeeded
If you want me to post the kernal log, I can do that next if nothing in here points anyone in the right direction. FYI - the system booted normally this morning after shutting it down overnight.

External Buffalo HD won't mount after update to 10.5.7.

As the title suggests, I have a 250 GB Buffalo external HDD connected to my mac mini (2009). I did the update via software update & after the restart the external HDD won't mount. Any ideas anyone please?

Not exactly a Buffalo drive, but my problem seems very similar, and I'm convinced it occurred after a recent operating system update.
I have a Tascam DP-01FX that I use infrequently and that functions perfectly. I have used the USB connection to transfer files back and forth to three computers; and old G4 Mac (now out of commission), a new iMac (running OS 10.5.8, and an old Dell Inspiron 5000 (running Windows XP). The last time I tried to connect it to the iMac, the System profiler indicated it was connected, but it never mounted on the desktop, and it could not be made to appear in Disk Utility. I tried all varieties of connection; through a high speed hub, directly to the computer (with ALL other USB devices disconnected including the keyboard), etc. I zapped the computer's PRAM, verified and repaired permissions on the system drive. I even unplugged the computer and everything connected to it for half an hour, then reconnected and zapped the PRAM again. Nothing I've done will make the Tascam device mount on the desktop. However, it mounted with no problems on the old Dell Inspiron 5000. The kicker is that I've successfully and easily used the DP-01FX on the iMac on a previous occasion. All this leads me to believe there is something in an Apple software update that is causing this problem. All other USB devices work flawlessly, including an external hard drive that I only use for special projects about once a week. It mounts and un-mounts without any problems. This has got to be an Apple "oops."

Many problems. Programs won't mount and fan runs a lot

Ever since I installed my Ipod shuffle I have had all kinds of problems. I doubt that has anything to do with it. Sometimes my computer will go to sleep and the fan will just run like crazy. The computer won't wake up. The only way is to reboot. I also have a problem with programs not opening but in the program bar they have the arrow. Then they won't close unless I reboot. The other problem is that downloaded programs won't mount and therefore won't open. When I double click it says program failed to mount? Any ideas?
Jason

Before doing an Archive and Install as MGW suggested, I would try the following first:
Except for your keyboard & mouse, disconnect all devices from your computer...........
Run disk repair & permissions directly from your Tiger DVD.
I would also suggest that you consider updating your OS & updating and/or downloading anything else your computer needs by using your Software Update control panel.
If you do the above, you will need to repair permissions after each installation.
By any chance do you have DiskWarrior, Techtool Pro or Drive Genius?
"Apple has been no help with anything with this computer. The little ball on the mighty mouse broke after a week of use and they wouldn't do anything about it."
I'm sorry but, I find this hard to believe. Like MGW already stated, Apple should have offered you a replacement as you were entitled to one under your "standard" one year warranty with Apple.

Shuffle won't mount, but it did!

My shuffle will not mount on my G5. It did up until Tuesday, then I added new songs and now it won't play, won't mount, and when I try to do a software restore, the updater program freezes up. Any ideas?

I'm currently having the same issue. For anyone reading this in Apple's quality deparment ( *crickets chirp * ), here's an account of the behavior:
- On Friday, I purchased a song from the iTunes music store. After downloading the song, I plugged in my iPod shuffle into a USB 1.1 port on my PowerBook.
- During the run, the iPod played all the other songs without a problem. Yet, I couldn't get the new song to play in either shuffle mode or straight mode.
- Monday, I lost the ability to connect my iPod as a disk to my home PowerBook or any number of machines at work, all running Windows XP but different hardware.
- Tonight, I tried to restore the iPod update from the most recent patch. The software asks me to connect an iPod. I plug in my iPod shuffle and the software updater never finds it.
- Using the System Info and USB Probe tools, I can find that the iPod is mounted as a device on the machine. I believe this means that hardware-to-hardware the iPod shuffle is connecting.
- My system.log contains a number of entries like "localhost kernel: USBF::4681.218 AppleUSBOHCI[0x2012000]::CreateGeneralTransfer - trying to queue to a stalled pipe" and "localhost kernel: USBF: 4681.218 AppleUSBOHCI[0x2012000]::DoIOTransfer - error 0xe000404f queueing request". Again, there's a physical connection, but I'm not sure what that means.
- When I run iTunes 6.0.1 with the iPod connected, I get nothing but the color swirl cursor. I haven't launched Spin Control to find the hangs, but that just might be the next thing on my list of areas to venture.
- My iPod, which still has the playlist from Friday, no longer plays the music. Just get the orange and green rapid fire lights.
- Now, I've started to look for answers in the discussion boards to try and get some resolve. This has led to frustration and hence this post after reading a number of other posts.
I agree with Phil, given the users having this problem (which seems linked to iTunes 6.0.1 and the iPod update), I would have expected a quality driven company to acknowledge the issue and respond to those users. I guess Apple is too busy trying to maintain the marketing dominance they forgot what quality engineering and coding was all about. Instead of worrying about the other 30% of the market, why not take care of the existing 70%. Otherwise, you'll upset so many people, you'll drive that market share down to 4%.
I know this was a foolish waste of my time. No one from Apple engineering is even going to get in contact with technically savy users to resolve this problem. I'm going back to CD's. At least I don't have to worry about updating those with faulty software.

HT2497 apple software won't mount on an apple computer

Similar Messages

Maybe you are looking for