Jump to content

  • [6.9.2] Problem with size of replacement parity drive

    S1ckh34d

    By S1ckh34d

      • Solved Minor

    Hello,

     

    i have replaced my faulty parity drive with a new SSD. 
    Now I can not start the array because unraid says: "Disk in parity slot is not biggest."

    I have checked the new drive and my second parity drive for "HPA" and size but there is no diffrence.

      

    root@Tower:~# hdparm -N /dev/sde
/dev/sde:
 max sectors   = 3907029168/3907029168, ACCESSIBLE MAX ADDRESS disabled
 
root@Tower:~# hdparm -N /dev/sdo
/dev/sdo:
 max sectors   = 3907029168/3907029168, HPA is disabled

     

     

    tower-diagnostics-20210529-1509.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    JorgeB

    Since v6.9 Unraid partitions SSDs to start on sector 2048 (for 512B sector devices), HDDs partitions start on sector 64, this means partitions on an SSD are always slight smaller than a same capacity HDD, so they can't be used as parity, unless all other arrays devices are also SSDs or they are smaller capacity HDDs.

    Link to comment
    JorgeB

    Forgot to mention, one way to workaround this is to downgrade to v6.8.3, it will allow to add the SSD as parity, start array and you can even cancel the parity sync and finish after upgrading back to v6.9, it will accept the device if already partitioned with the old layout.

    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...