Old Blade Volume won't mount

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    

Similar Messages

  • 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

  • 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 Henke

    There 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 Lion

    I 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 G3

    Thanks for the help. I restored my iPod on my older G3 and now it shows up on both systems again.

  • Old ipod won't mount to new macbook pro

    Hello, I just set up my new MacBook Pro, and when I try to connect my ipod, it won't mount either to the desktop or into iTunes. the screen of the ipod says "do not disconnect" just like with the old computer... and I transferred my account and music and settings from the old one to the new one.
    anyone have any ideas?
    thanks,
    Bruce
    Oh yeah... it's a 40 Gig with a scroll wheel... not sure the "name" of the generation, it says "copyright 2003" on the back.
    and my new shuffle works just fine with the new computer...

    Which version of iTunes does your new MacBook have? You will probably want to update it if it isn't 9.2. Do that first. Also, restart your MacBook book. That will make sure that everything else is working properly as well (I'm thinking USB ports).
    If your touch is still not recognized, you will need to make sure that Apple Mobile Device Services is running properly on the MacBook. See this article: http://support.apple.com/kb/HT1747
    And if you are close to an Apple store and tired of playing with it, make an appointment with Genius and take your MacBook and touch in and let Apple fix it.

  • Hard Disk Won't Mount Volume

    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.

  • External Hard Drive Won't Mount- Need to recover files

    Hello Everyone,
    I am hoping that one of you fine mac experts may be able to assist ~
    Problem: External Seagate FreeAgent Desktop USB external hard drive
    won't mount on desktop=ie: no access to my important files.. Please Help!
    Details:
    External seagate freeagent 500 GB Desktop USB HD ( only 2 months old)
    (using for document / file backup-not as a startup disc)
    on my Mac G3 350 MZ Blue & White Tower /768 ram/ running OSX 10.1.5 & OS9.2~
    ~
    Problem: Started using the external 500 GB HD 2 months ago -with no problems-until this morning. Tried to double click to open it to access files
    and got the "beach ball of death" and needed to restart.
    My trusty G3 started up fine, however, the external HD was now
    not showing up on the desktop as normal. I troubleshooted -by restarting,
    trying different a/c plugs/ different USB ports , ran disk utility..called
    seagate -not much help . Seagate said to try the HD on another mac-which I did-
    a G5 tower- same problem.
    ~
    The External hard drive will show up in disk utility, but is grayed out.
    and when click "mount" same two messages keep showing:
    message 1: "a disk attempting to mount as unknown has failed verification or has failed to
    mount.please use disk utility to check the disk"
    ~
    message 2- when unplugging and repluggin the usb in-and upon
    restart:" you have inserted a disk containg no volumes that mac osx
    can read to use unreadable volumes,click initialize to continue with the disk inserted ,click continue"
    ~
    ( I really need access to these files- and do not want to re-initialize the HD!!)
    I ran Disk Utility /first aid "verify & repair , the following info came up:
    Repairing disk "main backup 2007 ".
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Invalid key length ( <<<IN RED )
    Repair completed. "
    ~~
    Though it said the repair was completed, the "invalid key length" issue
    still comes up when re-running disk utility...Hard drive would still not
    mount on desktop-even after restarting .
    ~~~~~
    If there is a mac genius out there that can help?- it would be greatly
    appreciated. I have tried to call seagate several times in the last several hours-
    1st time-they disconnected me after being on hold 10 minutes-2nd call
    I was put on hold for 40 minutes ..Finally spoke to someone ( they are not mac users or mac experts!)and he said I would need to send it to Seagate's Data Recovery-... for a fee of course!
    ~~~
    At this point, I am hoping to just get the files and photos off
    the hard drive- I heard about Disk Warrior-should I use that and if so
    what version?
    Thank you very much!
    L

    Will zapping the PRAM be of any use in getting the external to mount on the desktop?
    Your external Hard drive is already recognized. But it cannot be mounted on the desktop due to its directory damage. You can certainly Zap the PRAM, and it will not hurt anything, but I am skeptical that it will change the situation.
    Do you think the Disk Warrior 4.0 cd will even work on my G3 350MHZ running Mac OS 10.1.5?
    If you boot from the CD and run it from the CD, absolutely yes. If you attempt to INSTALL it from a download or a CD, probably not.
    Have you ever used Disc Warrior and is using it complicated?
    I own and use Disk Warrior. You select the drive to be rebuilt, it builds a proposed new directory from the information and file fragments available.
    When complete, it will provide a list of problems encountered, tell you what files have been placed in the "Rescued Items" folder, and allow you too look at your drive using the proposed new directory. Your only decision is whether the new directory seems to be an improvement over the old \[in your case, hopelessly corrupted] directory. You then tell it whether to replace the old directory with the proposed new directory, or to abandon its work and leave your Hard Drive unchanged.
    Is there a good chance that the ext HD will still have my files on it- or do you think from what I've described that they are gone ?
    From what you have described, your files are very likely to still be there. Sometimes in a situation like this, a handful of files cannot be recovered.
    My other thought was to take the external HD there and have them try to recover the files.
    Make sure you completely understand the costs involved. File recovery using a service like DriveSavers can run into many hundreds of dollars. They are prepared to disassemble your drive in a clean room and replace controller boards and read/write heads to achieve success. Your drive has serious, but not fatal, Directory damage. The Hardware, and most of your files, are likely just fine.

  • External hard drive won't mount any more

    I do a daily backup of the data on my internal HD to an external HD via FireWire. For some reason, the backup froze tonight - 10 minutes went by with no change in the progress. The only way I could get out of it was to quit everything, Force quit the ones that wouldn't respond, then reboot.
    The internal HD is fine, but the external HD that I back up to won't mount now. I ran Disk Utility, and it sees the drive, but the Finder doesn't. In Disk Utility, if I click on "Verify Disk," I get this message:
    Verifying volume “FireWire Disk”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    The volume FireWire Disk needs to be repaired.
    Volume check failed.
    Error: The underlying task reported failure on exit (-9972)
    1 volume checked
    0 HFS volumes verified
    1 volume failed verification
    Does this mean I have lost everything on the external disk? What do I need to do to get that disk running and mounted again? There were other files on the external disk, besides the backup. There were some large video files that I will have to capture from tape again if they cannot be recovered.
    Thank you for your help!

    Cornelius,
    Thank you for your reply. I was able to get out of the situation through luck. I read on another forum a post by someone in a similar situation, and they said that the drive would mount on a different Mac. So I tried plugging in the drive to my old iMac, and sure enough it mounted, although when Disk Utility was run, the same error message was given.
    Fortunately I was able to copy the files I need from the drive to the iMac's internal drive. The copy worked even though there was obviously a problem with the external drive. Then I erased the external drive using Disk Utility, and copied the files back onto it.
    So I'm back where I started, and I didn't lose any files that I really need. But it was pretty scary for a while - I thought I would have to re-do a lot of work. Fortunately I don't, but I realize how valuable it is to have a second backup in case the first one fails. I am now going to duplicate everything onto the iMac's drive until the project is finished and I can archive it all. I still don't know how the disk got so messed up, and I'm surprised that a disk can get corrupted so easily.

  • External Hard Drive Won't Mount in 10.2.8

    Greetings,
    I have a MacBook Pro running the latest version of Tiger. I have a Maxtor 300 GB external hard drive (Mac OS Extended [journaled] ) which I use with my MacBook to store music, video, other media, and backups. I connect that drive to my MacBook via FireWire, normally, but the drive can also do USB.
    Since wireless connectivity is so nice, I thought it would be nice to be able to access that hard drive from anywhere in my apartment, without being tethered to the drive by a FireWire cable.
    Enter my wife's iBook G3 and Mac OS 10.2.8.
    She has this computer from her school where she teaches. It has a G3 processor running at 600 mhz with 128 mb of ram. Since she rarely uses the old machine, I wanted to use it to "serve" my external hard drive to my MacBook.
    But when I connect the hard drive to the iBook via either USB or FireWire, it does not mount. I ran Disk Utility and the drive is visible in the pane on the left of the interface, but when I verify the disk I get lots of error messages that say, "Reserved fields in the catalog record have incorrect data."
    I don't want to let the iBook repair the disk because I am afraid it my screw the whole thing up and I would lose all my data...not a good proposition.
    So, my question: What is going on here? Is this drive simply not going to work with 10.2.8?
    I wish I could upgrade the machine to Tiger, but it does not have the minimum system requirements!
    Thank you very much for your help. I apologize if I missed something else in the forums that addressed this same issue.
    Macbook Pro 2.0 Ghz Intel Core Duo 1 GB Ram 15.4" LCD   Mac OS X (10.4.7)  

    All you need to upgrade the iBook for Tiger is another 128 MBs of RAM. It has both Firewire and USB ports. You do want to upgrade it for what you plan to do. The problem you may continue to have, however, may be due to the fact that the age of the computer is such the disk controller does not support hard drive volumes larger than 128 GBs, which is probably the reason the drive won't mount.
    The reason you get DU errors is likely because the drive was formatted using the Intel Tiger version of DU, while you were using the Jaguar version. That's a definite no-no.

  • Re: WD External drive won't mount

    Hi
    I have just experienced this issue today. I have gone through all the threads here and searched various other forums but haven't been able to come up with a solution yet. I might be missing something.
    I'm running a 2011 Mac Book Pro OS 10.9.5 Maverick.
    I have a 1TB My Passport for Mac that's a couple of years old now, it is used for my time machine backups. Using WD Drive Utilities, I can run a smart status scan which passes, the quick drive test Cancels.
    In disk utility it appears on the left but is greyed out. The info that is provided tells me it is: (bare with me I'm using my iPad as my MacBook Pro won't allow me to Ely to this forum, an issue to tackle after this one)
    type: partition
    mount point: not mounted
    owners enabled: no
    journeled: no
    disk utility is the only place I can see the drive appear. I don't Have the ability at the moment to connect the drive to a windows pc. I have also tried using disk utilities repair and erase options with no luck. I have tried using terminal and activity monitor several times as previously mentioned in this thread but again no luck but may have missed understood the directions.
    I would simple reformat the drive but suspect because it's greyed out its why I can't.
    any help or directions would be great?
    thanks for your time and knowledge.

    Read all the threads on this.  I am similar to Phoenix86.  I force quit fsck_hfs a few times when I started the bad drive but that did not prompt anything in finder. Currently I am imaging the drive to see if that gives me access to my files on the external.  Last night I did a restore, but the (brand new) drive it saved to behaves just like the bad one that disk utilities so still can't access the files since that one won't mount either.  I also tried a few things in terminal that someone else suggested, but like this repair:
    fsck_hfs -r /dev/disk2s3
    ** /dev/rdisk2s3 (NO WRITE)
    Can't open /dev/rdisk2s3: Permission denied
    I don't know what to do with this message... 
    I feel so stupid, like the files are right there, but I can't get to them to copy them over.  I can hear the disc spin, and it can eject from disk utility, can't open, not even in volumes directory. 

  • WD External drive won't mount

    Hello everyone! I haven't been here in a while because I just haven't had any Mac issues. Now I do.
    I have a 1 TB WD external HD that won't mount. I connect it via firewire to an Old G4 Sawtooth running OS 10.5.8. My mac sees the drive, it just won't mount. I've also tried to mount it via USB, but again, my system sees the drive, but won't mount it. I inadvertantly disconnected the firewire cable, which I didn't realize for several hours. I reattached the cable, tried to mount it, and nothing. I ran disc repairs, and Disc Utility actually told me the drive was successfully repaired. Again I tried to remount it, but nothing. I repaired permissions, and this didn't work. I've tried different cables, and this doesn't work.
    I don't have another Mac to connect it to, so I don't know if this would work. Here's where things get a little wierd, but interesting. I connected it to my PC laptop, and it mounted. Now, this is a drive that was formatted Mac OS Extended (Journaled) on my G4, so I have to use Mac Drive so my PC will recognize and mount The Drive. So My PC sees The Drive as Mac OS Extended, and mounts it. All files are in tact, and the drive runs normally. This is a music drive and it plays normally on my PC. Meanwhile, if I try connecting it back on My Mac, the name of The Drive randomly changes from 931.5 GB WD to 931.5 GB WD My Media Book. I believe My Media Book is the factory name of The Drive before OS formatting. The Volume name remains the same on my G4 each time I've tried to mount it.
    I do have another identical drive that mounts from all the bus ports on my G4. Any ideas here? Can I get my Drive to begin mounting on my G4 again? Any and all answers are appreciated.

    Terminal List. disk4 is the malfunctioning drive.
    Last login: Mon Feb 25 19:25:12 on ttys000
    raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *111.8 Gi   disk0
       1:        Apple_partition_map                         31.5 Ki    disk0s1
       2:             Apple_Driver43                         28.0 Ki    disk0s2
       3:             Apple_Driver43                         28.0 Ki    disk0s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk0s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk0s5
       6:             Apple_FWDriver                         256.0 Ki   disk0s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk0s7
       8:              Apple_Patches                         256.0 Ki   disk0s8
       9:                  Apple_HFS Mac Leopard II          91.8 Gi    disk0s10
      10:                  Apple_HFS Mac Tiger               19.7 Gi    disk0s12
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *186.3 Gi   disk1
       1:        Apple_partition_map                         31.5 Ki    disk1s1
       2:             Apple_Driver43                         28.0 Ki    disk1s2
       3:             Apple_Driver43                         28.0 Ki    disk1s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk1s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk1s5
       6:             Apple_FWDriver                         256.0 Ki   disk1s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk1s7
       8:              Apple_Patches                         256.0 Ki   disk1s8
       9:                  Apple_HFS Mac Leopard I           186.2 Gi   disk1s10
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *465.8 Gi   disk2
       1:        Apple_partition_map                         31.5 Ki    disk2s1
       2:             Apple_Driver43                         28.0 Ki    disk2s2
       3:             Apple_Driver43                         28.0 Ki    disk2s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk2s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk2s5
       6:             Apple_FWDriver                         256.0 Ki   disk2s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk2s7
       8:              Apple_Patches                         256.0 Ki   disk2s8
       9:                  Apple_HFS 500 GB HD               465.6 Gi   disk2s10
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *931.5 Gi   disk3
       1:        Apple_partition_map                         31.5 Ki    disk3s1
       2:             Apple_Driver43                         28.0 Ki    disk3s2
       3:             Apple_Driver43                         28.0 Ki    disk3s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk3s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk3s5
       6:             Apple_FWDriver                         256.0 Ki   disk3s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk3s7
       8:              Apple_Patches                         256.0 Ki   disk3s8
       9:                  Apple_HFS 1 TB Music Drive II     931.4 Gi   disk3s10
    /dev/disk4
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *931.5 Gi   disk4
       1:        Apple_partition_map                         31.5 Ki    disk4s1
       2:             Apple_Driver43                         28.0 Ki    disk4s2
       3:             Apple_Driver43                         28.0 Ki    disk4s3
       4:           Apple_Driver_ATA                         28.0 Ki    disk4s4
       5:           Apple_Driver_ATA                         28.0 Ki    disk4s5
       6:             Apple_FWDriver                         256.0 Ki   disk4s6
       7:         Apple_Driver_IOKit                         256.0 Ki   disk4s7
       8:              Apple_Patches                         256.0 Ki   disk4s8
       9:                  Apple_HFS 1TB Music Drive         931.4 Gi   disk4s10
    raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$
    Terminal info on disk4s10.
    Last login: Mon Feb 25 22:22:41 on ttys000
    raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$ diskutil info disk4s10
       Device Identifier:        disk4s10
       Device Node:              /dev/disk4s10
       Part Of Whole:            disk4
       Device / Media Name:      Apple_HFS_Untitled_1
       Volume Name:              1TB Music Drive
       Mount Point:             
       File System:              Journaled HFS+
       Owners:                   Disabled
       Partition Type:           Apple_HFS
       Bootable:                 Is bootable
       Media Type:               Generic
       Protocol:                 FireWire
       SMART Status:             Not Supported
       Volume UUID:              61A8EAFF-E1C9-3605-AF92-5A210E3C781A
       Total Size:               931.4 Gi (1000069726208 B) (1953261184 512-byte blocks)
       Free Space:               0.0 B (0 B) (0 512-byte blocks)
       Read Only:                No
       Ejectable:                Yes
       Whole:                    No
       Internal:                 No
    Disk Utility Info on 1TB Music Drive.
    Name :
    1TB Music Drive
    Type :
    Volume
    Disk Identifier :
    disk4s10
    Mount Point :
    Not mounted
    File System :
    Mac OS Extended (Journaled)
    Connection Bus :
    FireWire
    Device Tree :
    IODeviceTree:fwx/node@90a9c5c29aa50b/sbp-2@c000
    Writable :
    Yes
    Universal Unique Identifier :
    61A8EAFF-E1C9-3605-AF92-5A210E3C781A
    Capacity :
    931.4 GB (1,000,069,726,208 Bytes)
    Owners Enabled :
    No
    Can Turn Owners Off :
    Yes
    Can Be Formatted :
    Yes
    Bootable :
    Yes
    Supports Journaling :
    Yes
    Journaled :
    No
    Disk Number :
    4
    Partition Number :
    10
    I've read that WD uses crappy chipsets in their external drives. I'm wondering if the chipset is suspect here? Just not sure. I did discover that I can clone the drive from my PC as an exact Mac OS Extended (Journaled) drive, and my Mac doesn't even know the difference. I've also read that I can initialize the drive, and reinsert the drivers, and the drive should function normally. Interesting, huh? Well, let me know what you come up with BDAqua. And again, many, many thanks.

  • Time Machine Problems - Won't Launch Automatically, Won't Mount Disk Image

    Hi there,
    I have a MacBook Pro (Mid 2009) running OSX Mavericks 10.9.2.  I've had Time Machine running successfully with a 2TB Time Capsule for some time.  Recently, I reinstalled Parallels VM software and have been having issues with Time Machine ever since.  Initially, I had TM backing up the Virtual Machine, but decided that wasn't a great way to go, so turned it off in the VM configurations pane.
    Since then, however, I have been unable to successfully back up my MacBook.  I notice a few things:
    The Time Machine drive does not mount as it used to.  It does not show up on my desktop.
    When I go into Time Machine Preferences, the drive does not show the usual green disk icon.  The icon is blue and has the stick-figure people on it.
    I can remove the blue disk drive, and re-select the drive.  It stays green for about 30 seconds, then converts to the blue icon.
    I get a number of plist errors in the Time Machine dashboard app.  Here's the latest feed:
    Property list invalid for format: 200 (property lists cannot contain NULL)
    Property list invalid for format: 200 (property lists cannot contain NULL)
    Property list invalid for format: 200 (property lists cannot contain NULL)
    Starting manual backup
    Network destination already mounted at: /Volumes/Sean's Time Capsule
    Disk image /Volumes/Sean's Time Capsule/Sean's MacBook.sparsebundle mounted at: /Volumes/Time Machine Backups
    Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
    Backup canceled.
    At this point, I'm a bit stumped.  I've tried deleting the old sparsebundle, I've reset the Time Capsule, and I've come up with no ideas as to how I can get this woring again.  It seems like the property list needs 'something' but can't find the old file or the property list is corrupt or something.  I'm assuming that is why the Time Machine disk image won't mount?
    Thanks for your help - suggestions are welcome!

    1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
    2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
    3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the request of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
    Here's a summary of what you need to do, if you choose to proceed:
    ☞ Copy a line of text in this window to the Clipboard.
    ☞ Paste into the window of another application.
    ☞ Wait for the test to run. It usually takes a few minutes.
    ☞ Paste the results, which will have been copied automatically, back into a reply on this page.
    The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
    4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
    5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
    6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
    Triple-click anywhere in the line of text below on this page to select it:
    PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports 'com.autodesk.AutoCad com.evenflow.dropbox com.google.GoogleDrive' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^\([0-9]+\) /,"");n=$0;getline;} $NF=="'${p[45]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n\t(%s)\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}')printf("%s (UID %s) is using %s '${p[$2]}'\\\\n",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */   /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ s/ *:$//;x;s/\n//;/Apple|Genesy|Intel|SMSC/d;s/\n.*//;/\)/p;};/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;} ' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/:/;END { if(NR<100)print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { $4="";gsub("  "," ");gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}')print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR==2'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' ' s/^.{52}//;s/ .+//p ' ' /Launch[AD].+\.plist$/;END{if(NR<100)print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' '/\.(framew|lproj)/d;/plist:|:.+(M.+exec|scrip)/s/:[^:]+//p' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/;END{if(NR<100)print "/System/"};' '/^\/usr\/lib\/.+dylib$/p' '/\/etc\/(auto_m|hosts[^.]|peri)/s/^\.\/[^/]+//p' ' /\/(Contents\/.+\/Contents|Frameworks)\//d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| ","||kMDItem'${p[35]}'=");sub("^.."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a)print "CPU: "a;if(b)print "I/O: "b;if(c)print "Net: "c" (KiB/s)";if(d)print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' /lR/ { if($2<='${p[25]}')print $2;} ' ' BEGIN { FS=":";} $3~/(sh|ng|ic)$/ { n=split($3,a,".");sub(/_2.+/,"",a[n-1]);b=b"\n"$2" "a[n-1]" "a[n]" "$1;c=c$1;} END { d="sort|tail -n'${p[38]}'";print b|d;close(d);if(c)print("\n\t* Code injection");} ' ' NR!=4{next} {$NF=int($NF/10240)} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L)f=f"\n   "$0;} END { F=FILENAME;if(!F)exit;if(!f) f="\n   [N/A]";"file -b "F|getline T;if(T!~/^(A.+ E.+ text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n   ...and %s more line(s)\n",l-L);} ' ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ +B/{ s/.+= |(-[0-9]+)?\.s.+//g;p;} ' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' /:/{$0="'"${p[28]}"'"};1;' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil PlistBuddy whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup );c2=(com.apple.loginwindow\ LoginHook '-c Print /L*/P*/loginw*' '-c Print L*/P*/*loginit*' '-c Print L*/Saf*/*/E*.plist' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \)' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' '-c Print\ :'${p[35]}' 2>&1' '-c Print\ :Label 2>&1' '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status '-F bsd -k Sender kernel -k Message Req "Beac|caug|dead[^bl]|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA\(|pagin|proc: t|Roamed|rror|ssert|Thrott|timed? ?o|WARN" -k Message Rne "Goog|ksadm|SMC:" -o -k Sender fseventsd -k Message Req "SL"' '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/*/*.{BS,Bas,Es,OSXU,Rem}*.bom' '{/,}L*/Lo*/Diag* -type f \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true \) -execdir stat -f:%Sc:%N -t%F {} \;' '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto_master,{cron,fs}tab,hosts,{launchd,sysctl}.conf} /usr/local/etc/periodic/*/* .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n 'syscall::'${p[33+j]}':return {@out[execname,uid]=sum(arg0)} tick-10sec {trunc(@out,1);exit(0)}'";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP RSSI Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear;};for i in 0 1;do eval ' A'$((1+i))'() { v[0]=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "${v[0]}" ]];};A'$((3+i))'() { v[0]=` while read i;do eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "${v[0]}" ]];};A'$((5+i))'() { v[0]=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "${v[0]}" ]];};';done;A7(){ v[0]=$((`date +%s`-v[3]));};B2(){ v[$1]="${v[0]}";};for i in 0 1;do eval ' B'$i'() { unset v[0];((v['$((i+1))']==0))||{ v[0]=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v[0]=` paste -d: <(echo "${v[$1]}") <(echo "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v[0]=`grep -Fv "${v[$1]}"<<<"${v[0]}"`;};C0(){ test "${v[0]}"&&echo "$_";};C1() { [[ "${v[0]}" ]]&&printf "${f[$1]}" "${l[$2]}" "${v[0]}";};C2() { v[0]=`echo ${v[0]}`;[[ "${v[0]}" != 0 ]]&&C1 0 $1;};C3() { v[0]=`sed -E "${s[0]}"<<<"${v[0]}"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;A0;{ A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D22 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A4 14 6 11 0;B2 0 5;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A4 14 7 11 6;B2 0 7;B3 4 0 22;A4 14 6 11 0;B2 0 8;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D23 24 24 32 31;D13 25 37 32 33;A1 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D23 14 1 48 42;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;D22 32 31 43 38;D23 20 42 32 41;D23 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 14 3 49 5;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-  
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    7. Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
    8. If you see an error message in the Terminal window such as "syntax error," enter
    exec bash
    and press return. Then paste the script again.
    9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
    If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
    10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
    [Process completed]
    to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
    11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
    At the top of the results, there will be a line that begins with "Model Identifier." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
    If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
    12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
    Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
    Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

  • A volume failed to mount/Operation cannot be completed

    We bought a MacBook on the weekend. Our Apple concierge insisted that we can keep our music, videos and photos on our Windows XP desktop and "share" the files on the Mac--in other words, we can pull down what we need to edit or save on the Mac as need be.
    We've set up the shared directories on the Windows machine, renamed the Workgroup to match the Mac and disabled the firewall. We've "connected to server" using Finder and can see the two shared directories we've set up.
    But when I click on either one of them, I get an error message: "A volume failed to mount. The volume "Mac" could not be mounted."
    After some time of being on the network, I see a Shared directory in Finder with my PC. If I click on the icon, the title bar says: "Connected as: Guest". The window displays the same two directories as above but when I click on one or the other I get an error message: "The operation cannot be completed because the original item for "Mac" cannot be found."
    I've called Apple technical support and the agent's response was: I don't think you can do that. Just copy your files to the Mac using DVDs.
    Any ideas? We don't want to have to transfer a lifetime of photos, video and music to our laptop--we want to use the XP desktop as our hub.

    I'm having the same trouble. From an Intel Mac Mini running 10.5.3 I've been able to access smb shares fine on an old PC running XP pro. These are shared volumes on external drives on the PC. I can still access them fine from an old PowerBook G4 running 10.5.3, but while I can see computers on the network, if I try to connect to a share on the computer I get the message "the operation cannot be completed because the original item for <share name> cannot be found". If I try to mount it via a shortcut, I get the message "A volume failed to mount. The volume <share name> could not be mounted.
    In the console, I'm seeing things like:
    6/2/08 10:45:01 PM com.apple.coreservicesd[58] NOTE: Using non-mach-based version of client -> server communication, via direct function calls.
    but I don't know if that has anything to do with this or not.
    Has anyone heard of a fix for this?
    Thanks,
    Mark

Maybe you are looking for

  • Creation of multiple outbound delivery

    Hi experts,                  I have done inbound delivery having 3 line items (materials).    For 3 line items system has created as per requirement single inbound delivery document.  A single material document & single inbound delivery is created. 

  • CS4 and Windows 7?

    I have CS3 currently running on Vista Home Premium 64-bit. It was kind of a pain to get working. Microsoft is running a preorder sale on Windows 7 right now, and since the price is good, I am planning to upgrade (it'll be released in October I think)

  • Spotlight doesnt' index

    On both my old iBook and my new iMac, Spotlight doesn't work on the HDs (but works on any connected USB drive), Google Desktop doesn't work either ("no indexing"). Putting/deleting the HDs in the privacy part of Spotlight Preferences doesn't change a

  • Oracle listeners/dispatchers/shared servers

    Hi, Should the Oracle listeners/dispatchers/shared servers be set up to work with BEA's connection pooling features? If so how? Regards Vaidy

  • SAP ECC6.0 (EHP4) Installation

    Hi, Iam trying to install ECC6.0 with EHP 4.0 is compatible in windows server 2008 R2 standard OS? i Have 500 GB HHD,4 GB Ram in my laptop.it is intelcore i5 2nd Generation Processor. so Please Tell Which OS is compatible for ECC6.0? Iam trying in wi