Jump to content

  • 6.5.1-rc1 Array Stopped - stale configuration

    realies

    By realies

      • Closed Urgent

    Upon a graphics card crash, the system halted and had to be physically rebooted. After the reboot, the webGui is showing "Array Stopped - stale configuration" and the array devices are all unassigned with the cache drive the only populated device in the Main page. It seems that this is a bug, considering other people have faced it, although not sure how to reproduce without risking the data. Speaking of which, what is the recommended way of reassigning all devices and starting the array in this situation? Contents of disk.cfg here.

     

    Update: The super.dat file is NOT zero bytes, there's also a super.dat.CA_BACKUP. A filename called DISK_ASSIGNMENTS.txt contains the device order in details. One of the previously unassigned drives is missing from the system.

     

    Update2: Missing drive became available on next power cycle. Checking "parity is valid" and re-assigning disks according to old records seems to have brought the array online without losing data.

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    limetech

    Can't do much without diagnostics.zip.  If you can reproduce and and post diags, add comment here and I'll re-open.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...