Jump to content

  • 7.0.0-beta2 Unable to replace failed ZFS disk online

    custom90gt

    By custom90gt

      • Minor

    I had a disk failure on my ZFS array and tried to do the following to replace it:

     

    Procedure if you can have both the old and new devices connected at the same time:

     

    stop the array

    on the main page click on the pool device you want to replace/upgrade and select the new one from the drop down list (any data on the new device will be deleted)

    start the array

    a 'zpool replace' will begin and the new device will be resilvered

    progress can be seen by clicking on the first pool device and scrolling down to “pool status”

    when done again check "pool status" page to confirm everything looks good

     

    Unfortunately when I try to select the new drive the gui switches back to the failed drive and I am unable to re-open the select down menu. I figure it was just a visual bug but when I try to click start array nothing happens.  Same if I select no device.  I ended up having to shut down the array and physically removed the drive in order for the GUI to allow for a replacement of the drive.  I know there was a visual bug when selecting the type of parity for a ZFS array and I wonder if this is somehow related. 

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    JorgeB
    Quote

    Unfortunately when I try to select the new drive the gui switches back to the failed drive and I am unable to re-open the select down menu

     

    That's not normal, please post the diagnostics after a replace attempt.

    Link to comment
    JorgeB

    syslog-previous shows that you were having issues with the new device:

      

    Sep 18 07:13:47 Harley kernel: mpt3sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 12 TIMES] ###
Sep 18 07:13:47 Harley kernel: sd 3:0:7:0: [sdj] tag#2868 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Sep 18 07:13:47 Harley kernel: sd 3:0:7:0: [sdj] tag#2868 CDB: opcode=0x2a 2a 00 34 78 04 43 00 00 06 00
Sep 18 07:13:47 Harley kernel: I/O error, dev sdj, sector 7042245144 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0
Sep 18 07:13:47 Harley kernel: zio pool=zfs vdev=/dev/sdj1 error=5 type=2 offset=3605629480960 size=24576 flags=1074267264
Sep 18 07:13:47 Harley kernel: mpt3sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 8 TIMES] ###
Sep 18 07:13:48 Harley kernel: mpt3sas_cm0: log_info(0x3112010c): originator(PL), code(0x12), sub_code(0x010c)
Sep 18 07:13:48 Harley kernel: mpt3sas_cm0: log_info(0x31120303): originator(PL), code(0x12), sub_code(0x0303)
### [PREVIOUS LINE REPEATED 27 TIMES] ###
Sep 18 07:13:50 Harley kernel: sd 3:0:7:0: [sdj] tag#135 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s
Sep 18 07:13:50 Harley kernel: sd 3:0:7:0: [sdj] tag#135 CDB: opcode=0x2a 2a 00 00 00 00 0c 00 00 1c 00
Sep 18 07:13:50 Harley kernel: I/O error, dev sdj, sector 96 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
Sep 18 07:13:50 Harley kernel: zio pool=zfs vdev=/dev/sdj1 error=5 type=2 offset=16384 size=114688 flags=1573568

     

    Looks like a power/connection issue.

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