bobekdj

WARNING TO ALL USING PIA THE DEFAULT FOR THE CONTAINER IS NO LONGER CORRECT, IT IS "NL.PRIVATEINTERNETACCESS.COM" YOU NEED TO CHANGE NL to WWW Took me an hour and a half to troubleshoot and figure out by luck. Hope this helps someone, and maybe we can get the template default changed as well

I understand what your saying, and agree completely... if it isnt broke then dont fix (upgrade) it. The general information is not really applicable in this case. I had to upgrade my RAID controller cards to give me more ports for drives, also because the previous RocketRaid cards were not compatible with the new 6.3 OS, and I wanted to be able to have dual parity. I upgraded and everything is was fine, however lost my cache drives in the process and put new ones on there (no big deal, just pull the apps and sync my old appdata, should work no problem). However I think the CP is now a newer version because thats what was automatically downloaded... hence the problem at hand.

It is not the auto-start... mine is crashing and then re-opening (so mine continually runs), however it loops and spends most of it's time scanning my directories and minimal time uploading to CP. I have upgraded the ram to 5GB to see if that helps (I have 32 on my machine so can spare the space). It actually was working better, but still eventually crashes.

Agreed I am having this issue, I wonder why all of a sudden this is a problem... Need some serious help here before I loose my 3.5TB backed up to the cloud!!! (please and thanks)

UPDATE: May actually be a RAM issue causing it to crash since my backup was large... Increased to 5GB of ram, and we will see if it works. Need some help, my crashplan keeps crashing while trying to backup. I lost my cache drive and subsequently was not backing up my appdata folder (shame on me) since then i made a new docker, used community app to redownload CP, and then set it up from scratch again, choosing to restore from a previous PC option to sync the data. not sure what any of this means, but have been getting this similar error over and over any help is appreciated. Think the key is "ERROR: openbox-xdg-autostart requires PyXDG to be installed" Xvnc TigerVNC 1.7.0 - built Sep 8 2016 10:39:22 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11400000, The X.Org Foundation Initializing built-in extension VNC-EXTENSION Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension GLX Tue Mar 7 15:48:58 2017 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 4239 vncext: created VNC server for screen 0 Warning: could not find self.pem Using local websockify at /opt/novnc/utils/websockify/run Starting webserver and WebSockets proxy on port 4280 ERROR: openbox-xdg-autostart requires PyXDG to be installed WebSocket server settings: - Listen on :4280 - Flash security policy server - Web server. Web root: /opt/novnc - No SSL/TLS support (no cert file) - proxying from :4280 to localhost:4239 Mar 7 15:48:58 unRAID syslog-ng[31]: syslog-ng starting up; version='3.5.6' Navigate to this URL: http://unRAID:4280/vnc.html?host=unRAID&port=4280 Press Ctrl-C to exit

I would like to have VT-d enabled... is there any way to properly fix the cards so my drives work? (I am running 3 because they are left over from another system... I dont want to buy new card/s for 6.2 update)... Trying to downgrade now until a fix is reported working sadly.

Bump

Thanks. https://lime-technology.com/forum/index.php?topic=44989.msg430393#msg430393

I can answer this one, only MD5 checksums made by this plugin than can be verified by CORZ. Have you been able to try to BLAKE2 and it failed?

Finally able to read through the entire feed, and was unable to find an answer to the following questions (sorry for a lot of them, tried to split up to be easy to answer). Maybe the summary of *bitrot, *best method, and *compatability could be added to the sticky at the top of the thread to inform new users these questions? 3 different hashing methods, MD5, SHA2, BLAKE2... what are the pros and cons of each? From what I have gathered, related to this plugin it essentially comes down to speed of hash. Any of the options seem to be more than adequate at detecting bitrot? And as for universal compatibility... why does it matter since tools like corz and others can only tell you if your files are corrupt anyway and not do anything to help restore. In summary, it appears if your CPU supports it, BLAKE2 would be be the best option most recommend? Also there was some mention of using CORZ to verify the hashes produced... did anyone ever figure out if the BLAKE2 outputs were similar, or if they still use different variants (s)? Thanks for a great plugin and support!

