Global Storage

Global Storage Forum

Connect, collaborate, and stay informed with insights from across Storage

 View Only

  • 1.  Storwize How to refresh Array/drive info ..command equivalent to "detectmdisk"

    Posted Fri July 28, 2023 08:57 AM

    Hello,

    I have a storwize with offline array as it had lost too many drives.

    We replaced the drives but the array didn't start the rebuild and still had the old member drives that failed.

    How do we manually force the array/drive info refresh ? something like the "detectmdisk" commands for mdisks ?

    How can I force the array to rescan drive info and start to  initialize/resynchronise ? 

    Note that the data can be restored from back up, we just want to get the array online ? 

    Does the nodes or system reboot help ?

    Thank you



    ------------------------------
    Justine Uwase
    ------------------------------


  • 2.  RE: Storwize How to refresh Array/drive info ..command equivalent to "detectmdisk"

    Posted Mon July 31, 2023 02:01 AM

    Do you think that problem is mdisk, it is easy delete it and then recreate one.

    if problem is disk itself;

    Firat make drive unused by changing via right click menu.

    then take drive out wait 2 min and put it again.

    then make it candidate and if you will use Traif you will need to mark some of them spare.



    ------------------------------
    LEVENT AKSOY
    ------------------------------

    Original Message


  • 3.  RE: Storwize How to refresh Array/drive info ..command equivalent to "detectmdisk"

    Posted Mon July 31, 2023 03:31 PM
    Hello

    Unfortunately you cannot delete an mdisk/array if it is offline....and all options are grayed out on the drives...

    Thank you for your input 



    Original Message


  • 4.  RE: Storwize How to refresh Array/drive info ..command equivalent to "detectmdisk"

    Posted Tue August 01, 2023 02:01 AM
    Edited by Patrik Groß Tue August 01, 2023 02:03 AM

    --



  • 5.  RE: Storwize How to refresh Array/drive info ..command equivalent to "detectmdisk"

    Posted Tue August 01, 2023 07:56 AM
    Hello Patrick,


    Here are some infos .. and yes the machine isn't covered anymore and it would be ok to even delete the array and restore the data if there are no other choices... 
    The issue remains on array 128, the other degraded ones were repaired once the failed drives were replaced.

    node_code_version 7.8.1.16
    cluster_code_build 135.9.2208261120000
    product_mtm 2076-124



    svcinfo lsmdiskgrp -delim :
    id:name:status:mdisk_count:vdisk_count:capacity:extent_size:free_capacity:virtual_capacity:used_capacity:real_capacity:overallocation:warning:easy_tier:easy_tier_status:compression_active:compression_virtual_capacity:compression_compressed_capacity:compression_uncompressed_capacity:parent_mdisk_grp_id:parent_mdisk_grp_name:child_mdisk_grp_count:child_mdisk_grp_capacity:type:encrypt:owner_type:site_id:site_name
    0:Noncritical_Server:degraded:5:0:63.42TB:1024:63.42TB:0.00MB:0.00MB:0.00MB:0:80:auto:balanced:no:0.00MB:0.00MB:0.00MB:0:Noncritical_Server:0:0.00MB:parent:no:none::
    1:Noncritical_Server-1:offline:5:0:63.42TB:1024:63.42TB:0.00MB:0.00MB:0.00MB:0:80:auto:balanced:no:0.00MB:0.00MB:0.00MB:1:Noncritical_Server-1:0:0.00MB:parent:no:no


    svcinfo lsarray -delim :
    mdisk_id:mdisk_name:status:mdisk_grp_id:mdisk_grp_name:capacity:raid_status:raid_level:redundancy:strip_size:tier:encrypt:distributed
    0:mdisk0:online:0:Noncritical_Server:2.7TB:online:raid6:2:256:tier_enterprise:no:yes
    16:mdisk1:online:1:Noncritical_Server-1:2.7TB:online:raid6:2:256:tier_enterprise:no:yes
    32:mdisk2:online:0:Noncritical_Server:15.6TB:online:raid6:2:256:tier_enterprise:no:yes
    48:mdisk3:online:0:Noncritical_Server:15.6TB:online:raid6:2:256:tier_enterprise:no:yes
    64:mdisk4:degraded:1:Noncritical_Server-1:15.6TB:online:raid6:2:256:tier_enterprise:no:yes
    80:mdisk5:online:1:Noncritical_Server-1:15.6TB:online:raid6:2:256:tier_enterprise:no:yes
    96:mdisk6:online:0:Noncritical_Server:14.7TB:online:raid6:2:256:tier_enterprise:no:yes
    112:mdisk7:degraded:0:Noncritical_Server:14.7TB:degraded:raid6:1:256:tier_enterprise:no:yes
    128:mdisk8:offline:1:Noncritical_Server-1:14.7TB:offline:raid6:0:256:tier_enterprise:no:yes
    144:mdisk9:online:1:Noncritical_Server-1:14.7TB:online:raid6:2:256:tier_enterprise:no:yes


    svcinfo lsarray -delim : 128
    mdisk_id:128
    mdisk_name:mdisk8
    status:offline
    mode:array
    mdisk_grp_id:1
    mdisk_grp_name:Noncritical_Server-1
    capacity:14.7TB
    quorum_index:
    block_size:
    controller_name:
    ctrl_type:
    ctrl_WWNN:
    controller_id:
    path_count:
    max_path_count:
    ctrl_LUN_#:
    UID:
    preferred_WWPN:
    active_WWPN:
    fast_write_state:empty
    raid_status:offline
    raid_level:raid6
    redundancy:0
    strip_size:256
    spare_goal:
    spare_protection_min:
    balanced:exact
    tier:tier_enterprise
    slow_write_priority:latency
    fabric_type:
    site_id:
    site_name:
    easy_tier_load:
    encrypt:no
    distributed:yes
    drive_class_id:0
    drive_count:19
    stripe_width:10
    rebuild_areas_total:2
    rebuild_areas_available:0
    rebuild_areas_goal:2
    dedupe:no
    preferred_iscsi_port_id:
    active_iscsi_port_id:
    replacement_date:

    svcinfo lsarraymember -delim : 128 2>&1
    mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection:balanced:slow_write_count:slow_write_time_last
    128:mdisk8:0:136::0:exact:0:
    128:mdisk8:1:138::0:exact:0:
    128:mdisk8:2:139::0:exact:0:
    128:mdisk8:3:137::0:exact:0:
    128:mdisk8:4:141::0:exact:0:
    128:mdisk8:5:143::0:exact:0:
    128:mdisk8:6:144::0:exact:0:
    128:mdisk8:7:145::0:exact:0:
    128:mdisk8:8:149::0:exact:0:
    128:mdisk8:9:124::0:exact:0:
    128:mdisk8:10:151::0:exact:0:
    128:mdisk8:11:152::0:exact:0:
    128:mdisk8:12:153::0:exact:0:
    128:mdisk8:13:127::0::0:
    128:mdisk8:14:::0::0:
    128:mdisk8:15:157::0:exact:0:
    128:mdisk8:16:159::0:exact:0:
    128:mdisk8:17:130::0::0:
    128:mdisk8:18:161::0:exact:0:


    svcinfo lsarraymembergoals -delim : -bytes 128 2>&1
    mdisk_id:mdisk_name:member_id:drive_id:capacity_goal:tech_type_goal:RPM_goal:enclosure_id_goal:slot_id_goal:node_id_goal:enclosure_balance_goal:block_size_goal:drive_class_id_goal
    128:mdisk8:0:136:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:1:138:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:2:139:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:3:137:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:4:141:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:5:143:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:6:144:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:7:145:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:8:149:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:9:124:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:10:151:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:11:152:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:12:153:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:13:127:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:14::1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:15:157:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:16:159:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:17:130:1199706210304:tier_enterprise:10000::::no:512:0
    128:mdisk8:18:161:1199706210304:tier_enterprise:10000::::no:512:0

    svcinfo lsarrayinitprogress -delim : 128 2>&1
    mdisk_id:mdisk_name:progress:estimated_completion_time
    128:mdisk8:100:

    svcinfo lsarraysyncprogress -delim : 128 2>&1
    mdisk_id:mdisk_name:progress:estimated_completion_time
    128:mdisk8:86:

    svcinfo lsarraymemberprogress -delim : 128 2>&1
    mdisk_id:mdisk_name:member_id:drive_id:task:new_drive_id:progress:estimated_completion_time
    128:mdisk8:17:130:rebuild::77:


    20:online::spare:tier_enterprise:1.1TB::::1:2:::inactive:0
    21:online::spare:tier_enterprise:1.1TB::::1:14:::inactive:0
    22:online::spare:tier_enterprise:1.1TB::::1:3:::inactive:0

    42:online::spare:tier_enterprise:1.1TB::::2:1:::inactive:0
    44:online::spare:tier_enterprise:1.1TB::::2:11:::inactive:0

    46:online::spare:tier_enterprise:1.1TB::::2:6:::inactive:0
    60:online::candidate:tier_enterprise:1.1TB::::6:16:::inactive:0
    63:online::unused:tier_enterprise:1.1TB::::7:22:::inactive:
    94:online::spare:tier_enterprise:558.4GB::::1:20:::inactive:1



    Thank you



    Original Message


  • 6.  RE: Storwize How to refresh Array/drive info ..command equivalent to "detectmdisk"

    Posted Wed August 09, 2023 02:05 PM

    Hello, are you able to get the solution , kindly share 



    ------------------------------
    Sandeep Sharma
    ------------------------------

    Original Message


  • 7.  RE: Storwize How to refresh Array/drive info ..command equivalent to "detectmdisk"

    Posted Wed August 09, 2023 02:13 PM
    Hello


    Still no resolution....the array /mdisk infos aren't getting refreshed and  I am unable to force update.....



    Original Message


Related Content