This discussion is locked
DustinYoder
Level 1 (0 points)

Q: XSAN drive connecting after restart with different disk identifiers 'disk6' then 'disk9', etc...

This is a screen capture from disk utility on the Lion XServe.  The promise array is connected to this XServe which is also the metadata master through fibre channel switch. This XServe is the only computer connected to this fibre channel switch except for a tape backup drive.  So each time I run a tape backup with Retrospect it fails saying it can't find my source drive.  It is looking for Disk Id 'disk6' but after restart the XSan is mounted as 'disk9' or some other disk id.  It appears as though the connections still exist in disk util, but only the latest one has an actual disk volume with it.  See last CarlisleFile drive in the attached image. 

 

Any thoughts on how I can eliminate these extra drive connections and force my xsan to always mount using the same disk id?

Promise Problem.png

Xserve, Mac OS X (10.7.2)

Posted on Nov 30, 2011 3:02 PM

Close
DustinYoder

Q: XSAN drive connecting after restart with different disk identifiers 'disk6' then 'disk9', etc...

  • All replies
  • Helpful answers

  • by Blaidd Drwg,

    Blaidd Drwg Blaidd Drwg Dec 22, 2011 2:24 AM in response to DustinYoder
    Level 1 (109 points)
    Dec 22, 2011 2:24 AM in response to DustinYoder

    The "extra drives" appear to be the LUNs from your Xsan volume. You can't hide them in Disk Utility. The disk device nodes are dynamically assigned at startup. This is normal. You cannot rely on your Xsan volume always mounting from the same /dev/diskN device.