Duplication problem: Drive or volume on which mount attempted is unusable.

Greetings.
I have a duplication job that's been trying to complete. That is, it starts and eventually fails with the following in the transcript (I put parameters in place of the actual names):
+2010/01/21.10:34:27 No volume could be found in <library name> (for drive tape1) to use for job 8171.+
+2010/01/21.10:34:27 Volume ID <volume label> is needed to perform a restore.+
and in the Job Properties window:
+2010/01/21.10:00:01 Dispatching job to run on administrative server.+
+2010/01/21.10:34:27 Drive or volume on which mount attempted is unusable.+
The requirement for the job is the following:
volume <volume label> and family <family> and host <hostname> and any device@<hostname> and any device@<hostname>
The volume with the above volume label is in the library. There are a number of unlabeled volumes ready for use in the library. Finally, there are several expired volumes from the required media family in the library.
Any ideas?
Thank you for your attention.
-Jeff
Edited by: user12198316 on Jan 21, 2010 8:19 AM

It's pretty huge.
cut out 17th through 21st
2010/01/22.10:00:01 ______________________________________________________________________
2010/01/22.10:00:01
2010/01/22.10:00:01 Transcript for job 8171 running on backup01
2010/01/22.10:00:01
2010/01/22.10:00:01 (amh) qdv__automount_in_mh tape1 at 2010/01/22.10:00:01, flags 0x100
2010/01/22.10:00:01 (amh) mount volume options list contains:
2010/01/22.10:00:01 (amh) vtype 1, vid PASWLY-000215, vs_create 0, family (null), retain (null), size 0, scratch 0
2010/01/22.10:00:02 (amh) don't preserve previous mh automount state
2010/01/22.10:00:02 (amh) loaded volume has no barcode
2010/01/22.10:00:03 (amh) beginning pass 1
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PAS-RMAN-018887
2010/01/22.10:00:03 (mmr) oid 20543 (vid PAS-RMAN-018887, tag 000048L3) fails mount criteria
2010/01/22.10:00:03 (amh) 2 oid 20543 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000487
2010/01/22.10:00:03 (mmr) oid 20909 (vid PASDLY-000487, tag 000021L3) fails mount criteria
2010/01/22.10:00:03 (amh) 3 oid 20909 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 4 no vid
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000486
2010/01/22.10:00:03 (mmr) oid 20908 (vid PASDLY-000486, tag 000054L3) fails mount criteria
2010/01/22.10:00:03 (amh) 5 oid 20908 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000488
2010/01/22.10:00:03 (mmr) oid 20911 (vid PASDLY-000488, tag 000047L3) fails mount criteria
2010/01/22.10:00:03 (amh) 6 oid 20911 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000485
2010/01/22.10:00:03 (mmr) oid 20904 (vid PASDLY-000485, tag 000015L3) fails mount criteria
2010/01/22.10:00:03 (amh) 7 oid 20904 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000483
2010/01/22.10:00:03 (mmr) oid 20889 (vid PASDLY-000483, tag 000008L3) fails mount criteria
2010/01/22.10:00:03 (amh) 8 oid 20889 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000482
2010/01/22.10:00:03 (mmr) oid 20888 (vid PASDLY-000482, tag 000039L3) fails mount criteria
2010/01/22.10:00:03 (amh) 9 oid 20888 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000490
2010/01/22.10:00:03 (mmr) oid 20914 (vid PASDLY-000490, tag 000100L3) fails mount criteria
2010/01/22.10:00:03 (amh) 10 oid 20914 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000489
2010/01/22.10:00:03 (mmr) oid 20912 (vid PASDLY-000489, tag 000081L3) fails mount criteria
2010/01/22.10:00:03 (amh) 11 oid 20912 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000491
2010/01/22.10:00:03 (mmr) oid 20915 (vid PASDLY-000491, tag 000101L3) fails mount criteria
2010/01/22.10:00:03 (amh) 12 oid 20915 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000219
2010/01/22.10:00:03 (mmr) oid 20891 (vid PASWLY-000219, tag 000102L3) fails mount criteria
2010/01/22.10:00:03 (amh) 13 oid 20891 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000220
2010/01/22.10:00:03 (mmr) oid 20892 (vid PASWLY-000220, tag 000103L3) fails mount criteria
2010/01/22.10:00:03 (amh) 14 oid 20892 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 15 no vid
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != OFFWLY-000151
2010/01/22.10:00:03 (mmr) oid 20739 (vid OFFWLY-000151, tag 000032L3) fails mount criteria
2010/01/22.10:00:03 (amh) 16 oid 20739 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000484
2010/01/22.10:00:03 (mmr) oid 20903 (vid PASDLY-000484, tag 000106L3) fails mount criteria
2010/01/22.10:00:03 (amh) 17 oid 20903 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 18 no vid
2010/01/22.10:00:03 (amh) 19 no vid
2010/01/22.10:00:03 (amh) 20 no vid
2010/01/22.10:00:03 (amh) 21 no vid
2010/01/22.10:00:03 (amh) 22 no vid
2010/01/22.10:00:03 (amh) 23 no vid
2010/01/22.10:00:03 (amh) 24 no vid
2010/01/22.10:00:03 (amh) 25 no vid
2010/01/22.10:00:03 (amh) 26 no vid
2010/01/22.10:00:03 (amh) 27 no vid
2010/01/22.10:00:03 (amh) 28 no vid
2010/01/22.10:00:03 (amh) 29 no vid
2010/01/22.10:00:03 (amh) 30 no vid
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000218
2010/01/22.10:00:03 (mmr) oid 20890 (vid PASWLY-000218, tag 000005L3) fails mount criteria
2010/01/22.10:00:03 (amh) 31 oid 20890 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 32 cleaning tape
2010/01/22.10:00:03 (amh) end of pass 1 at 2010/01/22.10:00:03
2010/01/22.10:00:03 (amh) beginning pass 2
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PAS-RMAN-018887
2010/01/22.10:00:03 (mmr) oid 20543 (vid PAS-RMAN-018887, tag 000048L3) fails mount criteria
2010/01/22.10:00:03 (amh) 2 oid 20543 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000487
2010/01/22.10:00:03 (mmr) oid 20909 (vid PASDLY-000487, tag 000021L3) fails mount criteria
2010/01/22.10:00:03 (amh) 3 oid 20909 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20416 (000084L3) fails mount criteria
2010/01/22.10:00:03 (amh) 4 oid 20416 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000486
2010/01/22.10:00:03 (mmr) oid 20908 (vid PASDLY-000486, tag 000054L3) fails mount criteria
2010/01/22.10:00:03 (amh) 5 oid 20908 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000488
2010/01/22.10:00:03 (mmr) oid 20911 (vid PASDLY-000488, tag 000047L3) fails mount criteria
2010/01/22.10:00:03 (amh) 6 oid 20911 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000485
2010/01/22.10:00:03 (mmr) oid 20904 (vid PASDLY-000485, tag 000015L3) fails mount criteria
2010/01/22.10:00:03 (amh) 7 oid 20904 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000483
2010/01/22.10:00:03 (mmr) oid 20889 (vid PASDLY-000483, tag 000008L3) fails mount criteria
2010/01/22.10:00:03 (amh) 8 oid 20889 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000482
2010/01/22.10:00:03 (mmr) oid 20888 (vid PASDLY-000482, tag 000039L3) fails mount criteria
2010/01/22.10:00:03 (amh) 9 oid 20888 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000490
2010/01/22.10:00:03 (mmr) oid 20914 (vid PASDLY-000490, tag 000100L3) fails mount criteria
2010/01/22.10:00:03 (amh) 10 oid 20914 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000489
2010/01/22.10:00:03 (mmr) oid 20912 (vid PASDLY-000489, tag 000081L3) fails mount criteria
2010/01/22.10:00:03 (amh) 11 oid 20912 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000491
2010/01/22.10:00:03 (mmr) oid 20915 (vid PASDLY-000491, tag 000101L3) fails mount criteria
2010/01/22.10:00:03 (amh) 12 oid 20915 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000219
2010/01/22.10:00:03 (mmr) oid 20891 (vid PASWLY-000219, tag 000102L3) fails mount criteria
2010/01/22.10:00:03 (amh) 13 oid 20891 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000220
2010/01/22.10:00:03 (mmr) oid 20892 (vid PASWLY-000220, tag 000103L3) fails mount criteria
2010/01/22.10:00:03 (amh) 14 oid 20892 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20145 (000065L3) fails mount criteria
2010/01/22.10:00:03 (amh) 15 oid 20145 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != OFFWLY-000151
2010/01/22.10:00:03 (mmr) oid 20739 (vid OFFWLY-000151, tag 000032L3) fails mount criteria
2010/01/22.10:00:03 (amh) 16 oid 20739 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASDLY-000484
2010/01/22.10:00:03 (mmr) oid 20903 (vid PASDLY-000484, tag 000106L3) fails mount criteria
2010/01/22.10:00:03 (amh) 17 oid 20903 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20870 (000107L3) fails mount criteria
2010/01/22.10:00:03 (amh) 18 oid 20870 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20871 (000108L3) fails mount criteria
2010/01/22.10:00:03 (amh) 19 oid 20871 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20872 (000109L3) fails mount criteria
2010/01/22.10:00:03 (amh) 20 oid 20872 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20873 (000110L3) fails mount criteria
2010/01/22.10:00:03 (amh) 21 oid 20873 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20874 (000111L3) fails mount criteria
2010/01/22.10:00:03 (amh) 22 oid 20874 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20875 (000112L3) fails mount criteria
2010/01/22.10:00:03 (amh) 23 oid 20875 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20876 (000113L3) fails mount criteria
2010/01/22.10:00:03 (amh) 24 oid 20876 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20877 (000114L3) fails mount criteria
2010/01/22.10:00:03 (amh) 25 oid 20877 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20878 (000115L3) fails mount criteria
2010/01/22.10:00:03 (amh) 26 oid 20878 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20879 (000116L3) fails mount criteria
2010/01/22.10:00:03 (amh) 27 oid 20879 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20880 (000117L3) fails mount criteria
2010/01/22.10:00:03 (amh) 28 oid 20880 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20881 (000118L3) fails mount criteria
2010/01/22.10:00:03 (amh) 29 oid 20881 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 !=
2010/01/22.10:00:03 (mmr) oid 20882 (000119L3) fails mount criteria
2010/01/22.10:00:03 (amh) 30 oid 20882 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (mmr) vid PASWLY-000215 != PASWLY-000218
2010/01/22.10:00:03 (mmr) oid 20890 (vid PASWLY-000218, tag 000005L3) fails mount criteria
2010/01/22.10:00:03 (amh) 31 oid 20890 doesn't meet mount requirements - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:03 (amh) 32 cleaning tape
2010/01/22.10:00:03 (amh) end of pass 2 at 2010/01/22.10:00:03
2010/01/22.10:00:03 (amh) beginning pass 3
2010/01/22.10:00:03 (amh) 2 not unlabeled
2010/01/22.10:00:03 (amh) 3 not unlabeled
2010/01/22.10:00:03 (amh) 4 loading
2010/01/22.10:00:52 (mt) qdv__read_label() succeeded; read 65536 bytes
2010/01/22.10:00:52 (atv) automount failed after criteria check - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:00:52 (amh) 4 automount failed - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:01:26 (amh) 5 not unlabeled
2010/01/22.10:01:26 (amh) 6 not unlabeled
2010/01/22.10:01:26 (amh) 7 not unlabeled
2010/01/22.10:01:26 (amh) 8 not unlabeled
2010/01/22.10:01:26 (amh) 9 not unlabeled
2010/01/22.10:01:26 (amh) 10 not unlabeled
2010/01/22.10:01:26 (amh) 11 not unlabeled
2010/01/22.10:01:26 (amh) 12 not unlabeled
2010/01/22.10:01:26 (amh) 13 not unlabeled
2010/01/22.10:01:26 (amh) 14 not unlabeled
2010/01/22.10:01:26 (amh) 15 loading
2010/01/22.10:02:14 (mt) qdv__read_label() succeeded; read 65536 bytes
2010/01/22.10:02:14 (atv) automount failed after criteria check - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:02:14 (amh) 15 automount failed - volume doesn't meet mount criteria (OB device mgr)
2010/01/22.10:02:48 (amh) 16 not unlabeled
2010/01/22.10:02:48 (amh) 17 not unlabeled
2010/01/22.10:02:48 (amh) 18 loading
2010/01/22.10:03:31 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:03:31 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:03:31 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:03:31 (amh) 18 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:04:04 (amh) 19 loading
2010/01/22.10:04:46 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:04:47 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:04:47 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:04:47 (amh) 19 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:05:21 (amh) 20 loading
2010/01/22.10:06:05 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:06:05 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:06:05 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:06:05 (amh) 20 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:06:39 (amh) 21 loading
2010/01/22.10:07:23 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:07:24 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:07:24 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:07:24 (amh) 21 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:07:58 (amh) 22 loading
2010/01/22.10:08:42 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:08:43 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:08:43 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:08:43 (amh) 22 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:09:16 (amh) 23 loading
2010/01/22.10:10:00 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:10:00 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:10:00 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:10:00 (amh) 23 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:10:34 (amh) 24 loading
2010/01/22.10:11:18 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:11:18 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:11:18 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:11:18 (amh) 24 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:11:52 (amh) 25 loading
2010/01/22.10:12:37 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:12:37 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:12:37 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:12:37 (amh) 25 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:13:12 (amh) 26 loading
2010/01/22.10:13:58 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:13:59 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:13:59 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:13:59 (amh) 26 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:14:32 (amh) 27 loading
2010/01/22.10:15:18 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:15:19 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:15:19 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:15:19 (amh) 27 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:15:53 (amh) 28 loading
2010/01/22.10:16:39 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:16:39 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:16:39 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:16:39 (amh) 28 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:17:14 (amh) 29 loading
2010/01/22.10:18:00 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:18:00 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:18:00 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:18:00 (amh) 29 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:18:34 (amh) 30 loading
2010/01/22.10:19:15 (mt) qdv__read_label() failed - blank medium encountered (OB device mgr)
2010/01/22.10:19:15 (atv) volume unusable for reading - not labeled (it's blank)
2010/01/22.10:19:15 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:19:15 (amh) 30 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:19:48 (amh) 31 not unlabeled
2010/01/22.10:19:48 (amh) 32 cleaning tape
2010/01/22.10:19:48 (amh) end of pass 3 at 2010/01/22.10:19:48
2010/01/22.10:19:48 (amh) beginning pass 4
2010/01/22.10:19:48 (amh) 2 not unlabeled
2010/01/22.10:19:48 (amh) 3 not unlabeled
2010/01/22.10:19:48 (amh) 4 not unlabeled
2010/01/22.10:19:48 (amh) 5 not unlabeled
2010/01/22.10:19:48 (amh) 6 not unlabeled
2010/01/22.10:19:48 (amh) 7 not unlabeled
2010/01/22.10:19:48 (amh) 8 not unlabeled
2010/01/22.10:19:48 (amh) 9 not unlabeled
2010/01/22.10:19:48 (amh) 10 not unlabeled
2010/01/22.10:19:48 (amh) 11 not unlabeled
2010/01/22.10:19:48 (amh) 12 not unlabeled
2010/01/22.10:19:48 (amh) 13 not unlabeled
2010/01/22.10:19:48 (amh) 14 not unlabeled
2010/01/22.10:19:48 (amh) 15 not unlabeled
2010/01/22.10:19:48 (amh) 16 not unlabeled
2010/01/22.10:19:48 (amh) 17 not unlabeled
2010/01/22.10:19:48 (amh) 18 loading
2010/01/22.10:20:29 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:20:29 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:20:29 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:20:29 (amh) 18 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:21:01 (amh) 19 loading
2010/01/22.10:21:44 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:21:44 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:21:44 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:21:44 (amh) 19 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:22:19 (amh) 20 loading
2010/01/22.10:23:03 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:23:03 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:23:03 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:23:03 (amh) 20 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:23:36 (amh) 21 loading
2010/01/22.10:24:27 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:24:27 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:24:27 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:24:27 (amh) 21 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:25:01 (amh) 22 loading
2010/01/22.10:25:45 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:25:46 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:25:46 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:25:46 (amh) 22 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:26:39 (amh) 23 loading
2010/01/22.10:27:22 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:27:23 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:27:23 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:27:23 (amh) 23 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:27:56 (amh) 24 loading
2010/01/22.10:28:40 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:28:40 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:28:40 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:28:40 (amh) 24 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:29:13 (amh) 25 loading
2010/01/22.10:29:56 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:29:57 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:29:57 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:29:57 (amh) 25 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:30:31 (amh) 26 loading
2010/01/22.10:31:17 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:31:18 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:31:18 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:31:18 (amh) 26 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:31:52 (amh) 27 loading
2010/01/22.10:32:38 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:32:39 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:32:39 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:32:39 (amh) 27 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:33:13 (amh) 28 loading
2010/01/22.10:33:59 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:34:00 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:34:00 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:34:00 (amh) 28 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:34:34 (amh) 29 loading
2010/01/22.10:35:20 (mt) qdv__read_label() failed - filemark encountered (OB device mgr)
2010/01/22.10:35:20 (atv) volume unusable for reading - not labeled (it's unlabeled)
2010/01/22.10:35:20 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:35:20 (amh) 29 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:35:55 (amh) 30 loading
2010/01/22.10:36:35 (mt) qdv__read_label() failed - blank medium encountered (OB device mgr)
2010/01/22.10:36:36 (atv) volume unusable for reading - not labeled (it's blank)
2010/01/22.10:36:36 (atv) automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:36:36 (amh) 30 automount failed - invalid backup image label (OB device mgr)
2010/01/22.10:37:08 (amh) 31 not unlabeled
2010/01/22.10:37:08 (amh) 32 cleaning tape
2010/01/22.10:37:08 (amh) end of pass 4 at 2010/01/22.10:37:08
2010/01/22.10:37:08 (amh) reporting no match in library
2010/01/22.10:37:08 (amh) end of automount at 2010/01/22.10:37:08 (0x20009624)
2010/01/22.10:37:08 ---
2010/01/22.10:37:08 No volume could be found in px500-1 (for drive tape1) to use for job 8171.
2010/01/22.10:37:08 Volume ID PASWLY-000215 is needed to perform a restore.

Similar Messages

  • 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.
    Thanks

    That 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.

  • What's Happening?? Some days after installing latest security up date for 10.5.8 on G4, both inernal CD/DVD drives failed to mount disks other than a cleaning disk which mounted and was imported into iTunes.No other CD or DVD disk will mount.

    What's Happening?? Some days after installing latest security update for 10.5.8 on G4, both inernal CD/DVD drives failed to mount disks other than a cleaning disk which mounted and was imported into iTunes. No other CD or DVD disk will mount.Is this a unique experience?

    Hello Robert,
    First, Safe Boot , (holding Shift key down at bootup), use Disk Utility from there to Repair Permissions, test if things work OK in Safe Mode.
    Then move these files to the Desktop...
    /Users/YourUserName/Library/Preferences/com.apple.finder.plist
    /Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
    /Users/YourUserName/Library/Preferences/com.apple.desktop.plist
    /Users/YourUserName/Library/Preferences/com.apple.recentitems.plist
    Reboot & test.
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.

  • AppleRAID Volume no longer mounting

    i applied the "itunes 7.7.1" and "security update 2008-005" updates this morning, which required a reboot.
    after rebooting, my concatenated AppleRAID volume no longer mounts!
    if i run a "diskutil listRAID", it returns:
    RAID SETS
    ===============================================================================
    Name: JINGORAID
    Unique ID: F585E2F9-1ECA-4B8B-942D-9DD156007871
    Type: Concat
    Status: Online
    Size: 1398869557248 B
    Apple RAID Version: 2
    # Device Node UUID Status
    0 disk1s2 EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2 Online
    1 disk3s2 9488CE07-B8CE-4FCC-9987-CF9780D59049 Online
    2 disk4s2 114E4753-E461-49BF-B0C7-EDCD308B628C Online
    ===============================================================================
    in the console log, there is the following info relating to this (filtered only "JINGORAID" entries):
    Aug 14 08:35:29 imac mds[33]: (/Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-959 2FA8E4526)(Error) IndexCI in openPayload:open err: 2, live.0.shadowIndexTermIds
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002d9 detected for set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871), member EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2, set byte offset = 3285610496.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002d9 detected for set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871), member EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2, set byte offset = 4578750464.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::recover() member EB9F670B-9BDD-4F97-9DA2-CF81597EC1C2 from set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871) has been marked offline.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::recover() member 9488CE07-B8CE-4FCC-9987-CF9780D59049 from set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871) has been marked offline.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::recover() member 114E4753-E461-49BF-B0C7-EDCD308B628C from set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871) has been marked offline.
    Aug 14 09:05:09 imac kernel[0]: AppleRAID::restartSet - restarting set "JINGORAID" (F585E2F9-1ECA-4B8B-942D-9DD156007871).
    Aug 14 09:06:09 imac shutdown[737]: reboot by jingo_man:
    Aug 14 10:35:01 imac fsck_hfs[121]: fsck_hfs(121) malloc: * error for object 0x401380: Non-aligned pointer being freed (2)\n* set a breakpoint in mallocerrorbreak to debug
    Aug 14 10:35:16 imac ReportCrash[315]: Formulating crash report for process fsck_hfs[121]
    Aug 14 10:35:16 imac ReportCrash[315]: Saved crashreport to /Library/Logs/CrashReporter/fsckhfs_2008-08-14-103516imac.crash using uid: 0 gid: 0, euid: 0 egid: 0
    Aug 14 10:35:17 imac diskarbitrationd[44]: unable to repair /dev/disk5 (status code 0x0000000B).
    Aug 14 10:35:17 imac mds[34]: (/Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-959 2FA8E4526)(Error) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-9592 FA8E4526/live.1.; needs recovery
    Aug 14 10:35:17 imac mds[34]: (/Volumes/JINGORAID/.Spotlight-V100/Store-V1/Stores/A00BA05E-2636-4606-ABEF-959 2FA8E4526)(Error) IndexCI in openPayload:open err: 2, live.0.shadowIndexTermIds
    just as i was writing this, a pop-up came on screen saying there is imminent failures or something, and has mounted the drive (think this is the last entry in the system.log, above). timing, huh
    what is the cause of this issue?

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of this test is to determine whether the problem is localized to your user account. Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
    While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
    Test while logged in as Guest. Same problem?
    After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
    *Note: If you’ve activated “Find My Mac” or FileVault in OS X 10.7 or later, then you can’t enable the Guest account. The "Guest User" login created by "Find My Mac" is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

  • Mobile accounts WHICH MOUNT POINT?

    How does a machine handling a mobile account
    a. know how to set $HOME ?
    b. know where to mount the folder during sync?
    The scenario and problem:
    (can u help?)(you'll win a free beer if you come to Switzerland).
    I have the user's files stored in /Volumes/team1/users/user1
    The folder /Volumes/team1 is mounted on a local drive on server1.
    The server1 share point, called 'users' is /Volumes/team1/users
    (sounds simple.. doesn't it
    In config-scenario1 I do this:
    The user's share point URL is afp://server1.disneyland.ch/users
    The path to home folder is user1
    The full path is /Network/Servers/server1.disneyland.ch/users/user1
    THIS WORKS ON CLIENT MAC1
    When logged in (via login panel), the $HOME is set to /Users/user1
    and during syncing I see /Volumes/users mounted temporarily (weird,.. it used to show the temporary mount as /Network/Servers/server1.disneyland.ch/users )
    user1@mac1:~ > pwd
    /Users/user1
    user1@mac1:~ >
    THIS WORKS ON SERVER1
    When I ssh into the user, on server1,
    I see $HOME set to /Network/Servers/server1.disneyland.ch/users/user1
    user1@server1:~ > pwd
    /Network/Servers/server1.disneyland.ch/users/user1
    user1@server1:~ >
    THIS DOES NOT WORK ON SERVER2
    On server2 where the same external drive is mounted (it's an Xsan using fiber-channel)
    I get this:
    user1$ cd ~
    -bash: cd: /Network/Servers/server1.disneyland.ch/users/user1: No such file or directory
    SOLUTION1 (that fails)(aka config-scenario 2)
    The user's share point URL is afp://server1.disneyland.ch/users
    The path to home folder is user1
    Set the full path to /Volumes/team1/users/user1
    THIS WORKS ON MAC1
    THIS WORKS ON SERVER1
    THIS CAUSES PROBLEMS ON SERVER2 : (see this posting: http://forums.macosxhints.com/showthread.php?p=581557 ).
    Questions :
    1. How is the HOME folder determined by the computer? Despite the two config-scenarios, the client mac1 uses HOME as /Users/user1 (as it should) but not on Server1 or Server2 (on Server1 it always uses the value in the full path specified in the Mobility>Home for the user)(In Server2 it sometimes uses that value and sometimes it uses the previous configuration value).
    2. How is the MOUNT on the client determined? It seems that it is always /Volumes/users (as it should?); Perhaps it is identified by the system seeing what is behind the user's share point? What's weird is that I'm sure/certain that at one point, under config-scenario1, the mount point on mac8 was NOT /Volumes/users but rather /Network/Servers/server1.disneyland.ch ! Did I dream that ?
    3. How can I PREVENT the mount happening on Server2 (it's mounting on top of the existing /Volumes/team1/users !!) ?
    4. If I DO accept config-scenario1, couldn't I just create a symbolic link on server2 in /Network/Server/server1.disneyland.ch/users-->/Volumes/team1/users ?? Actually this doesn't work because even with sudo I can't mkdir /Networks/Servers/server1.disneyland.ch into which I wold have make the users-> link
    ARGHHH!
    Thanx for any insight.
    /shawn

    DrKdev wrote:
    I've bumped the topic over there:
    Then please do not do so here. The point of posting to the appropriate forum is to attract users with interest & expertise in that area. Bumping here, in an inappropriate forum, is annoying since it just keeps the topic near the top of this forum's list where users that have no expertise with or interest in the issue will keep seeing it.
    This generally does not increase your chances of a reply; if anything it will prompt some users to ignore both of your topics.

  • I have a problem with my 4s camera which has come up recently. Everytime I take a picture and look it up via the 'Photos' app, it shows as blank. But when I click on edit on the blank picture, it comes up and I am able to save it back on my photo album.

    I have a problem with my 4s camera which has come up recently. Everytime I take a picture and look it up via the 'Photos' app, it shows as blank. But when I click on edit on the blank picture, it comes up and I am able to save it back on my photo album as a proper image. Besides, I have also experiences the camera working a bit wiered (slow and often blanks out the moment I am ready to take a photo). Any help on this pls?

    Hi Noob Søren
    There are a few things that are confusing in your question.
    As far as I know, you dont have to install Time Machine on this OS as it is already installed for you. You only need to connect a hard drive to your computer via firewire or usb, click on the Time Machine icon, Open Time Machine Preference in the drop down menu and select a disk: your connected hard drive.
    You can of course reformat this connected device, partition it into a few volumes to organise data if you so wish.
    I find it strange that your mac's hard drive is divided into two volumes... perhaps this was created through bootcamp?
    You can access the configuration of your hd through Applications/Utilities/Disk Utilities.
    Clicking on one of the icons on the right hand panel will bring the details of the contents of your hardDrive and volumes. From there you can decide to erase a partition, reformat etc....
    If your hd contains more than one volume, and one of them is empty, you could decide to remove it. Back up all your important data before doing so.
    Hope this helps
    WN

  • Internal Hard Drive Won't Boot or Mount

    I don't know if this is the right forum for this but...
    My 24" iMac running 10.5.2 won't start up. Meaning I can't get past the grey screen. I fsck the disk in single user mode and got back "invalid nobe structure (4,19621)" and repairs failed, then quickly shut down. As I understand it the (4,19621) means that the file with catalog node ID 19621 in the Catalog B-Tree portion of the disk directory has an invalid extent entry. I might be wrong here. If any knows how to correct that problem that would be helpful. But thats not the real problem.
    I should add I tried to boot from the install DVD and repair the disk with disk utility and it would not repair the disk either.
    Disk Utility recognizes the disk as "232.9 GB AAPL Firewire Target Media" and thats all while in target disk mode.
    The real problem is the disk won't mount in firewire target disk mode. I would like to try to recover some of the fills that I haven't backed up mainly in my documents folder or repair this problem.
    I am going to install (well not me) a new hard drive Monday and have a fresh and new system but in the mean time I would like to try to recover some of my files if possible.
    I should add the one time it did mount, all the folders were there but none of the files. And it gave no worrying. I checked the S.M.A.R.T. status and the start up volume yesterday and got the report the disks seems to be okay.
    Any help in getting the disk to mount in firewire target disk mode to repair and/or recover some files would help.
    Message was edited by: windylove

    Thank you for the reply. That was the best and most logical reply.
    DW never got to that point if thats what you are talking about nor did it get past "Inspecting disk" and Step 1: Searching entire disk in final rescue attempt". After hours of the beach ball spinning.
    I am not within my apple care 3 years time frame. When they replace the hard drive tomorrow they said they might be able to recover some of my data in my Users folder.
    Do you think that is possible?
    That is more what I am worried about at this point. All of my important files have been back up there are just a few that weren't.
    You confirmed what I was thinking. Thanks

  • My external hard drive (G-DRIVE Slim 500GB) won't mount?

    My external hard drive (G-DRIVE Slim 500GB) won't mount?
    All of a sudden my hard drive didn't show up in my finder. I checked in disk utility and it was there but greyed out. If I tried mounting it told me that could not be mounted and that I should try 1st aid.
    When I try to verify disk I get a message to tell me that the disk needs to be repaired with the information shown below.
    Verifying volume “G-DRIVE slim”
    Checking file systemChecking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    The volume G-DRIVE slim could not be verified completely.
    Error: This disk needs to be repaired. Click Repair Disk.
    When I perfrom the disk repair it tells me that the disk cannot be repaired and I should back up as much of my files as possible, reformant the disk, and restore my backed up files. The information shown is below:
    Verify and Repair volume “G-DRIVE slim”
    Checking file systemChecking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    The volume G-DRIVE slim could not be verified completely.
    Volume repair complete.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    When I try the same thing on another Mac Book Pro I have the same situation but it tells me the disk is ok and still won't mount after.
    I'm not sure what to do..........

    You need to make your own decision on which to purchase.  Read up on them on their websites because each do something a little different.
    Techtool Pro
    DiskWarrior (Highly Recommended for Directory Damage Repair)

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

  • How do you get Photos to recognize the "old" iPhoto Library on an external drive without it copying it to the internal drive on the computer which is low in HD space?

    How do you get Photos to recognize the “old” iPhoto Library on an external drive without it copying it to the internal drive on the computer which is low in HD space?

    Launch Photos while holding down the alt/options key.
    This will show the Library Chooser panel. Select the library on the external drive. Photos will create a Photos Library on the same drive.
    Photos may not be able to open the library, however, if your external drive has an incompatible file system. It needs to be formatted MacOS Extended (Journaled) and locally mounted, not a remotely mounted volume, as described here:  Format external drives to Mac OS Extended before using with Aperture

  • Disabling USB hard drives but allowing USB keys mounting, possible ?

    Hi all,
    I have a tricky request from one of my customers : they would like to block any external hard drives (firewire and USB) from mounting on the Desktop, BUT would like to allow USB keys only.
    All the clients are unmanaged (local accounts, NOT bound to an Open Directory Master server) and are running OS X 10.4.8 (Intel).
    I found the easy way to prevent any Firewire device to show up.
    I also found how to disable all USB devices (except for keyboard/mouse) : renaming /System/Library/Extensions/IOUSBMassStorageClass.kext
    Problem is, this method won't make any difference between a hard drive and a key, it will block it, period.
    Is there any way to allow some (or all) USB keys only to mount ? My only guess would be to unload some extensions which are listed by the "kextstat" command.
    That could only be possible if USB keys and USB hard drives don't use the same kind/brand of controller/bridge and therefore don't use the same kernel extension.
    Does anyone have a clue on this ?
    Many thanks.
      Mac OS X (10.4.8)  

    Hi all,
    I have a tricky request from one of my customers : they would like to block any external hard drives (firewire and USB) from mounting on the Desktop, BUT would like to allow USB keys only.
    All the clients are unmanaged (local accounts, NOT bound to an Open Directory Master server) and are running OS X 10.4.8 (Intel).
    I found the easy way to prevent any Firewire device to show up.
    I also found how to disable all USB devices (except for keyboard/mouse) : renaming /System/Library/Extensions/IOUSBMassStorageClass.kext
    Problem is, this method won't make any difference between a hard drive and a key, it will block it, period.
    Is there any way to allow some (or all) USB keys only to mount ? My only guess would be to unload some extensions which are listed by the "kextstat" command.
    That could only be possible if USB keys and USB hard drives don't use the same kind/brand of controller/bridge and therefore don't use the same kernel extension.
    Does anyone have a clue on this ?
    Many thanks.
      Mac OS X (10.4.8)  

  • Time Machine backup volume will not mount

    Once I goy Time Machine up and running over almost two years ago, I have had little cause for concern. A few lengthy backups here and there but I have been able to restore without any problems whatsoever. It has been extremely useful many times.
    A couple of days ago, I noticed that the backup volume was not mounted (I backup to one of my four internal drives) and launched Time Machine. I got the error:
    The storage location for Time Machine backups can't be found.
    When I run Disk Utility the generic disk icon is in the left hand pane but not the volume. None of the tasks are available except Erase and Partition - there is no option to Verify Disk, Repair Disk, Verify Disk Permissions or Repair Disk Permissions.
    According to my logs, the last backup at 18:12 on 20th November was successful. I didn't notice that the volume had not mounted the until the next day.
    I'm very concerned that I have lost almost two years of data security. Is there any way I can repair the disk or recover the backups?
    Thanks.

    If Disk Utility can't see any partitions, it's not good.
    First, turn TM off.
    Then try ejecting, disconnecting and powering the drive off for a few minutes, then reattaching it. Then try again with Disk Utility. If still no help, the drive is likely dead.
    There's a very small chance that +Disk Warrior+ (version 4.1.1 or 4.2 only), or another heavy-duty disk repair app can fix it, if you already have one. But I wouldn't suggest spending the $$ for one unless you think you'll need it in the future -- DW is about $100.
    Most likely, your disk is dead. There's a small chance that a +Data Recovery+ app such as +Data Rescue+ can recover some of the data. Check via Google, VersionTracker.com, or MacUpdate.com for +Data Recovery.+ There are services and apps, none cheap. Some of the apps have a free demo or test mode that will tell you if there's anything that can be recovered, and perhaps actually recover a single file; then you pay for it and recover whatever else can be recovered. You'll need another external disk to receive the recovered items.
    You won't get the normal Time Machine folder structure, though, just "raw" files. Even if you do recover files, you'll most likely have to figure out what goes where and copy them to the right places manually.
    So I'd suggest immediately getting a new drive and doing a new TM backup to it, so you have something. Put a second partition on it that you can use for the recovered files if and when you do that.
    If those are your only backups, I'd recommend getting a second external, perhaps a portable one, and using CarbonCopyCloner or SuperDuper to make a full "bootable clone" to it, then take it to your safe deposit box, workplace, relative's house, or other secure location. And/or, you might want to look at Mozy, Carbonite, or other online backup services.

  • Volume will NOT mount

    We have much the same issue as others here in other threads have spoken about - after a reboot a raid volume will not mount.
    Disk Utility can 'see' the drive and array, but will not mount it. RAID Admin reports no problems. I tried updating the firmware to no avail.
    Then I tried a new FC card in the server, a different controller card in the xRAID, different cables and connecting the FC cable to a different XServe. No mount with any of these attempts.
    XServe 2 ea 2.3Ghz G5, 2GB RAM, 1 80GB drive (cluster node config)
    OSX Server 10.3.9
    7 ea 180GB drives, RAID5; 1 TB array
    RAID Admin 1.5 (controller firmware - now: 1.5/1.50f)
    Any ideas what to try next? And no we don't have 100% backups, close but no... ;-( so any ideas worth trying appreciated!
    Tks, Mark

    Mark,
    We recently had a similar problem. We have an XServe RAID fully populated -- split into 2 volumes. One volume would mount the other would not (after a reboot). Tried swapping fibre channel cables, re-seating fibre channel cards, etc. Our solution was replacing the PCI-Fibre card in the XServe.
    Another thing we have had happen is, after reboot, one volume mounts and the other mounts about 15 mins later -- after completing fsck.
    Hope this helps.
    --Bonnie

  • "Volume Fails To Mount" Error

    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

  • WD mycloud fehler 004 : Data volume failed to mount

    Hallo, Seit einiger zeit habe ich nurnoch eine rote LED und kein zugriff auf meine WD Mycloud 2TB ins Mycloud daschboard komme ich noch sporadisch. zeigt aber fehler 004 Haupsächlich hatte ich die mycloud als speicher für fotos genutzt, die natürlich nirgendwo anderst gespeichert sindKomme ich irgendwie wieder an meine Fotos ?? DankeMatthias  

    Hast Du mal über das Dashboard "nur System" auf Werkseinstellungen zurück gesetzt? Wenn es dann icht geht, kannst Du den Support kontaktieren. Die werden Dir aber vermutlich nicht dabei helfen Deine Daten wiederzubekommen, sondern bestenfalls ein neues/repariertes Gerät ohne Deine Daten senden. Ansonsten hatte hier jemand das gleiche Problem lösen können:http://community.wd.com/t5/WD-My-Cloud/Data-volume-failed-to-mount/td-p/631497Versuchen kannst Du es: This is "my" solution, may not work for everyone. But it would seem that datablocks would corrupt when power is abruptly cut to the drive. SSH must be enabled for this to work. 1. Log onto the drive, root and welc0me are the default username/password combo.2. Make sure your paritions are intact. # parted -l will tell you this.3. Type # mke2fs -n /dev/sda4. This will get you the filesystem, but more importantly at the end give you the superblock backup locations by block location.4. Pick one, then enter this command. e2fsck -b blocknumber /dev/sda4 It will look for bad blocks and ask for your confirmation to continue/ignore then write over any corrupted ones. Yes to ignore, yes to rewrite. It will do up to five passes of diagnostics, prompting if it finds anything out of the ordinary such as file countes and errant inodes. I answered yes to everything. When it is complete it will either report "Killed" or a summary. Type # reboot and let the drive rebuild its library. 30-ish minutes later (depending on how much data you had on it) you should have access to your files.

Maybe you are looking for

  • AFS - ATP "T" Status Problem

    Hi All, We're having a problem with ATP checks ignoring stock assigned to status T - Temporarily assigned stock/requirements, and double-promising against any quantity that hasn't been yet allocated to R - Reserved or F - Fixed. For example, batch 00

  • Oracle 9i Lite Mobile Server deploye Problem As Apache Module

    I am trying to get the Oracle9i Lite Mobile Server run as a Module under Apache. my platform is Linux 7.2, which of course is documented as an option. I managed to install the mobile server and the following document is the latest from ORACLE site. a

  • Display archived data in Internal Orders

    Hi Gurus I would like to know if there is any report for Internal Orders which can show data for years that have been archived? Or is there any way by which I can see the archived data or line items for Internal Orders. Thank You in advance. Reg SAPa

  • LMS 3.2 vlan configuration

    Hi, I have some port to configure to have a vlan + a voice vlan. How can i do that using LMS 3.2 ? I have check the vlan port assignement but i haven't seen a option to define 2 vlan. typically our port are configure like this one interface FastEther

  • No streaming video on ipad

    My iPad mini is no longer steaming video.  I am not able to view news casts any more? Any ideas, pls help. Thank you.