Is 6320 array ready disabled?

If you like me have to deal with Sun StorEdge 6320 array, I bet that at least once in your life you’ve seen it reporting that some of its disk are in “ready disabled” state. When I saw it for the very fist time I scratched my head extensively and the only remedy reported on sunsolve was to recreate the whole volume from the ground with .vol init fast command. Note, that the dot commands are only available to the authorized personnel and could be activated by issuing “sun” command from the cli. It asks for a password, so if you know nothing about it, obviously you’re not allowed to use it.
So lets take a look at how it looks like from the console:

T4:/:<231>fru stat d
DISK    STATUS   STATE       ROLE        PORT1      PORT2      TEMP  VOLUME
------  -------  ----------  ----------  ---------  ---------  ----  ------
u1d01   ready    disabled    data disk   ready      ready      23    T4_pool_0
u1d02   ready    disabled    data disk   ready      ready      26    T4_pool_0
u1d03   ready    disabled    data disk   ready      ready      23    T4_pool_0
u1d04   ready    disabled    data disk   ready      ready      27    T4_pool_0
u1d05   ready    disabled    data disk   ready      ready      23    T4_pool_0
u1d06   ready    disabled    data disk   ready      ready      23    T4_pool_0

I found that the only way to cure it is by unmounting the volume, deleting all slices followed by volume abolition. But just before that, don’t forget to save the geometry of your slices to recreate them lately using the same size/offset and hence keep your data intact. Saving the output from “lun map list” is also a good idea.

T4:/:<232> volslice list -v T4_pool_0
Slice         Slice Num     Start Blk     Size Blks     Capacity      Volume
T4_L00       0             0             536883200      256.005 GB   T4_pool_0
T4_L01       2             536883200     536883200      256.005 GB   T4_pool_0
T4_L02       3             1073766400    268451840      128.007 GB   T4_pool_0
T4_L03       4             1342218240    89415680        42.636 GB   T4_pool_0
-             -             1431633920    6400             3.125 MB  T4_pool_0

T4:/:<233>vol unmount T4_pool_0
T4:/:<234>volslice remove -v T4_pool_0
T4:/:<235>vol remove T4_pool_0
WARNING - The volume and any slices on it will be deleted.
Continue ? [N]: Y

Lets take a look at our disks now:

T4:/:<236>fru stat d
DISK    STATUS   STATE       ROLE        PORT1      PORT2      TEMP  VOLUME
------  -------  ----------  ----------  ---------  ---------  ----  ------
u1d01   ready    enabled     unassigned  ready      ready      22    -
u1d02   ready    enabled     unassigned  ready      ready      25    -
u1d03   ready    enabled     unassigned  ready      ready      22    -
u1d04   ready    enabled     unassigned  ready      ready      25    -
u1d05   ready    enabled     unassigned  ready      ready      22    -
u1d06   ready    enabled     unassigned  ready      ready      21    -

See, they’re all “ready enabled” but unassigned. All we have to do now is to build our volume again using the information we smartly backed up beforehand:

T4:/:<237>vol add T4_pool_0 data u1d01-6 raid 5
T4:/:<238>volslice create T4_00 -s 0 -z 256GB T4_pool_0
T4:/:<239>volslice create T4_01 -s 536883200 -z 256GB T4_pool_0
T4:/:<240>volslice create T4_02 -s 1073766400 -z 128GB T4_pool_0
T4:/:<241>volslice create T4_03 -s 1342218240 -z 42.639GB T4_pool_0

T4:/:<242>volslice list -v T4_pool_0
Slice         Slice Num     Start Blk     Size Blks     Capacity      Volume
T4_00        0             0             536883200      256.005 GB   T4_pool_0
T4_01        2             536883200     536883200      256.005 GB   T4_pool_0
T4_02        3             1073766400    268451840      128.007 GB   T4_pool_0
T4_03        4             1342218240    89415680        42.636 GB   T4_pool_0
-             -             1431633920    6400             3.125 MB  T4_pool_0

Everything looks good and we could proceed with the final step:

T4:/:<243>sun
Password: 
sun: commands enabled
T4:/:<244>.vol init T4_pool_0 fast
WARNING - Existing volume data won't be changed.
Continue ? [N]: Y

At this stage we’re ready to configure lun mappings, permissions and mount the volume.

Posted on August 5, 2009 at 11:21 am by sergeyt · Permalink
In: Sun

2 Responses

Subscribe to comments via RSS

  1. Written by sluge
    on November 15, 2013 at 11:53 am
    Reply · Permalink

    O! Great! This is really helpful. But why disks become “ready disabled”?

    • Written by sergeyt
      on November 15, 2013 at 2:36 pm
      Reply · Permalink

      Hi and thanks for stopping by.
      Since that was quite a while ago I’ve already lost the track why the disks became “ready disabled” in my case. The only reason I could think of is either our array was wonky or it was caused by a premature and unclean shutdown due to a power loss.

      Cheers.

Subscribe to comments via RSS

Leave a Reply