saneguy Posted April 11, 2022 Share Posted April 11, 2022 A disk in my host keeps going out of service. I am able to rebuild the device without any issues (stop array -> remove device -> start array -> stop array -> add device -> start array -> rebuild). During the rebuild, the disk is perfect fine. But as soon as the rebuild is done, within a day, the disk goes out of service again. This has now happened 2 times. Please advise. diagnostics-20220410-1845.zip Quote Link to comment
trurl Posted April 11, 2022 Share Posted April 11, 2022 disk5 isn't connected. Check all connections, SATA and power, both ends, including splitters. Then attach new diagnostics to your NEXT post in this thread. Quote Link to comment
saneguy Posted April 27, 2022 Author Share Posted April 27, 2022 On 4/10/2022 at 7:15 PM, trurl said: disk5 isn't connected. Check all connections, SATA and power, both ends, including splitters. Then attach new diagnostics to your NEXT post in this thread. Update: I reseated the cable and its been a few days since I have seen this. Even after reseating the cable, the Unraid GUI was still reporting the disk as emulated. I rebuilt the disk again. Question: Shouldn't the GUI update when the disk is reachable again? Will a temporary cable seating issue force a rebuild of the disk? Quote Link to comment
itimpi Posted April 27, 2022 Share Posted April 27, 2022 12 minutes ago, saneguy said: Will a temporary cable seating issue force a rebuild of the disk? This. Once a disk is disabled (whatever the reason) then there are writes to it that have been lost so it is probably out-of-step with parity. The user therefore has to rebuild the disk to not lose such writes, or decide they can be lost and go via the New Config tool to accept the physical drive and rebuild parity instead to match the drive. Quote Link to comment
saneguy Posted April 27, 2022 Author Share Posted April 27, 2022 3 minutes ago, itimpi said: This. Once a disk is disabled (whatever the reason) then there are writes to it that have been lost so it is probably out-of-step with parity. The user therefore has to rebuild the disk to not lose such writes, or decide they can be lost and go via the New Config tool to accept the physical drive and rebuild parity instead to match the drive. Makes sense. Thank you for the clarification. Quote Link to comment
Recommended Posts
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.