May 9, 200818 yr I did a parity check last night as all the drives I have are now in the array. Now for one of my drives it says I have 266 errors on the main html page. This disk is blank I don't have any data on it yet so I'm not worried, but what do I do now. Is there some sort of "error checking" utility I can use to check to see if the disk is bad before I start writing data to it? Thanks.
May 9, 200818 yr Instructions are in the wiki here: http://lime-technology.com/wiki/index.php?title=Troubleshooting#Hard_drive_failures Errors can also be caused by poor quality cables, poor power supplies, bad ram... read errors such as you described are not a good way to start out. To figure out if it is the disk itself you will need to try it on a different port/cable/disk controller. good luck.
May 9, 200818 yr Author I understand what you linked to, but let me clarify to make sure I've got it. I don't have a red ball by the drive. I have a green ball. So the errors it says I have, have already been fixed and drive is good to go. So what I should do now is check all the cables and re-run a parity check and then everything should be ZERO again. If not then I might have a bad drive? Is that how it works? Thanks.
May 9, 200818 yr Farther down the page in Joe's link are some instructions for checking the SMART report, and for doing a disk test through the SMART system.
May 9, 200818 yr I understand what you linked to, but let me clarify to make sure I've got it. I don't have a red ball by the drive. I have a green ball. So the errors it says I have, have already been fixed and drive is good to go. So what I should do now is check all the cables and re-run a parity check and then everything should be ZERO again. If not then I might have a bad drive? Is that how it works? Thanks. The errors you see were "read" errors. unRAID supplied the contents by reading from the other data drives in combination with parity and then also wrote those same blocks back to the failing disk. If the blocks on the disk were bad, the "smart" system might have re-allocated them elsewhere and you will be fine. However, if the errors continue, you have a bad drive, drive cable, power-supply, memory... something. A write error to a drive would give you a red indicator.. at that point it is off-line and any writes or reads to/from it are actually written to the parity drive until you can get the failed drive replaced. At that point you are OK unless a second drive fails, then you lose data on both the failed drives. It is good you do not have this kind of failure. Joe L.
May 9, 200818 yr Author I'm really annoyed!! When I was checking the cable I pulled out a HDD power cable by accident. Luckily for me all drives at this point were spun down. I shutdown properly and now that it's back up a the drive cable that I pulled out now has a red ball by it. NOW WHAT DO I DO. P.S. The cable I pulled out was on a different disk than the one I was talking about previously. I know the data is not corupt becuase I pulled the power cable out of the drive when I was spun down do I have to rebuild the drive?? So what should I do?
May 9, 200818 yr Basically, the instructions are here in the wiki: http://lime-technology.com/wiki/index.php?title=Troubleshooting The section of it you need says: Okay, the cable was lose, or I think the failure was fluke - how can I get unRAID to reuse this same disk that it thought had failed? You can re-enable the hard drive and try to reconstruct it as follows: * Stop the array, go to the Devices page and unassign the disk. * Reboot * Stop the array, go to the Devices page and re-assign the disk * Go to Main - system should detect a "new" drive for the one disabled, click Start to start parity-reconstruct of the disk. Good luck... Joe L.
May 9, 200818 yr Author That's what I figured out and then I read the manual. Thanks for all the help. Basically the system problem free it's just getting to know the inconsistencies of it. Meaning I can't boot without a monitor attached, I found away around that but still pain in the a**, especially since my MOBO doesn't have the boot on all errors thingy.
May 10, 200818 yr Author Ok that didn't work. WHAT NOW??? It shows the failed disk as NOT FAILED but the only options it gives me are: 1. REFRESH Bring the array online and start data rebuild. or 2. Restore will initialize the stored array... How can I check the contents of the disk that it said failed? or should I just rebuild the dam drive?
May 10, 200818 yr It is doing exactly what it is supposed to to... don't panic. Choice #1 will use the parity drive in combination to rebuild the contents of the failed drive onto it. This is the choice you should take. While the data is being rebuilt you can use the array and get to your files. Once the data is re-built, the drive will be put back online. Choice #2 will throw away the existing parity data and then attempt to use the currently assigned drives to rebuild parity. If you at all suspect the contents of the failed drive DO NOT USE the "RESTORE" button since if the failed drive cannot be read for any reason (example:the cable is still not plugged in well), you have made recovery of the data on it impossible by throwing away the parity data. So... You want choice #1. (I think there is a checkbox to check before you can start the array and the data re-build onto the "replacement" of the failed drive.) Do NOT use choice #2... it could cause a loss of data if the bad drive (the one marked as bad) has anything wrong with it Joe L.
May 10, 200818 yr Author Thanks, I knew the drive was intact so I went with choice 2 after talking with some other people. That works. Thanks for all the help. It went fine and now everything's working and I have no errors after the most current parity check.
Archived
This topic is now archived and is closed to further replies.