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
Similar Messages
-
External HD won't mount, lots of errors
I bought a 250GB Maxtor internal harddrive and installed it inside a no-name external enclosure. It's connected through USB2. When I connect it, I get a pop-up that says "disk not recognized" with options to initialize, ignore, or eject. I went into Disk Utility and partitioned the disk...still won't mount. I then reinstalled the 10.4.3 combo updater...still no luck. When I try to repair the disk through Disk Utilities it says:
"Verify and Repair disk “disk1s3”
Volume check failed.
Error: The underlying task reported failure on exit
1 HFS volume checked
1 volume could not be repaired because of an error
What can I do to get this hard drive to mount and work?Put it into a FireWire enclosure. USB is basically useless; normally unbootable. You can get a decent FW/USB combo enclosure for under $50. I like this one (I have two): http://www.pcmicrostore.com/PartDetail.aspx?q=p:10500933 ($38 US + S&H).
Note: I have no financial interest with this seller or product. -
External Hard Disc won't mount - Partition Map error. Can't repair with Disk Utility
Happy New Year all and thanks in advance for any support/advise.
I have some important data on an external drive that does not seem to want to mount. The drive is a 500 GB Seagate connected via USB. I am currently on an iMac 3.06 GHz Intel Core 2 Duo running Yosemity 10.10.1
What I've tried:
Multiple computers - connected the drive to various apple computers with the same result.
New enclosure: I have removed the actual HD from the enclosure and connected it using a new one.
Disk Utility: Verifying Disc reports the following error: 'Error: Partition map check failed because no slices were found.' Screenshot below:
I have searched this and other forums and run a few commands in Terminal that seem relevant to the issue, but am out of my depth in terms of interpreting the results. Thank again for your attention!!!
Commands run in Terminal:
diskutil list
diskutil cs list
mount
diskutil info disk1
Full Results pasted below:
diskutil list...
Ethan-Smiths-iMac:~ Ethan$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 999.3 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk1
1: Microsoft Reserved 134.2 MB disk1s1
diskutil cs list...
Ethan-Smiths-iMac:~ Ethan$ diskutil cs list
No CoreStorage logical volume groups found
mount...
Ethan-Smiths-iMac:~ Ethan$ mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
diskutil info disk1...
Ethan-Smiths-iMac:~ Ethan$ diskutil info disk1
Device Identifier: disk1
Device Node: /dev/disk1
Part of Whole: disk1
Device / Media Name: ST950032 5AS Media
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): GUID_partition_scheme
OS Can Be Installed: No
Media Type: Generic
Protocol: USB
SMART Status: Not Supported
Total Size: 500.1 GB (500107862016 Bytes) (exactly 976773168 512-Byte-Units)
Volume Free Space: Not applicable (no file system)
Device Block Size: 512 Bytes
Read-Only Media: No
Read-Only Volume: Not applicable (no file system)
Ejectable: Yes
Whole: Yes
Internal: No
OS 9 Drivers: No
Low Level Format: Not supportedSelect the disk1s1 volume under the main drive entry, then click on the Mount icon in the Disk Utility toolbar if it goes active and see if a volume then mounts on your Desktop. If it does not, then you need to reformat the drive. And, you cannot access the volume in order to copy your data somewhere else. If you are willing to spend money on the problem, then you can always try using a software recovery utility:
General File Recovery
If you stop using the drive it's possible to recover deleted files that have not been overwritten by using recovery software such as MAC Data Recovery, Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive. Two free alternatives are Disk Drill and TestDisk. Look for them and demos at MacUpdate or CNET Downloads. Recovery software usually provide trial versions that enable you to determine if the software would help before actually paying for it. Beyond this or if the drive has completely failed, then you would need to send the drive to a recovery service which is very expensive.
The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
Also visit The XLab FAQs and read the FAQ on Data Recovery. -
Hello. We currently have 2 xraid's. One raid has 7 open slots on one side. The desired use of these slots is to plug in a raid set that was previously used and is full of data for quick archival retreival purposes. We currently have a set of blades that were filed away and pulled to retrieve from, however when plugged into the raid set and booted up everything looks good both in raid admin and on the raid itself, but the old volume does not mount and is not accesible for us to use.
Any ideas why this process currently is not working, and how I can get it to work? I repaired The LUN map which it gave me an error on and I also ran the "verify parity data" utility as well. Thank you for your help!Glad to hear of your (at least partial) success!
If you're getting errors from one half of the RAID it probably comes from:
1) Failing but not failed disk
2) Poorly seated drive
2) Bad fibre cable
3) Other hardware (controller) error
If you really want to track this down you can swap cables, swap fibre ports, re-seat the drives and check the logs for disk errors on the flakey volume. If none of these turn up signs the checking gets more complex - ie swapping controllers around. You could also eject all over volumes and see if it behaves as the only volume - but I'd be surprised if that's it.
Chances are one of the drives is acting up or poorly seated. The 1.5.1 firmware reportedly throws errors more aggressively than previous versions making the process of looking for suspect drives more scientific than doing file copies and watching for drive light lag.
Good luck,
=Tod
G5/2.0x2, Dual XServes x2, XRAID, beige G3 501Mhz -
Time Capsule "Data" Volume won't Mount
I've been using a Time Capsule (4th Gen/2TB) for both my rMBP Time Machine backups and as a NAS device. After upgrading to Mountain Lion, I've experienced some problems. For the past few weeks, my Time Machine backups have been frequently interrupted with an error message stating that my Backup Disk is non-journaled and non-extended, and to please choose an alternate disk. Although unsettling, after pressing return - and upon connecting the power cord (as I opted only to backup when using the power cord), Time Machine has always propmtly resumed. This has probably occurred daily.
Today however, I've been unable to actually mount the Data volume, although my network is functioning properly, and I can access the Internet. The Time Capsule status indicator is green, its icon appears in the Finder sidebar, and Airport Utility recognizes it and displays its correct settings. Upon trying to connect (via Finder), however, an error message states that the server (in this case, the Time Capsule, I guess) can't be located, and suggets I check my network settings and try again. Needless to say, the settings appear fine.
An admittedly brief search within this forum yielded no discussions concerning this specific problem, but I'm hoping the community's more knowledgable members will be able to at least provide some helpful insights, if not a solution to this problem.
The inability to back up my rMBP, access my spasebundle, or manage my externally stored files is very disconcerting. Any solutions, or insights regarding this issue will be gratefully received.
Michael HenkeThere is clearly a bug in Lion that was exacerbated in Mountain Lion, which Apple is yet to fess up to. This loss of connection happens and there is no fix I can give you other than reboot to get the network running again.
I would strongly recommend against using the TC as a NAS.. it is designed as a backup target for Time Machine.
If you want a NAS then buy a true NAS, synology or Qnap, being the top products in that field. They have raid and automatic backup with units where you can access hard disks and can replace them. TC is a sealed unit without any way to back itself up. The design was never as a NAS.
Since your TC is an older one, can you try running 7.5.2 firmware. None of the TC made in the last year or more can go back that far.. they are all stuck on 7.6, the earlier Gen4 did have 7.5.2 which I think has better stability..
Now exactly what issues come up with ML I am not sure, but I would be interested to hear your experience.
Please do a backup particularly of your itunes before you start fiddling.
Is the TC main router in the network or is it bridged? I have a few suggestions for each type of setup, which may keep it running longer.. but nothing is absolute fix.
Note also the TC seems to be the main problem device.. but the OS does still have issues.. some changes were made with AFP security at Lion, which have not worked very well. -
TS1541 volume won't mount for main user-intel imac with mountain lion-what to do?
After logging in to admin user, grey screen with spinning arrow
Can login to Guest User but that is just set up for Safari only
Tried starting in Safe Boot, zapped the PRAM, removed all peripherals, rebooted with installation disk and used Disk Utility - disk greyed out and says not mounted
How can that be?
this is an Intel-based iMac purchased last summer, recently installed Mountain LionI have the same problem. Installed Mountain Lion, got the spinning orb with no escape so I powered down. Upon re-boot I have the dreaded "?" Tried restarting several times to no avial.
In desperation, I inserted the 10.5 (Leopard) disk to install the original system version that came with my iMac. Now the install disk cannot find or mount my hard drive. I'm stuck.
Anyone?? -
IPod used as external drive won't mount
My 3rd generation iPod recently crashed and I restored it using the Restore in iTunes on my Intel iMac. I enabled disk mode and reloaded my playlists, iPod works fine, and mounts on my iMac, but it won't mount on my older PM G3. It does shows up in System Profiler and Disk Utilities but the volume won't mount.
The Console Log shows the following error:
Mac OS X Version 10.2.8 (Build 6R73)
## Component Manager: attempting to find symbols in a component alias of type (regR/carP/x!bt)
Nov 12 17:32:19 BeigeG3 /sbin/autodiskmount[204]: disk1s3 hfs no yes GOT iPod [not mounted]
Nov 12 17:32:19 BeigeG3 /sbin/autodiskmount[204]: DiskVolumemountforeign: unrecognized return code from foreignMountDevice: -4
Nov 12 17:32:19 BeigeG3 /sbin/autodiskmount[204]: disk1s3 hfs no yes GOT iPod [not mounted]
Nov 12 18:45:23 BeigeG3 WindowServer[171]: CGXDisableUpdate: Updates disabled by connection 0x5807 for over 1.000000 seconds
GOT iPod* malloc[406]: Deallocation of a pointer not malloced: 0x12bf320; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
: for architecture i386 object: ./Applications/iTunes.app/Contents/MacOS/iTunes malformed object (unknown flavor for flavor number 0 in LC_UNIXTHREAD command 27 can't byte swap it)
GOT iPodGOT iPod## Component Manager: attempting to find symbols in a component alias of type (regR/carP/x!bt)
I use the disk mode to transfer large files between the two systems.
Thanks in advance for your help.
iMac 20" CoreDuo Mac OS X (10.4.8) Power Mac G3Thanks for the help. I restored my iPod on my older G3 and now it shows up on both systems again.
-
Backup Volume cannot be mounted
Time machine stopped working for me back in July. I've looked at every post and tried nearly everything, and I cannot get it working again. The error through the Time Machine pref pane is "The Backup volume cannot be mounted." The errors in the console are the following:
Sep 4 23:19:25 tesla /System/Library/CoreServices/backupd[50182]: Backup requested by user
Sep 4 23:19:25 tesla /System/Library/CoreServices/backupd[50182]: Starting standard backup
Sep 4 23:19:25 tesla /System/Library/CoreServices/backupd[50182]: Network mountpoint /Volumes/Backup not owned by backupd... remounting
Sep 4 23:19:26 tesla /System/Library/CoreServices/backupd[50182]: Failed to remount network volume.
Sep 4 23:19:31 tesla /System/Library/CoreServices/backupd[50182]: Backup failed with error: 19
This is a network volume. It's a 750GB firewire drive, formatted HFS+ with a GUID partition table connected to an iMac. The iMac can back up just fine to it. My MBP cannot. It worked before.
It appears it is failing to remount the drive as root rather than myself, as backupd runs as root. Others are having the same problem, and I've seen no resolution for this particular issue. Is Apple even aware of it? Do they even read the discussion forums?Paul,
Give these ideas some condsideration:
First, it is important to distinguish this error message from another, similar Time Machine error that states “The backup volume could not be found”. This is important as the causes and cures for these two errors can be very different.
Give each topic separate consideration. If one does not resolve your issue, move on the next one.
*Time Machine Has Lost Its’ Backup Disk*
If Time Machine was NOT setup to recognize a hard disk for backup, and “Back up now” was selected from the Time Machine Dock icon, an error would report “No backup volume has been selected. To select a backup volume, open . . “ The Console log would report:
+Backup failed with error: 17+
But if Time Machine HAD BEEN setup to use a specific disk for backups, but if had lost its’ connection to the drive, it would report “The backup volume could not be mounted”. The Console log would say:
+FSMatchAliasBulk returned -35 while resolving alias to backup target+
+Backup failed with error: 19+
When you check the Time Machine preferences you may see the name of your backup disk greyed-out and a generic hard drive icon beside it. More than likely this means Time Machine has lost is physical connection to the drive. Either the drive is not plugged in, it’s not turned ON, the drives’ cable is bad, the drives internal controller has failed, or the drive has a sleep function that is preventing it from waking when a backup is called for.
*Airport Has Been Turned Off* (For Time Capsule / AirDisk Users) #
Look and the Airport menu at the top of the screen. Does it no longer display the radiating bands of wireless signal strength? The Airport has been turned off on this computer.
Go to System Preferences.
Select Network.
Click “Turn Airport On”
Now try backing up.
*File Sharing Has Been Disabled* (For Time Capsule / AirDisk Users) #
Launch Airport Utility.
Click "Manual Setup".
Select "Disks" in the tool bar at top of window.
Click "File Sharing".
Verify that "Enable file sharing" is checked.
If not, check it, click “Update”.
Once the Time Capsule has finished restarting, close Airport Utility and try backing up again.
*Password Has Changed/Become Corrupted* (For Time Capsule / AirDisk Users) #
[Mac OS X 10.5.3 or later: Time Machine - "Backup volume could not be mounted" after changing network volume's password]
*Proper Computer Name* #
Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
(0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
Also, if the name of your backup devise contains any special characters (like an apostrophe) consider removing them and trying a backup again.
Let is know if any of the ideas above helped.
Cheers! -
NEED HELP Xsan volume is not mounted (strange problem)
I ask the help in solving the volume mount problem. (advance I am sorry for my english)
All began with the fact that the MDC is rebooted and on the two LUNs were gone XSAN label. I relabeled these LUNs using commands:
cvlabel -c >label_list
then in the file label_list I corrected unknown disks on the label with a same names that were. Then I ran the cvlabel label_list command. Finally I got the correct label on all drives.
# cvlabel -l
/dev/rdisk14 [Raidix meta_i 3365] acfs-EFI "META_I"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk15 [Raidix QSAN_I 3365] acfs-EFI "QSAN_I"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
/dev/rdisk16 [Raidix meta_ii 3365] acfs-EFI "META_II"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk17 [Raidix 2k_I 3365] acfs-EFI "2K_I"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk18 [Raidix 2k_II 3365] acfs-EFI "2K_II"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk19 [Raidix QSAN_II 3365] acfs-EFI "QSAN_II"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
The volume [2K] starts successfully.
but not mounted on the MDC and client.
I ran a volume check:
sh-3.2# cvfsck -wv 2K
Checked Build disabled - default.
BUILD INFO:
#!@$ Revision 4.2.2 Build 7443 (480.8) Branch Head
#!@$ Built for Darwin 12.0
#!@$ Created on Mon Jul 29 17:01:44 PDT 2013
Created directory /tmp/cvfsck3929a for temporary files.
Attempting to acquire arbitration block... successful.
Creating MetadataAndJournal allocation check file.
Creating Video allocation check file.
Creating Data allocation check file.
Recovering Journal Log.
Super Block information.
FS Created On : Wed Oct 2 23:59:20 2013
Inode Version : '2.7' - 4.0 big inodes + NamedStreams (0x207)
File System Status : Clean
Allocated Inodes : 4022272
Free Inodes : 16815
FL Blocks : 79
Next Inode Chunk : 0x51a67
Metadump Seqno : 0
Restore Journal Seqno : 0
Windows Security Indx Inode : 0x5
Windows Security Data Inode : 0x6
Quota Database Inode : 0x7
ID Database Inode : 0xa
Client Write Opens Inode : 0x8
Stripe Group MetadataAndJournal ( 0) 0x746ebf0 blocks.
Stripe Group Video ( 1) 0x746ffb60 blocks.
Stripe Group Data ( 2) 0xe45dfb60 blocks.
Inode block size is 1024
Building Inode Index Database 4022272 (100%).
4022272 inodes found out of 4022272 expected.
Verifying NT Security Descriptors
Found 13 NT Security Descriptors: all are good
Verifying Free List Extents.
Scanning inodes 4022272 (100%).
Sorting extent list for MetadataAndJournal pass 1/1
Updating bitmap for MetadataAndJournal extents 21815 ( 0%).
Sorting extent list for Video pass 1/1
Updating bitmap for Video extents 3724510 ( 91%).
Sorting extent list for Data pass 1/1
Updating bitmap for Data extents 4057329 (100%).
Checking for dead inodes 4022272 (100%).
Checking directories 11136 (100%).
Scanning for orphaned inodes 4022272 (100%).
Verifying link & subdir counts 4022272 (100%).
Checking free list. 4022272 (100%).
Checking pending free list.
Checking Arbitration Control Block.
Checking MetadataAndJournal allocation bit maps (100%).
Checking Video allocation bit maps (100%).
Checking Data allocation bit maps (100%).
File system '2K'. Blocks-5784860352 free-3674376793 Inodes-4022272 free-16815.
File System Check completed successfully.
check not helping
sh-3.2# cvadmin
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1>*2K[0] located on big.local:64844 (pid 5217)
Select FSM "2K"
Created : Wed Oct 2 23:59:20 2013
Active Connections: 0
Fs Block Size : 16K
Msg Buffer Size : 4K
Disk Devices : 5
Stripe Groups : 3
Fs Blocks : 5784860352 (86.20 TB)
Fs Blocks Free : 3665561306 (54.62 TB) (63%)
Xsanadmin (2K) > show
Show stripe groups (File System "2K")
Stripe Group 0 [MetadataAndJournal] Status:Up,MetaData,Journal,Exclusive
Total Blocks:122088432 (1.82 TB) Reserved:0 (0.00 B) Free:121753961 (1.81 TB) (99%)
MultiPath Method:Rotate
Primary Stripe [MetadataAndJournal] Read:Enabled Write:Enabled
Stripe Group 1 [Video] Status:Up
Total Blocks:1953495904 (29.11 TB) Reserved:270720 (4.13 GB) Free:129179 (1.97 GB) (0%)
MultiPath Method:Rotate
Primary Stripe [Video] Read:Enabled Write:Enabled
Stripe Group 2 [Data] Status:Up
Total Blocks:3831364448 (57.09 TB) Reserved:270720 (4.13 GB) Free:3665432127 (54.62 TB) (95%)
MultiPath Method:Rotate
Primary Stripe [Data] Read:Enabled Write:Enabled
I checked the availability of LUNs on MDC and client, there also all right.
But, unfortunately, the Volume is not mounted
xsanctl mount 2K
mount command failed: Unable to mount volume `2K' (error code: 5)
Please help me to figure out this situation, I will be grateful for any information.
ThanksThat looks like an I/O error. You may have an issue with one or more of the data LUNs. Check the system log for errors.
-
Can't get around "mount failed" - "on error" won't do it - help appreciated
Hi
I'm using this syntax to mount a volume, and it works well if the volume can in fact be mounted:
try
mount volume "afp://username:[email protected]/MyDir"
on error
display dialog "blah blah"
end try
BUT, if the volume can't be mounted because the directory specified is incorrect, I a dialog saying "Mount Failed" opens with the only option being 'OK'. Under some other mount failure circumstances this dialog doesn't appear, and the script does eventually time out and disappear all by itself. But if this dialog appears, I have no option other than to manually press OK. It stays open forever. This dialog appears before the script passes the error to the display dialog part, so it prevents the "on error" part of the script from running. This is the only example I know of where 'on error' fails to let the scripter move on and manage the error.
What I would really like to do is to get the 'on error' functionality to actually work properly, because I can determine the PID of the process using Terminal and could then kill it using a shell script if , BUT none of this is possible because the script never gets to the 'on error' state because a real human must press the dialog's OK. I can't seem to use system events to send anything to it because the whole applescript just hangs at this point until the OK is checked.
Does anyone know a workaround? I've tried using a with timeout step around the whole thing but also won't work.
Thanks for any advice you could give me.
Chris.I'm having the same trouble, but for different reasons. I was trying to determine a method for examining all the mounted volumes on my desktop and then detecting which mounted volume came from which network server. There doesn't seem to be any way to determine this via any filesystem metadata or anything. The only solution that I could think of was to build an afp url for each server/volume combination for any given mounted volume I wanted to test and then try mount volume on each url (thinking that the on error handler would trap the errors and then I could branch accordingly). Doesn't work. It's interesting that if you try mount volume afp://validerserver/badvolume, you get the mount failed error before your on error handler kicks in. If you try mount volume afp://badserver/validvolume, the on error handler fields the resulting -35 error. If you try mount volume afp://emptystring, you get a connection failed dialog before the on error handler again. Really annoying.
I filed a bug on this. -
I have Leopard 10.5.8 and am trying to connect to a Windows Vista share via SMB. The two systems can communicate and authenticate without issue. After using Finder's Go To Server and connecting via SMB, I am prompted for a username and password. Once given, the Vista machine authenticates and presents me with a list of shared folders to chose from. At this point, when I select a folder, Leopard immediately returns with the "Volume Fails To Mount" error and I am returned to the list of shares after closing the dialog box. Thinking it might be an issue with Finder, I found and downloaded an application, AutomountMaker. Its results were the same. I can connect from the Vista machine to Leopard with no issues whatsoever, so I know the machines are working together. I have been unable to find any explanation for this error message nor how to correct the issue. I would appreciate it if anyone can offer some ideas.
As a bit of additional information, I have another machine that is running Windows 7 and I was able to connect to a share on its drive from Leopard without a problem.This page may help http://www.ifelix.co.uk/tech/3022.html
-
Bootpartition won't mount, fsck finds no errors
Hi guys,
got a strange situation here. My Bootpartition /dev/sda2 won't mount in Arch anymore.
mount /dev/sda2:
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
Manchmal liefert das Syslog wertvolle Informationen – versuchen
Sie dmesg | tail oder so
The same error appers during boot. I don't know how Arch can boot without bootpartition but ist does...
Another strange thing is that it mounts fine in Mandriva running on the same machine. Also testdisk under Windows didn't complain.
dmesg | tail
EXT2-fs (sda2): error: corrupt root inode, run e2fsc
e2fsck /dev/sda2
e2fsck 1.41.14 (22-Dec-2010)
archboot: sauber, 43/36288 Dateien, 33179/144584 Blöcke
grep -i archboot /etc/fstab
LABEL=archboot /boot ext2 defaults 0 1
file -s /dev/sda2
/dev/sda2: Linux rev 1.0 ext2 filesystem data, UUID=c477713e-ff47-40f3-92f0-537291f24937, volume name "archboot
So what now? Any help is appreciated.no changes to any partitions were made, just did a fatal "pacman -Syu"...
i removed the /boot completely from fstab and tried to mount the partition manually.
i also recreated the whole partition under ubuntu. copied the files out, deleted the entire partition, recreated it and copied the files back.
arch linux still can't mount it.
also when i'm trying to mount my jfs partition, the "mount" command hangs completely. even "kill -SIGKILL $pid" can't get rid of it.
the jfs partition also mounts fine under ubuntu, i ran tests on every partition under ubuntu, they're all clean.
mounting an jfs partition don't give any logfile entry, dmesg is also empty. it's just hanging. the funny thing is, that ext4 and vfat partitions are mounting fine.
could something be wrong with hal or dbus?
here's e2fsck output:
e2fsck -pvf /dev/sda8
35 inodes used (0.15%)
4 non-contiguous files (11.4%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 10/6/0
35980 blocks used (37.34%)
0 bad blocks
0 large files
22 regular files
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
26 files
--------EDIT:
finally found it!
for some reason (i don't know why) the /boot partition was not mounted during update and thus the kernel26 image was written into the /boot directory of the root partition instead of the /boot partition (where it belongs). this means on next bootup the system was booting with the older kernel but the updated system. maybe some things in filesystem handling were changed between the two versions of the kernel.
i mounted the arch partitions within ubuntu and copied the files from the /boot directory to the partition which should be mounted in /boot on startup.
everything's working now.
Last edited by thok (2011-03-22 16:44:32) -
I have a hard disk that won't mount. It was previosly part of a software mirror RAID. The raid was degraded, so I tried to rebuild the second raid mirror. THis failed, and now the master won't mount either. In TechTools, the drive is reported as being fine, but the volume still won't mount. Any suggestions? This is really setting us back a bit.
Mini, iBook, PowerMac G5, XServe G4 Mac OS X (10.4.4)If you know what you are doing you can check out Article number 106987. If that looks too complicated for you you might want to take the computer to an Apple specialist.
-
External drive volume is recognized but won't mount.
I've searched the support forum and I can't seem to find this problem... MacBook Pro 2.5Ghz Intel Core2Duo. External LaCie 500GB drive. I bought TechTool Pro 5 last week to clean this external drive out and repartition. I did a 7 pass erase, surface scan, and repartitioned the drive for 3 partitions. Everything went smoothly and no errors occurred. So, I attempted to change the Icon for one of the partitions. Ever since then, the volume will not mount to the desktop, therefore is not available in Finder. Using Disk Utility, the volume is there and will verify and checks out without needing repair. Using Tech Tool to rebuild the volume checks out as well. I'm stumped!! Any ideas? I'm sure it's some silly thing I've just never heard of, but I don't have any ideas left in me.
other checkpoints.... In Disk Utility: the drive is in the sidebar, but there is no "Mount" option available for the drive, since it is, apparently, already mounted.
Also... If I use the Finder menu item Go -> Go to Folder and enter "/Volumes" (without the quotes), I can see all 3 volumes on the external drive.
There is about 28GB of data on this volume, but I do have it backed up.
Thanks for any info.Kujawa wrote:
I bought TechTool Pro 5 last week to clean this external drive out and repartition. I did a 7 pass erase, surface scan, and repartitioned the drive.
I'm curious why you didn't try to use Disk Utility to do this.
I attempted to change the Icon for one of the partitions. Ever since then, the volume will not mount to the desktop, therefore will is not available in Finder. Using Disk Utility, the volume is there and will verify and checks out without needing repair.
In Disk Utility, when you select that volume in the "sidebar", under the "File" menu is the "Mount ..." menu item available? If so, what happens if you invoke it?
I'm not suggesting that you use this approach every time, but it might provide additional information that would help others solve your problem. -
Disk utility: Disk without errors but won´t mount after testing
I have a strange problem with disk utilities. I tested an external FW drive and disk utility says that the disk is oK. Unfortunately after testing the disk and closing disk utility the disk won´t mount again. I did this several times but without success. Any hints whatßs going wrong?
Thanks for your help
Best regards
WolfgangPower down and disconnect the FWHD, Restart, zapping the PRAM as detailed in http://support.apple.com/kb/HT1379 and restart. Reconnect the FWHD and power it up. That should do the trick.
Maybe you are looking for
-
Follow up action to set delete flag after UD (QS41, QS51)
Hi all, If user give UD as 'not good' for Equipment (eg Vernier Caliper) then he has to set delete flag for maintenance plan no and Equipment no through IP02 and IE02 respectively now he want that, above delete flag should set automatically after giv
-
Help: Songs Do Not Appear When Importing an itunes Library XML file
I have 2 apple IDs and 2 libraries I want to combine. I've been working on this for hours. I found detailed instructions on making sure all the right preferences are checked, locations are in public folders, and so on. There are no error messages whe
-
System Landscape and System Group
Hi I am trying to find out the difference between adding a system to a System Group and Adding a system to a System Group in System Landscape Directory. I know that adding to a system group has effect on the transport routes while transporting.Howeve
-
Couldn't open Photoshop Lightroom 4-1.pkg package/
I've downloaded the beta Lightroom 4 package, but I'm getting this message that the downloaded file cannot be opened. I have a IMAC with an Intel Core 2 Duo (2.4 GHz) running Mac OS X (10.5.8). I saw the posts that the duo core 2 chip does not suppor
-
mid-late 2007? can you be a bit more specific, will Mavericks work on Intel Core 2 Duo 2.66 GHz 4GB ?