Shadowrunner

Members
  • Posts

    68
  • Joined

  • Last visited

Everything 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. Looks like github has caught up, it;s installed ok now. Thanks for looking into it so quick. SR
  3. Still the same, I'll try it again tomorrow. SR
  4. Tried that, but still getting the bad MD5 error. SR
  5. 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
  6. Skipped that one as I wasn't upgrading from 6.3.5 I'll take a look. SR
  7. Just upgraded from 6.4.0 and now none on my VMs are available and the VMs tab is completely blank. VMs are enabled. Rolled back now and everything is working fine. Pre-rollback diagnostics attached. SR tower-diagnostics-20180209-1454.zip
  8. I'm getting the same, although only since the latest update to the docker. Wasn't a problem before that. SR
  9. That looks like it's running much faster, thanks for that. I'll keep an eye on it, strange it's not been an issue before though. Thanks, SR
  10. Full diagnostics attached. Thanks, SR tower-diagnostics-20171030-1334.zip
  11. 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
  12. @johmei I'd accepted at that point that I was going to have to re-upload everything anyway so may have just clicked through, but I don't remember getting any warnings. Sorry SR
  13. I switched over and my full 17TB migrated without having to re-upload anything, I'm not alone in this either. SR
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. FYI - now iNotify is built-in to 6.3, the plugin no longer detects it. SR
  20. I have Plex set to "make my CPU hurt" and it still only peaks at around 70C, and that's with passive cooling. 95C is way hotter than I'd be comfortable with, I'd check the CPU cooler asap, and try to improve the airflow through the case as much as possible too. SR
  21. What makes you say that? I've backed up nearly 15TB to-date with no problems at all. SR
  22. Looks like you got lucky, Amazon UK cancelled my order SR