-
Posts
128 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Moussa
-
-
Looks like the Crashplan client updated to 4.7.0 for me. But now when the container restarts the Crashplan client starts a block synchronization check which can take a whole day in my case. Is this an issue with the Crashplan client or the container?
-
The update fixed the black screen issue for me, thanks gfjardim! Great work.
-
I've updated the container with the recent update and now I only get a black screen when using the web VNC viewer. Already tried forcing an update of the container and restarting it, any other ideas?
-
There are about 29 pages to this. I didn't read them all so sorry if it was already asked. My main reason for going with btrfs was for the hashing protection against data rot, even though I've heard the recovery tools for it aren't as mature as XFS. So how does using this with XFS compare to using btrfs in UnRAID?
This plugin only detects bit corruption, it can't repair it. You would still need backups.
-
Thanks bonienl for a fantastic plugin. I know you've made export a manual task now but is there any reason why we can't have an option for it to run once a day or so automatically? I like having an upto date listing of all the files in my array but I don't want to have to manually do it every night. Unless there's a way to add the task to a cronjob?
-
I may be being stupid here but I've read through the entire thread and the help command for bunker but couldn't find the answer. Can I simply just calculate the checksums of the file and export them to a text file WITHOUT writing them to the file extended attributes?
No that is not possible. The export function reads the values stored in the extended attributes and writes them to a file.
I see, thanks for the answer!
-
I may be being stupid here but I've read through the entire thread and the help command for bunker but couldn't find the answer. Can I simply just calculate the checksums of the file and export them to a text file WITHOUT writing them to the file extended attributes?
-
Drive looks great!
Awesome, thanks!
-
Hi guys. Just got myself an 8TB Seagate Archive drive and after a long preclear (136 hours!) I just wanted to double check my results were good before I stuck it in as my new parity drive. I think these look perfectly fine?
========================================================================1.15b == invoked as: ./preclear_bjp.sh -f -A -c 3 /dev/sdd == ST8000AS0002-1NA17Z Z8405JVN == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 20:11:47 (110 MB/s) == Last Cycle's Zeroing time : 16:58:37 (130 MB/s) == Last Cycle's Post Read Time : 21:38:49 (102 MB/s) == Last Cycle's Total Time : 38:42:39 == == Total Elapsed Time 135:57:31 == == Disk Start Temperature: 28C == == Current Disk Temperature: 36C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 116 100 6 ok 103093464 Seek_Error_Rate = 72 100 30 ok 8628490947 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 64 72 45 near_thresh 36 Temperature_Celsius = 36 28 0 ok 36 Hardware_ECC_Recovered = 116 100 0 ok 103093464 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
-
Hmmm working for me. Which is to say... It works... So what is different?
can you walk us through how to start it?
Settings -> Folder Caching -> Status:Stopped
Cant seem to see the start button either
Change the 'Folder caching function' setting to Enabled and then the Apply button at the bottom.
-
========================================================================1.15 == invoked as: ./preclear_disk.sh -A -c 3 /dev/sdd == ST3000DM001-1CH166 Z1F51MFZ == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 6:42:28 (124 MB/s) == Last Cycle's Zeroing time : 5:00:57 (166 MB/s) == Last Cycle's Post Read Time : 12:06:13 (68 MB/s) == Last Cycle's Total Time : 17:08:10 == == Total Elapsed Time 58:23:11 == == Disk Start Temperature: 31C == == Current Disk Temperature: 38C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 100 6 ok 161579360 Seek_Error_Rate = 60 100 30 ok 1116436 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 98 100 0 ok 2 Airflow_Temperature_Cel = 62 69 45 near_thresh 38 Temperature_Celsius = 38 31 0 ok 38 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
Just to confirm, these results look good right?
-
I added a modified version, which should work on v6b6. Please give it a try and report problems. For sql support maria db should be supported. The plugin is still in old unraid plugin design structure.
Is this for b6 specifically or would it work for any of the earlier betas? I'm still on b3 as I'm waiting for Dynamix to support b4+.
-
It will be updated. But not at the moment. V6 is still beta and a lot of things are in the flux. I'll wait until final before I upgrade my server. And only then the plugin will follow. Sorry.
No problem, that makes perfect sense. Thanks!
-
Will this plugin be updated for unRAID v6 or does it by any chance work anyway?
-
Your disk is perfectly fine.Hi guys. This is my first time building an unRAID server and I just wanted to make sure that I'm correct in thinking that this preclear report is A-OK. The only things that have me worried are the Spin_Retry_Count and the End-to-End_Error values because they seem to be near the thresholds. Thanks for any advice
Thanks for any advice.
Some initial values are put purposely close to their affiliated failure threshold by the manufacturer.
Example: Even a few spin-up-failures (subsequently requiring a re-try) would indicate a mechanical issue with the drive. Therefore, the failure threshold is very close to the starting value for that parameter on that disk.
That makes sense. Got the drive in my array now, all working fine. Thanks.
-
Hi guys. This is my first time building an unRAID server and I just wanted to make sure that I'm correct in thinking that this preclear report is A-OK. The only things that have me worried are the Spin_Retry_Count and the End-to-End_Error values because they seem to be near the thresholds.
The important number for those is the VALUE, which for both is 100, as in 100% perfect, can't be any more perfect than that. It's not that they are close to the threshold, but that the manufacturer has factory set the thresholds to start so close to 100, who knows why. Your SMART reports for that drive appear to be perfect, nothing to worry about.
That's good to hear, thanks for the help!
-
Hi guys. This is my first time building an unRAID server and I just wanted to make sure that I'm correct in thinking that this preclear report is A-OK. The only things that have me worried are the Spin_Retry_Count and the End-to-End_Error values because they seem to be near the thresholds. Thanks for any advice
Thanks for any advice.
preclear_start
Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: W1F3J6S6 LU WWN Device Id: 5 000c50 06a5ae556 Firmware Version: CC27 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Feb 14 03:30:24 2014 GMT ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 105) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 327) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. 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 - 194593040 3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 12 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 419986 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 44 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 12 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 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 071 067 045 Old_age Always - 29 (Min/Max 17/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 - 10 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 45 194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 16 0 0 0) 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 - 41h+39m+16.926s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 17581599648 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 27037241817 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
preclear_finish
Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: W1F3J6S6 LU WWN Device Id: 5 000c50 06a5ae556 Firmware Version: CC27 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Feb 15 19:05:38 2014 GMT ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 105) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 327) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. 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 099 006 Pre-fail Always - 125433192 3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 12 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 792073 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 84 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 12 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 0 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 070 067 045 Old_age Always - 30 (Min/Max 17/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 - 10 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 46 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 16 0 0 0) 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 - 81h+09m+32.314s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 29302666080 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 56755436299 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
preclear_rpt
========================================================================1.14 == invoked as: ./preclear_disk.sh -A -M 3 -c 2 /dev/sdb == ST3000DM001-1CH166 W1F3J6S6 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 2 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 5:49:09 (143 MB/s) == Last Cycle's Zeroing time : 5:08:45 (161 MB/s) == Last Cycle's Post Read Time : 11:44:01 (71 MB/s) == Last Cycle's Total Time : 16:53:45 == == Total Elapsed Time 39:35:14 == == Disk Start Temperature: 29C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 118 6 ok 125433192 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 70 71 45 near_thresh 30 Temperature_Celsius = 30 29 0 ok 30 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
[Support] Djoss - CrashPlan PRO (aka CrashPlan for Small Business)
in Docker Containers
Posted
Hi there. I'm having an issue with my Crashplan backup since updating from 6.3.5 to 6.4.1 (not sure if it's related at all, but just adding a data point). The app seems to want to backup my entire backup set again, claiming only a few GBs are completed. I've tried clearing out the cache folder and even changing the `<dataDeDupAutoMaxFileSizeForWan>` value back to 0 in my.service.xml. After a (day and a half long) file scan it seems to right itself and continues uploading only unbacked up files but then the next time it does a 'Full filesystem scan' it falls over again and goes back to saying everything needs to be uploaded. Anyone with a similar issue?