XSAN No Controller

Hi,
My xsan shows no controller.
Even I am unable to connect to Xsan.
Even I the permission to Remove a computer is Grey
But when I open from terminal using cvadmin
it shows the controller.
Can I add the previous controller again as its not showing in XSAN.
The OS is 10.5
and Xsan is 2.0
Please suggest what I should do.

Ended up hard rebooting it.
Ran cvfsck after it rebooted and it came out clean.

Similar Messages

Using XSan for Home Directories

I'm having trouble setting my XSan drive as a destination for home directories.
When I log in it says the directory is unavailable, and it hasn't created it. If I allow everyone read/write access to the share it creates a home containing only a desktop and library folder with none of the files from the user template.
What am I doing wrong? I'm using Active Directory for authentication, both the XSan Primary Controller and secondary controller are bound, and the secondary is an Open Directory Master and resharing the Xsan drive for user directories. If I use a server local drive all works fine.
Many thanks for any suggestions

Video editing indeed. (we are a broadcasting company)

Failing over from MDC02 back to MDC01 on XSan

cross-posted from Xsan discussion...
Looking for some advice on an XSan MetaData controller problem. Last week, we had a failover from our primary MetaData controler (metasvr01) to our backup MetaData Controller (metasvr02). So far, so good.
After some investigation, it looked like metasvr01 had locked up - so we rebooted it. It appears to have come back alive somewhat normally, except the cvadmin command is not seeing both MetaData servers (like it used to).
Should it be "safe" to try a metadata server failover to metasvr01?
Are there any potential problems / "gotcha's" we should be aware of?
Here's the output from metasvr01:
========================================================
metasvr01:~ metasvr01$ sudo cvadmin
Password:
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1> EditB[0]         located on metasvr01.private:49248 (pid 140)
2> EditA[0]         located on metasvr01.private:49247 (pid 139)
No FSSs are active.
Select FSM "none"
Here's the output from metasvr02:
========================================================
metasvr02:~ metasvr02$ sudo cvadmin
Password:
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1>*EditB[0]         located on metasvr02.private:49200 (pid 128)
2>*EditA[0]         located on metasvr02.private:49201 (pid 127)
Select FSM "none"
NOTE:
==========================================================
Prior to this incident, we would see both metadata servers (on both metasvr01 and metasvr02) - with the "active" one having the asterisk indicating correctly.
Original XSan / XRaid systems.
Still running XSan version 1.4.x
Here are the details regarding metasvr01:
OS/X Server 10.5.5
Normally serving as the primary / active metadata controller.
Here are the details regarding metasvr02:
OS/X Server 10.5.5
Normally serving as the secondary / backup metadata controller,
                         secondary / backup Open Directory Server,
                         secondary / backup DNS server
Here are the details regarding xsangw01:
OS/X Server 10.5.5
Normally serving as the primary / master Open Directory server,
                         primary / master DNS server,
                         smb / afp shares throughout the LAN.
================================================================================ ===
One final set of notes regarding these servers. Over the last couple of months, the servers have been increasingly "problematic". So far, we've lost the following capabilities on them:
- no more ARD access (generally)
- no more local KB, Mouse, & Monitor access (generally)
- no more XSan GUI / Server tools GUI access
================================================================================ ==

It is common that when only one of the Xsan servers are restarted that their configuration would get out of sync.
It looks like your metasvr01 thinks it is still hosting the volumes that were failed over.
What you can try to do is from metasvr02 demote metasvr01 to a client and then promote it back to controller. That will force a configuration rewrite and bring metasvr01 back in sync. If cvadmin shows you a correct configuration, then you could safely fail over back to metasvr01 assuming you are confident that whatever issue led to the failover is solved.
A full restart of the XSAN would probably work too (shutdown order - clients, controllers, raids, switches and power on on reverse order)
I would also recomend regular maintenance tasks, like checking disk and permissions on the servers and stopping the volume(s) and running cvfsck.

