Visit Open-E website
Results 1 to 10 of 12

Thread: Raid failed on one DSS node

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Aug 2014
    Location
    Netherlands
    Posts
    8

    Default Raid know in good state

    I have delete the Volume en recreate with no init option. After that i see the Volumes in DSS But DSS said that there is no SYSTEM Volume.
    I have repaired the volume in DSS and have no errors anymore. The next step is to sync the data from the failover server. The data on the failed DSS is not correct so i want to resync all the data. How can i do that. The Failover services is not running on the failed dss. At this moment i can't see replication task. On the failover server i see the replication tasks. The volumes are source selected.

    Is the next to start the failover services. Set the volumes on destination on the failed DSS en clear the metadata on the failover server (Where the volumes has status sources). Or is there still a problem because at this moment i can't see any replication task on the failed DSS. On the failover server i see the replication task as reverse.

  2. #2
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    restore the old settings and configuration to see if the tasks come back.

  3. #3
    Join Date
    Aug 2014
    Location
    Netherlands
    Posts
    8

    Default Almost there

    Thanks for the answers. I wil do a restore Setup en configuration and hope that i got the replication task back.

    The backup units holds now the Volume and is the source one.
    De failed DSS (primary) is now destination. De data on the primary (failed DSS status destination) is not good so i must do a complete sync.
    Where must i clear the metadata. On the backup unit where the volume is source or must i clear it on the failed one (primary) where the volume is destination.

  4. #4

    Default

    On the failed Primary DSS if you clear the metadata in the Volume Replication keep in mind that this will do a full sync, again this is in the volume replication part of the GUI.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  5. #5
    Join Date
    Aug 2014
    Location
    Netherlands
    Posts
    8

    Default Last steps

    I have done a restore of the setup and configuration. De replication tasks are back.
    I also cleared the metadata on the primary (failed DSS) en select Volume destination.

    The last steps (correct me if i'am wrong) is: starting replication services on the primary DSS and select the sync button in the backup unit (wich hold the souce volume)
    When the sync is completed i can do a fallback so that de primary is the active node en de backup DSS is the passive node.

    Is that correct?

    Thanks for the answers.

  6. #6
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    Try to start failover service from Primary and then click sync from secondary. Once synced, try failback

  7. #7
    Join Date
    Aug 2014
    Location
    Netherlands
    Posts
    8

    Default Volume syncen

    I have selected the sync button and that is working. The speed is about 16000 kb/s wich is not so high. It takes 50h to complete.
    But when the sync is starting the performance is realy bad. We have several terminal servers and when you login it takes 10 minutes to get in. Also the linux servers get a kernel panic. After the kernel panic i reboot the linux server but then they will not boot or it takes to long. I have shutdown the primary host and everything is working normal. I dont know what i can do now. Also i dont know how i can stop the sync. I have now shutdown the primary host otherwise he is starting the sync.

    How can i fix this?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •