dikkiedirk Posted February 12, 2013 Share Posted February 12, 2013 Many of us have seen it happening. Suddenly we see a red balled disk in our array. What is the best way to deal with it? What are the possible scenarios? How do I secure data-integrity? Can someone give me pointers on how to act? Quote Link to comment
grither Posted February 12, 2013 Share Posted February 12, 2013 always have a precleared drive ready take note of failed drive serial number stop array shutdown server remove failed drive insert pre cleared drive boot server main menu, replace failed drive slot with pre cleared drive start array, unraid will rebuild parity. Quote Link to comment
Joe L. Posted February 12, 2013 Share Posted February 12, 2013 start array, unraid will rebuild parity. Almost accurate. It should read: start array, unRAID will re-construct the failed drive by use of all the remaining drives in the server. Quote Link to comment
RobJ Posted February 13, 2013 Share Posted February 13, 2013 A guide to red balls on the UnRAID wiki would be a good idea. Perhaps we can all throw out ideas, how to deal with the various possible scenarios, and later someone can put a guide together from the comments here. The first thing I would want mentioned is to PLEASE capture a syslog BEFORE you reboot! We want to see the history of what happened, as that may make a huge difference. The first big decision is whether the drive is truly bad or not. There is no one strategy for dealing with a red-balled drive, it depends on the true situation. Quote Link to comment
Joe L. Posted February 13, 2013 Share Posted February 13, 2013 A guide to red balls on the UnRAID wiki would be a good idea. Perhaps we can all throw out ideas, how to deal with the various possible scenarios, and later someone can put a guide together from the comments here.Look here: http://www.lime-technology.com/wiki/index.php/FAQ#What_does_the_Red_Ball_mean.3F The first thing I would want mentioned is to PLEASE capture a syslog BEFORE you reboot! We want to see the history of what happened, as that may make a huge difference. The first big decision is whether the drive is truly bad or not. There is no one strategy for dealing with a red-balled drive, it depends on the true situation. It is not perfect, but it does mention figuring out why a disk was disabled by looking in the syslog. Quote Link to comment
mrklaw Posted February 14, 2013 Share Posted February 14, 2013 for preclearing disks to have sitting ready - can you just stop an array and pull a drive out to give you a spare slot to do the preclearing? All of my available slots are full with active drives currently. Quote Link to comment
RobJ Posted February 14, 2013 Share Posted February 14, 2013 A guide to red balls on the UnRAID wiki would be a good idea. Perhaps we can all throw out ideas, how to deal with the various possible scenarios, and later someone can put a guide together from the comments here.Look here: http://www.lime-technology.com/wiki/index.php/FAQ#What_does_the_Red_Ball_mean.3F The first thing I would want mentioned is to PLEASE capture a syslog BEFORE you reboot! We want to see the history of what happened, as that may make a huge difference. The first big decision is whether the drive is truly bad or not. There is no one strategy for dealing with a red-balled drive, it depends on the true situation. It is not perfect, but it does mention figuring out why a disk was disabled by looking in the syslog. I had completely forgotten about that FAQ, Hard Drives section, and the Troubleshooting page, Hard drive failures section. They need some updating though. I'll try to get around to it, if no one else does. 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.