Not sure if it will work for you, but I use a plugin called "unassigned devices" It allows you to see any usb drive connected (thumb drive, external hdd, etc), and lets you mount them. Depending on the type of failure of your external you may or may not be able to use it. You can also install a preclear web gui to preclear devices and it plays nice with unassigned devices from the main screen. (please note preclearing the device WILL DESTROY ALL OF YOUR DATA! this was mentioned because at some point it may be worth preclearing the drive to check it for stability before reusing it)

What do you have stored on the test server?

Hey all, From my research, it seems that the following two methods are preferred based on the forums, if anyone has any experience with either and would like to comment please do. Main data array filesystem: XFS Checksum/monitor for bitrot: Dynamix File Integrity Plugin Any other recommendations? I know BTRFS is suppose to have some of these features built in, but for some reason does not seem stable/to play nice with current versions of unraid? Thanks

Ok, I may try to just let it run a few days and see what happens. I am not as familiar how to detect errors, but know some of the old drives were questionable in a previous unRAID server. Was just trying to keep as many old ones as i could. Thanks for the info!

THANK YOU THIS IS A GOOD SUMMARY!!

I pre-cleared an older drive I had, I am struggling to determine what info is important to consider, and what flags mean the drive should just be thrown away. Below are the outputs from preclear script, as well as the unRAID GUI SMART testing (downloaded SMART Report). Any resources or explanation is greatly appreciated (g.com and yt.com were not help with smart info interpretation). Preclear: ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdd = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 35C, Elapsed Time: 23:30:10 ========================================================================1.15 == ST2000DL003-9VT166 5YD22M1T == Disk /dev/sdd has been successfully precleared == with a starting sector of 64 ============================================================================ ** 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 120 6 ok 105815952 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Reported_Uncorrect = 1 1 0 near_thresh 145 Airflow_Temperature_Cel = 65 68 45 near_thresh 35 Temperature_Celsius = 35 32 0 ok 35 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. root@unRAID:/usr/local/emhttp# unRAID GUI: smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.17-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda Green (AF) Device Model: ST2000DL003-9VT166 Serial Number: 5YD22M1T LU WWN Device Id: 5 000c50 032d1cc1f Firmware Version: CC32 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5900 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Mar 3 08:49:53 2016 PST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: ( 612) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. 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: ( 339) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30b7) SCT Status supported. SCT Feature Control supported. SCT Data Table 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 116 097 006 Pre-fail Always - 105821192 3 Spin_Up_Time 0x0003 095 084 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1093 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 11455524 9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 14277 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 207 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 145 188 Command_Timeout 0x0032 100 098 000 Old_age Always - 15 189 High_Fly_Writes 0x003a 097 097 000 Old_age Always - 3 190 Airflow_Temperature_Cel 0x0022 066 057 045 Old_age Always - 34 (Min/Max 31/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 - 402 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1114 194 Temperature_Celsius 0x0022 034 043 000 Old_age Always - 34 (0 16 0 0 0) 195 Hardware_ECC_Recovered 0x001a 020 003 000 Old_age Always - 105821192 197 Current_Pending_Sector 0x0012 100 097 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 097 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 10 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 195670120077502 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2907446593 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2917276995 SMART Error Log Version: 1 ATA Error Count: 94 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 94 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 98 4b f2 02 Error: UNC at LBA = 0x02f24b98 = 49433496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 98 4b f2 42 00 00:18:16.986 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:16.985 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:16.985 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:16.984 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 00:18:16.984 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 93 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 98 4b f2 02 Error: UNC at LBA = 0x02f24b98 = 49433496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 00 30 f2 42 00 00:18:13.544 READ FPDMA QUEUED 60 00 08 f8 2f f2 42 00 00:18:13.521 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:13.521 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:13.520 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:13.520 SET FEATURES [set transfer mode] Error 92 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 d8 2c f2 02 Error: UNC at LBA = 0x02f22cd8 = 49425624 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 d8 2c f2 42 00 00:18:10.147 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:10.147 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:10.146 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:10.146 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 00:18:10.146 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 91 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 d8 2c f2 02 Error: UNC at LBA = 0x02f22cd8 = 49425624 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 78 11 f2 42 00 00:18:06.708 READ FPDMA QUEUED 60 00 08 70 11 f2 42 00 00:18:06.683 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:06.682 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:06.682 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:06.681 SET FEATURES [set transfer mode] Error 90 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 90 0c f2 02 Error: UNC at LBA = 0x02f20c90 = 49417360 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 90 0c f2 42 00 00:18:03.309 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:03.308 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:03.308 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:03.308 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 00:18:03.307 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 14266 - # 2 Short offline Completed without error 00% 14261 - # 3 Short offline Completed without error 00% 12884 - # 4 Extended offline Completed without error 00% 12126 - # 5 Short offline Completed without error 00% 11333 - # 6 Short offline Completed without error 00% 10789 - # 7 Short offline Completed without error 00% 10695 - 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. Thanks again for taking the time to look.

