[SOLVED] Unable to detect array drive


Recommended Posts

Hi, I am puzzled. I had a failed drive in my array and I have precleared replacement drives for this 1 drive, however when I powered up the array today to do the parity replacement/upgrade procedure as the new drive is bigger than the previous drive I got error messages from another drive that it had read errors. So I shutdown the array again and verified that the SATA cable and power cable was properly connected. However the next time the array would give errors again. So I moved the drive to a different cage which is connected on a different controller and ever since then the array will not detect this 8 TB drive anymore. The serial number is Disk 14 - WDC_WD80EZAZ-11TDBA0_1EG3446N. I have 2 diagnosis files one from this morning when the drive was still detected and another from now where it is no longer detected. I know that the location in the cage works as another drive in the same position is detected without issues. In addition I have a 2nd PC  which I use for running Preclear and there the 8tb drive is detected every time and I was even able to mount via UD plugin. I ran the xfs_repair script and it does not show anything either:

 

Linux 4.19.107-Unraid.
root@Tower:~# xfs_repair -v /dev/md1
Phase 1 - find and verify superblock...
        - block cache size set to 125072 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 2069017 tail block 2069017
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...

        XFS_REPAIR Summary    Thu Jun 11 10:27:13 2020

Phase           Start           End             Duration
Phase 1:        06/11 10:25:57  06/11 10:25:57
Phase 2:        06/11 10:25:57  06/11 10:25:58  1 second
Phase 3:        06/11 10:25:58  06/11 10:26:36  38 seconds
Phase 4:        06/11 10:26:36  06/11 10:26:36
Phase 5:        06/11 10:26:36  06/11 10:26:36
Phase 6:        06/11 10:26:36  06/11 10:27:12  36 seconds
Phase 7:        06/11 10:27:12  06/11 10:27:12

Total run time: 1 minute, 15 seconds
done

 

I am stumped and don't know what else to do. I have now connected it to the onboard SATA and 2 different SAS controllers and it is not detected anymore.

tower-diagnostics-20200611-1019.zip tower-diagnostics-20200611-1625.zip

Link to comment
  • JorgeB changed the title to [SOLVED] Unable to detect array drive

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
Reply to this topic...

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