Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Storage Spaces UI missing disks when a controller reports the same UniqueID for all attached disks (e.g. Supermicro AOC-SASLP-MV8)

Unanswered Storage Spaces UI missing disks when a controller reports the same UniqueID for all attached disks (e.g. Supermicro AOC-SASLP-MV8)

  • Wednesday, June 06, 2012 6:15 AM
     
     
    Sign In to Vote
    1

    Summary: The Storage Spaces UI has several problems when there are more than 21 physical disks available to Storage Spaces.

    I have 28 SATA disks connected over 6 controllers. 2 are used for an Intel motherboard RAID1 for OS (PhysicalDisk0), so that leaves 26 data disks for Storage Spaces. [The plan is to get to 36 data disks in due course by adding disks (this 36-bay chassis: http://www.supermicro.com/products/chassis/4U/847/SC847A-R1400LP.cfm)]

    Initially, there were 23 data disks (5x 1TB, 1x 640GB, 14x 500GB, 3x 250GB) as PhysicalDisk1-23 (in that order), which I put into a storage pool. I created a parity disk over all 23 disks. It looks like it is working fine, albeit very slowly on writes.

    I've now added 3 more 4TB disks, as PhysicalDisk24-26, and taken them offline, and have now noticed errors in the Storage Pools UI in the Server Manager. For example:

    * No more than 21 disks ever show up in the "Physical Disks" area in the lower right. When the 23 disks are connected, only the first 21 show up in the pool I created. With 26 disks connected, only the first 20 show up in the pool, and only 1 more of the new 3 (PhysicalDisk26) shows up in the Primordial group.

    * In the Properties of the parity Virtual Disk created over the 23 disks, the disks are shown incorrectly. Again, only 21 disks are shown, and PhysicalDisk26 is incorrectly shown as part of the virtual disk. See image:

    * Using the New Storage Pool Wizard, I cannot add more than 1 of the new 3 disks to a new Storage Pool (only PhysicalDisk26 is available). And the details incorrectly refer to PhysicalDisk21. See image (a WDC WD2500JD-22H is a 250GB disk, not a 4TB disk). Thus I cannot use the new disks in a new storage pool.

    According the blog post at http://blogs.msdn.com/b/b8/archive/2012/01/05/virtualizing-storage-for-scale-resiliency-and-efficiency.aspx:

    Q) What is the minimum number of disks I can use to create a pool? What is the maximum?
    You can create a pool with only one disk. However, such a pool cannot contain any resilient spaces (i.e. mirrored or parity spaces). It can only contain a simple space which does not provide resiliency to failures. We do test pools comprising multiple hundreds of disks – such as you might see in a datacenter. There is no architectural limit to the number of disks comprising a pool.

    However, the UI currently does not seem to correctly work with more than 21 physical disks. Please advise.

    Using Server 2012 RC.

    Hardware: Supermicro X8SAX (BIOS v2.0), Intel i7-920 2.67GHz, 6x 2GB DDR3-1333 (certified Crucial CT25664BA1339.16SFD)

    Disk controllers: 2x RAIDCore BC4852 (PCI-X, final 3.3.1 driver) (15 ports used), 2x Supermicro AOC-SASLP-MV8 (PCIe, 4.0.0.1200 Marvell driver to allow >2TB disks) (6 ports used), Sil 3114 (PCI, latest 1.5.20.3 driver) (1 port used), motherboard Intel in RAID mode (4 ports used for data, plus 2 for OS RAID1).


     

All Replies

  • Wednesday, June 06, 2012 6:15 PM
     
     
    Sign In to Vote
    0

    Hi David,

    With regards to UI display issue you are seeing, Could you share the output of the following PowerShell command.

    Get-PhysicalDisk | ft FriendlyName, UniqueId, ObjectId, BusType –auto

    Currently we are looking into an issue where multiple PhysicalDisks report same UniqueId and so UI displays only 1 of the PhysicalDisk matching with the UniqueId.

    The New 3 PhysicalDisks added, were they connected to same RAID controller? Are all the missing PhysicalDisks having  RAID Bustype ?

    Thanks,

    VJagdale

     
  • Wednesday, June 06, 2012 8:17 PM
     
     
    Sign In to Vote
    0

    Thanks. Yes, it looks like all 6 drives attached to the first Supermicro AOC-SASLP-MV8 are reporting the same UniqueID (0050430000000000). These are the 3x 250GB (PhysicalDisk21-23) and the 3x 4TB drives (PhysicalDisk24-26).

    There are no drives currently connected to the second Supermicro AOC-SASLP-MV8. This is a very popular PCIe card that provides 8-ports for SAS/SATA drives using 2 internal mini-SAS connectors. It is used in many servers designed for software RAID over a large number of SAS/SATA disks. It uses the Marvel 6480 chip, and has no RAID functionality: http://www.supermicro.com/products/accessories/addon/AOC-SASLP-MV8.cfm

    But yes, the bus type does show up as "RAID" in the UI for all drives connected to this controller.

    [by the way, the RAIDCore BC4852 PCI-X cards incorrectly show up as Fibre Channel bus. But they should be RAID. These are PCI-X RAID cards with 8 SATA ports each]

    So it doesn't look like you can rely on the UniqueID to uniquely identify disks in the UI. Both the PhysicalDisk# and ObjectID are unique and Windows Disk Management shows all the disks separately and correctly.

    PS C:\Users\administrator.TROUNCE> Get-PhysicalDisk | ft FriendlyName, UniqueId, ObjectId, BusType –auto

    FriendlyName   UniqueId                                                                                    ObjectId
    ------------   --------                                                                                    --------
    PhysicalDisk10 00280000004000004FB116493C169A1A                                                            {7ab38e00...
    PhysicalDisk11 00280000004000001AE48E5088028D0D                                                            {7ab38e02...
    PhysicalDisk12 002800000040000020C9A6680224E32F                                                            {7ab38e04...
    PhysicalDisk13 0028000000400000FDE73E7254A60C4C                                                            {7ab38e06...
    PhysicalDisk14 00280000004000000F7F3C300CCDB231                                                            {7ab38e08...
    PhysicalDisk15 0028000000400000BCD5E16D72532C2F                                                            {7ab38e0a...
    PhysicalDisk16 0028000000400000C39CB438B3A9D655                                                            {7ab38e0c...
    PhysicalDisk17 00280000004000006988870BE5B4CB48                                                            {7ab38e0e...
    PhysicalDisk21 0050430000000000                                                                            {7ab3900f...
    PhysicalDisk18 0028000000400000F091961AA4E59A19                                                            {7ab38e10...
    PhysicalDisk22 0050430000000000                                                                            {7ab39011...
    PhysicalDisk19 0028000000400000BE5539286AE4DE7A                                                            {7ab38e12...
    PhysicalDisk23 0050430000000000                                                                            {7ab39013...
    PhysicalDisk20 0028000000400000E51BDA05056FE060                                                            {7ab38e14...
    PhysicalDisk5  SCSI\Disk&Ven_ST350063&Prod_0AS&Rev_3.AA\5&348f5b2&0&000000:Trounce-Server2                 {7ab38e16...
    PhysicalDisk1  IDE\DiskSAMSUNG_HD103UJ_________________________1AA01109\4&180adc7b&0&0.1.0:Trounce-Server2 {7ab38e19...
    PhysicalDisk2  IDE\DiskSAMSUNG_HD103UJ_________________________1AA01109\4&180adc7b&0&0.2.0:Trounce-Server2 {7ab38e1b...
    PhysicalDisk3  IDE\DiskSAMSUNG_HD103UJ_________________________1AA01109\4&180adc7b&0&0.3.0:Trounce-Server2 {7ab38e1d...
    PhysicalDisk4  IDE\DiskSAMSUNG_HD103UJ_________________________1AA01108\4&180adc7b&0&0.4.0:Trounce-Server2 {7ab38e1f...
    PhysicalDisk24 0050430000000000                                                                            {66530261...
    PhysicalDisk25 0050430000000000                                                                            {66530263...
    PhysicalDisk26 0050430000000000                                                                            {66530265...
    PhysicalDisk0  IDE\DiskOS1.0.00__\4&180adc7b&0&0.0.0:Trounce-Server2                                       {66530268...
    PhysicalDisk6  002800000040000037638531D4A17419                                                            {7ab38df8...
    PhysicalDisk7  0028000000400000AB7400464090110C                                                            {7ab38dfa...
    PhysicalDisk8  0028000000400000843B0D6E41DBA95F                                                            {7ab38dfc...
    PhysicalDisk9  00280000004000005396CC47AA8AD97B                                                            {7ab38dfe...



     
  • Monday, July 02, 2012 6:59 PM
     
     
    Sign In to Vote
    0

    An update. I added 16x SATA disks across 2x Supermicro AOC-SASLP-MV8. All 16 disks report the same UniqueID.

    I have 25 disks in the pool now (23 as parity; 2 as journal added via PowerShell). 10 of these are on the two AOC-SASLP-MV8 controllers. Only the first 16 disks show up in the UI, so 9 are missing from the UI - which is consistent with this UI bug where only one disk per UniqueID shows up. PowerShell does work to manage the SS.

    PS C:\Users\administrator.TROUNCE> Get-PhysicalDisk | format-list FriendlyName, UniqueId, ObjectId, BusType


    FriendlyName : PhysicalDisk6
    UniqueId     : 00280000004000004FB116493C169A1A
    ObjectId     : {7ab38e00-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk7
    UniqueId     : 00280000004000001AE48E5088028D0D
    ObjectId     : {7ab38e02-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk8
    UniqueId     : 002800000040000020C9A6680224E32F
    ObjectId     : {7ab38e04-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk9
    UniqueId     : 0028000000400000FDE73E7254A60C4C
    ObjectId     : {7ab38e06-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk23
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e08-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk22
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e0a-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk21
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e0c-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk20
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e0e-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk5
    UniqueId     : 0028000000400000272BA74A52309853
    ObjectId     : {7ab3900f-ab87-11e1-bbbd-002590520253}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk19
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e10-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk4
    UniqueId     : 00280000004000009DE164099941430A
    ObjectId     : {7ab39011-ab87-11e1-bbbd-002590520253}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk18
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e12-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk11
    UniqueId     : 0028000000400000967EB0559AB4E351
    ObjectId     : {7ab39013-ab87-11e1-bbbd-002590520253}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk17
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e14-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk24
    UniqueId     : 0050430000000000
    ObjectId     : {7ab38e16-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk10
    UniqueId     : 0028000000400000B22A722C8AD2557B
    ObjectId     : {df23f916-c19f-11e1-bbf5-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk16
    UniqueId     : 0028000000400000DA4D24536A847E52
    ObjectId     : {7ab38e19-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk15
    UniqueId     : 00280000004000005DEDFF007783A242
    ObjectId     : {7ab38e1b-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk14
    UniqueId     : 002800000040000018C9CF6EBE605911
    ObjectId     : {7ab38e1d-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk13
    UniqueId     : 0028000000400000B64436290D155A48
    ObjectId     : {7ab38e1f-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk0
    UniqueId     : IDE\DiskOS1.0.00__\4&180adc7b&0&0.0.0:Trounce-Server2
    ObjectId     : {df23f925-c19f-11e1-bbf5-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk31
    UniqueId     : 0050430000000000
    ObjectId     : {df241daf-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk32
    UniqueId     : 0050430000000000
    ObjectId     : {df241db2-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk27
    UniqueId     : 0050430000000000
    ObjectId     : {df241cbe-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk28
    UniqueId     : 0050430000000000
    ObjectId     : {df241cc1-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk34
    UniqueId     : 0050430000000000
    ObjectId     : {df241dc4-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk29
    UniqueId     : 0050430000000000
    ObjectId     : {df241cca-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk33
    UniqueId     : 0050430000000000
    ObjectId     : {df241dcf-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk30
    UniqueId     : 0050430000000000
    ObjectId     : {df241cd3-c19f-11e1-bbf5-002590520253}
    BusType      : RAID

    FriendlyName : PhysicalDisk2
    UniqueId     : 002800000040000037638531D4A17419
    ObjectId     : {7ab38df8-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk3
    UniqueId     : 0028000000400000AB7400464090110C
    ObjectId     : {7ab38dfa-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel

    FriendlyName : PhysicalDisk1
    UniqueId     : IDE\DiskWDC_WD6400AAKS-00A7B2___________________01.03B01\4&180adc7b&0&0.1.0:Trounce-Server2
    ObjectId     : {7ab38dfc-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : RAID

    FriendlyName : PhysicalDisk12
    UniqueId     : 00280000004000005396CC47AA8AD97B
    ObjectId     : {7ab38dfe-ab87-11e1-bbbd-806e6f6e6963}
    BusType      : Fibre Channel


     
  • Tuesday, July 03, 2012 6:10 PM
     
     
    Sign In to Vote
    0

    The UI also impedes functionality. I created a new storage pool with 8 disks attached to the same AOC-SASLP-MV8 controller. The only way to do this is via PowerShell.

    Even then, I can't create a new parity virtual disk from this pool using the UI, as "The storage pool does not contain enough physical disks to support the selected storage layout". The UI only shows one of the 8 disks in the pool, and the logic in the UI does not seem to be the same as PowerShell.

     
  • Thursday, July 05, 2012 9:25 PM
     
     
    Sign In to Vote
    0

    Hello David!

    Thanks a lot for sharing your experience with this specific set of hardware.

    In Server Manager our goal is to manage multiple servers on a single pane of glass.

    That includes storage as well. In order to accomplish this, we rely on the unique ID of a disk to identify if this is the same or a different disk when seen from more than one node.

    We are aware that unfortunately some hardware out in the market today does not fulfill this logo requirement.
    We currently are working with all the industry leaders to re-emphasize on the need for unique IDs but we cannot comment on potential future firmware updates and
    their like for your specific hardware.

    What that means for you is Server Manager is still a very valuable tool for many of the management tasks, including all higher layers in storage management. Basically anything other than pool and virtual disk creation/manipulation. For that part Powershell is  a way to circumvent the unique ID requirement and we hope it won’t be too inconvenient for you to continue your evaluation that way.

     
  • Thursday, July 05, 2012 9:54 PM
     
     
    Sign In to Vote
    0

    Thanks Fabian. Ok, so do I read from your post that you are not planning to make changes to the Server Manager UI for RTM, to work with controllers that report the same UniqueID (but different ObjectIDs) for different disks?

    I understand it would be better if the controllers reported different UniqueIDs for different disks. Maybe future firmware upgrades may support that. But for now, if you don't make any changes to better support these controllers, you will cause enormous usability problems and confusion about missing disks - for both users and for Microsoft support.

    This is particularly true since Storage Spaces is targeted at attaching large numbers of commodity disks using SAS/SATA. And the cheapest and most popular controller for that is the Supermicro AOC-SASLP-MV8 (with 8 SATA ports on PCIe for $100).

     
  • Monday, July 09, 2012 7:29 PM
     
     
    Sign In to Vote
    0

    I'm using a RocketRaid 622 with a Sans Digital TRM5+ and have this same issue.  I tried using PowerShell, but I get an error indicating that IsPooled is an invalid parameter.  This won't run for me:

    $Disks = Get-PhysicalDisk –IsPooled $False

    Get-StorageSubsystem | New-StoragePool –PhysicalDisk $Disks –Friendlyname “Storage Pool 1”

    Will you provide the method to circumvent the unique ID requirement?  Thanks in advance.

     
  • Monday, July 09, 2012 8:00 PM
     
     
    Sign In to Vote
    0

    Josh - that seems to be a different issue.

    I think the documentation at http://technet.microsoft.com/en-us/library/hh848686 is wrong.

    It refers to an "-IsPooled" parameter that doesn't seem to exist.

    Try "Get-PhysicalDisk -CanPool $True" instead. That works for me, but it isn't documented.

    EDIT: Microsoft online documentation has been corrected to refer to the correct CanPool parameter, not the non-existent IsPooled parameter
     
  • Sunday, July 15, 2012 6:15 PM
     
     
    Sign In to Vote
    1

    It turns out that using the v3.1.0.22 driver returns different UniqueIDs for all different disks (e.g. of the form "SCSI\Disk&Ven_Hitachi&Prod_HDS725050KLA360&Rev_K2AO\5&24aa82bb&0&000000:Trounce-Server2").

    So with this driver, the UI works fine. But this driver doesn't allow the use of drives >2TB.

    Using the v4.0.0.1200 drivers allows you to use drives >2TB. But it returns the same UniqueID ("0050430000000000") for all drives.

    Supermicro support is now aware of the issue - hopefully there will be an updated driver that does both correctly in due course. Hope this information helps others.

     
  • Friday, September 07, 2012 6:33 AM
     
     
    Sign In to Vote
    1

    Having just blown ~12 hrs on this very thing, I figured I would share what I have learned with Storage Spaces and Server 2012 RTM thus far (yes, this issue still exists in Server 2012 RTM):

    1) The HighPoint RocketRAID 2314 does the exact same thing as reported by the OP - every drive on the array has the same 'UniqueID' and thus the Storage Spaces GUI only sees 1 device. All devices can be manually pooled using PowerShell, but they appear as 1 Disk devices, and so mirroring/parity will not work in this configuration with this device. So I decided to use the integrated Mainborad RAID.

    2) My server is a small server I use for testing and household storage duties. That being said, it is an AMD Athlon II x4 on an Asus AMD mainboard using the SB700 I/O controller. I am aware of the 10-drive limitation for this chipset and it is running 6x WD 1.5TB HDDs, 2x Hitachi 2TB HDDs, 1x WD 160G HDD and a DVD-RW (all SATA). All drives except the DVD-RW and the 160G HDD (used for OS) are in a SANS Digital TRM-8B ESATA array (used 2x4 SATA port multipliers). The drivers that come built-in to Server 2012 for the RAID function of this chipset do not work very well at all. If the drives are set as stand-alone or RAID-Ready, they are invisible to the OS and the lights on my Array are off for these drives. If a drive is actually configured as RAID (in my case the 2x Hitachi 2TB HDDs are RAID-0), the installer will see it, but not the OS after install is completed. Manually installing the Windows 7 x64 RAID Drivers for this chipset from AMD worked perfectly (Note: Actual AMD installer will not work. You need to run the AMD installer and then using Device Manager, browse to the actual drivers and manually install them).

    3) After all of that, 2 of my 6 WD 1.5TB HDDs insisted on having the same UniqueID regardless of anything I did. After a couple of hours, and some drive swaps (I have 2 other of those drives as spares) I discovered 2 things. Firstly, it did not matter which port the drives were connected to - it was always the same 2 physical drives that shared the same UniqueID. Swapping out either of these drives with the a spare retained the same UniqueID for the new physical drive as well. After a LOT of putzing around with that, I went into the RAID BIOS and saw that 2 of the HDD's were marked as stand-alone drives, and the other 4 were marked as RAID-READY. I set the other 2 drives as RAID-READY and the OS now had a completely unique UniqueID for each drive, resolving that issue and letting me set up my Storage Spaces using the GUI with all 6 WD 1.5TB HDDs.

    I figured that after all the PITA I experienced getting that working correctly, I would share and save someone else the nightmare. All of that being said, the system is running beautifully so far. The only other issues I have had (both drivers and very simple) were that I had to manually install the Asus ATK0110 ACPI Utility driver (Windows Update gets that on Win 7 and Win 8 but not Server 2012, and it doesn't really do anything anyway unless you are using the Asus utility software - which I'm not), and the integrated video (Radeon HD 4200) had to use the Windows 7 x64 video driver from the Windows Update Downloads site (The AMD Windows 8 RTM drivers did not detect the video device in Server 2012 and I could not manually install them).


    • Edited by mvmiller12 Friday, September 07, 2012 6:35 AM Clarified I was using Server 2012 RTM
    •  
     
  • Thursday, October 11, 2012 3:49 PM
     
     
    Sign In to Vote
    0

    Hi

    I have a similar issue as you can see here:
    "Storage space and JMicron SATA controler" thread

    But in my case I wasn't able to create a storage space even with Powersheel :(

    Now I use the mainboard controler, and on the JMicron I have non-pooled drive. But I'll need to use the controler for pooled drive... 
    Will I be able to add drives that are connected to th JMicron controler, with powersheel, even with this UniqueID issue ?

    Or will I need to change my mainboard or find a SATA controler card without this issue ?

     
  • Thursday, February 14, 2013 7:05 PM
     
     
    Sign In to Vote
    0

    Hi all.

    I have the same Error Here, but with the RedHat VirtIO Disk Device (Thats seems to be a special iSCSI Driver).

    In My Case, I can create a Storage Pool using Powershell, but I really need to test de Mirror Feature.

    For Now, I'll Open a ticket against RH Folks and keep you guys in touch.

    Gabriel Cavalcante