Macintosh HD won't mount
Hi, I'm fairly new to Macs, just got my first a year ago and I'm not familiar with the system. So I have a Macbook pro with Bootcamp installed. The mac side crashed and wouldn't boot, so I tried all the solutions for a fix but nothing worked, so I was going to simply reformat it. I copied the disk image onto an external hard drive earlier this morning so data recovery shouldn't be a problem I'm hoping.What happened was I went to reinstall mac os x Mountain Lion and the Macintosh HD was locked. So i went ahead and looked up some stuff and I got a bit hasty and erased my Macintosh HD partition. However, that caused it to unmount and when I open up the reinstall screen the drive doesn't even show. Now, it won't mount. It tells me to try first aid. When I try to repair it with first aid, it says it can't and to back up and reformat, which was what I was trying to do. I'm headed off to college really soon, so I need to get this fixed fast, any help would be appreciated!
No, it's there. It's there on all my backup images. I used to be able to mount it. 10.9.4 won't let me mount it, for some reason. Even tried to mount from the recovery partition. No joy. It's just grayed out. Try to manually mount and it says could not mount. Use First-Aid and try again. First-Aid can't find anything wrong. Still won't mount.
Similar Messages
-
Backup of Macintosh HD won't mount
I back up my entire system making an image with Disk Utility (as well as Time Machine). Time Machine doesn't back up Paralells VM files, so I went to grab it from my Disk Utility .dmg file that I made. It mounts "Boot Camp" just fine, but refuses to mount "Macintosh HD", which is where the file is stored.
Any ideas? It has to be possible to mount this!
MacBook Pro Retina (Mid 2012), OS X 10.9.4, WD 2 TB ExternalNo, it's there. It's there on all my backup images. I used to be able to mount it. 10.9.4 won't let me mount it, for some reason. Even tried to mount from the recovery partition. No joy. It's just grayed out. Try to manually mount and it says could not mount. Use First-Aid and try again. First-Aid can't find anything wrong. Still won't mount.
-
Macintosh HD won't mount in Mac, but can be seen in Windows
So, of course there was a bad storm here in Florida and my computer shut down and now won't start up. When you try to start it, it gets to the apple and the loading bar but just shuts off after the loading bar fills up. I got in with the recovery disk and used Disk Utility to repair which just gets stuck at "Updating boot support partitions for the volume as required." I'm pretty sure this means that my hard drive is ruined and I need to get a new one or something. I have Applecare still so I can take it in.
The only problem is, like most dumb users I don't have any of my stuff backed up. I'd love to be able to get my important info off the drive before I take it in. I tried to do target disk mode but the other computer doesn't see the Macintosh HD. I also tried to reinstall Mac OS X using the disc but I can't choose the Macintosh HD as a place to install. In fact, the only way I can see the Macintosh HD at all (besides in Disk Utility - and it's greyed out), is if I boot into Windows. Windows will let me see the HD and I can try to get some of those files but the stupid Windows doesn't let me move everything because it won't accept certain filenames or something Windows-y and dumb.
Anyways, is there some reason Windows can see it but the Mac won't?In the settings for the netboot image in server admin check the box "Diskless". This will allow the local HD to be erased.
So I think it will be mounted in /Volumes but haven't checked. If you need a more detailed way to enable the "Diskless" setting say so. -
Disk utility, input/output error, setup fail
Had issue partitioning 2TB my passport drive, got input/output error while using disk utility.
Here is what I did to get my external disk back
In Disk Utility
1) Try to use erase option first, it failed
2) Try to partition the disk, failed as well.
3) Then try erase option again, then ... it worked !! -
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. -
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 7TFHere 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 -
MacBook Air - My Passport 1T won't mount after Yosemite update
1) Tried to switch cables2) Won't mount on Linux or Windows3) Mac WD Drive Tools - shows me drive 1T click on - run drive status check, nothing ...same with other buttons.4).Not showing in Disk Utility or terminal 5). Lights...... 2-3 minutes steady light, then flashing with 2.5 second delay.6). Interesting note, while loading in recovery mode and then restart drive light is constantly flashing. SOS
Hello
Welcome to the WD Community.
Have you tried using the WD Macintosh +TURBO Drivers ?
-
I realise this isn't exactly a FCS question, but this seems to be the right community. All of a sudden my Sony XR520VE won't mount on the desktop. I haven't used it for a couple of months, but there was never any problem before. Now when I plug it in (this is USB of course), the cam screen says "preparing" and it's been like that for about 20 mins now.
Any suggestions? I can think of two possible changes since I last plugged it in -
1. I've reinstalled the system recently and my have lost something in the reinstall. I did have to retrieve a copy of QuickTime MPEG-2 Playback and may have lost something else (but this seems highly unlikely - this sounds more like a deeper problem). But I have no problem mounting anything else - hard drives, cameras, etc.
2. There's been some sort of OS update over the past few months that has done something.
Using 10.6.7 on a MacBook Pro 2.53 GHz Intel
Thanks for any advice.When I open this question, I see aseveral "more like this" posts in the right column. Try some of those?
Image Capture and iMovie will sometimes see device es FCP will not show. Reinstalling an OS is weird with Macintosh so whatever caused you to decide that was necessary may have destroyed several functions including any special Sony software you may have installed years ago.
Aside from that, take your camera to another Mac. If ti doesn't mount there, it's the cable or the conector on the camera. Maybe.
bogiesan -
Can't install Snow Leopard on MacBook Pro - DVD won't mount
I am unable to install Snow Leopard on my MacBook Pro as the DVD won't mount. This is an early 2008 vintage MacBook Pro, intel core duo...
I'm using a OS X Snow Leopard install DVD (family licensed). This DVD has been used to install 3 other Macs in my house without a problem (about a year ago), but cannot be used to upgrade my MBP. Actually, this disk mounted on the MBP exactly once - inserted with system up, the disk mounted. Upon running the installed (a year ago), the computer restarted but hung in boot. After getting the disk ejected and the computer restarted, the disk would never mount again. I've defered upgrade for a year but at this point need to upgrade my MBP at least to Snow Leopard and possibly Lion.
The problem doesn't seem to be with the DVD, since it continues to mount fine in other computers, and in fact a borrowed Snow Leopard DVD also will not mount on the MBP.
BUT ... the problem also does not seem to be with the optical drive in my computer, as it can read & mount the install/restore disks that came with the computer as well as other CDs and DVD ROMs. Only the Snow Leopard install DVDs fail to mount.
I've also tried mounting the 10.6 install DVD on my Mac Pro desktop, making it available over the network (ethernet) with DVD/CD sharing. I can mount the remote disk from my MBP that way, but when I launch the installer, the application launches (its own menus are displayed, I can quit from menu, for example) but does nothing -- no windows open, nothing.
I've also tried "Remote Install" (again with the DVD made available with the Remote Install MacOS X application on my desktop), but when I boot the MBP with option held down, the remote disk is not available as a startup disk.
Zapping the PRAM did not help.
Am off to the store to get an optical drive cleaning kit and a blank DVD big enough to burn a new disk image, but would appreciate any further ideas at this point....Solution that worked: Copy the Install DVD to a USB flash drive and boot from that.
http://www.maciverse.com/install-os-x-snow-leopard-from-usb-flash-drive.html
Up and running with Snow Leopard now and working on the updates. -
I have a MacBook Pro and an 1TB WD my passport for mac. I bought a second hard drive to act as back up and when I went to do this the original passport won't mount. It is showing in disc utility but it will not repair. I am told the mac cannot repair it and I need to back up the files and then restore the hard drive. But I can't open the hard drive to move the files onto the new one!
Help me please. I am not very technical so please answer as if I have no clue!! This hard drive has my iPhoto on it and all my pictures of my son, wedding and my current photography course so I desperate to get it back!
Any help will he appreciated!disk0s2: I/O error.
disk0s2: I/O error.
The MBP's disk is damaged and requires replacement.
Genius Bar Reservations: http://www.apple.com/retail/geniusbar/ -
Thunderbolt external SSD won't mount
I'm using the Elgato Thunderbolt SSD as an external hard disk with my 2013 MBP. Since I'm also using a Thunderbolt display, I usually daisy-chain the disk to the display.
Recently I disconnected the Thunderbolt display from my computer without unmounting the external SSD. Since this also disconnected the disk, I got the usual ticking-off ("You should eject a disk before disconnecting it").
However... since then, the external disk won't mount. It doesn't show up on the desktop or in Disk Utility, though it DOES show up ("Thunderbolt SSD") in System Information.
Because the SSD gets warm when it's in use, I think it's still working. I just can't access it.
Can anyone help?Is the Apple Thunderbolt Display at the END of the daisy-chain? That's where it should be - all other TB devices should be connected first, with the Display at the end of the chain.
As to why you're having a problem getting the TB SSD to work, I'm stumped. It seems as if you've done everything that I would try to do to get everything working... and I'm assuming that you have powered down and unplugged the Display and all other devices for 15 minutes or so?
Just make sure that the Display is at the end of the TB chain - that's really the only advice that I can offer.
Clinton -
My MacBook Pro (13" mid 2010, Yosemite) doesn't feel like booting up. It gives me the no symbol after the progress bar is about 1/4 of the way through.
Additionally, it won't mount in the Recovery HD. It shows up as disk0s6 and clicking Mount does nothing. Can't seem to mount it in the Terminal either.
The disk partition is encrypted, so unfortunately I can't pull the hard drive out of my MBP and pull the stuff off it with my PC.
I tried First Aid - "no problems found" (such LIES!)
I tried PRAM - didn't work
I tried Verbose Mode - went fine for the first minute, then hung for a while before returning to the "No" screen and in the bottom right corner "Still waiting for root drive".
I tried SMC - didn't work
Most recently I did install rEFInd - which is a boot manager. I was afraid it screwed up the EFI partition -seemingly not, as it will boot to Recovery and external drives.
The data still seems to be there, but the OS is having trouble accessing it.
Do you know what would be causing this? I really need that data back :/It appears I can unlock the partition, using diskutil via the Terminal (diskutil coreStorage unlockVolume <UUID> -passphrase <passphrase>).
However the volume doesn't have a UUID. It lists the partition type as "FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF" (which is a UUID) but using that doesn't work.
Additionally when I use diskutil coreStorage list, it comes up with nothing. I'm at a loss here, the partition doesn't even know it's own UUID or that it's encrypted. It seems quite damaged to me but I don't have the slightest idea why, as I CAN boot to it and enter the password but it will stop at the "no" symbol part of the way along. -
Ipod classic won't mount after updating to itunes 11.0.2
ipod classic won't mount after updating to itunes 11.0.2.
I updated to itunes 11.0.2 today, after delaying it for a looong time (I have it @ work and don't like the new layout).
Since then, none of my ipods will mount/show up/update. I've tried all USB ports, 3 ipods, 3 cords. Wondering if you know of any issues. I've restarted the mac about 15-20 times today since as soon as I hook up an ipod, itunes immediately spins the beach ball and won't let me click out of it.
I've restarted the ipods 10+ times each.
All of the ipods DO show up on my desktop though. Just not in itunes anywhere with 11.0.2.
One more thing: It's not the cables or the ipods: they both mount fine when connected to my laptop (running old *** 10.4.11 and itunes 9.)
Machine is a Mac Pro running 10.6.8.Finding this Post took some time but I thought it was me talking when I read it. I was having the exact same issue. I have a G3 I've been upgrading like mad, including a Sonnet G4-500 CPU a Maxtor 60gb & 80gb HDs 1gb of RAM a new LaCie Firewire800 PCI card Graphics card etc. the latest was installing Panther 10.3.9 on the new 80gb HD and also swapping out the old CD-ROM and replacing with the (Apple standard) Pioneer DVD-RW DVR-110D combo drive in it's place. got everything up and booted and poof! no burning. Toast worked read/write no problem. iTunes could read and import no problem, but wouldn't burn a CD.
Downloaded "PatchBurn 3.1.3" installed, re-booted and all is OK in burner land again :>)
I wanted to just post my additional thanks to the lead to Patchburner, and I'm going to donate to the cause. It's worth a $20 donation just for my joy of not throwing this computer out the window!! -
Upgraded to Mavericks. Now External HDD Enclosure Won't Mount. Is there a fix?
Upgraded to Mavericks. Now I can't get my external HDD enclosure to mount. A little about this enclosure, as it's not the usual settup . I have four 3TB HDDs in a RAID5 settup. The most unique part is that they are formatted as a Windows NT Filesystem (Tuxera NTFS). Basically, when I set this up, I had to get a lot of info from a Windows-formatted HDD, but also be able to read/write afterwards. It's worked fine for ~ 1 year, but now that I've upgraded to Mavericks, nothing will mount. I ran Disk Utility, where I see the HDDs (I've partitioned them into four drives of varying sizes), but they are greyed out. I tried to mount them, but it says it won't and that I should run First Aid. So I did...tried to "Repair Disk," but it just gets stuck on "Updating boot support partitions for the volume as required." For over an hour it's been on that message.
So, does anybody out there have a fix? I've read several similar posts about people having a hard time mounting and, overall, dealing with external HDDs after upgrading to Mavericks. But nothing seemed to fit my exact circumstances. Lastly, I should mention that I've used both Firewire and USB connections. Both resulted in the same.
Thanks.I can't help with specifics for your issue, but some general thoughts:
The upgrade and the disk problem may be a coincidence. It would help you if you could verify that the drive still works fine on a windows machine. If you run a windows virtual machine or have a windows pc, or a friend does, verify full functioning that way. If it still won't mount on the mac, try to copy/backup it's data onto the windows machine (maybe another external drive connected to it. You could then scrub the disk in windows, leave it unpartitioned, unformatted. Connect it back to the mac and format it as HFS+ (Mac extended journalled) and transfer the data back to it by sharing the windows machine external drive and connecting the two machines with a network cable. -
Time Capsule won't mount after upgrade to iTunes 9
See my full post in the Time Capsule support section ("Help! Time Capsule won't mount after installing iTunes 9"). My music library is on my Time Capsule, but after installing iTunes 9, it won't mount on my iMac G5. I can use the internet, but the disk won't mount. My Powerbook hasn't been updated yet and the Time Capsule mounts fine.
To make it easier, here's the post:
"My music library is on my 500 Gb Time Capsule. I just installed iTunes 9 on my iMac. It updated my library and synced my iPhone. Now, the TC won't mount. I still have internet connectivity, but I can't access my media or print to my printer connected to the TC. I can use the computer and everything, but if I hover my mouse over the TC disks menu bar icon, I get the spinning beach ball there. If I try to connect using my Network icon in the sidebar, it allows me to log in and get to the screen to select the volume I want to mount, then stops responding. In the Activity Monitor, AFP Client & AirPort Base Station Agent are not responding. I also have a Powerbook G4 w/Leopard (10.5.8) which hasn't been updated to iTunes 9 yet. The Time Capsule mounted fine on it."
Maybe you are looking for
-
Using external hard drive connected to desktop as time machine disk for laptop
I recently purchased an external hard drive for the purpose of backing up my laptop and desktop macs. Both are running Mountain Lion (10.7.5). The desktop is physically connected to both the hard drive and to my modem. I have enabled pretty much ever
-
Problem with approval notification
Hi Experts for some unknown reason we get in the process workflow the error like: Activity Definition Name Is Final Approver Internal Name HR_IS_FINAL_APPROVER_FCT Type Function Description Is Final Approver Activity Version 4 Result Type Yes/No/Erro
-
ME31L/ME32L, ME31K/ME32K badi/user exits at item level
hi all, i need to check tax jurisdiction code per item of scheduling agreement and contract. coz i need to prompt an error message "tax jurisidation code at line XX is blank" if no tax jurisdiction code is specified. can you help me what badi or user
-
Hello Security folks, We are implementing SAP J2EE and ABAP across multiple systems. We have been working with CA eTrust to assist us in hardening the OS platform. We are running on AIX. We recognize that eTrust does not use the SAP technology for ex
-
i've dowloaded some music to my mac from i tunes but it shows a '!' in the list and it says it can't be used because the origional file can't be found. why? how can i fix this?