March 31, 201214 yr Loaded 4 * 2TB disks with data and then added a parity drive. During initial parity build i got 15792 sync errors (corrected) displayed in Unmenu. System is HP N40L microserver, 4*2TB + 2TB parity, unraid 5.0 r14 Is this reasonable or should i be concerned. It seems all of the errors came from 1 disk and below is that drives smart output - does this seem ok (smart says passed) or should i be convcerned? I am just moving some data around now with the parity showing green ball and will then run another parity check to see if thigs improve. Just looking for drive insight and to know what i should be expecting or worried about. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 1882 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 068 068 025 Pre-fail Always - 9906 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 67 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 124 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 28 181 Program_Fail_Cnt_Total 0x0022 252 252 000 Old_age Always - 0 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 2 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 28 (Min/Max 18/32) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 098 098 000 Old_age Always - 303 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 318 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 67
March 31, 201214 yr Looks like your drive has had a bit of a rough life (dropped twice): 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 2 There are 303 bad sectors pending re-allocation: 197 Current_Pending_Sector 0x0032 098 098 000 Old_age Always - 303 If the drive is still in warranty, I would RMA it
March 31, 201214 yr Author This is not going so well ..... After first parity build with the sync errors above i moved some files around with the parity disk in place and then set off another parity check (no correct) this came to a grinding halt at some point when the rate went down to less than 30kbs, !!! The whole system became unresponsive to the web gui so i did a restart. Now it is going through another parity check, just hope this one does better To try to help out i have attached a syslog from yesterday when i was sorting things out, the one from today when it froze up and in case it helps the smart output for all 5 disks in the hope someone can nail the problem Parity disk SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 130515839 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 76 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 930955 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 227 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 67 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 098 000 Old_age Always - 60130459665 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 066 049 045 Old_age Always - 34 (Min/Max 32/34) 194 Temperature_Celsius 0x0022 034 051 000 Old_age Always - 34 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 053 032 000 Old_age Always - 130515839 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 89421219103049 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3283091807 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3807020046 Data 1 - this could be the one with some issues but it pre cleared nop problem and still says ok in smart health? SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 4509 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 068 068 025 Pre-fail Always - 9723 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 76 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 128 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 29 181 Program_Fail_Cnt_Total 0x0022 252 252 000 Old_age Always - 0 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 2 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 30 (Min/Max 18/32) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 097 097 000 Old_age Always - 379 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 318 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 76 Data 2 SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 198344800 3 Spin_Up_Time 0x0003 095 082 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 506 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 3731670 9 Power_On_Hours 0x0032 089 088 000 Old_age Always - 9921 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 50 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 067 057 045 Old_age Always - 33 (Min/Max 31/33) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 24 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 506 194 Temperature_Celsius 0x0022 033 043 000 Old_age Always - 33 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 034 006 000 Old_age Always - 198344800 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 278992485615179 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2013618352 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2256376783 Data 3 SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 1 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10074 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 88 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 329 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 66 181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 7455 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 107 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 30 (Min/Max 20/47) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 107 Data 4 SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 108 099 006 Pre-fail Always - 15592720 3 Spin_Up_Time 0x0003 094 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 64 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 1844253 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 259 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 49 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 097 097 000 Old_age Always - 3 190 Airflow_Temperature_Cel 0x0022 065 049 045 Old_age Always - 35 (Min/Max 33/35) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 46 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 65 194 Temperature_Celsius 0x0022 035 051 000 Old_age Always - 35 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 037 008 000 Old_age Always - 15592720 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 154816391151875 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3723615705 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3169964417 syslog-2012-03-31.zip
March 31, 201214 yr Author And i am sure its supposed to be going quicker than this ! Total Size 1,953,514,552 KB Current 295,533,976 (15.1%) Speed 63 KB/sec Finish 431855 minutes Sync Errors 1 (corrected) And everything is very unresposive to the gui for refresh, and the number of errors seems to be going up and up (snipet from currently building syslog below to go with previouse syslogs - no better still i have attached it as its so full of red lines in Unmenu its worrying me now Also a note on above disk info - disk 3 seems to have 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 107 Whick would make it seems like its been in a war, but its the same as 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 107 So is that just reading wrong, coincidence? When i built my HP n40L and loaded in my disks and moved all of my data i thought this was a great solution - now i have tried to add paraty to try to ensure a degree of safety it all seems to be going wrong !! is this to be expected, are there things i can do - should i be worried? and will it get better ........ :-( :-( :-( Thanks in advance for any support syslog_updated-2012-03-31.zip
March 31, 201214 yr Author And now some of the drives have spun down as they have been idle for more than 30 mins and an error has appeared in windows as the drives are no longer visible to windows - how can they be idle during a parity check as i though this was a pretty full on task ? ........
April 1, 201214 yr Author Update: My main page showed disk 1 as a red ball ..... I have been trying to move all of the data off this disk by mapping the disks in windows explorer and moving stuff from disk 1 to disk 4 as this has almost enough space - but i am not sure now if i am doing the right thing in moving stuff around and off the failed drive. My parity drive is still showing green but to be honest with all the initial errors detailed above i do not know if it is showing green becuase its fine or if i can really trust it > if it shows green is this 100% sure i have a good parity disk or not? So i am going to stop doing anything else as i do nopt know if i am digging myself into a bigger hole. The data on the failed disk is not stuff i can get back and so i need to be able to save it. I do not know if moving it from the disk to another disk is a good or bad idea. I have tried to read everything i can before asking for help but now i am out of my depth. I do not want to use the "trust my array" procedure as i dont !! I read that you can stop the array, unasign the bad disk, start the array, stop it again, assign the disk back (or a new one which is on order ...) and the drive will be rebuilt using the parity information 1. if the green parity disk really is ok 2. if my moving things around has not screwed things up. A step by step of what to do and why would be much appreciated by those here who know far more than i do. Loading the disks with data was fine, this step to add parity has been a nightmare and i do not even know if it is a bad disk or not .... I ran a short smart test on the pad drive and it came out with no changes to the info above and still said passed Adding the current system log before i power down so that everything is captured and i hope it helps as now it just looks like a nighmare to me :'( syslog-2012-04-01.zip
April 1, 201214 yr Author Syslog for restart of server after soft power down, remove drive, check and reseat etc just to check everything is coming up ok syslog-2012-03-31reboot.zip
April 2, 201214 yr Apologies for the slow response - have been away from my PC this weekend. Sorry unraid is giving you such grief. It sounds like you moved data to the array without parity enabled... for reference, although faster it is much riskier and you put yourself at risk (as you are seeing). As you are no doubt aware, you're disk 1 is failing. In the second set of SMART reports, you can see the currently pending has increased by nearly 100 sectors. Please read this wiki to get a better understanding of the situation. This would be my advice to you if the data on the disk is important and worth a couple hundred bucks. Firstly print out (or write down) the configuration of your array (which HDDs are in which slots), then shut down your unraid array - honestly I don't know if your moving files around is doing more harm, but it certainly isn't doing more good! Pull out the failing drive (carefully!) Get yourself a USB 1 or 2 TB HDD from Amazon (depending on the amount of data on the drive - like this and a SATA-USB adaptor (like this), and plug both into your computer. Then move the data from failing to new hard disk. You've then saved the data from that disk, so if it finally dies you've got no data loss from that disk. Now - do not turn the unraid server back on until you've got your replacement drive installed (sounds like it's on order). Once it's installed, run a preclear on it, but don't start the array. Once it clears successfully, then follow these instructions to replace the drive you removed. You'll note there is no stop-start-stop-start as you suggest in your posting. Unraid will attempt to rebuild the data on the drive using parity. This may or may not work depending on whether the failing drive corrupted parity, but in any case you also have the back-up on the USB drive should it fail. Hope this is helpful - the most important thing with these issues is to go slowly and don't click without understanding what you are doing.
April 2, 201214 yr Author Christuf - Many thanks for the reply. I am away on business for a week now (currently on stop over in Dubai airport) but it does give me time to stop and think about what my steps need to be. You are right about a new disk being on order so that should be at home when i get back next weekend. I will then move all of the data on Disk 1 of the array all together, i have a NAS which i think still has enough space and a spare 1.5TB drive i can throw into a quick change dock which should be enough - so step 1 is to get all the data on disk 1 somewhere safe - which currently is not my unraid box ! And yes i was loading data on so it would be quicker than with parity but also i already had full disks and could not buy a complete new set so my process was buy 1 new one, move data from 1 onto new, perclear 1 and add to array, move data from 2 onto 1 and so on until i was left with the last disk to add as parity > seemed to be a good plan until the final step turned out like this I will read through all of the posts you have indicated so i know the steps needed and come back if i have some open questions so that by the time i get home i have a step by step "how to ...." Couple of questions now for clarification: 1. You mean do the data removal from the disk outside of the array / server? 2. If i remove the suspect disk and put it into a normal caddy will a windows 7 machine be able to see it or is it not formatted in a way windows will be happy with or is there something that needs to be done so that it will simply be picked up as a portable drive 3. I cannot be certain but i think when i start the server the array starts automaticaly - i assume this will not happen as there will be a disk missing rather than just disable by the array. Just checking as would not like it to start on its own 4. Once this disk is out is there some test or process i should go through for the drive to try to fix itself and to remap the bad sectors or is it just too much risk and just get rid of it or try to get a replacement (it is still under seagate warranty - i checked the numbers on the seagate web site) From the other info does everything else look ok and is it just that i have this failing disk (which by the way seemed perfectly fine when i was using it outside of the array and was fine in pre clearing) Again, many thanks. Sounds like i have some work but if the drive holds out a little longer then its just effort and not the disaster it was starting to look like at the end of yesterday
April 2, 201214 yr Christuf - Many thanks for the reply. You're welcome 1. You mean do the data removal from the disk outside of the array / server? Not sure what statement you're referring to here 2. If i remove the suspect disk and put it into a normal caddy will a windows 7 machine be able to see it or is it not formatted in a way windows will be happy with or is there something that needs to be done so that it will simply be picked up as a portable drive Yes - the data is readable by a windows machine - refer here 3. I cannot be certain but i think when i start the server the array starts automaticaly - i assume this will not happen as there will be a disk missing rather than just disable by the array. Just checking as would not like it to start on its own Right - I'm 99.9999% certain it will not autostart when there's a change in the config. I have my array set to non-autostart so can't say I've ever tried it. 4. Once this disk is out is there some test or process i should go through for the drive to try to fix itself and to remap the bad sectors or is it just too much risk and just get rid of it or try to get a replacement (it is still under seagate warranty - i checked the numbers on the seagate web site) Once you've got the data off, new drive settled in and you're happy, then get it replaced through Seagate's RMA. Once a drive has proven itself untrustworth, it's got to go! An absolute no-brainer as it's under warranty - well worth the $5 shipping.
April 2, 201214 yr Author Thanks for all of the info. My comment on moving data outside of server meant I remove the disk and sort the data on a different machine, sorry if that was confusing. The tip about using ubuntu is a good one from Joe.l as I happen to have a disc as I put it on someone elses old machine. If I use this to move the files onto an external drive will I need it again to move them to the server, just want to be clear otherwise I will stick with windows and what I know. While that is going on I will preclear new drive (without starting the array) and then follow the other link you gave to put new disk in array. I gather from your first comment that at this point it will do a rebuild, or at least attempt one. After that I will do a second test - want to be safe this time. When all is good I will add any missing files from the saved data - with parity in place After that disk is going back ! I cannot get to server this week but will read up some more and write myself a plan of attack. I will let you and everyone else know how this goes Thanks again
April 3, 201214 yr All good... just be careful, take it step-by-step and don't click on anything you don't understand! Windows vs. Unbuntu - you're preference. Never done a reiserfs driver install on a windows machine, so don't know how difficult it is. Unbuntu is pretty straightforward to use. Good luck and keep us posted on the results!
April 9, 201214 yr Author Hi, just an update Got new disk, precleared ok and now installed and parity is rebuilding - will feedback just what i have in terms of data when this is completed. I have the old disk in a dock and am using YAReG to copy the data over to a spare 1.5TB drive - its slow but its working. Looks like this will give me my data as a safety if something is not in the right place one parity is rebuilt I will then want to give the disk a good work out so can i connect it by USB to my HP N40L server and use the preclear script to clear the dirve and see if i get any errors and to update the smart software as i would like to use the disk if it seems ok. Will a preclear checking every sector give me an idea if the drive is ok given it seemed to fail for a write failure? Is this the easiest check? should i run multi preclears (and how do i run 2 or 3 cycles other than manual?) Interesting that the array started on reboot even with a disk removed? Where would i set the array to never autostart after a restart as i would sooner have control over this as a safety feature. More updates will follow - but things are looking better right now :-)
April 10, 201214 yr Got new disk, precleared ok and now installed and parity is rebuilding - will feedback just what i have in terms of data when this is completed. Great - hope that parity rebuilds everything without a problem! I will then want to give the disk a good work out so can i connect it by USB to my HP N40L server and use the preclear script to clear the dirve and see if i get any errors and to update the smart software as i would like to use the disk if it seems ok. Will a preclear checking every sector give me an idea if the drive is ok given it seemed to fail for a write failure? Is this the easiest check? should i run multi preclears (and how do i run 2 or 3 cycles other than manual?) Please RMA this drive... please. We know the drive is going bad from the previous SMART reports - running it through preclear may put its life to an end once and for all... and maybe it won't. In either case, it is beyond foolhardy to trust a known-bad drive with data. Interesting that the array started on reboot even with a disk removed? Where would i set the array to never autostart after a restart as i would sooner have control over this as a safety feature. Go to the settings page > Disk settings > Enable auto start > Switch to "No"
April 10, 201214 yr Author Thanks Disk is going back, going to do the RMA today, as you say no good trusting a suspect drive The array is set to "no", dont know why it started but all seems ok now and it has rebuild the drive data correctly. Will run iot through another parity check later after i have moved some more stuff onto the drives. Only thing i am suffering from now is target becomes unavailable or not founf in teracopy after a while and then refuses to work properly, not the end of the worlkd but a pain. Will search the forums for some guidance on this
April 11, 201214 yr Author Going to update this to solved. Rebuild of data onto new disk completed OK I move more data onto the array (only problem is teracopy stopping after a while with permissions but will look for a solution elsewhere for that) Ran a second parity check and this went through with no errors, so all seems to be back in place RMA created for the dodgy disk and will send that back to Seagate at the weekend Thanks for all the support :-) it is said often but everyones input, especialy those really in the know is much appreciated by us less capable people
April 11, 201214 yr Excellent - you're very welcome. Glad you had a good outcome. Sorry - no experience with Terracopy or issues in moving data to the array, so perhaps you can find a topic on the board or I'm sure someone else can help you (create a new thread as people won't look at a "solved" thread now). One thing that I do which I feel is worthwhile is a monthly sweep through all the SMART reports for the drives in my array. You just need to understand what you're looking for (mainly the various reallocated sector statistics), but this can save your bacon before you have a problem. I found my parity drive was starting to go bad, and immediately RMA'd it before I had any problems with my array. A stitch in time saves nine!
April 17, 201214 yr Author Quick update for completeness. Dodgy drive RMA'd and new one dispatched after only 4 days so new 2TB drive will be waiting for me when i get home :-) Not sure now if i will use this to add another drive into the array or put it into my old readynas duo, set it to JBOD and use it as backup storage for the most important 4TB of my data (and keep it a a relatives house between updates) - just on the is it pretty easy to set this up at someones house and connect into it securly to do a back up over the internet and then get them to turn it off? I had problems with the replacement disk and had to do a tree rebuild of the new drive due to an error but that is now fixed and after a greem parity check i added some more date and then did another parity check and all still green, no errors This has been a bit of a painful and steep learning process but we got there in the end - maily thanks to a few good and knowledagble people on here who are willing to help those of us who know less and need help
Archived
This topic is now archived and is closed to further replies.