awesome thank you! Seems to be working. Going to clear off a drive and give it a try now on the main rig. Thanks again -D

Ok thank you. And looking at the modifiers rsync -a -v --delete --delete will go through the backup drive and delete the files I have deleted from unraid? -a is archive mode where it will keep the original file properties (modified date, etc)? -v verbose... im assuming this makes the beeping and notification functions work? *the last question has to do within the script button of unraid - there is a slider called "Run in background"... what does this do in the practical sense to the script?

Yes i found the first one, have been playing with it and 2 flash drives to test... Am I able to just add additional rsync lines to the script for multiple folders? #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # AVAIL : available space # USED : used space # SIZE : partition size # SERIAL : disk serial number # ACTION : if mounting, ADD; if unmounting, REMOVE # MOUNTPOINT : where the partition is mounted # FSTYPE : partition filesystem # LABEL : partition label # DEVICE : partition device, e.g /dev/sda1 # OWNER : "udev" if executed by UDEV, otherwise "user" # PROG_NAME : program name of this script # LOGFILE : log file for this script case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 sleep 2 if [ -d $MOUNTPOINT ] then if [ $OWNER = "udev" ] then beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 logger Started -t$PROG_NAME echo "Started: `date`" > $LOGFILE logger Pictures share -t$PROG_NAME rsync -a -v --delete /mnt/user/SCANS $MOUNTPOINT/ 2>&1 >> $LOGFILE ###I ADDED THE LINE BELOW### rsync -a -v --delete /mnt/user/appdata $MOUNTPOINT/ 2>&1 >> $LOGFILE ### ### logger Syncing -t$PROG_NAME sync beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 beep -r 5 -l 100 -f 2000 logger Unmounting PicturesBackup -t$PROG_NAME /usr/local/sbin/rc.unassigned umount $DEVICE echo "Completed: `date`" >> $LOGFILE logger Pictures Backup drive can be removed -t$PROG_NAME /usr/local/emhttp/webGui/scripts/notify -e "unRAID Server Notice" -s "Server Backup" -d "Pictures Backup completed" -i "normal" fi else logger Pictures Backup Drive Not Mounted -t$PROG_NAME fi ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; esac

Any chance you can post a sample of your script and where you save it? Think its the script button on the main page for each device? How do i configure the script for specific shares/drives?

Hello all, have searched g/com and forum, and does not appear to be a good solution to the below problem. I have an unRAID box I am beginning to use again after a massive failure (likely my fault from clicking away). I have the system backing up as a whole to crashplan, so i am covered for an online copy. However, I want to automate critical folder backups to 2TB USB drives, which can be alternated and then stored in a fireproof safe/off-site. I have looked into several options, but can not figure out how to get BTSync to sync folders locally to a local usb. Crashplan stores a database file and I want the raw data available as a backup. The plugin "Unassigned Devices" seems like a good option to get the drive mounted and accessible, however I am at a loss to find a docker solution to complete this task. I realize I could use VM options, but that seems more cumbersome to install/maintain. Any advice on where to look, or your personal setups would be helpful. P.S. I realize that a 2nd unraid server would be beneficial, however I only have one location available right now, and having 2 servers does prevent from HW failure, but does nothing for fire or theft... Thanks again for your help. -D