XSan data without the xSan...?

So you have a raid array setup with your xSan. If you removed the Metadata controller server from the equation and just had your array, would you still be able to access the data? And could you access it from any machine? Or do you HAVE to have an xSan client to see it.

From [What is Xsan?|http://www.apple.com/xsan/whatisxsan.html] ...
Xsan metadata controller
Xsan includes software called the “metadata controller,” which acts as the traffic cop for the SAN.
When an Xsan client attempts to read or write to a file, it gets permission from the metadata
controller, then accesses the data directly on the SAN over high-speed Fibre Channel. Any Xserve
or Mac Pro running Mac OS X Server can be an Xsan metadata controller.
Any clustering scheme (distributed shared write) requires distributed coordination, or Bad Things Happen.

Once again... Installing xsan 1.4.2 on 10.5. HOW?!

So long story short, has ANYONE gotten 1.4.2 to install on a clean 10.5 install?
I have tried hacking the pkg, hacking the SystemVersion.plist, installing all the files by sudo in terminal. NOTHING WORKS!
Installing tiger first is not an option since we are on Intel xserves now.
I will consider ANY solutions.
I have seen this page:
http://support.apple.com/kb/TA24380
On there is says:
Standalone Installer
A standalone installer is available from Apple Downloads.
But it seems no one has been able to find this.
Help guys.

I recently clean installed our Intel MDC with 10.5.8 and xsan 1.4.2. This is how I did it.
Clean install Leopard server and update to 10.5.8 v1.1
When setting up the install, do not select xsan metadata controller as it will ask you for the disk, just create a standalone server.
When your server is finished install xsan 1.4 from your disk, then update to 1.4.2. I have never seen a standalone installer for xsan 1.4.2. I always install 1.4 and then update.
The other option is to install xsan 2.1.1 which I have found much more stable than 1.4.2
Hope this helps

Can't Enable Device Management

I am getting the dreaded 'An error with code -1 occurred' when trying to enable device management on 2 different XSAN deployments. This is an secondary XSAN metadata controller. The primary metadata controller starts up Device Management fine. This is in the logs of the faulty system:
1:: [17200] [2015/04/26 12:23:02.166] EXCEPTION: Error <-[SCEPHelper odRootCertificate] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Base/Support/SCEPHelper.m:61): "'((SCEPHELPER_GetODRootCertificate(self.connection, &root, &rootCnt)))' error 1">
    USERINFO: {
        NSLocalizedDescription = "Operation not permitted";
Any thoughts? Thanks!
Michael

Sure. Thanks for the reply and apologies on the slow response. Again, from what I can tell,
The environment is an XSAN deployment, so servers are on Yosemite 10.10.3, running Server 4.1. DNS, OD and XSAN are running well on both. Other services on this machine include Calendar, Messages and File Sharing, but all other services were set up after the failure of Profile Manager.
Basically I cannot enable device management for Profile Manager. Didn't work initially, so I tried the steps here: OS X Server: How to reset Profile Manager to its original state - Apple Support. Didn't work again. The log output makes me think it has a problem with the server's certificates, but server2 only has a SSL cert signed by server1.
I must be missing something, so any thoughts greatly appreciated.
devicemgrd.log output:
[67233] [2015/04/30 14:49:55.925] -[SULogFileCollection setGlobalLogLevelPrefix:]: YES
0:: [67233] [2015/04/30 14:49:55.928]
    devicemgrd-886.204 (PID:67233, OS:14D136, SERVER:14S1092, ARCH:x86_64) starting
    LA: devicemgrd
    Log verbosity level = 1
    UID = 220, EUID = 220
1:: [67233] [2015/04/30 14:49:55.936] Incoming request: readSettings
0:: [67233] [2015/04/30 14:49:56.059] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [67233] [2015/04/30 14:49:59.048] Profile Manager service STOPPED
1:: [67233] [2015/04/30 14:49:59.068] Wrote MDM URL bag to /Library/Server/ProfileManager/Config/ServiceData/Data/FileStore/MDMServiceConf ig.json
1:: [67233] [2015/04/30 14:49:59.068] Wrote DEP Anchor Certs to /Library/Server/ProfileManager/Config/ServiceData/Data/FileStore/DEPAnchorCerts .json
1:: [67233] [2015/04/30 14:49:59.078] Ready to receive external socket requests.
1:: [67233] [2015/04/30 14:49:59.170] Incoming request: readAppDistributionSettings
1:: [67233] [2015/04/30 14:49:59.173] Incoming request: readSimplifiedDeviceEnrollmentSettings
[67337] [2015/04/30 14:50:35.699] -[SULogFileCollection setGlobalLogLevelPrefix:]: YES
0:: [67337] [2015/04/30 14:50:35.712]
    devicemgrd-886.204 (PID:67337, OS:14D136, SERVER:14S1092, ARCH:x86_64) starting
    LA: devicemgrd
    Log verbosity level = 1
    UID = 220, EUID = 220
0:: [67337] [2015/04/30 14:50:35.735] +[PGConnection reloadPreferences]: DBDebug = NO, DBLogNotices = NO, DBLogSQL = NO, DBMonitor = NO
0:: [67337] [2015/04/30 14:50:37.930] Profile Manager service STOPPED
1:: [67337] [2015/04/30 14:50:37.938] User 'nobody' not found, creating...
0:: [67337] [2015/04/30 14:50:38.431] Loaded strings from '/Applications/Server.app/Contents/ServerRoot/usr/share/servermgrd/bundles/serv ermgr_devicemgr.bundle/Contents/Resources/en.lproj/default.strings'.
1:: [67337] [2015/04/30 14:50:38.440] Incoming request: readSettings
0:: [67337] [2015/04/30 14:50:38.655] -[NSString(devicemgr_Additions) dateFromOpenSSLString]: 'Apr 26 20:57:28 2017 GMT'
1:: [67337] [2015/04/30 14:50:38.675] Wrote trust profile to /Library/Server/ProfileManager/Config/ServiceData/Data/FileStore/Trust_Profile_ for_mdc02.mobileconfig
1:: [67337] [2015/04/30 14:50:38.686] Wrote MDM URL bag to /Library/Server/ProfileManager/Config/ServiceData/Data/FileStore/MDMServiceConf ig.json
1:: [67337] [2015/04/30 14:50:38.688] Wrote DEP Anchor Certs to /Library/Server/ProfileManager/Config/ServiceData/Data/FileStore/DEPAnchorCerts .json
0:: [67337] [2015/04/30 14:50:38.718] Parsing enterprise app icons
1:: [67337] [2015/04/30 14:50:38.718] Parsing enterprise apps with missing icons...
1:: [67337] [2015/04/30 14:50:38.720] Ready to receive external socket requests.
0:: [67337] [2015/04/30 14:50:39.519] Created default profile 'Settings for Everyone'
1:: [67337] [2015/04/30 14:50:39.523] Incoming request: readAppDistributionSettings
1:: [67337] [2015/04/30 14:50:39.526] Incoming request: readSimplifiedDeviceEnrollmentSettings
1:: [67337] [2015/04/30 14:50:45.889] Incoming request: writeSettings
1:: [67337] [2015/04/30 14:50:45.911] EXCEPTION: Error <-[SCEPHelper getIdentityDataForPersistentRef:encryptedWithPassword:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Base/Support/SCEPHelper.m:217): "'((SCEPHELPER_GetIdentityFromRef(self.connection, mCertRef, mCertRefCnt, mPassword, mPasswordCnt, &mPKCS12Data, &mPKCS12DataCnt)))' error 1">
    USERINFO: {
        NSLocalizedDescription = "Operation not permitted";
1:: [67337] [2015/04/30 14:50:54.400] Completed parsing enterprise apps with missing icons!
1:: [67337] [2015/04/30 14:51:21.438] Incoming request: activateOD
1:: [67337] [2015/04/30 14:51:21.438] EXCEPTION: Error <-[SCEPHelper odRootCertificate] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-886.204/Compiled/Fr amework-Base/Support/SCEPHelper.m:61): "'((SCEPHELPER_GetODRootCertificate(self.connection, &root, &rootCnt)))' error 1">
    USERINFO: {
        NSLocalizedDescription = "Operation not permitted";

Failing over from MDC02 back to MDC01

Looking for some advice on an XSan MetaData controller problem. Last week, we had a failover from our primary MetaData controler (metasvr01) to our backup MetaData Controller (metasvr02). So far, so good.
After some investigation, it looked like metasvr01 had locked up - so we rebooted it. It appears to have come back alive somewhat normally, except the cvadmin command is not seeing both MetaData servers (like it used to).
Should it be "safe" to try a metadata server failover to metasvr01?
Are there any potential problems / "gotcha's" we should be aware of?
Here's the output from metasvr01:
========================================================
metasvr01:~ metasvr01$ sudo cvadmin
Password:
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1> EditB[0]         located on metasvr01.private:49248 (pid 140)
2> EditA[0]         located on metasvr01.private:49247 (pid 139)
No FSSs are active.
Select FSM "none"
Here's the output from metasvr02:
========================================================
metasvr02:~ metasvr02$ sudo cvadmin
Password:
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1>*EditB[0]         located on metasvr02.private:49200 (pid 128)
2>*EditA[0]         located on metasvr02.private:49201 (pid 127)
Select FSM "none"
NOTE:
==========================================================
Prior to this incident, we would see both metadata servers (on both metasvr01 and metasvr02) - with the "active" one having the asterisk indicating correctly.
Original XSan / XRaid systems.
Still running XSan version 1.4.x
Here are the details regarding metasvr01:
OS/X Server 10.5.5
Normally serving as the primary / active metadata controller.
Here are the details regarding metasvr02:
OS/X Server 10.5.5
Normally serving as the secondary / backup metadata controller,
                         secondary / backup Open Directory Server,
                         secondary / backup DNS server
Here are the details regarding xsangw01:
OS/X Server 10.5.5
Normally serving as the primary / master Open Directory server,
                         primary / master DNS server,
                         smb / afp shares throughout the LAN.
================================================================================ ===
One final set of notes regarding these servers. Over the last couple of months, the servers have been increasingly "problematic". So far, we've lost the following capabilities on them:
- no more ARD access (generally)
- no more local KB, Mouse, & Monitor access (generally)
- no more XSan GUI / Server tools GUI access
================================================================================ ==

It is common that when only one of the Xsan servers are restarted that their configuration would get out of sync.
It looks like your metasvr01 thinks it is still hosting the volumes that were failed over.
What you can try to do is from metasvr02 demote metasvr01 to a client and then promote it back to controller. That will force a configuration rewrite and bring metasvr01 back in sync. If cvadmin shows you a correct configuration, then you could safely fail over back to metasvr01 assuming you are confident that whatever issue led to the failover is solved.
A full restart of the XSAN would probably work too (shutdown order - clients, controllers, raids, switches and power on on reverse order)
I would also recomend regular maintenance tasks, like checking disk and permissions on the servers and stopping the volume(s) and running cvfsck.

Change .local zone to .lan

We have 3 servers.
1 PowerMac G5 - Mac OS X Server 10.5.8 - Primary DNS Server
1 MacPro 2.8 Quad - Mac OS X Server 10.6.7 - Primary OD - DNS Replica - XSAN Meta controller
1 MacPro 2.8 Quad - Mac OS X Server 10.6.7 - Replica OD - DNS Replica - Secondary XSAN Meta controller
We already have two DNS zones defined in DNS.
.local - 192.168.1.xx
.xsan - 10.10.10.xx
After having many issues with network logins and workgroup manager freezing. We have determined that we need to get rid of the .local and change it to .lan.
The question is, can we jsut change the .local tld in Server Manager, or is there much more to it?

I'd go to a real and registered domain here. Why ask for Yet Another Migration, later on?
I'd go from two private subnets into one, if your network configuration (physical or organizational topology) can permit that.
Migrating domains is (usually) fixing local DNS and then the changeip command, plus finding and extricating existing references to the old domain from local scripts and settings and such. (No, beyond the changeip references, there's not much detail on this sequence.)

Changing IP for server, what's the process?

Hi all-
I have a Xserve running 10.5 Server. It is an XSAN metadata controller and Open Directory master. The powers that be decided to switch to a faster internet service, meaning we are losing the static IPs that the outside network is using. I'm wondering what the best way to switch over to the new network will be.
All the computers on the Fibre network have 2 NICs- currently one is on 216.87.x.x (outside), and the other is on 10.0.0.x (inside). The fibre network communicates over the inside, but the Open Directory communicates over the outside network.
The inside network will not be changing. We will be moving the outside network to a 10.1.10.x IP.
Since the clients use Open Directory via the outside network to login, what is the process to switch them over? I am assuming I switch over the server, and then the clients, correct? Then, I would log in using a local account, and add the new Open Directory server to Directory Utilities. Then, I should be able to log in to the Open Directory accounts.
Anything else I should be thinking of? Tips? Advice?
Thanks!

Very simple, export them as VCARDS then drag them into Address Book. Assuming your PC's mail program can export more than one at a time the whole process should take less than 10 minutes. We aren't PC people here so you need to look into the mail program you're using on it and look for the Export command. Almost surely it can export to VCARD. Once you have the VCARDS, open Address Book and drag them onto the Address Book and you're done.

Thoughts on xServe RAID replacement?

Hi everyone. Thanks for reading.
I am replacing an aging xServe RAID in a clients network. They currently use the xServe RAID as storage for their mobile home folders, company file shares (RAID 5 w/ 500GB storage), mailstore (RAID 1 w/ 250GB storage) and backup for other servers (RAID 5 w/ 3TB storage). This is hooked up directly via FC to an Intel xServe running 10.6.8 server. They would like to replace this simply because they need more storage for files, and the age (about 7 to 8 years old).
I would still use the existing xServe RAID as backup storage, however, we are looking for replacements. Right now I am pricing out a Promise VTrak E-Class with 8TB of storage (most likely will go RAID 10, so 4TB of useable storage) and a new 4Gbs quad fiber card. Total for both is around $8500. I am not convinced however they need that fast of storage for their use. They can get a Drobo 800i (bear with me here) with 8TB of storage (if dual drive redundancy is on the useable is around 3.6TB) and a dual 1GB PCI ethernet card for around $4300. In the past, we have only used the DroboPro, and think that particular unit is too slow for anything but archival data or backup. We have yet to use the 800i (nor the 1200i).
What does everyone think? Or is there another product we should also be looking at? Network is 1GB for around 40 users. Mobile accounts just sync at logoff, and useage of file shares is probably light to medium.
Thanks again.

The Promise range is what Apple originally recommended as a replacement for the discontinued XServe RAID. However you could also look at Active Storage, see http://getactivestorage.com/
They even have a 1U rackmount box that can act as an XSan metadata controller (instead of an XServe).

Backup Controller cannot mount XSAN Volume

Hi Guys,
I've really have a big problem regarding the XSAN that I've just setup: There are 3 Xserves connected to the SAN - one for the main controller, one for backup and another one for fileserver. After a fresh install of the Leopard Server 10.5.6 on all servers and fresh install of Xsan 2.0 updated to 2.1.1, I tried creating an SAN from the main controller, I added first the main and backup controllers, authenticated them properly and was successful adding them to the SAN. After this, I created the volume and it mounted properly on the main controller. What I don't understand is that whenever I try to mount the volume to the backup controller, it is saying unable to mount and even I tried forcing it to mount in terminal using the command xsanctl mount VOLNAME, its giving me an error saying
"unable to mount volume, Cannot mount XSAN volume error code: 5"
What is that error message? When I tried typing cvadmin to the main controller, it only gave me this message:
Main Controller:
File System Services (* indicates service is in control of FS)
1>*XSAN[0] located on 10.0.0.101:49930 (pid 317)
Select FSM "XSAN"
When I type the same cvadmin to the backup controller, it gave me this message:
Backup Controller:
File System Service (* indicates service is in control of FS)
1> XSAN[1] located on 10.0.0.102:50384 (pid 331)
No FSSs are active
Select FSM "none"
What is happening? both servers are having a DNS name. Before I created the SAN, from the authenticate window, the server name is just the IP address of the Ethernet 0 (first ethernet port). Now whenever I fire up Xsan Admin, both controllers are now offline and if you authenticate them, the server name info suddenly changed from IP address to a DNS Name (e.g. from 194.170.34.12, changed to hct-mdc.ad.hct.ac.ae) which even if I type my admin username and password cannot authenticate saying "server not found in network"
I really don't know now what to do and they need to fix the issue asap.
I would really appreciate your help guys!
Thanks.
jantoniophi

Hi,
I am accessing this WS via ARD, so public LAN is definitely there. I have not connected the "Xsan" network (but it should be no problems communicating the Xsan traffic over this single LAN connection).
With the firewall, the situation is more strange. When I try to open the Firewall settings on Sharing, there is a dialog "Other firewall software is running on this computer." I googled this and it seems that this was a common problem on 10.3. They suggest to delete com.apple.sharing.firewall.plist file but it is not there on 10.4.
"sudo ipfw list" shows this:
00001 allow udp from any 626 to any dst-port 626
65535 allow ip from any to any
Any ideas on how to make Firewall behave as expected? I will try to reinstall if I don't receive a reply.
Thanks.

HELP (after XSAN controller crash files are not accessible)

Hi,
We are having a major issue with one of our XSAN setups. During my breah one of the Xsan controller crashed and burned. So a college that to resuce it by rebuilding the contoller and adding the Luns to the Xsan volume.
The files are not showing up but they are still there when doing a data recovery scan.
So where I Need help with (never done this before) to get the files back. What would be next steps to get the data back?
Oh yeah, I will veryfy this today but I think the LUNS have the same identifiers and LUN ID asigned as the previous controller settings.
This Xsan setup is made out of Mac Pro Mountain Lion Xsan 3.0 (controller), two Promise Vtrak E-Class Raids and one Sandbox.
Appreciate any help thanks!

Here is the result for cvfsck -nv
Re-creating File System cvfsck Directory '/Library/Logs/Xsan/data/XSAN/trace'.
Created directory /tmp/cvfsck15730a for temporary files.
Creating MetadataAndJournal allocation check file.
Creating Video allocation check file.
** NOTE ** Read Only Check.
File system journal will not be recovered.
The results may be inconsistent and mis-leading.
Super Block information.
FS Created On               : Tue Aug 6 13:15:39 2013
Inode Version               : '2.7' - 4.0 big inodes + NamedStreams (0x207)
File System Status          : *Dirty*
Allocated Inodes            : 1536
Free Inodes                 : 1527
FL Blocks                   : 1
Next Inode Chunk            : 0x2934
Metadump Seqno              : 0
Restore Journal Seqno       : 0
Windows Security Indx Inode : 0x5
Windows Security Data Inode : 0x6
Quota Database Inode        : 0x7
Client Write Opens Inode    : 0x8
Stripe Group MetadataAndJournal             ( 0) 0x2ba7b90 blocks.
Stripe Group Video                          ( 1) 0x3691cc40 blocks.
Inode block size is 1024
Building Inode Index Database 1536 (100%).
   1536 inodes found out of 1536 expected.
Verifying NT Security Descriptors
Verifying Free List Extents.
Scanning inodes 1536 (100%).
Sorting extent list for MetadataAndJournal pass 1/1
Updating bitmap for MetadataAndJournal extents 4 (100%).
Checking for dead inodes 1536 (100%).
Checking directories 1 (100%).
Scanning for orphaned inodes 1536 (100%).
Verifying link & subdir counts 1536 (100%).
Checking free list. 1536 (100%).
Checking pending free list.
Checking Arbitration Control Block.
Checking MetadataAndJournal allocation bit maps (100%).
Checking Video allocation bit maps (100%).
File system 'XSAN' was modified.
File system 'XSAN'. Blocks-915524672 free-915514163 Inodes-1536 free-1527.
File System Check finished.

Assigning XSAN MDC to a RAID controller

In reading the XSan administration guide, it specifies that you should assign data LUNS to each controller for balance. So LUN 1 goes to controller (A) LUN 2 goes to controller (B) LUN 3 Goes to controller (A) LUN 4 goes to contoller (B)
I am looking at my current set up that was installed by an integrator and all of the Data LUNS are assigned to one controller (A) and the MetaData LUN is assigned to LUN (B). I also noticed that Force Read Ahead is disabled on both controllers.
I am having some performance issues and plan on running a file system correct when I can take the XSan offline. Since I will be taking it down, and these settings appear incorrect... I was wondering if I should change the Controller assignments for the LUNS and enable Forced Read Ahead?
Any thoughts?
Thanks,
Ray

The VTrak config scripts in Apple's KB all have LUNs divided evenly between controllers. See the scripts in articles linked from Promise VTrak: Configuring for optimal performance. I'm not sure if the x30 VTrak built in scripts do the same thing.
Re Forced Read Ahead see this guidance in http://kb.promise.com/Attachment378.aspx:
• Controller Settings, Forced Read Ahead: Enable or Disable (aggressive pre-fetch)
o Controller Forced Read Ahead should be enabled for large block sequential access such as rich
media type applications
o Controller Forced Read Ahead should be disabled for Random IO type applications
You should test with each enabled to see which works better for you.

Had to replace Xserve RAID controller and now I get Xsan Admin: duplicate LUN label RAID1-Left1

after we replace the controller volumes are mounting. Any advice on what to do with the duplicates?

Try reconnecting to the Xsan by closing the window in Xsan Admin, clicking "disconnect", then File -> New -> Connect to existing SAN. If you still see the duplicate LUNs after reconnecting, try shutting everything down and starting back up again in the order provided in this article: http://support.apple.com/kb/HT4027.

Had to replace Xserve RAID controller and now I get Xsan Admin: ERROR: duplicate LUN label RAID1-Left1

I need some help, I had one of my five Xserve RAID boxes fail. The upper controller card needed to be replaced and so we replaced it. But now only one of my volumes is loading and I am seeing the following error in my Console.
7/18/12 9:23:18.550 AM Xsan Admin: ERROR: duplicate LUN label RAID1-Left1
This raid box holds three LUNs. the left is split into two with one being the metadata / Journal for the main volume and the 2nd being the same for my secondary volume. The right side of this box is the second volume while the remaining 4 RAID boxes are my main volume. Here is the rub, the main volume is using the left1 LUN and the secondary is left2. The left2 is the one that is not working and when I go into the LUN info the WWN number does not match the actual id on the raid box.
HELP!!!!
Thanks,
Kevin Rosenthal

Did you try turning it off and on again? I mean, the full SAN shutdown/startup: http://support.apple.com/kb/HT4027
You're probably seeing "duplicate LUN labels" because the MDC has seen two LUNs with the same label but different serial numbers since it has been online. The serial number (which I think is based off the WWN) would have changed when the RAID controller changed. A reboot should fix that specific error message.
If the volume still doesn't start after rebooting, then you would want to check the cvlog for that volume.

XSAN No Controller

Similar Messages

Maybe you are looking for