January 22, 201610 yr I have a data drive showing up on the dashboard as faulty (red x). This was the most recently added drive to the array and has been working in the past. I upgraded to 6.1.7 today and the array won't start because of this error. I'm not extremely technical, but I don't see any glaring issues that indicate the drive is really bad. Before I buy a new drive to replace it, I thought I'd ask if anyone has suggestions for things I can do to troubleshoot. I've attached the diagnostics file. Thank you. tower-diagnostics-20160122-1520.zip
January 22, 201610 yr Community Expert Is it this drive? Jan 22 15:20:09 Tower kernel: md: import disk10: [8,80] (sdf) ST4000DM000-1F2168_S300LZXM size: 3907018532 ... Jan 22 15:20:26 Tower kernel: md: disk10 removed ... Jan 22 15:20:33 Tower kernel: md: import disk10: [8,80] (sdf) ST4000DM000-1F2168_S300LZXM size: 3907018532 SMART looks OK. Check connections. You can rebuild it to itself. What do I do if I get a red X next to a hard disk?
January 23, 201610 yr Author Yep, that's the drive giving me trouble. Thanks for the link. I'll give it a shot.
January 23, 201610 yr Author Still no luck. On the Main page, there is no option to unassign disk 10. Where I would expect to see unassign in the dropdown, it instead says "no device".
January 23, 201610 yr Try rebooting. (If you haven't, your HBA / mobo might not properly support hot plugging) If it still doesn't show up, then either the drive is bad, or you have further cabling issues
February 6, 201610 yr Author I've tried a few things and I'm still stuck. Attached is an updated diagnostics file. I've swapped cables and this physical drive continues to show up with the red x. I'm far from an expert, but I'm thinking it's not a cable issue. I bought another drive hoping to do a swap. I'm thinking my parity drive might be bad, or else I'm not doing something right. When I choose to start the array to do the rebuild, it stops the array. I see the dashboard says parity is invalid. Is that because I have a bad data drive, or is it because I have bad parity? What's my best course of action here? Thanks. tower-diagnostics-20160205-1838.zip
February 6, 201610 yr Community Expert The red X will never go away until the drive is rebuilt. Post a screenshot of Main showing Array Devices, and one showing Array Operation.
February 6, 201610 yr Community Expert You have to rebuild the disk10, since SMART looks fine I would try first to rebuild to the same disk. Stop array, unassign disk10, start array, stop array, reassign disk10 and start array to begin rebuild.
February 8, 201610 yr Author I think my problem at this point is that I don't know how to get the array started in order to do the rebuild. I don't see how to unassign disk 10. Attached is a screen shot of the array. The bad disk is sdg. The new disk is sdf. And the third choice in the dropdown is "no device". I can't start the array by choosing any of those three choices. I hope I'm missing something basic.
February 8, 201610 yr Community Expert Selecting the new disk should let you start the array after checking the box "I want to do this "(or similar), if it's not working maybe try with a different browser.
February 9, 201610 yr Author How do I know if the drive is rebuilding? After checking the "I want to do this" box and selecting start, I don't get any feedback that it's doing anything. How can I verify? Attached is an updated diagnostics file. tower-diagnostics-20160209-0902.zip
February 9, 201610 yr Community Expert Usually you will see something in the Array Operation section of Main. If not post a screenshot.
February 9, 201610 yr Community Expert Did you try a different browser? You can also try to chhdsk the flash drive on a windows pc.
February 9, 201610 yr Author Finally found my issue. I deleted the startState line from the disk.cfg file. After reboot, the array started as expected. Thank you all for your help.
Archived
This topic is now archived and is closed to further replies.