Xsan client stopped mounting raid
Good Morning Community, I have xsan 2.2 and os 10.7.5
two of my clients stopped mounting the raid. they authenticate to the mdc but will not mount. erro on client says check fiber connections. i have switched computer with working connection and problem follows machine. xsan is working with all other machines only two. MDC system log shows
error mounting volume...operation coundn't be completed (SANTractionErrorDomain error 100007.) (100007)
any ideas? All help is greatly appreciated
thank you
Have you checked DNS and can the client receive a kerberose ticket? I know these don't sound relavant to a XSAN but after doing this for 8 years I can assure you it is.
Similar Messages
-
NFS4-with-Kerberos client stopped mounting
This was working fine till several days ago. Then I started getting:
mount.nfs: access denied by server while mounting <server>:<share>
Looking in the journal found this:
kernel: rpc.gssd[11749]: segfault at 1 ip 00007f036db91d75 sp 00007fffbb5b9df0 error 4 in libgssglue.so.1.0.0[7f036db8e000+9000]
systemd[1]: rpc-gssd.service: main process exited, code=dumped, status=11/SEGV
systemd[1]: Unit rpc-gssd.service entered failed state.
systemd-coredump[11764]: Process 11749 (rpc.gssd) dumped core.
Without rpc.gssd operating, no wonder the mount fails.
On suspicion of a recent upgrade breaking something, I downgraded:
- nfs-utils from 1.2.8-3 to 1.2.7-1
- libtirpc from 0.2.3-1 to 0.2.2-4
- rpcbind from 0.2.0-11 to 0.2.0-8
Those were all updated on May-10-2013. After downgrading, NFS mounting works normally again on the client.
EDIT: Reported as bug https://bugs.archlinux.org/task/35327
Last edited by Cassino (2013-05-16 15:48:43)This was working fine till several days ago. Then I started getting:
mount.nfs: access denied by server while mounting <server>:<share>
Looking in the journal found this:
kernel: rpc.gssd[11749]: segfault at 1 ip 00007f036db91d75 sp 00007fffbb5b9df0 error 4 in libgssglue.so.1.0.0[7f036db8e000+9000]
systemd[1]: rpc-gssd.service: main process exited, code=dumped, status=11/SEGV
systemd[1]: Unit rpc-gssd.service entered failed state.
systemd-coredump[11764]: Process 11749 (rpc.gssd) dumped core.
Without rpc.gssd operating, no wonder the mount fails.
On suspicion of a recent upgrade breaking something, I downgraded:
- nfs-utils from 1.2.8-3 to 1.2.7-1
- libtirpc from 0.2.3-1 to 0.2.2-4
- rpcbind from 0.2.0-11 to 0.2.0-8
Those were all updated on May-10-2013. After downgrading, NFS mounting works normally again on the client.
EDIT: Reported as bug https://bugs.archlinux.org/task/35327
Last edited by Cassino (2013-05-16 15:48:43) -
Xsan will not mount on clients
Xsan updated recently to 1.4. Problem started on 1.3 Working fine until reboot of one of the client computers. Now Xsan volume will not mount on any client. Updated to 1.4, ran cvfsck. Still no go. Volume is over 90%. I have read that this may cause issues. How can I get files off if I cannot mount? Thanks!
Try the following:
From finder -->Go --> Go to folder --> /Volumes
Delete the alias for the XSAN volume you want to mount.
For whatever reason the alias sticks even if the volume was unmounted. Below is an explanation from Apple.
Xsan mounts will fail if they have the same name
Xsan will not mount any volume that has the same name as any existing volume or folder located at /Volumes/.
Unlike some mounting mechanisms that automatically resolve name conflicts (for example, the Finder will append characters to each mounted volume name), the Xsan backend agent simply won't mount the volumes.
To avoid this issue, create a unique name for each volume to be mounted. -
XSan clients with 2 scsi controllers
Hi all!
I have an Xsan with 6 Mac clients with an Apple Fibre Channel card each. Some of them have an Atto scsi controller connected to an external disk tower too. These client don't work if the external disk tower is connected. The client boots but when login the finder can't start and freeze.
I'm using the latest update 1.3
Logging in via ssh on the client I get this in /var/log/system.log:
Apr 27 18:21:37 localhost diskarbitrationd[96]: disk0s2 hfs 2B44F0E7-8C49-3AD4-BB8A-F9F2E3643E57 Macintosh HD /
Apr 27 18:21:37 localhost diskarbitrationd[96]: disk14 hfs 03BB7013-9B81-3D1F-9F81-D91095711495 Raid [not mounted]
Apr 27 18:21:37 localhost SystemStarter: Starting SecurityServer
Apr 27 18:21:37 localhost SystemStarter: Avvio Apple Multicast DNS Responder
Apr 27 18:21:37 localhost SystemStarter: Inizializzo network
Apr 27 18:21:37 localhost ConsoleMessage: Checking disks
Apr 27 18:21:37 localhost mDNSResponder[194]: mDNSResponder-58.8.1 (Jan 31 2005 21:11:41) starting
Apr 27 18:21:37 localhost diskarbitrationd[96]: disk10 acfs B3B884A6-BD45-35C9-824D-7C32E50F1202 XRAID1RightSmall [not mounted]
Apr 27 18:21:37 localhost diskarbitrationd[96]: disk11 acfs 83C6884B-3543-3AE3-9B4D-A842AD3DF156 XRAID1RightBig [not mounted]
Apr 27 18:21:37 localhost diskarbitrationd[96]: disk12 acfs 98BF0B54-15E9-30B0-A8E0-D6DD26CD27C7 XRAID1LeftSmall [not mounted]
Apr 27 18:21:37 localhost diskarbitrationd[96]: disk13 acfs 952512A1-A3E0-37D7-8D3A-4142FB882471 XRAID1LeftBig [not mounted]
Apr 27 18:21:50 localhost SystemStarter: Attendo Xsan File System
Apr 27 18:21:51 localhost /System/Library/CoreServices/ARD Agent.app/Contents/MacOS/ARD Agent: ******Launched Agent******
Apr 27 18:21:53 localhost SystemStarter: Attendo Xsan File System
Apr 27 18:21:56 localhost SystemStarter: Attendo Xsan File System
Apr 27 18:21:58 localhost SNFS:
Apr 27 18:21:58 localhost SNFS: File System Server:
Apr 27 18:21:58 localhost SNFS: Server Revision 2.7.200 Build 92.2
Apr 27 18:21:58 localhost SNFS: Built for Darwin 7.0
Apr 27 18:21:58 localhost SNFS: Created on Thu Apr 20 15:47:16 PDT 2006
Apr 27 18:21:58 localhost SNFS:
Apr 27 18:21:58 localhost SNFS:
Apr 27 18:21:58 localhost SNFS: File System Client:
Apr 27 18:21:58 localhost SNFS: Client Revision 2.7.200 Build 92.2
Apr 27 18:21:58 localhost SNFS: Built for Darwin 7.0
Apr 27 18:21:58 localhost SNFS: Created on Thu Apr 20 15:53:03 PDT 2006
Apr 27 18:21:58 localhost SNFS: Built in /SourceCache/XsanFS/XsanFS-270.92.2
Apr 27 18:21:59 localhost sudo: root : TTY=unknown ; PWD=/Library/Filesystems/Xsan/debug ; USER=root ; COMMAND=/sbin/kextload -v -s /Library/Filesystems/Xsan/debug
Apr 27 18:21:59 localhost kernel: Xsan Client Revision 2.7.200 Build 92.2 Built for Darwin 7.0 Created on Thu Apr 20 15:53:03 PDT 2006
Apr 27 18:21:59 localhost sudo: root : TTY=unknown ; PWD=/Library/Filesystems/Xsan/debug ; USER=root ; COMMAND=/sbin/kextload -v -s /Library/Filesystems/Xsan/debug
Apr 27 18:21:59 localhost ConsoleMessage: Current socket buffer size: 262144
Apr 27 18:21:59 localhost SystemStarter: Current socket buffer size: 262144
Apr 27 18:21:59 localhost ConsoleMessage: Setting max socket buffer size: 16777216
Apr 27 18:21:59 localhost SystemStarter: Setting max socket buffer size: 16777216
Apr 27 18:21:59 localhost ConsoleMessage: Starting fsmpm
Apr 27 18:21:59 localhost SystemStarter: Starting fsmpm
Apr 27 18:21:59 localhost SystemStarter: Attendo Xsan File System
Apr 27 18:21:59 localhost /Library/Filesystems/Xsan/bin/fsmpm: PortMapper: No fsroutes file - No preferred routes will be registered.
Apr 27 18:22:00 localhost /Library/Filesystems/Xsan/bin/fsmpm: PortMapper: self (mac03.local) IP address is 192.168.15.22 .
Apr 27 18:22:00 localhost /Library/Filesystems/Xsan/bin/fsmpm: PortMapper: Added FSS route from '127.0.0.1' to '192.168.15.22'
Apr 27 18:22:00 localhost /Library/Filesystems/Xsan/bin/fsmpm: NSS: Primary Name Server is '192.168.15.186' (192.168.15.186)
Apr 27 18:22:00 localhost fsmpm[414]: NSS: Name Server '192.168.15.186' (192.168.15.186) port is 49161.
Apr 27 18:22:00 localhost fsmpm[414]: Portmapper: ComputerInfo: computer_name = "mac03", hostname = "mac03"
Apr 27 18:22:00 localhost fsmpm[414]: PortMapper: Listening on TCP socket mac03.local (0.0.0.0):49212
Apr 27 18:22:00 localhost fsmpm[414]: NSS: Listening on UDP socket mac03.local:49165
Apr 27 18:22:00 localhost diskarbitrationd[96]: disk14 hfs 03BB7013-9B81-3D1F-9F81-D91095711495 Raid [not mounted]
Apr 27 18:22:00 localhost fsmpm[414]: PortMapper: CVFS Volume XRAID1RightSmall on device: /dev/rdisk10 (blk 0xe00001e raw 0xe00001e) con: 2 lun: 0 state: 0xf4 inquiry
Apr 27 18:22:00 localhost fsmpm[414]: PortMapper: CVFS Volume XRAID1LeftSmall on device: /dev/rdisk12 (blk 0xe000020 raw 0xe000020) con: 2 lun: 0 state: 0xf4 inquiry [Apr 27 18:22:00 localhost fsmpm[414]: PortMapper: CVFS Volume XRAID1RightBig on device: /dev/rdisk11 (blk 0xe00001f raw 0xe00001f) con: 2 lun: 1 state: 0xf4 inquiry [AApr 27 18:22:00 localhost fsmpm[414]: PortMapper: CVFS Volume XRAID1LeftBig on device: /dev/rdisk13 (blk 0xe000021 raw 0xe000021) con: 2 lun: 1 state: 0xf4 inquiry [APApr 27 18:22:00 localhost fsmpm[414]: PortMapper: No fsmlist file - No File System Services launched.
Apr 27 18:22:00 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadfss: [374] main: Waited 2 secs for fsmpm to start (now running)
Apr 27 18:22:00 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadfss: [374] main: Will detach its own daemon
Apr 27 18:22:00 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadfss: [420] main: Detached its own daemon
Apr 27 18:22:00 localhost fsmpm[414]: PortMapper: Creating sync file </Library/Filesystems/Xsan/debug/fsmpm-sync.278>
Apr 27 18:22:01 localhost ConsoleMessage: fsmpm started
Apr 27 18:22:01 localhost SystemStarter: fsmpm started
Apr 27 18:22:01 localhost ConsoleMessage: Starting cvfsd
Apr 27 18:22:01 localhost SystemStarter: Starting cvfsd
Apr 27 18:22:01 localhost mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/sbin/diskarbitrationd": exited as a result of signal 6 [pid 96]
Apr 27 18:22:01 localhost fsmpm[414]: Disk rescan found 4 disks
Apr 27 18:22:02 localhost fsmpm[414]: PortMapper: Local FSD client is registered.
Apr 27 18:22:02 localhost diskarbitrationd[431]: disk0s2 hfs 2B44F0E7-8C49-3AD4-BB8A-F9F2E3643E57 Macintosh HD /
Apr 27 18:22:02 localhost diskarbitrationd[431]: disk14 hfs 03BB7013-9B81-3D1F-9F81-D91095711495 Raid [not mounted]
Apr 27 18:22:02 localhost SystemStarter: Attendo Xsan File System
Apr 27 18:22:03 localhost diskarbitrationd[431]: disk13 acfs 952512A1-A3E0-37D7-8D3A-4142FB882471 XRAID1LeftBig [not mounted]
Apr 27 18:22:03 localhost diskarbitrationd[431]: disk10 acfs B3B884A6-BD45-35C9-824D-7C32E50F1202 XRAID1RightSmall [not mounted]
Apr 27 18:22:03 localhost diskarbitrationd[431]: disk12 acfs 98BF0B54-15E9-30B0-A8E0-D6DD26CD27C7 XRAID1LeftSmall [not mounted]
Apr 27 18:22:03 localhost diskarbitrationd[431]: disk11 acfs 83C6884B-3543-3AE3-9B4D-A842AD3DF156 XRAID1RightBig [not mounted]
Apr 27 18:22:03 localhost /Library/PreferencePanes/BlueHarvest.prefPane/Contents/Resources/BlueHarvestMon itor: BH: Started.
Apr 27 18:22:04 localhost ConsoleMessage: cvfsd started
Apr 27 18:22:04 localhost SystemStarter: cvfsd started
Apr 27 18:22:04 localhost ConsoleMessage: Mounting Xsan File System volumes
Apr 27 18:22:04 localhost SystemStarter: Mounting Xsan File System volumes
Apr 27 18:22:04 localhost SystemStarter: Avvio completato.
Apr 27 18:22:06 localhost mach_init[2]: Server 0 in bootstrap d03 uid 0: "/usr/sbin/diskarbitrationd": exited as a result of signal 6 [pid 431]
Apr 27 18:22:07 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadvol: [421] ERROR: mountvolumenamed(XsanVol): Could not remove mount point directory /Volumes/XsApr 27 18:22:12 localhost /Library/PreferencePanes/BlueHarvest.prefPane/Contents/Resources/BlueHarvestMon itor: BH: Main engine start.
Apr 27 18:22:36 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadfss: [420] ERROR: getlabeleddisks: Error -1 iterating over list
Apr 27 18:22:36 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadfss: getlabeleddisks: SNFS Generic Error
Apr 27 18:22:36 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadfss: [420] ERROR: getlocalproperties: Did not save reply because no disk or status=100047/0
Apr 27 18:22:36 localhost /usr/share/servermgrd/cgi-bin/servermgr_nomadfss: [420] ERROR: synchronizeconfiguration_ifclient: 192.168.15.22 sees 0 disks
Any ideas?
Thanks
DiegoYou may have what are called corrupt free inodes. Inodes are the actual containers in the file system that store your data. Here are some similar threads that may help you:
http://www.xsanity.com/forum/viewtopic.php?p=3521
http://www.xsanity.com/forum/viewtopic.php?p=4408
In the first thread, they were able to simply rebuild their Xsan and restore from backup, but in the second, they were able to use cvfsck -C to perform a "clobber" which removes the bad inodes, so new, uncorrupted inodes can be created.
The problem is, if you have an Xsan with this kind of corruption, it will usually re-appear, so your best bet is to do what you have to to get your volume back online long enough to grab your data, then re-create your volume again from scratch. If you did a volume expansion in the past without running cvfsck and making sure your file system was clean first, this kind of corruption will sometimes happen.
Without seeing more, this is all just a guess, but if you find that corrupt inodes are what you're running into, here are some notes from when I've had to fix this myself:
http://www.jasonmyres.com/2010/11/xsan-2-0-troubleshooting/
Good luck.
JM -
I can't join XSAN clients to the XSAN
i have a 10.8 XSAN MDC, volume mounts no issues.
We have two identical MacPro's running 10.8.
Things were "kind of" working a week or two ago, but the MDC was unstable so we rebuilt it. Now the clients won't join the new XSAN.
They don't even show as available to the XSAN in the add computer screen, although if I click add remote, they show up, it just fails on authentication.
If I boot to a new, fresh 10.8 install and join the Open Directory and join the XSAN, it works perfectly.
Obviously I could rebuild these workstations, but they are video production machines, and that's literally days of work...
I've deleted kerberos, deleted xsan prefs, unjoined/rejoined the open directory, nothing is working. There must be some latent setting on the workstation that is preventing me from joining the SAN. WHERE IS IT?
Any help is appreciated. In fact, if you can help me, I'll tell you how to get an iSCSI volume mounted as an XSAN volume ;-) (the genesis of this whole project).
Thanks!"unable to connect to xsand: No such file or directory"
probably because there is no config, because I can't even get it to join the XSAN.
In the past, it's been a DNS or related error. Going to check something there... -
User sip folder have manu Mailitem&username&.cache files until folder is full and Lync client stops working.
Hi,
You can try to change the Lync Profile name. After you do it, Lync will create a new Profile. The Lync Profile path is following:
%UserProfile%\AppData\Local\Microsoft\Office\15.0\Lync
If the issue persists, please repair Office 2013 and then test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support -
Drives stopped mounting with FW800, but FW400 is OK. Worked OK before, but won't now. Tried new cables, zapping pram, Disk Repair Utility. Any suggestions? Thanks.
If your external drive does not have an independent power supply, you may wish to consider a couple of lower-cost options before tossing the drive. Bus-powered drives have no external power source and must get all their power from the computer. They can exceed the computer's USB energy budget.
Cheapest option:
1 Meter USB 2.0 A to 5 Pin Mini B Cable - Auxiliary USB "Y" Power Design for external hard drives.
This gets power from two of the computers USB porst sna can provide enough power to wake up an under-performaing bus-powered drive.
If you don't have enough ports to use this, try the next cheapest option:
Newer Technology 7 Port Hi-Speed USB 2.0 Hub with Power Adapter for Mac & PC
Such a hub has a an independent power supply to make up for wahat the comptuer fails to provide. -
Does anyone know why my three USB drives have stopped mounting? Disk Utility can't see them either? One is a portable one that draws power from the bus, that is still drawing the power. Is it a permissions problem?
Mine is model HD-HB250U2, which has also been discontinued. I've fixed permissions twice, plus reset PRAM and NVRAM. Still can't mount the drive. It's ironic that this is the drive I'm using for Time Machine.
My next step was to install the 10.5.7 Combo update. I think I can do this, even though I'm at actually at 10.5.7, based on this article.
http://www.macfixit.com/article.php?story=20070824012114701
Can any advise if running the 10.5.7 Combo update is safe to do? -
Nfs client ls /data/rw10 nfs client on mount: Permission denied
We are running an 800 cpu amd solaris 10 x64 cluster for HPC and an 512 cpu ultrasparc cluster solaris 10 for high
throughput.
Until now the nfs servers played ball and I did not experience real difficulties.
I am running two Solaris 10 x64 servers serving a total of 80 TB over nfs4, one Thumper serving 17 TByte over nfs4
and 7 linux serving 30 TByte over nfs3.
Today for the first time I got a massive rejection of mounts with the following error on the client.
May 9 18:24:10 m2001 nfs: [ID 664466 kern.notice] NFS compound failed for server c-store2: error 12 (RPC: Remote system error)
May 9 18:24:10 m2001 last message repeated 1 time
May 9 18:24:10 m2001 automountd[428]: [ID 834250 daemon.error] Mount of c-store2:/data2 on /data/rw10: I/O error
The load is not heavy by my standards as there are only 50 concurrent clients trying to mount that file space and the
same clients are mounting the thumper and do not get this problem.
I have had considerably heavier loads on the linux based nfs3 servers when 300 concurrent jobs were accessing one
file space at a time and I did not get this problem.
Have any of you seen this and found a remedy. any hints would be welcomeThe problem solved itself mysteriously overnight, without any interference from myself.
The systems are again perfectly happily mounting the file space (650 clients of them all at the same time
mounting up to 6 filesystems from the same server) and the server is happily serving again as it has been for the past 2 years.
My idea is that there has been a network configuration clash, but considering that the last modification of NIS hosts file was about 4 weeks ago and the latest server was installed then and has been serving since then, I have no
idea how such clash could happen without interference in the config files. It is a mystery and I will have to make
every effort to unravel it. One does not really like to sweep incidents like that un-investigated under the carpet.
If anybody has any suggestions and thoughts on this matter please post them here.
Lydia -
Some Video DVDs have stopped mounting on my OPTIARC Superdrive
I have a Mac Pro 8 core with 10.6.4, and suddenly some (but not all) Video DVDs have stopped mounting with the OPTIARC DVD RW AD-7170A superdrive. After inserting the Video DVD disc, the drives just sort of makes a clicking noise, and then after a few minutes ejects the disc. Other Video DVDs mount just fine.
Audio CDs, DVDs that have been burned, and other Video DVDs mount and play just fine. The same Video DVDs that now refuse to mount on this Superdrive, mount and play just fine on my other Super Drive equipped Mac's. I am pretty sure the DVDs are not faulty and that all are the correct region.
Any ideas are appreciated.Hi Gary,
I am seeing a very similar problem with the drive sporadically reading/not reading any dvd, and only sporadically successfully burning a dvd.
From what I have read so far, it seems that the drive is just faulty. There may be a firmware upgrade available here: http://liggydee.cdfreaks.com/page/en/Optiarc-AD-7170A/
That said, I'm not sure how to flash the drive yet, and there is a risk in doing so.
My details:
OPTIARC DVD RW AD-7170A:
Firmware Revision: 1.NC
Interconnect: ATAPI
Burn Support: Yes (Apple Shipping Drive)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
Write Strategies: CD-TAO, CD-SAO, CD-Raw, DVD-DAO
Will post again if I get a result in my investigation... -
External FW 400 G-Drive stopped mounting
Suddenly, one of my external G-Drives stopped mounting. Shows up in Disk utility as unmounted. Shows up in system profiler, but won't show up in Tech Tools Pro4. Has it died?
BoeIf the drive is connected via USB and is "bus-powered" (does not have its own power brick), the USB port on the computer may not be providing enough power. That can cause the drive to be inaccessible even though its electronics show up in DU.
If you don't wish to replace the drive with one that brings its own power brick to the party, you can usually overcome this by getting an inexpensive powered hub, again, one with its own power supply.
On the surface, the above recommendation seems ludicrous in that a bus-powered device that once worked stopped working later. However, some electronic devices can demand more power as they age. -
Quad stopped mounting firewire devices.
After recognizing my new FW800 hard drive, MOTU 828 and iSight camera, yesterday when I booted up my new Quad G5 stopped mounting these devices and a System Profile showed no firewire ports even present. A simple "disconnect all peripherals and zap the PRAM" fixed it.
Today the same thing happened again so I did the rest again, but nothing happened. I then reset the NVRAM as well -- still nothing.
My relationship with Apple has been love-hate for the last 12 years; right now, after dropping major $$ on a new Quad G5 (against my better judgment because we allllll know that the first round of new computers that Apple puts out is always chock-full of lemons) I am in "hate" mode. 6 Apple computers in 12 years, and all 6 (I'm not kidding) were broken right out of the box.
Can anyone recommend something that I might be missing?Hey ds,
Thanks for the tips. I actually tried those, along with all of the troubleshooting tips that the phone tech support folks gave me. The only thing that has worked is unplugging the power cord from the CPU, then plugging it back in, and zapping the pRAM on startup -- then the firewire devices will mount.
Because tech support couldn't figure out why that's happening, they've declared it a hardware problem and said that I got a lemon... and I'm off to the Apple Store first thing in the morning to drop off my Quad.
6 lemons out of 6 purchased over 12 years.... ouch. -
Client Stop reporting in WSUS after Approval patches
Hi Team,
Recently i faced lot of issue in my wsus server during patching activity, After approving patches certain client stop reporting in wsus . I have tried all the troubleshooting but no one help.
can any one help me and provide troubleshooting steps which required in this type of cases
Regards, TriyambakI am facing same issue in one of server , here is the log file
2014-06-24 02:56:11:066
852 c18
PT WARNING: SOAP Fault: 0x00012c
2014-06-24 02:56:11:066
852 c18
PT WARNING: faultstring:Fault occurred
2014-06-24 02:56:11:066
852 c18
PT WARNING: ErrorCode:ServerChanged(4)
2014-06-24 02:56:11:066
852 c18
PT WARNING: Message:Server rolled back since last call to GetCookie
2014-06-24 02:56:11:066
852 c18
PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2014-06-24 02:56:11:066
852 c18
PT WARNING: ID:2f956ab6-fac3-4e68-bffa-48557d580e88
2014-06-24 02:56:11:066
852 c18
PT WARNING: PTError: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: GetCookie_WithRecovery failed : 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: RefreshCookie failed: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: RefreshPTState failed: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: Sync of Updates: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: Cached cookie has expired or new PID is available
2014-06-24 02:56:11:066
852 c18
PT Initializing simple targeting cookie, clientId = 60adbf7d-5194-4cd9-90c7-e00efccedcb7, target group = WSUS 2003 x32 Prod Group 1, DNS name = lpsjcmwbp13.sumcweb.com
2014-06-24 02:56:11:066
852 c18
PT Server URL = http://lpchweb-wsus.sumcweb.com/SimpleAuthWebService/SimpleAuth.asmx
2014-06-24 02:56:30:488
852 c18
Agent * WARNING: Failed to synchronize, error = 0x80244015
2014-06-24 02:56:30:504
852 c18
Report CWERReporter finishing event handling. (00000000)
2014-06-24 02:56:30:504
852 c18
DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
2014-06-24 02:56:30:504
852 c18
Agent Server changed and need resyncing with server
2014-06-24 02:56:30:895
852 c18
PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-06-24 02:56:30:895
852 c18
PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
2014-06-24 02:56:35:692
852 c18
PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-06-24 02:56:35:692
852 c18
PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
an AU detection already in progress
2014-06-24 01:35:37:030
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:030
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:077
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:077
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:296
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:296
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:562
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:562
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:655
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:655
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:968
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:968
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:015
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:015
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:343
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:343
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:515
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:515
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:655
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:655
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:937
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:937
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:999
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:999
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:421
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:421
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:421
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:421
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:640
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:640
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:968
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:968
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:312
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:312
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:374
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:374
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:609
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:609
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:859
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:859
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:030
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:030
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:202
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:202
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:374
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:374
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:515
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:515
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:796
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:796
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:952
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:952
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:077
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:077
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:374
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:374
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:499
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:499
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:671
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:671
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:952
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:952
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:062
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:062
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:327
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:327
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:499
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:499
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:624
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:624
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:984
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:984
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:218
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:218
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:343
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:343
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:687
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:687
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:984
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:984
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:281
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:281
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:343
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:343
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:749
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:749
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:749
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:749
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:984
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:984
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:281
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:281
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:452
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:452
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:593
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:593
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:765
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:765
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:968
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:968
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:124
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:124
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:343
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:343
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:515
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:515
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:734
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:734
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:015
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:015
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:109
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:109
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:327
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:327
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:499
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:499
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:702
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:702
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:906
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:906
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:49:234
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:49:234
832 1378
AU Piggybacking on an AU detection already
Regards, Triyambak -
2 of my 8 Xsan clients are not mounting. Get fsmpm is not running.
OK, I need some help. Being new to Xsan and Xserve I am now at a loss. Today 2 of my 8 workstations just stopped connecting and mounting to the volumes.
On each of the workstations I get fsmpm is not running. When I look at the logs this is wht the client machines report.
Feb 29 12:20:18 om xsand[46]: kern.coredump: 1 -> 1
Feb 29 12:20:18 om xsand[46]: kern.corefile: '/cores/core.%P' -> '/cores/core.%N.%P'
Feb 29 12:20:18 om xsand[46]: kern.ipc.maxsockbuf: Result too large
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[116]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[117]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[122]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[120]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[118]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[115]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[121]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om com.apple.qmaster.qmasterd[76]: compressord[119]: installing XSanTest signal handler for SIGUSR1 (_xsanTestFlag = 0)
Feb 29 12:20:30 om sandboxd[140]: portmap(86) deny network-outbound /private/var/tmp/launchd/sock
Feb 29 12:20:32 om com.apple.launchd[1] (com.apple.SystemStarter): Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
Feb 29 12:20:33 om servermgrd[52]: xsan: [52/2112D0] ERROR: open_fs_connection: fsmpm is not running, cannot get connection
Feb 29 12:20:33 om servermgrd[52]: xsan: [52/2112D0] ERROR: open_proxy_fs_connection: SNFS Name Service connection to 127.0.0.1 failed: The Xsan File System Services on 127.0.0.1 may be stopped.
Feb 29 12:20:33 om servermgrd[52]: xsan: [52/2112D0] ERROR: process_notifications: Cannot connect to FS
Feb 29 12:20:34 om xsand[46]: Synchronizing with fsmpm.
Feb 29 12:20:34 om configd[14]: network configuration changed.
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID4-Zim1 on device: /dev/rdisk6 (blk 0xe000010 raw 0xe000010) con: 1 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '6000393000021E5D01000000D52B0C53' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID3-Right on device: /dev/rdisk8 (blk 0xe000012 raw 0xe000012) con: 1 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '60003930000207D801000000D52CCF2A' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID5-Zim4 on device: /dev/rdisk10 (blk 0xe000014 raw 0xe000014) con: 1 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '600039300001E30401000000D52AE4D4' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID1-Right on device: /dev/rdisk12 (blk 0xe000016 raw 0xe000016) con: 1 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '600039300001CEF301000000E5CF72FE' Size: 4688443359 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID1-Left1 on device: /dev/rdisk14 (blk 0xe000018 raw 0xe000018) con: 1 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '6000393000010D6E01000000DA4EABCE' Size: 781383647 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID1-Left2 on device: /dev/rdisk15 (blk 0xe000019 raw 0xe000019) con: 1 lun: 1 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '6000393000010D6E0200000094A2C9EA' Size: 781383647 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID2-Right on device: /dev/rdisk13 (blk 0xe000017 raw 0xe000017) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '600039300001CC4E01000000DC40FE22' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID2-Left on device: /dev/rdisk11 (blk 0xe000015 raw 0xe000015) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '600039300001D0EE01000000D591CFC8' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID3-Left on device: /dev/rdisk7 (blk 0xe000011 raw 0xe000011) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '600039300002083501000000D52CB1C0' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID4-Zim2 on device: /dev/rdisk5 (blk 0xe00000f raw 0xe00000f) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '6000393000021EB801000000D52AF882' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: PortMapper: CVFS Volume RAID5-Zim3 on device: /dev/rdisk9 (blk 0xe000013 raw 0xe000013) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.51] controller # 'default' serial # '600039300001E3E701000000D636DB1E' Size: 8790767583 Sector Size: 512
Feb 29 12:20:34 om fsmpm[147]: Disk arb runloop starting
Feb 29 12:20:35 om _mdnsresponder[163]: /usr/libexec/ntpd-wrapper: scutil key State:/Network/Global/DNS not present after 30 seconds
Feb 29 12:20:35 om loginwindow[58]: Login Window Started Security Agent
Feb 29 12:20:35 om loginwindow[58]: Login Window - Returned from Security Agent
Feb 29 12:20:35 om loginwindow[58]: USER_PROCESS: 58 console
Feb 29 12:20:35 om _mdnsresponder[169]: sntp options: a=2 v=1 e=0.100 E=5.000 P=2147483647.000
Feb 29 12:20:35 om _mdnsresponder[169]: d=15 c=5 x=0 op=1 l=/var/run/sntp.pid f= time.apple.com
Feb 29 12:20:35 om _mdnsresponder[169]: sntp: getaddrinfo(hostname, ntp) failed with nodename nor servname provided, or not known
Feb 29 12:21:05 Om fsmpm[147]: NSS: Name Server '10.0.1.220' (10.0.1.220) heartbeat lost, unable to send message.
Mar 1 10:40:25 Om servermgrd[52]: xsan: [52/3701E10] ERROR: -[SANFilesystem(PrivateMethods) doXsandManagementRpcWithCommand:]: Unable to connect to xsand: No such file or directory
Mar 1 10:40:25 Om servermgrd[52]: xsan: [52/3701E10] ERROR: -[SANFilesystem mountVolumeNamed:writable:withOptions:]: unable to send 'mount' message to xsand
Mar 1 10:40:55 Om /usr/sbin/serialnumberd[246]: New xsan serial number permanently registered by pid 52.
Mar 1 10:56:53 Om fsmpm[312]: NSS: Name Server '10.0.1.220' (10.0.1.220) heartbeat lost, unable to send message.
Mar 1 10:58:23 Om xsand[309]: Failed to synchronize with fsmpm (error 2).
I have checked my metadata network switch and all green lights. I have 6 other clients that are running just fine. I fear rebooting them in case that would cause them to fail as well.
Any ideas??!?!?!? HELP!!!
Thanks ,
KevinThe fsnameserver config file was missing the ip for the backup MDC. I added it and all is working once again.
-
Oddball client not mounting XSan Volumes
Background: My client, a TV News broadcast station, had Apple and a third-party design and install a Apple based XSan storage and network. They ran all new fiber and gigabit ethernet to each station to use the XSan. It has been working great, with the exception noted below.
Setup: 2 MD Controllers, 1 XServe, 4 XRaids, each make up two 2 large TB volumes (raid 5, stripped together).
XServe, XRAID, MD controllers, and all clients are all connected together on a Fibre and Fiber Optic network using QLogic switches. SUBNET: 10.200.1.x.
Ethernet Network, also connected all the above together on HP Gigabit Switches. SUBNET: 10.100.1.x The public WAN is made available on this subnet by a connection to the HP switches. Still getting details on how this was done.
Everything is running OS X 10.4.8 or better, XSan File System 1.4.
Setup
There are 8 workstations (edit bays) that act as infusion and editing stations. Each station has two XSans volumes mounted NEWS01 and NEWS02. They have the odd numbered bays use NEWS01 and the even numbered bays use NEW02.
PROBLEM
All bays mount the XSan volumes, except one. FCP08 will not mount the XSan volumes. We have rebooted the workstation, and even went to the extreme of shutting down the entire setup all bays and MD controllers, File Servers, etc.. then bringing everything backup up. Same problem.
Based on some forum discussion, we have tried the following:
* Ensured that there is no empty mount point in /Volumes
* Uninstalled all XSan Software and resinstalled v1.4 from Apple's website.
* Removed the client from the XSan Admin, and readded it, made sure to enter valid serial number, etc..
* Verified that all fibers are working, all link lights look good, and you can ping across the MD network.
When you use the XSan admin from either FCP08 (edit bay 08) or from the server, and you add both MD XSans to it, you see the client, and you click on the client and click either Mount (read-only) or Mount (Read/write).
It will show "Mounting..." and then it will flip back to "not mounted". The only feedback we have received so far is "ACCESS DENIED". All affinity setting are set to rwxrwxrwx (wide open), and all the volumes and workstation logins all have the same access to the volumes. I can not find any restrictive permissions anywhere.
I plan on trying to move them away from a /etc/hosts type setup to a proper DNS Server running on their XServe using the DNS Server function of OS X Server. But currently all edit bay stations have the same /etc/hosts file installed, which accounts for MD and ethernet networks.
ANY IDEAS what is wrong with this workstation? With the setup?
I have had extreme ideas from some who have said that we need to blitz the entire client, and reinstall the operating system. I am not willing to go down that route, since each edit bay was built manually without an image (another aspect I will remedying soon). It will take sometime to rebuild this edit bay client if I that is the only solution.
The only this question I have if that is the popular opinion, is what is different from a client OS install and the existing one regarding the XSan? This are edit bays, not private workstations, and no one installs any extra software or surfs the net, etc.. They are used for ingest and editing only.
HELP!
Mac OS X (10.4.10)Hi,
You could check if it is Fibre Channel related:
from a terminal do a cvlabel -l
this should give you a list of the lun's in your volume.
When this tool does not show luns, you might have a zoning issue.
Regards
Donald
Maybe you are looking for
-
No storage space available for extending an internal table.
Hi All, I am using Function Module : VC_I_GET_CONFIGURATION in FI related Sales Order Report to get configuration data for fields Model/Engine and Line no. when the program executed in Production environment, It is giving Runtime Error TSV_TNEW_PAGE
-
I am Making the Switch: Vaio to Macbook... What do I need to Know?
So I am moving over to a mac My vaio has been a great machine, but i dropped it last week, so the data is being pulled right now and I have been looking for a replacement. I decided on the 15" Macbook Pro... 250GB 4 GB RAM 2.6GHZ INTEL duo so i need
-
Can I add a sound to a transition in a Keynote slide show?
I understand how to add sound to a slide, but I want the sound to play during the transition. Can I do that?
-
Apple's 500GB Wireless Time Capsule external drive.....PC?
If I buy the Wireless Time Capsule drive from Apple, will it back up my husband's PC just as it will my Mac? I read both, when looking at the information about it at the apple site.
-
DIAdem 9.1 access violations
Hello, We are getting about 4 to 5 times a day on this "ACCESS VIOLATION" errors while developing a Crash Analysis software. Here are the error logs that we have collected, hope you guys could toss us few possible solutions to this. Note that error #