Shadowrunner

Members
  • Posts

    68
  • Joined

  • Last visited

Posts posted by Shadowrunner

  1. Just upgraded from 6.11.5 to 6.12.1 with no issues.

     

    No so much a bug as an irritant, but since the update, everything I upload to the array has the executable bit set. It's easy enough to remove with chmod of course, but it's a pain to have to do this for everything. Is this normal in the new version or have I missed a setting somewhere?

     

    Thanks,

     

    SR

  2. Just had an update for the Cache Dir plugin appear on the plugins tab (although it's dated from April), it's reporting a bad MD5 when I try and update though and it's killed the plugin. I've tried removing and reinstalling both from Community Applications and manually but get the same error.

     

    Any suggestions?

     

    Thanks,

     

    SR

  3. Hi all,

     

    Recently replaced a 4TB WD Green with an 8TB Seagate, the data rebuild has so far taken 2 days and is 67% done. This seems to be taking far longer than other posts on here suggest it should. Although I didn't use the preclear utility to test the drive, I did run 3 extended tests in Data Lifeguard before swapping the drives. SMART data is as follows (full report from diagnostics attached):

     

    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   081   064   006    Pre-fail  Always       -       136625016
      3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       2
      5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000f   073   060   030    Pre-fail  Always       -       19299397
      9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       103
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       2
    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   099   099   000    Old_age   Always       -       1
    190 Airflow_Temperature_Cel 0x0022   063   062   040    Old_age   Always       -       37 (Min/Max 29/38)
    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       -       6
    193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       74
    194 Temperature_Celsius     0x0022   037   040   000    Old_age   Always       -       37 (0 18 0 0 0)
    195 Hardware_ECC_Recovered  0x001a   081   064   000    Old_age   Always       -       136625016
    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      -       99 (158 44 0)
    241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       10517978030
    242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       15628200165

    SMART Error Log Version: 1
    No Errors Logged

     

    Several of the error attributes look sky-high, but I believe this can be normal for Seagates...

     

    Thanks,

     

    SR

    ST8000AS0022-1WL17Z_Z840QVGA-20171030-1334.txt

  4. 9 hours ago, snowboardjoe said:

    Was starting to review steps needed to migrate to PRO and was so happy to see this thread here. A few questions, though:

     

    1. I'm backing up 11TB and Code42 has already indicated it can't migrate anything over 5TB and will need to perform a full backup from scratch. I assume there is no need for me to migrate any data then? Or do I still need to do copy "/mnt/user/appdata/CrashPlan" to CrashPlanPRO?

     

    2. Long ago I had to modify the code/config to avoid deduplication by CP as it bogged down multi-terabyte backups. Will I need to make that modification again with PRO? I need to find in my notes how I did this long ago. With dedupe turned on my backup never would not have finished as it was too aggressive.

     

    I switched over and my full 17TB migrated without having to re-upload anything, I'm not alone in this either.

     

    SR

  5. I bit the bullet and decided to upgrade to the Crashplan Pro option, I only have 1 device so it was still way cheaper than anywhere else. 

     

    I fully expected to have to re-upload my 17TB but the whole lot migrated over, so I think the 5TB limit isn't totally rigid. Other users have confirmed this happened for them too. I've also checked with Crashplan support that it wasn't just a display error or something, and they have confirmed it's all migrated across.

     

    SR

  6. It did that on me too. CP support told me it was just because the migration hadn't completed yet. I left it overnight and all was fine the next day.

     

    I'd try leaving it for a bit and see if it comes back. If not, or if it's already been a while I'd log a ticket with support. They've been pretty good in the past when I've needed them, even running with an unsupported headless installation.

     

    SR

  7. Just migrated to the Pro version, docker updated ok. 

     

    Also - Having fully expected to re-upload my 17TB, the whole lot migrated over without having to re-upload a single byte. I've confirmed this is correct with Crashplan support as I didn't want any nasty surprises if something had gone wrong.

     

    This might not be the case for everybody, but it looks like the 5TB migration limit isn't that rigid.

     

    SR

    • Upvote 1
  8. Oh well...

     

    No biggy, it is working despite the error and I don't access the settings enough for it to be really annoying.

     

    I know you're not really supporting this anymore, so thanks for looking.

     

    SR

  9. That was quick...

     

    After looking a bit deeper it does appear that the monitor is working, although I get the "iNotify NOT installed" pop-up when accessing the settings, and the monitor status shows as not installed.

     

    SR