This discussion is locked
mhenstell
Level 1 (0 points)

Q: XSAN can't see LUNs - error message

I'm having trouble with Xsan detecting some of my LUNs - some of them show up with "serial: unknown" in cvlabel and don't appear in Xsan Admin. A recurring error message in the console reads: Error: [lun-name] has a malformed serialNumber." Any help would be greatly appreciated. Thanks!

Mac Pro, Mac OS X (10.6.2)

Posted on Mar 19, 2010 8:36 PM

Close
mhenstell

Q: XSAN can't see LUNs - error message

  • All replies
  • Helpful answers

  • by Strontium90,

    Strontium90 Strontium90 Mar 21, 2010 5:16 PM in response to mhenstell
    Level 5 (4,087 points)
    Servers Enterprise
    Mar 21, 2010 5:16 PM in response to mhenstell
    I am assuming this is on a new installation? Otherwise, we are talking volume loss. So, if this is a new installation, then the assumption is that you've formatted the LUNs using Disk Utility first. This is a no no as you have already placed a format on the LUNs and now Xsan will not use them.

    Let the forum know if this is the case. I hesitate to make a recommendation as I don't want to suggest something that will result in data loss.

    What storage arrays are you using? When you run a diskutil list, what does the metadata controller return to you?

    Hope this helps

  • by mhenstell,

    mhenstell mhenstell Mar 22, 2010 7:42 AM in response to Strontium90
    Level 1 (0 points)
    Mar 22, 2010 7:42 AM in response to Strontium90
    This is a new installation, so we're not worried about data loss. The LUNs have not been formatted, and I've tried the dd command outlined in http://support.apple.com/kb/TS1268. Diskutil shows all the LUNs I want are present with no Type Name. Still getting the same ERROR: LUN (null) has malformed serialNumber 'unknown'

    I'm running Rorke Aurora LS arrays for data and a Rorke (infortrends) HDX for metadata. Swapped out all the SFPs with apple SFP copper cables, no luck. Any suggestions greatly appreciated, thanks!

  • by Strontium90,

    Strontium90 Strontium90 Mar 22, 2010 3:16 PM in response to mhenstell
    Level 5 (4,087 points)
    Servers Enterprise
    Mar 22, 2010 3:16 PM in response to mhenstell
    You said in your original post "some" of the LUNs. Can you make heads or tails as to which ones are working and which are not? Is it isolated to a specific device? Rorke, huh. Ouch. Good luck with that.

    Have you tried setting the LUN labels outside of Xsan admin? Use the cvlabel command.

  • by mhenstell,

    mhenstell mhenstell Mar 22, 2010 3:23 PM in response to Strontium90
    Level 1 (0 points)
    Mar 22, 2010 3:23 PM in response to Strontium90
    Turns out the problem lies with Xsan Admin. Editing the config file by hand and using cvlabel and cvadmin produced an (apparently) working volume. Xsan Admin still freaks the heck out (see my other topic with picture). Still getting the serialNumber error, although it seems to be unrelated to FSM functioning. So I guess my question is - am I the only person for which Xsan Admin is completely busted?