Hey all, I have a system that has been upgraded and working great for years. Put some new drives in it and also upgraded to v6 a while back and have had a lot of issues with stability compared to the previous version of UnRAID... Here is the most current error: Aug 20 04:19:12 unRAID kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 20 04:19:12 unRAID kernel: ata3.00: configured for UDMA/133 Aug 20 04:19:12 unRAID kernel: ata3: EH complete Aug 20 04:53:40 unRAID kernel: __readpage_endio_check: 17 callbacks suppressed Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 380981248 csum 16691946 expected csum 1953271402 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 381091840 csum 2566472073 expected csum 2534422075 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 381222912 csum 2566472073 expected csum 1477846970 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 381353984 csum 2566472073 expected csum 1239327588 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 381485056 csum 2566472073 expected csum 751436214 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 381747200 csum 2566472073 expected csum 1867103920 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 381878272 csum 2566472073 expected csum 3884828937 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 382009344 csum 2566472073 expected csum 211276863 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 382140416 csum 2566472073 expected csum 2432515920 Aug 20 04:53:40 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 381616128 csum 2566472073 expected csum 1025059578 Aug 20 04:54:00 unRAID kernel: __readpage_endio_check: 6 callbacks suppressed Aug 20 04:54:00 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 380981248 csum 16691946 expected csum 1953271402 Aug 20 04:54:01 unRAID shfs/user: shfs_read: read: (5) Input/output error Aug 20 04:54:01 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 380981248 csum 16691946 expected csum 1953271402 Aug 20 04:54:01 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 380981248 csum 16691946 expected csum 1953271402 Aug 20 04:54:01 unRAID shfs/user: shfs_read: read: (5) Input/output error Aug 20 04:54:01 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 380981248 csum 16691946 expected csum 1953271402 Aug 20 04:54:01 unRAID shfs/user: shfs_read: read: (5) Input/output error Aug 20 04:54:01 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 380981248 csum 16691946 expected csum 1953271402 Aug 20 04:54:01 unRAID kernel: BTRFS warning (device md1): csum failed ino 8677 off 380981248 csum 16691946 expected csum 1953271402 Aug 20 04:54:01 unRAID shfs/user: shfs_read: read: (5) Input/output error Aug 21 00:57:36 unRAID kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x90200 action 0xe frozen Aug 21 00:57:36 unRAID kernel: ata3: irq_stat 0x00400000, PHY RDY changed Aug 21 00:57:36 unRAID kernel: ata3: SError: { Persist PHYRdyChg 10B8B } Aug 21 00:57:36 unRAID kernel: ata3: hard resetting link Aug 21 00:57:43 unRAID kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 21 00:57:43 unRAID kernel: ata3.00: configured for UDMA/133 Aug 21 00:57:43 unRAID kernel: ata3: EH complete Aug 21 23:27:41 unRAID kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x90200 action 0xe frozen Aug 21 23:27:41 unRAID kernel: ata3: irq_stat 0x00400000, PHY RDY changed Aug 21 23:27:41 unRAID kernel: ata3: SError: { Persist PHYRdyChg 10B8B } Aug 21 23:27:41 unRAID kernel: ata3: hard resetting link Aug 21 23:27:47 unRAID kernel: ata3: SATA link down (SStatus 0 SControl 310) Aug 21 23:27:47 unRAID kernel: ata3: hard resetting link Aug 21 23:27:53 unRAID kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 21 23:27:53 unRAID kernel: ata3.00: configured for UDMA/133 Aug 21 23:27:53 unRAID kernel: ata3: EH complete Aug 22 17:21:51 unRAID emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Sadly I had a catastrophic data loss around 6-8 months ago and am very nervous to trust UnRAID again (even though it has served me flawlessly through a fire, hardware upgrades, and constant use. Hope the community can help me decipher the code above and know why my drive (again) was red-balled. Thanks

Seems for some reason since upgrading to 6.0 I have been getting red-balled frequently as of late. Current one happened randomly, and here is the SMART output and UNRAID logs: Please help, cant afford more data loss at this point SMART: Disk 1 attached to port: sdc Vendor: /4:0:0:0 Product: >> Terminate command early due to bad response to IEC mode page: A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 Unfortunatly it froze when i was trying to get SMART status test complete and rebooted, so heres the log file, not sure if it will be helpful or not:

I have bought from microcenter mainly because for $10-20 you guarantee a working $100-130 HDD (and can use to upgrade if needed since they basically give you a gift card). Agreed, think ssh without screen will drop in the middle of a preclear if it looses connection right? I enjoy not having monitor/keyboard on my unRaid and have managed everything remotely thusfar.

Oh ok, do you ssh or type into the terminal directly? Also, i think the reason for the code is it will limit memory usage, as well as run the preclear script 3 times. I remember reading there is a risk of running preclear once, and 3x helps with burn in (actually one WD RED drive went bad during preclear and i was able to exchange for a working one with no problems). Any benefit to preclearing multiple times your aware of?