February 13, 201610 yr I have never had any issues with Unraid or my server. Always operated correctly, never failed a parity check, nothing. I just upgraded to v6 and now immediately after starting parity sync its telling me that my parity is invalid. What the hell did I do wrong? I read the guide on the wiki step by step and did a flash drive format. All help and suggestions much appreciated. I really hope I haven't lost anything. Thanks, Andrew I am attaching the system log download as I am assuming you gurus can decifer what some of it means. I am an Unraid newb when it comes to this. Like I said Ive never had any issues before. Any and ALL help much appreciated! Andrew tower-syslog-20160213-0151.zip
February 13, 201610 yr Author Here is the download from the Diagnostic tab. Thanks again guys! PS. I've canceled the parity sync until I hear from you guys. I don't know if its writing corrections or not. I didn't see the option to uncheck write correction. tower-diagnostics-20160213-0154.zip
February 13, 201610 yr Community Expert You did not give any details on the exact upgrade process you followed! My suspicion is that you reassigned your disks and thus unRAID currently thinks it does not have a current parity and is therefore going to generate one. In such a case the parity will be indicated as invalid until the first parity sync has completed.
February 13, 201610 yr Community Expert It's normal to show invalid parity during a parity sync. If your parity is OK you can do a new config and check the box "parity is already valid " before starting the array.
February 13, 201610 yr You did not give any details on the exact upgrade process you followed! My suspicion is that you reassigned your disks and thus unRAID currently thinks it does not have a current parity and is therefore going to generate one. In such a case the parity will be indicated as invalid until the first parity sync has completed. I assigned them exactly as they were in v5. Was i not supposed to do that? I formated flash, unzipped v6 onto flash, placed .key file into config folder as well as the other config files listed in the wiki and my shares config folder. I didn't copy anything else. I'm not doing anything fancy with my unit it's just a NAS. Thanks guys. I'll let it run.
February 13, 201610 yr Community Expert You did not give any details on the exact upgrade process you followed! My suspicion is that you reassigned your disks and thus unRAID currently thinks it does not have a current parity and is therefore going to generate one. In such a case the parity will be indicated as invalid until the first parity sync has completed. I assigned them exactly as they were in v5. Was i not supposed to do that? I formated flash, unzipped v6 onto flash, placed .key file into config folder as well as the other config files listed in the wiki and my shares config folder. I didn't copy anything else. I'm not doing anything fancy with my unit it's just a NAS. Thanks guys. I'll let it run. Nothing wrong with that, but if you assigned the drives rather than bringing the existing configuration (in super.dat) forward you will not have a valid parity until unRAID has finished the parity sync. When the parity sync completes it is a good idea to start a parity check to ensure that the parity sync was done without error.
February 13, 201610 yr You did not give any details on the exact upgrade process you followed! My suspicion is that you reassigned your disks and thus unRAID currently thinks it does not have a current parity and is therefore going to generate one. In such a case the parity will be indicated as invalid until the first parity sync has completed. I assigned them exactly as they were in v5. Was i not supposed to do that? I formated flash, unzipped v6 onto flash, placed .key file into config folder as well as the other config files listed in the wiki and my shares config folder. I didn't copy anything else. I'm not doing anything fancy with my unit it's just a NAS. Thanks guys. I'll let it run. Nothing wrong with that, but if you assigned the drives rather than bringing the existing configuration (in super.dat) forward you will not have a valid parity until unRAID has finished the parity sync. When the parity sync completes it is a good idea to start a parity check to ensure that the parity sync was done without error. O you make me feel so much better. Ok thank you. I did not copy the file you started over. I will do what you said run sync then a check. I also have one drive showing a warning but ill get the parity completed first. Thanks!
February 13, 201610 yr Community Expert ... I also have one drive showing a warning but ill get the parity completed first... V6 is much better at telling you about drive problems. Most likely the warning is about an issue you already had but were unaware of on v5. You can get more information by clicking the drive in Main and looking at its attributes. In fact you should do that without waiting for the parity sync to complete and let us know by posting the result.
February 13, 201610 yr Author Ok! Here is the attributes for the disk that is showing me a orange triangle on the dashboard tab. Number 187 is highlighted in yellow. # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 118 099 006 Pre-fail Always Never 174541792 3 Spin up time 0x0003 092 092 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 887 5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 0 7 Seek error rate 0x000f 070 060 030 Pre-fail Always Never 11828431 9 Power on hours 0x0032 066 066 000 Old age Always Never 30088 (3y, 5m, 5d, 16h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 32 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 089 089 000 Old age Always Never 11 188 Command timeout 0x0032 100 100 000 Old age Always Never 0 0 0 189 High fly writes 0x003a 089 089 000 Old age Always Never 11 190 Airflow temperature cel 0x0022 081 058 045 Old age Always Never 19 (0 2 22 17 0) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 11 193 Load cycle count 0x0032 055 055 000 Old age Always Never 91166 194 Temperature celsius 0x0022 019 042 000 Old age Always Never 19 (128 0 0 0 0) 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 2062h+11m+53.584s 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 46156149712796 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 163771859904553 ST3000DM001-9YN166_Z1F0PM60-20160213-1027.txt
February 13, 201610 yr Community Expert According to blackblaze anything above 0 it’s not good news and there’s a much higher probability of failure in the near future, I’ve no personal experience with that attribute, and I’ve seen many here on the forum with higher values, since the disk is 3 yeas old and you don't know how long it's been like that I would monitor value for a few weeks and see it stays stable, also always good to have a spare handy.
February 14, 201610 yr Author According to blackblaze anything above 0 it’s not good news and there’s a much higher probability of failure in the near future, I’ve no personal experience with that attribute, and I’ve seen many here on the forum with higher values, since the disk is 3 yeas old and you don't know how long it's been like that I would monitor value for a few weeks and see it stays stable, also always good to have a spare handy. Ok thanks. Will do. I usually do have a hot 3 pass preclear drive ready but 2 days ago decided to make it a cache drive as I had never previously used a cache. I need to get another hot spare. Thanks!
Archived
This topic is now archived and is closed to further replies.