May 1, 20179 yr Rebooted my array because I needed to upgrade a video card. When the server came up, 1 drive had a red x, contents emulated. Smart report attached. It has passed a short smart test twice without error. Drive is in an MD1000 enclosure. I stopped the array and swapped positions with that disk and a neighbor disk to determine if there was an issue in the enclosure. The neighbor disk showed up but the x disk did return to normal operation. I then pulled the disk and placed it into another server's enclosure and unassigned devices recognized it but I did not attempt to mount it. If I stop the array and cycle the unassigned devices it will sometimes appear there momentarily and then disappear. I replaced the interposer with another one to rule out that being the problem. Parity shows valid. So, assuming the disk is good, do I just rebuild it? And if so, what are the steps for that? Asking so I don't screw it up thinking I know what I'm doing. Thanks! Smart-20170501-1034.zip
May 1, 20179 yr TL;DR: Stop array Unassign disk Start array Stop array Reassign disk Start array to begin rebuild https://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_X_next_to_a_hard_disk.3F
May 1, 20179 yr Author 2 hours ago, trurl said: TL;DR: Stop array Unassign disk Start array Stop array Reassign disk Start array to begin rebuild https://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_X_next_to_a_hard_disk.3F Thanks, all I could find was the page that said "Don't do this"
Archived
This topic is now archived and is closed to further replies.