| View previous topic :: View next topic |
| Author |
Message |
Bgarmen
fully protected
Joined: 13 Feb 2009
Posts: 12
|
 Posted: Thu Oct 08, 2009 10:34 am Post subject: |
 |
|
What if I have a few PPC that are still running 2.1.1, then can't upgrade to 2.2. even if I try they can't.
Do I have to remove them from the xsan before it will work again? |
|
| Back to top |
|
 |
abstractrude
Xsan Master
Joined: 13 Mar 2008
Posts: 881
|
| Posted: Thu Oct 08, 2009 12:44 pm Post subject: |
|
|
| thats the serial number fix... right? |
|
| Back to top |
|
|
abstractrude
Xsan Master
Joined: 13 Mar 2008
Posts: 881
|
| Posted: Thu Oct 08, 2009 12:45 pm Post subject: |
|
|
| the best thing to do would be to keep your PPC clients at 10.5.6 2.1.1 |
|
| Back to top |
|
|
abstractrude
Xsan Master
Joined: 13 Mar 2008
Posts: 881
|
| Posted: Fri Oct 09, 2009 12:20 pm Post subject: |
|
|
im pretty sure this is the serial number bug. but it sounds like the only way to fix it on the client is to move your intel clients to 2.2. if not you need to go down to 10.5.6/7 with 2.1.1
i apple had a compatibility/bug matrix |
|
| Back to top |
|
|
Bgarmen
fully protected
Joined: 13 Feb 2009
Posts: 12
|
| Posted: Sat Oct 17, 2009 3:48 pm Post subject: |
|
|
The issue is not just happening to one client, it is happening to all the client and mdc across the board, intels and PPC are not mounting the volume right.
I have upgrade everything to 10.5.8 and xsan 2.2 and they are doing the same thing. I can get to the volume via /volumes but it will not show up on the desktop.
In Xsan admin everything show it is mounted and happy, I just don't know why the volume will not mount to the desktop.
I try to isolate it. I shut everything down and start up only the mdc and the volume, see if I could get it to mount just the the mdc and nothing, it still will not show up on the desktop.
Very frustrating. I am out of ideas, anyone have any suggestions? |
|
| Back to top |
|
|
CitraMalus
Been around the blocks
Joined: 19 Mar 2008
Posts: 23
|
| Posted: Mon Oct 19, 2009 1:09 am Post subject: |
|
|
Discard if it sounds silly. just trying to help you.. so try these and see if it works.
1. Please unmount the Volume on a client through Xsan Admin and see if the volume shows up in CLI. If it still shows up, then you might have to use 'rm' command to remove that Volume name. Once you removed it, try mounting again from the Xsan Admin, see if it appears on desktop.
2. See if the 'External Disks' is checked in the Finder Preferences, apart from Hard drives.
3. Run repair disk permissions from the disk utility.
Let us know..
Cheers !!! |
|
| Back to top |
|
|
Bgarmen
fully protected
Joined: 13 Feb 2009
Posts: 12
|
| Posted: Mon Oct 19, 2009 8:25 pm Post subject: |
|
|
1. Please unmount the Volume on a client through Xsan Admin and see if the volume shows up in CLI. If it still shows up, then you might have to use 'rm' command to remove that Volume name. Once you removed it, try mounting again from the Xsan Admin, see if it appears on desktop.
I try to remove and add in the volume on two different clients and it work as expected, it was gone and then it was there.
2. See if the 'External Disks' is checked in the Finder Preferences, apart from Hard drives.
did, it was always checked
3. Run repair disk permissions from the disk utility.
did, no difference |
|
| Back to top |
|
|
JonThompson
Xsan Master
Joined: 06 Apr 2007
Posts: 123
|
| Posted: Fri Oct 30, 2009 8:47 am Post subject: |
|
|
I'm getting the same error. Also, every morning for the past week, my SAN is getting so slow that users can't login and email no longer operates. Rebooting takes care of it. I have been on 10.5.8v1.1 since mid September. Issues have only appeared in the last week.
I've run cvfsck and it shows a clean SAN. I cannot move to 2.2 due to a PPC MDC that I cannot afford to replace.
| Code: | Oct 30 08:14:56 mail com.apple.metadata.mds[83]: ERROR: _MDSChannelXsanRequest: dead channel
Oct 30 08:14:56 mail mds[83]: (Error) Message: MDSChannel RPC failure (storeAttributes:forOIDArray:context:)
Oct 30 08:14:56 mail mds[83]: (Error) Store: <MDSDistantStore: 0x35aa50>{channel:0x39abf0 localPath:'/Volumes/GatiSAN'} MDSChannel failed -- initiating recovery
Oct 30 08:15:00 mail com.apple.launchd[1] (0x113b90.cron[25123]): Could not setup Mach task special port 9: (os/kern) no access
Oct 30 08:15:07 mail com.apple.metadata.mds[83]: XSANFS_FSCTL_SpotlightRPC fsctl failed (errno = 45)ERROR: _MDSChannelInitForXsan: _XsanCreateMDSChannel failed: 45
Oct 30 08:15:07 mail com.apple.metadata.mds[83]: ERROR: _MDSChannelXsanRequest: dead channel
Oct 30 08:15:07 mail mds[83]: (Error) Message: MDSChannel RPC failure (storeAttributes:forOIDArray:context:)
Oct 30 08:15:07 mail mds[83]: (Error) Store: <MDSDistantStore: 0x35aa50>{channel:0x370eb0 localPath:'/Volumes/GatiSAN'} MDSChannel failed -- initiating recovery
Oct 30 08:15:18 mail com.apple.metadata.mds[83]: XSANFS_FSCTL_SpotlightRPC fsctl failed (errno = 45)ERROR: _MDSChannelInitForXsan: _XsanCreateMDSChannel failed: 45 |
Update: The error only appears when I try and open the SAN on the client server via ARD (which is a AFP reshare server)
Also, I don't seem to have a problem this morning, although I did nothing yesterday to resolve it. |
|
| Back to top |
|
|
ravi
Xsan Master
Joined: 06 Mar 2008
Posts: 149
|
| Posted: Sat Oct 31, 2009 5:13 am Post subject: |
|
|
| Bgarmen wrote: | Filesystem Size Used Avail Capacity Mounted on
/dev/disk7 23Ti 18Ti 5.1Ti 79% /Volumes/XSAN
..
afp_4r8hUY000dAS0000oM0000VU-1.2e000005 23Ti 18Ti 5.1Ti 79% /Volumes/XSAN-1 |
The first mount above is the direct mount via fibre and the second mount is via AFP, so you need to disable the AFP mount mechanism if it is done automatically on reboot/login. |
|
| Back to top |
|
|
leomark
JBOD
Joined: 07 May 2010
Posts: 3
|
| Posted: Sun Jun 13, 2010 2:52 pm Post subject: Re: volume mount but will not show up on desktop |
|
|
[quote="Bgarmen"]xsan admin say everything is mounted and working, nothing strange going on in the logs that I can find. However if I go to /Volumes on the clients, I can see the xsan volume and everything in it.
Hey Bill, did you ever resolve this issue?
We had the exact same thing happen to us this past Thursday and we're all on the latest versions.
Appreciate any insight you can give.
Thanks, |
|
| Back to top |
|
|
David Green
partially protected
Joined: 19 May 2005
Posts: 9
|
| Posted: Thu Apr 21, 2011 2:16 am Post subject: |
|
|
Hello,
Did you find a solution to this issue? This happened to one of my sites today. OS X 10.6.5 and Xsan 2.2.1.
I'm working with Apple Support on the case and will update the thread when the issue is resolved.
Any advice is appreciated.
Thanks,
David |
|
| Back to top |
|
|
ravi
Xsan Master
Joined: 06 Mar 2008
Posts: 149
|
| Posted: Fri Apr 22, 2011 1:46 am Post subject: |
|
|
| David Green wrote: | Hello,
Did you find a solution to this issue? This happened to one of my sites today. OS X 10.6.5 and Xsan 2.2.1.
I'm working with Apple Support on the case and will update the thread when the issue is resolved.
Any advice is appreciated.
Thanks,
David |
Hello David
What does the df output show? As I pointed out earlier in the thread the original problem seem to be the case of two mounts of the same volume in the same machine: Xsan volume mount and AFP mount of the same Xsan volume. |
|
| Back to top |
|
|
David Green
partially protected
Joined: 19 May 2005
Posts: 9
|
| Posted: Fri Apr 22, 2011 1:07 pm Post subject: |
|
|
Thanks for your response.
df shows the two internal disks and the Xsan volume.
| Code: | Filesystem Size Used Avail Capacity Mounted on
/dev/disk3s2 931Gi 698Gi 233Gi 75% /
devfs 120Ki 120Ki 0Bi 100% /dev
map -hosts 0Bi 0Bi 0Bi 100% /net
map auto_home 0Bi 0Bi 0Bi 100% /home
/dev/disk4s2 2.7Ti 1.4Ti 1.3Ti 51% /Volumes/Internal
/dev/disk13 53Ti 34Ti 19Ti 65% /Volumes/XSAN |
Here's the output of ls -lh in /Volumes
| Code: | f01:Volumes root# ls -lh
total 65552
drwxrwxr-x 21 user staff 782B Apr 12 16:13 Internal
lrwxrwxr-x 1 root admin 1B Apr 21 18:05 Macintosh HD -> /
drwxrwxrwx@ 14 admin staff 2.0K Apr 21 09:19 XSAN
f01:Volumes root# |
The Xsan volume mounts fine through Xsan admin, and I don't see anything standing out in system.log.
The results are the same on the MDC's also.
People could work and access the SAN through their editing applications, but it would be nice to have the SAN visible on the desktop again. |
|
| Back to top |
|
|
lotte
Xsan Master
Joined: 11 Dec 2008
Posts: 190
|
| Posted: Sat Apr 23, 2011 6:02 am Post subject: |
|
|
Have you looked at the Finder preferences?
Lotte |
|
| Back to top |
|
|
ravi
Xsan Master
Joined: 06 Mar 2008
Posts: 149
|
| Posted: Sun Apr 24, 2011 1:55 am Post subject: |
|
|
| On Lotte's point, yes, also are those Finder Preferences centrally managed since the problem is there on all the machines. |
|
| Back to top |
|
|
|
Xsanity Forum
Forum Search
Forum Help
Log in to check messages
Xsanity Articles
