August 4, 201213 yr thanks so much - array is back up. not sure what's been lost yet, but my photo's seem to be ok which is the main thing! Now that you have access to your photos, read this post: http://lime-technology.com/forum/index.php?topic=5072.msg47122#msg47122 Then make a backup copy of your precious files. Store them in your safe-deposit box, a network storage cloud, or somewhere OTHER than in your home. The backups can be on a portable hard disk, or on DVDs, or CDs. Just anything that will hold the volume of data involved. Probably easiest is a 3TB portable hard disk, currently selling for about $115 to$150 at Costco or equivalent)
August 4, 201213 yr It's currently running parity, and even though I haven't yet replaced that drive, it's not yet reporting any errors. I'll let it run for now. The errors that are showing in the smart report you posted for the parity drive show this as the cause of your errors: 199 UDMA_CRC_Error_Count 0x003e 182 182 000 Old_age Always - 6 These are usually indications of noise picked up by the data cable to the drive. UDMA CRC errors are usually caused by either a poor connection, or connector poorly seated, or the cable too close to others, and poorly shielded, picking up noise induced from nearby conductors. If you've re-seated the connectors to the parity disk, and the errors stop, then you've fixed it. If you have tie-wrapped all the cables to make it really neat looking, you've introduced the close coupling of cables that might cause the errors. (The solution, be less OCD and get some distance between cables... or... get shielded cables and see if they help) Definitely DO NOT run the data cables tied to power cables. With any luck, the parity calc should complete without errors. When done, perform a manual parity check to VERIFY you can read what you just wrote to the parity drive.
August 4, 201213 yr Author Thanks Joe (and everyone else) for your help so far. Very interesting advice regarding the SMART error and effects of cabling! I had done quite a bit of cable management, so have loosened these off. Parity is still running, and is now up to 80% and 4.7M writes with no errors so fingers crossed. EDIT: parity is now complete, with no errors!
August 5, 201213 yr Author Joe, I've re-read that post you linked me to, but I'm still not sure if unraid_partition_disk.sh can fix HPA, or if it is to re-write the MBR after removing HPA with hdparm. Once parity is complete should I replace the current disk1 with the old disk1, or add it as a new disk? Expect either way that I then need to wait for parity to re-calculate. From there I run hdparm to remove HPA, and then unraid_partition_disk.sh to fix MBR? Since it will then be a new disk, will it want to be formatted/precleared when I start the array (before rebuild can occur)?
August 5, 201213 yr Joe, I've re-read that post you linked me to, but I'm still not sure if unraid_partition_disk.sh can fix HPA, or if it is to re-write the MBR after removing HPA with hdparm.It cannot remove the HPA. It can only fix the partition once the HPA is removed to be identical to how unRAID would have set the partition. (and in that way, unRAID will recognize it as one it created instead of one it must clear and re-format.) you must use hdparm to remove the HPA (or some other equivalent utility if hdparm does not work through your disk controller) Once parity is complete should I replace the current disk1 with the old disk1, or add it as a new disk? I had thought you had already put the original disk 1 in place and removed the HPA on it? Please clairify? Expect either way that I then need to wait for parity to re-calculate. From there I run hdparm to remove HPA, and then unraid_partition_disk.sh to fix MBR? NO, not once you have parity established. To fix the HPA once parity is established you must un-assign the drive, start the array with it un-assigned, remove the HPA, then stop the array once more and re-assign the drive. When you next re-start it, it will be re-constructed with the old contents. Since it will then be a new disk, will it want to be formatted/precleared when I start the array (before rebuild can occur)? No, it will be a replacement of the existing disk. (unless you have already dealt with it, and it is now the spare, and you are adding an ADDITIONAL disk to the parity protected array, not replacing an existing one.)
August 5, 201213 yr Author No, I have not put the original disk1 back in yet, and it will still have HPA (HPA has so far only been removed from disk2). I expect it (original disk1) also has data on it that would otherwise be lost, since parity was an issue. Should I REPLACE the current disk1 with the original disk1, or should I leave the current disk1 in place and ADD the original disk1 to the current array (as disk9)?
August 5, 201213 yr No, I have not put the original disk1 back in yet, and it will still have HPA (HPA has so far only been removed from disk2). I expect it (original disk1) also has data on it that would otherwise be lost, since parity was an issue. Should I REPLACE the current disk1 with the original disk1, or should I leave the current disk1 in place and ADD the original disk1 to the current array (as disk9)? The screen shot shows disk1 as green. What is on disk1 (8730)?
August 5, 201213 yr Author Virtually nothing as I have been trying not to write to the array. It's the new drive I swapped in to replace the old disk1 (as a means to get around HPA). The old disk1 was healthy when I pulled it. I was having trouble using hdparm and HDAT2 to remove HPA so thought I could swap it out and fix it in another PC, then rotate it back in (to replace one of the other drives with HPA).
August 5, 201213 yr Virtually nothing as I have been trying not to write to the array. It's the new drive I swapped in to replace the old disk1 (as a means to get around HPA). The old disk1 was healthy when I pulled it. I was having trouble using hdparm and HDAT2 to remove HPA so thought I could swap it out and fix it in another PC, then rotate it back in (to replace one of the other drives with HPA). Does 8730 contain the correct disk1 content?
August 6, 201213 yr Done, and parity rebuilding again... Make ABSOLUTELY certain you are writing to parity, and not writing to the new disk1. If you see writing to disk1, and reading from all the others, stop the process immediately. (if not sooner :'() dgaschk did not instruct you to set a new disk configuration after replacing disk 1, and if you did not you are now re-constructing the new-empty disk 1 onto the old disk1. (effectively erasing it) Odds are you are OK, as the older disk was slightly smaller because of the HPA, and odds are unRAID would not have let you use it as a replacement for the newer slightly larger disk, but not knowing what you did to it, I'm just being cautious. That missing step of setting a new disk configuration could cost you the data on that disk1, with no ability to recover. Joe L.
August 7, 201213 yr Author Thankyou, yes - all good. Parity complete with no errors. Should I attempt hdparm on one of the other HPA affected drives now?
Archived
This topic is now archived and is closed to further replies.