Jump to content

Albin

Members
  • Content Count

    112
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Albin

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. I just checked the File Activity log and it appears to be working.
  2. I uninstalled and reinstalled the file activity plugin. I also made sure that flash\config\plugins\file.activity did not exist at the time of reinstall. After re-installation, I started file activity, but I do not see any logs or results, even after hitting refresh. Status shows as running. I did adjust my inotify value (from 524288 to 2524288) with tips and tweaks (thanks for the tips and tweaks plugin!) I can't figure out why do not get results with file activity. I attached the diagnostics. Thanks for any insight into this. tower2-diagnostics-20190717-1617.zip
  3. I am having the same issue. I have a share called "Main" that I created years ago and have had no problems accessing it until today. I attempted a reboot of my windows 10 machine, then the server and the win10 machine, and neither helped. I thought it was a SMB issue, but after some trouble shooting I realized that I could access some child folders and but not all child folders but I could not drill down from parent to child: I could access Main\Downloads\folder1 (I had to type it out or use an existing shortcut to the location) I could access Main\Downloads\folder2 (I had to type it out or use an existing shortcut to the location) I could not access Main\Downloads\folder3 (this folder has files on the cache drive folder1 and folder2 do not have files on cache drive) I cannot access Main\Downloads (I am guess it is because of folder3 having files on the cache drive) I can Main\ (which I would have thought I would not be able to because of folder3 having files on the cache drive) I invoked mover to see what this would do, but it did not seem to help. I installed the "Tips and Tweaks" Plugin and changed my "Max Watches 'fs.inotify.max_user_watches'" from 524288 to 2524288 (just added a 2 to the front of the default value, and will play around with this value over time, if need be.) see Still not enough inotify watches? As soon as I adjusted the inotify value, I could access folder1, folder2 and any other problem folder I had. Not sure if these will help but I attached the diagnostics file before and after the inotify changes. Unfortunately I invoked mover and also adjusted the inotify value with in minutes of each other, so I am not certain which of the changes allowed access to the offending folders. Thanks dlandon for the plugin Tips and Tweaks ! tower2-diagnostics-20190717-1617.zip tower2-diagnostics-20190717-1454.zip
  4. Very Helpful Squid! Thanks. I first tried newperms on a particular share, but it did not seem to fix an issue I was having with some old backups that I am trying to purge. I ended up using chmod -R 0777 /mnt/user/SHARENAME There seems to be files that this does not work on. I have not completely narrowed it down, but it seems it is either extremely long file names, file names with special characters, or folders with special characters that the command is not working on (I thought it also had to do with files or folders that had spaces in them but that does not seem to be the case. Is there a command that can be added as a catch all for those type conditions? OR is there a way to strip special characters from file names, or truncate long file names?
  5. Attempting to dig some more on this and get this working, I noticed in an error log something about certificate/s. Could my issue be related to SSL Certificates. It looks like there are a cert.crt, with cert.key file but it is under apache keys.
  6. Hey, I am struggling to get this going. Here is what I have: Unraid 6.3.5 Apache Web Server to serve up the VirtualBox GUI interface instead of using commandline phpVirtualBox GUI for virtualbox Virtualbox Unraid go script edited to change unraid GUI to port 81 /usr/local/sbin/emhttp -p 81 & Rebooted Apache is installed to /mnt/user/appdata/apache with Host port 1 set to 80 Host port 2 set to 443 phpVirtuabox phpvirtualbox-5.0-5 dwonloaded and unzipped to /mnt/cache/appdata/apache/www/phpvb changed config.php-example to config.php removed # commenting out line: var $noAuth = true; (not really needed) Virtualbox Virtualbox v5.1.22 local version and installed version virtualbox extension v5.1.22 local version and installed version virtualbox guest additions local version and NOT showing an installed version virtualbox plugin v2017.05.19e VirtualbBox symbolic link set to: /boot/custom/vbox (Two things I do not see this folder on unraid and do I need to change this location so it is not on the flash drive?) (I created the folder "custom" and then added the folder "vbox" to get /boot/custom/vbox .... not sure if this is needed) vboxwebsrv host IP: 127.0.0.1 vboxwebsrv Port 18083 Vboxwebserver log file location /boot/config/plugins/virtualbox/vbox (verbose mode YES) (just checked this location on the flash drive and there is no folder "vbox" under /boot/config/plugins/virtualbox) (I added the folder "vbox" ..... not sure if this is needed) (after doing the below and watching the folder, nothing appeared in vbox....) Starting VirtualBox plugin: Went to Dockers and Started Apache Went to Plugins and Clicked "Start vboxwebsrv" Opened a New Chrome Tab and went to http:\\tower/phpvb/ or IP Address/phpvb By the way I have no VM's running plenty of Ram and space, and once I start the above process, I have to use terminal to do a "PowerDown" this process locks up the gui screen and I can not gain access to any part of gui from any computer or from the screen connected to the tower. At the very bottom of the Virtualbox plugin tab it says: "/opt/VirtualBox/VBoxManage setproperty websrvauthlibrary null vboxwebsrv service started" I saw the phpVirtualbox GUI but it was light (still loading) after waiting five minutes or so I refreshed and then the light outline of the GUI shows for a second and then goes away and does not come back and I get the message: "An error occurred communicating with your vboxwebsrv. No more requests will be sent by phpVirtualBox until the error is corrected and this page is refreshed. The details of this connection error should be displayed in a subsequent dialog box." and the message: "Could not connect to host (http://127.0.0.1:18083/)[code] Exception Object ( [message:protected] => Could not connect to host (http://127.0.0.1:18083/) [string:Exception:private] => [code:protected] => 64 [file:protected] => /config/www/phpvb/endpoints/lib/vboxconnector.php [line:protected] => 220 [trace:Exception:private] => Array ( [0] => Array ( [file] => /config/www/phpvb/endpoints/lib/vboxconnector.php [line] => 5763 [function] => connect [class] => vboxconnector [type] => -> [args] => Array ( ) ) [1] => Array ( [file] => /config/www/phpvb/endpoints/lib/vboxconnector.php [line] => 951 [function] => remote_vboxGroupDefinitionsGet [class] => vboxconnector [type] => -> [args] => Array ( [0] => ) ) [2] => Array ( [file] => /config/www/phpvb/endpoints/api.php [line] => 316 [function] => __call [class] => vboxconnector [type] => -> [args] => Array ( [0] => vboxGroupDefinitionsGet [1] => Array ( [0] => [1] => Array ( [0] => Array ( [data] => Array ( [responseData] => Array ( ) ) [errors] => Array ( ) [persist] => Array ( ) [messages] => Array ( ) ) ) ) ) ) [3] => Array ( [file] => /config/www/phpvb/endpoints/api.php [line] => 316 [function] => vboxGroupDefinitionsGet [class] => vboxconnector [type] => -> [args] => Array ( [0] => [1] => Array ( [0] => Array ( [data] => Array ( [responseData] => Array ( ) ) [errors] => Array ( ) [persist] => Array ( ) [messages] => Array ( ) ) ) ) ) ) [previous:Exception:private] => ) Location:http://127.0.0.1:18083/ [/code] Here is the first several lines of my vboxwebsrv.log file: VirtualBox web service 5.1.22 r115126 linux.amd64 (Apr 28 2017 16:59:05) release log 00:00:00.001416 main Log opened 2017-08-27T11:56:00.979746000Z 00:00:00.001419 main Build Type: release 00:00:00.001422 main OS Product: Linux 00:00:00.001423 main OS Release: 4.9.30-unRAID 00:00:00.001424 main OS Version: #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017 00:00:00.001467 main DMI Product Name: CYPRESS11 00:00:00.001477 main DMI Product Version: 1.0 00:00:00.001551 main Host RAM: 128913MB (125.8GB) total, 107021MB (104.5GB) available 00:00:00.001556 main Executable: /opt/VirtualBox/vboxwebsrv 00:00:00.001557 main Process ID: 83003 00:00:00.001558 main Package type: LINUX_64BITS_GENERIC 00:00:00.006024 main IPC socket path: /tmp/.vbox-root-ipc/ipcd 00:00:00.014135 main Pumping COM event queue 00:00:00.014159 main Pumping COM event queue 00:00:00.014250 Watchdog Watchdog thread started 00:00:00.014262 Watchdog Watchdog: sleeping 5 seconds 00:00:00.014963 SQPmp Socket connection successful: host = 127.0.0.1, port = 18083, master socket = 12 00:00:05.014420 Watchdog Watchdog: checking 0 websessions 00:00:05.014458 Watchdog Statistics: 0 websessions, 0 references 00:00:05.014474 Watchdog Watchdog: sleeping 5 seconds 00:00:10.014603 Watchdog Watchdog: checking 0 websessions 00:00:10.014656 Watchdog Watchdog: sleeping 5 seconds 00:00:15.014332 main Pumping COM event queue 00:00:15.014747 Watchdog Watchdog: checking 0 websessions 00:00:15.014772 Watchdog Watchdog: sleeping 5 seconds It just repeats from here on out (checking and sleeping) I feel I am close, but I just can't get it working. Any pointers would be greatly appreciated. I am looking forward to using this! EDIT: The VirtualBox Plugin page finally gave me the option (buttons) to Restart or shutdown virtualbox (but it took forever) Thanks, Albin
  7. Remove the volume mapping for /config -> /mnt/cache/appdata/crashplan-desktop. that conflicts with --volumes-from CrashPlan After removing the container and the image I tried again. This time I I did not change anything after hitting add. I left the volume mapping empty I left the port mapping the way it was (Container 3389 > host 3389) and I had left the --volumes-from CrashPlan in the Extra Parameters section. After hitting add I get the following: Command: root@localhost:# /usr/bin/docker run -d --name="CrashPlan-Desktop" --net="bridge" -e TZ="America/New_York" -p 3389:3389/tcp --volumes-from CrashPlan gfjardim/crashplan-desktop time="2015-07-30T17:01:23-04:00" level=fatal msg="Error response from daemon: Could not apply volumes of non-existent container "CrashPlan"." The command failed. I am not sure what I am doing wrong. Are there unRaid settings that I need to change. I am running 6.0.1 This is a fresh install of 6.0.1 My docker image is at the root of my cache drive mnt/cache/docker.img I have my appdata on the cache drive as a cache only share mnt/usr/appdata I deleted any share that I created specifically for crash plan during my first attempts. Thanks for any advice. Albin Have you installed the CrashPlan docker (Not the Desktop version) You need both, CrashPlan is the service and the Desktop is just a conduit to configuring the CrashPlan docker. Thanks for pointing me in the correct direction. I installed the crashplan service. Looks like things are working now. Thanks for your help!
  8. I cannot seem to get CrashPlan-Desktop to install. When I first added the container I was thinking that I needed to do volume mapping. Then I saw ljm42 post Remove the volume mapping for /config -> /mnt/cache/appdata/crashplan-desktop. that conflicts with --volumes-from CrashPlan After removing the container and the image I tried again. This time I I did not change anything after hitting add. I left the volume mapping empty I left the port mapping the way it was (Container 3389 > host 3389) and I had left the --volumes-from CrashPlan in the Extra Parameters section. After hitting add I get the following: Command: root@localhost:# /usr/bin/docker run -d --name="CrashPlan-Desktop" --net="bridge" -e TZ="America/New_York" -p 3389:3389/tcp --volumes-from CrashPlan gfjardim/crashplan-desktop time="2015-07-30T17:01:23-04:00" level=fatal msg="Error response from daemon: Could not apply volumes of non-existent container "CrashPlan"." The command failed. I am not sure what I am doing wrong. Are there unRaid settings that I need to change. I am running 6.0.1 This is a fresh install of 6.0.1 My docker image is at the root of my cache drive mnt/cache/docker.img I have my appdata on the cache drive as a cache only share mnt/usr/appdata I deleted any share that I created specifically for crash plan during my first attempts. Thanks for any advice. Albin
  9. I took at look at your smart reports and you can see my comments below. The drive sizes of the drives included are as follows: sda - 750G sdb - 500G sdd - 500G sde - 750G sdf - 1T sdh - 500G Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider. But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left. Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature. reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing. pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be. temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned. The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible. If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned. Let me know if any questions on the information below: 1 sda == ST3750330NS 9QK0D9WY == Disk /dev/sda has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 119 6 ok 120090706 Spin_Retry_Count = 100 100 97 near_thresh 8 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 60 64 45 near_thresh 40 Temperature_Celsius = 40 36 0 ok 40 Hardware_ECC_Recovered = 45 34 0 ok 120090706 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. 1 sector had been re-allocated before the start of the preclear. 4 sectors are re-allocated at the end of the preclear, a change of 3 in the number of sectors re-allocated. ======================================================================= This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array). 2 sdb == ST3500630NS 5QG1HKD0 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 66 68 45 near_thresh 34 Temperature_Celsius = 34 32 0 ok 34 Hardware_ECC_Recovered = 57 71 0 ok 8218259 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. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ======================================================================= This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty. 3 sdd == ST3500630AS 9QG0GA2R == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 56 62 45 near_thresh 44 Temperature_Celsius = 44 38 0 ok 44 Hardware_ECC_Recovered = 53 65 0 ok 7699123 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. 114 sectors had been re-allocated before the start of the preclear. 114 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ======================================================================= Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones. 4 sde == ST3750640NS 5QD0ELXR == Disk /dev/sde has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 55 58 45 near_thresh 45 Temperature_Celsius = 45 42 0 ok 45 Hardware_ECC_Recovered = 62 65 0 ok 64838030 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. ======================================================================= No signs of failure. 5 sdf == ST31000340AS 9QJ1VHF6 == Disk /dev/sdf has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 110 6 ok 183656712 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 61 62 45 near_thresh 39 Temperature_Celsius = 39 38 0 ok 39 Hardware_ECC_Recovered = 50 36 0 ok 183656712 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. ======================================================================= No signs of failure. 6 sdh == SAMSUNGHD502IJ S1PZJDWQ669795 == Disk /dev/sdh has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 0 ok 26 Temperature_Celsius = 74 76 0 ok 26 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. ======================================================================= No signs of failure. I ran 3 more cycles on sda sdb and sdd. There were no changes to the sectors re-allocated for these drives. (the numbers held steady)! I attached results for cycle 3 and 4. 1_sda_ST3750330NS___9QK0D9WY_Pass_3_and_4_no_new.txt 3_sdd_ST3500630AS___9QG0GA2R_pass_3_and_4_no_new.txt 2_sdb_ST3500630NS___5QG1HKD0_pass_3_and_4_no_new.txt
  10. Thanks Bjp999 I appreciate you taking the time to reply. The information you provided was very helpful. I am going to run more preclears on the drives you suggested. I will let you know what happens. Thanks, Albin Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones. 4 sde == ST3750640NS 5QD0ELXR == Disk /dev/sde has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 55 58 45 near_thresh 45 Temperature_Celsius = 45 42 0 ok 45 Hardware_ECC_Recovered = 62 65 0 ok 64838030 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. ======================================================================= No signs of failure. 5 sdf == ST31000340AS 9QJ1VHF6 == Disk /dev/sdf has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 110 6 ok 183656712 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 61 62 45 near_thresh 39 Temperature_Celsius = 39 38 0 ok 39 Hardware_ECC_Recovered = 50 36 0 ok 183656712 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. ======================================================================= No signs of failure. 6 sdh == SAMSUNGHD502IJ S1PZJDWQ669795 == Disk /dev/sdh has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 0 ok 26 Temperature_Celsius = 74 76 0 ok 26 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. ======================================================================= No signs of failure.
  11. I decided to do a fresh install of unRAID. I figured I would move my data off the server and preclear all the drives. I was hoping for some input as to which drives I should consider retiring. I did preclear most of these at the same time. Any input wold be greatly appreciated. Thanks, Albin 1 sda ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 1, partition start on sector 63 = 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: 40C, Elapsed Time: 19:01:52 ========================================================================1.15 == ST3750330NS 9QK0D9WY == Disk /dev/sda has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 119 6 ok 120090706 Spin_Retry_Count = 100 100 97 near_thresh 8 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 60 64 45 near_thresh 40 Temperature_Celsius = 40 36 0 ok 40 Hardware_ECC_Recovered = 45 34 0 ok 120090706 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. 1 sector had been re-allocated before the start of the preclear. 4 sectors are re-allocated at the end of the preclear, a change of 3 in the number of sectors re-allocated. =======================================================================END sda 2 sdb ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 63 = 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: 34C, Elapsed Time: 14:16:15 ========================================================================1.15 == ST3500630NS 5QG1HKD0 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 66 68 45 near_thresh 34 Temperature_Celsius = 34 32 0 ok 34 Hardware_ECC_Recovered = 57 71 0 ok 8218259 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. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================END sdb 3 sdd ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdd = cycle 1 of 1, partition start on sector 63 = 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: 44C, Elapsed Time: 14:09:42 ========================================================================1.15 == ST3500630AS 9QG0GA2R == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 56 62 45 near_thresh 44 Temperature_Celsius = 44 38 0 ok 44 Hardware_ECC_Recovered = 53 65 0 ok 7699123 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. 114 sectors had been re-allocated before the start of the preclear. 114 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================END sdd 4 sde ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 63 = 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: 45C, Elapsed Time: 18:32:23 ========================================================================1.15 == ST3750640NS 5QD0ELXR == Disk /dev/sde has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 55 58 45 near_thresh 45 Temperature_Celsius = 45 42 0 ok 45 Hardware_ECC_Recovered = 62 65 0 ok 64838030 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. =======================================================================END sde 5 sdf ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 63 = 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: 39C, Elapsed Time: 22:37:55 ========================================================================1.15 == ST31000340AS 9QJ1VHF6 == Disk /dev/sdf has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 110 6 ok 183656712 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 61 62 45 near_thresh 39 Temperature_Celsius = 39 38 0 ok 39 Hardware_ECC_Recovered = 50 36 0 ok 183656712 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. =======================================================================END sdf 6 sdh ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdh = cycle 1 of 1, partition start on sector 63 = 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: 26C, Elapsed Time: 16:30:41 ========================================================================1.15 == SAMSUNGHD502IJ S1PZJDWQ669795 == Disk /dev/sdh has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 0 ok 26 Temperature_Celsius = 74 76 0 ok 26 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. =======================================================================END sdh drives_1_thru_6_.txt
  12. Very Help! Thanks. I just upgraded from 5.0 to 6.0.1 and tried to install the Community Applications Plugin and got the following: plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg ... done Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error I then stopped the array then went to settings>system settings>network settings and changed my DNS1 to my gateway IP address which is 192.168.2.2 (this is what I had in my DNS settings for my unraid 5.0 box) . After saving the settings and starting the array, I attempted to install the plugin and I had no issues with the installation process. I was not sure if my gateway IP address is or would be the best setting for this. (I am guess my gateway router redirects dns lookups to the DNS1 and DNS2 records that it has on file.) I wanted to try Googles Public DNS Lookup and compare the results of the plugin installation log. So to do this I uninstalled the plugin first. Then I went to settings>system settings>network settings and changed my DNS settings to Googles Public DNS. So for DNS1 I set it to 8.8.8.8 and DNS2 I set it to 8.8.4.4 After saving the settings and starting the array, I attempted to install the plugin and I had no issues with the installation process. There was no difference in speed or in the log between the two plugin installations. Log from Installation was the same for both network settings: plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg ... done plugin: downloading: https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2015.07.08.txz ... done +============================================================================== | Installing new package /boot/config/plugins/community.applications/community.applications-2015.07.08.txz +============================================================================== Verifying package community.applications-2015.07.08.txz. Installing package community.applications-2015.07.08.txz: PACKAGE DESCRIPTION: Package community.applications-2015.07.08.txz installed. ---------------------------------------------------- community.applications has been installed. Copyright 2015, Squid, gfjardim, bergware Version: 2015.07.08 ---------------------------------------------------- plugin: installed I am not sure it matters but, I do have a VPN for a remote office, but the VPN internet traffic is not routed over the VPN. The gateway which is also the hardware that has my VPN configurations, uses google public dns records also. At some point along the way (in the past) I changed from using my gateway ip address to using my isp DNS servers settings for DNS1 and DNS2. I am guessing their lookup was having issues or something. I am going to leave it set to 8.8.8.8 and 8.8.4.4 and leave DNS3 empty unless someone else has a better suggestion? Thanks again, Albin
  13. Worked for me also! I was upgrading from 5.0 to 6.0.1 and could not get the array to start. After removing startState="" the array started with no problem. Thanks for the help! Albin
  14. I am attempting to use Intel's CPU Feature list to narrow down the list of CPUs that would be most optimal for UNRAID 6 and unRAID 6.0-beta15 and potentially future releases. Some of the listed Features are confusing. I am not sure if they are needed or need to be avoided for an unraid build. My goal is take advantage of UnRaids support of KVM QEMU and OVMF/UEFI. I see some sites talk about needing to disable TXT or Trusted Execution Technology. In the Intel features selection criteria you can select YES or No for TXT. This is just one of the features that I really do not know if I need or want to avoid. Also it is not clear to me if, YES for some of these give an indication the CPU has that feature, or that one can disable that option, or does it mean it has it and you cannot disable it. For the time that I have spent trying to figure things out, it appears that having the ability to disable certain things, is important to the success of ones unraid build. Description of TXT Intel® Trusted Execution Technology for safer computing is a versatile set of hardware extensions to Intel® processors and chipsets that enhance the digital office platform with security capabilities such as measured launch and protected execution. It enables an environment where applications can run within their own space, protected from all other software on the system. I also see some chips that have Execute Disable Bit. This does not seem to be a filter option but is listed under the cpu description section Intel® Platform Protection Technology Execute Disable Bit is a hardware-based security feature that can reduce exposure to viruses and malicious-code attacks and prevent harmful software from executing and propagating on the server or network. There are other options that can be selected but it is unclear to me what items should be set to YES, which ones should be set to NO, and which ones don't matter. Technologies Intel Turbo Boost Technology (options are 1, 2, NO) Intel Hyper-Threading Technology (YES or NO) Intel Wireless Display (YES or NO) Intel Quick Sync Video (YES or NO) Intel Virtualization Technology (VT-x) (YES or NO) Intel VT-x with Extended Page Tables (EPT) (YES or NO) Intel Virtualization Technology for Directed I/O (VT-d) (I have this set to YES) AES New Instructions (YES or NO) Enhanced Intel SpeedStep® Technology (YES or NO) Intel Demand Based Switching (YES or NO) Trusted Execution Technology (also called TXT) (YES or NO) Intel 64 (I have this set to YES) Intel vPro Technology (YES or NO) I am guessing VT-d which has IOMMU DMA remapping would be most ideal. Should I select YES for any of the other features to get a list of the most compatible CPUs? Should I select NO for some to be sure to avoid them? Here is my understanding of what one may want in a CPU to get the most out of visualization (I understand that some may have specific wants based on their current build, but this is specific to virtualization, and unless there is a strong recommendation it is not for filtering socket type, speed, cache size, core count, ....: VT-d with IOMMU support (I am not sure if VT-d that do not support IOMMU, but definitely want IOMMU) needs to support OVMF/UEFI (I am not sure if this is somehow the same as IOMMU or is an additional feature needed) Not sure if there should be other must or must nots for a CPU If anyone has used Intel's Feature filter to find the best cpu, and give me some pointers I would greatly appreciate it. A Good, Better, Best list of CPU's would be awesome. Thanks, Albin