| View previous topic :: View next topic |
| Author |
Message |
altavek
fully protected
Joined: 02 Jul 2009
Posts: 13
|
 Posted: Mon Jul 16, 2012 11:09 am Post subject: Missing LUNs on XRAID |
 |
|
I've got 2 LUNs on the top controller that are not showing up in XSAN admin and even Disk Utility. I've reset the RAID controller, checked all cables, cleaned all dust out of the connections on the mid-plane board, repaired the LUN map, renamed them to something other than what they were previously named, even swapped the controllers. I can see them in RAID admin and nothing is reporting an error.
Any help would be greatly appreciated. Thanks! |
|
| Back to top |
|
 |
singlemalt
Xsan Master
Joined: 27 Feb 2009
Posts: 109
|
| Posted: Mon Jul 16, 2012 11:27 am Post subject: |
|
|
Off hand The only things I can think of are either lun masking or
switch zoning. |
|
| Back to top |
|
|
altavek
fully protected
Joined: 02 Jul 2009
Posts: 13
|
| Posted: Mon Jul 16, 2012 12:49 pm Post subject: |
|
|
Hrm, I thought I had disabled LUN masking but it seems it turned it self back on after updating the firmware to 1.5.1.
Well, I've turned it off but still not seeing the arrays listed in disk utility… |
|
| Back to top |
|
|
singlemalt
Xsan Master
Joined: 27 Feb 2009
Posts: 109
|
| Posted: Mon Jul 16, 2012 1:29 pm Post subject: |
|
|
Wow. Thats odd. Luckily you can roll the firmware back to 1.5 and re-disable it. You should be able to upgrade to 1.5.1 and keep lun masking disabled.
I've done it several times, albeit a very long time ago. |
|
| Back to top |
|
|
altavek
fully protected
Joined: 02 Jul 2009
Posts: 13
|
| Posted: Mon Jul 16, 2012 2:14 pm Post subject: |
|
|
OK, all my LUNS are visible after restarting the MDC but when I try to create a volume, it fails. Here's the contents of the logs:
Sys log:
| Code: | Jul 16 15:07:10 MDC /usr/sbin/serialnumberd[44104]: New xsan serial number permanently registered by pid 43433.
Jul 16 15:07:10 MDC servermgrd[43433]: Got error -9806 for SSLHandshake remote address is 10.0.0.2:36336
Jul 16 15:07:10 MDC servermgrd[43433]: Exception in threadListen: Socket: Connect failed
Jul 16 15:07:10 MDC xsand[43424]: Resetting reachability table
Jul 16 15:07:10 MDC xsand[43424]: fsm shutdown after 0 seconds
Jul 16 15:07:10 MDC xsand[43424]: Synchronizing with fsmpm.
Jul 16 15:07:10 MDC fsmpm[44132]: altpmap_init: v6 bind failed: 48
Jul 16 15:07:11 MDC xsand[43424]: fsmpm exited unexpectedly (exit code = 1)
Jul 16 15:07:11 MDC xsand[43424]: fsm shutdown after 0 seconds
Jul 16 15:07:11 MDC servermgrd[43433]: xsan: [43433/290F790] ERROR: -[SANFilesystem(PrivateMethods) doXsandManagementRpcWithCommand:]: unexpected EOF reading reply
Jul 16 15:07:11 MDC servermgrd[43433]: xsan: [43433/290F790] ERROR: -[SANFilesystem roleChanged]: unable to send 'roleChanged' message to xsand
Jul 16 15:07:11 MDC com.apple.launchd[1] (com.apple.xsan[43424]): Exited with exit code: 1
Jul 16 15:07:11 MDC servermgrd[43433]: xsan: [43433/665AF0] ERROR: -[SANFilesystem(PrivateMethods) doXsandManagementRpcWithCommand:]: Unable to connect to xsand: No such file or directory
Jul 16 15:07:11 MDC servermgrd[43433]: xsan: [43433/665AF0] ERROR: -[SANFilesystem sanConfigChanged]: unable to send 'sanConfigChanged' message to xsand
Jul 16 15:07:43 MDC servermgrd[43433]: xsan: [43433/603250] ERROR: -[SANFilesystem(PrivateMethods) doXsandManagementRpcWithCommand:]: Unable to connect to xsand: No such file or directory
Jul 16 15:07:43 MDC servermgrd[43433]: xsan: [43433/603250] ERROR: -[SANFilesystem disksChanged]: unable to send 'disksChanged' message to xsand
Jul 16 15:07:48 MDC servermgrd[43433]: xsan: [43433/603250] 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.
Jul 16 15:07:48 MDC Xsan Admin[43491]: ERROR: Error labeling luns: The operation couldn’t be completed. (SANTransactionErrorDomain error 1.) (1)
Jul 16 15:10:02 MDC servermgrd[43433]: xsan: [43433/28A9210] ERROR: initialize_volume_named(XSAN): cvmkfs had an error (status 2). Output: [Xsan File System Initializer.\n\nRe-initializing file system 'XSAN'.\n\n\nForce Stripe Alignment is no longer usedShared Meta Data File System.\nMeta Data Root is on "MetadataAndJournal".\n*Fatal*: Cannot initialize stripe groups for I/O - The Xsan File System Services on 127.0.0.1 may be stopped.\n\n\nThe creation of file system 'XSAN' failed - Bad file descriptor.\n]. Error: []
Jul 16 15:10:02 MDC Xsan Admin[43491]: ERROR: Error adding volume…: The operation couldn’t be completed. (SANTransactionErrorDomain error 100010.) (100010) |
fsmpm log:
| Code: | [0716 15:07:10] 0x7fff70429cc0 (debug) PortMapper: Unable to open /Library/Filesystems/Xsan/debug/verbose, using default debug flags, errno = 2
[0716 15:07:10] 0x7fff70429cc0 INFO Xsan PortMapper (FSMPM) starting.
[0716 15:07:10] 0x7fff70429cc0 INFO NSS: Primary Name Server is '10.0.0.2' (10.0.0.2)
[0716 15:07:10] 0x7fff70429cc0 (debug) No fsports file - port range enforcement disabled.
[0716 15:07:10] 0x7fff70429cc0 ERR altpmap_init: v6 bind failed: 48 |
|
|
| Back to top |
|
|
singlemalt
Xsan Master
Joined: 27 Feb 2009
Posts: 109
|
| Posted: Mon Jul 16, 2012 3:33 pm Post subject: |
|
|
That could be a lot of things. Just to make sure you're starting out fairly clean
I'd bring everything down then back up as per.
http://support.apple.com/kb/HT4027
If it still won't create then you'll need to supply,
which systems ( Xserve, MAcPro?, etc).
Which OS
Which version Xsan
Is stornext involved
Which model switch
Is the switch set up as per http://support.apple.com/kb/HT1084
Are there two separate e.net networks?
If yes are the ports in the right order on all systems.
Is DNS setup for at least the public network (preferably for both).
That should be enough to get started. |
|
| Back to top |
|
|
altavek
fully protected
Joined: 02 Jul 2009
Posts: 13
|
| Posted: Mon Jul 16, 2012 4:13 pm Post subject: |
|
|
Ok, going through the switch set up per the link but have a question:
Would the RAID be an initiator and everyone else a target? |
|
| Back to top |
|
|
singlemalt
Xsan Master
Joined: 27 Feb 2009
Posts: 109
|
| Posted: Mon Jul 16, 2012 4:56 pm Post subject: |
|
|
Targets are storage ( RAIDS usually)
Initiators are computer systems. |
|
| Back to top |
|
|
altavek
fully protected
Joined: 02 Jul 2009
Posts: 13
|
| Posted: Tue Jul 17, 2012 8:29 am Post subject: |
|
|
That seemed to do the trick! I had done a factory reset on the switch but never knew about those settings. Thanks!
One quick ?, what did you mean when you said:
| singlemalt wrote: | | If yes are the ports in the right order on all systems. |
|
|
| Back to top |
|
|
singlemalt
Xsan Master
Joined: 27 Feb 2009
Posts: 109
|
| Posted: Tue Jul 17, 2012 9:11 am Post subject: |
|
|
Regarding the ethernet ports in the right order...
Typically you want separate your meta data traffic from regular ethernet traffic.
So in Xsan deployments where there are two different ethernet networks you want the
Public traffic's port to be first in the service order followed by the meta data traffic.
This is set in System preferences -> Network. There's a gear pull down menu under the
port listing side bar. In the menu is the item " Set Service order". In the sheet that drops
down from choosing it you can re-order the "Service Order" by dragging items in the list.
Glad you got it going. |
|
| Back to top |
|
|
altavek
fully protected
Joined: 02 Jul 2009
Posts: 13
|
| Posted: Tue Jul 17, 2012 9:48 am Post subject: |
|
|
| Ah, I gotcha. Yes those are all set as Public first and Meta second. Thanks for clarifying! |
|
| Back to top |
|
|
altavek
fully protected
Joined: 02 Jul 2009
Posts: 13
|
| Posted: Wed Aug 01, 2012 10:00 am Post subject: |
|
|
So just as an update, it seems that the settings for the fibre switch were the fix. We've had total SAN stability for over a week now.
Now, I am seeing something pop up in the Console on pretty regular intervals:
| Code: | 8/1/12 10:48:19 AM Xsan Admin[64533] ERROR: UUID mismatch for client that was not manually entered? [7D25D85F-9AAF-4B18-820B-F9A857550821/E1E74CD3-FB9F-46BA-B0FD-214113E411D5] comp = <SANManagedComputerObject: 0x12e9f1f40> (entity: Computer; id: 0x12e9f2710 <x-coredata:///Computer/tD0A16A1D-BE11-4F68-B568-410D1287F706120136> ; data: {
authSecret = nil;
authenticationStatus = 2;
availableNetworkInterfaceNames = nil;
clientFSVersion = nil;
computerKind = nil;
"configParsable_automount_plist" = 1;
"configParsable_config_plist" = 1;
"configParsable_notifications_plist" = 1;
connectionState = 0;
cpuCount = nil;
cpuKind = nil;
cpuSpeed = nil;
failoverPriorities = (
);
fsmNotRunning = (
);
fsmpmRunning = 1;
hasPendingTransaction = 0;
hostedVolumes = (
);
isController = 0;
isLegacyXsanVersion = 0;
isOpenDirectoryReplica = 0;
isResolvingDNS = 0;
isServer = 0;
keychainServerAddress = "192.168.1.36";
keychainUsername = skylineadmin;
legacyHostName = smoke;
license = nil;
luns = (
);
macOSVersion = nil;
manuallyEnteredClient = 0;
memberOfSAN = 1;
mounts = (
"0x12b0f6ba0 <x-coredata:///Mount/tD0A16A1D-BE11-4F68-B568-410D1287F706120139>"
);
multicastDNSName = smoke;
name = smoke;
nameForNote = smoke;
nameServers = nil;
needsUpdate = nil;
networkInterfaces = (
"0x12e9f4c10 <x-coredata:///NetworkInterface/tD0A16A1D-BE11-4F68-B568-410D1287F706120137>",
"0x12e8d17b0 <x-coredata:///NetworkInterface/tD0A16A1D-BE11-4F68-B568-410D1287F706120138>"
);
note = nil;
pendingIPAddress = nil;
ramSize = nil;
role = CLIENT;
sanProperties = nil;
searchPolicy = nil;
serverAssistantDSType = nil;
serverAssistantRole = nil;
serverFSVersion = nil;
technicalComputerKind = nil;
temporary = 0;
uuid = "E1E74CD3-FB9F-46BA-B0FD-214113E411D5";
volumes = (
);
xsanVersion = nil;
}) |
This is coming from a system that is running 10.6.7 but Xsan 2.2.2. Anyone care to explain to me what it means? I thought it meant that there was a mismatch in OD with the computer's UUID but I checked and it is correct. |
|
| Back to top |
|
|
|
Xsanity Forum
Forum Search
Forum Help
Log in to check messages
Xsanity Articles
