themaxxz

Hi, Not sure what is going on, but it's not working for me. Now nothing gets excluded and everything gets backed up. Output from ps. root 13033 0.0 0.0 11640 2608 ? SN 23:15 0:00 sh -c /usr/bin/rsync -avXHq --delete --exclude "/mnt/user/docker.img" --exclude "/mnt/user/appdata/Community_Applications_VM_XML_Backup/" --exclude "/mnt/user/appdata/deluge/" --exclude "/mnt/user/appdata/EmbyServer/" --exclude "/mnt/user/appdata/mariadb/" --exclude "/mnt/user/appdata/plexmediaserver/" --exclude "/mnt/user/appdata/sabnzbd/" --exclude "/mnt/user/appdata/sickrage/" --exclude "/mnt/user/appdata/sonarr/" --exclude "/mnt/user/appdata/Sync/" --log-file="/var/lib/docker/unraid/ca.backup.datastore/appdata_backup.log" "/mnt/user/appdata/" "/mnt/user/unRaidBackup/[email protected]" > /dev/null 2>&1 root 13034 4.7 0.0 21244 6372 ? SN 23:15 0:04 /usr/bin/rsync -avXHq --delete --exclude /mnt/user/docker.img --exclude /mnt/user/appdata/Community_Applications_VM_XML_Backup/ --exclude /mnt/user/appdata/deluge/ --exclude /mnt/user/appdata/EmbyServer/ --exclude /mnt/user/appdata/mariadb/ --exclude /mnt/user/appdata/plexmediaserver/ --exclude /mnt/user/appdata/sabnzbd/ --exclude /mnt/user/appdata/sickrage/ --exclude /mnt/user/appdata/sonarr/ --exclude /mnt/user/appdata/Sync/ --log-file=/var/lib/docker/unraid/ca.backup.datastore/appdata_backup.log /mnt/user/appdata/ /mnt/user/unRaidBackup/[email protected] root 13035 0.1 0.0 89468 5004 ? SN 23:15 0:00 /usr/bin/rsync -avXHq --delete --exclude /mnt/user/docker.img --exclude /mnt/user/appdata/Community_Applications_VM_XML_Backup/ --exclude /mnt/user/appdata/deluge/ --exclude /mnt/user/appdata/EmbyServer/ --exclude /mnt/user/appdata/mariadb/ --exclude /mnt/user/appdata/plexmediaserver/ --exclude /mnt/user/appdata/sabnzbd/ --exclude /mnt/user/appdata/sickrage/ --exclude /mnt/user/appdata/sonarr/ --exclude /mnt/user/appdata/Sync/ --log-file=/var/lib/docker/unraid/ca.backup.datastore/appdata_backup.log /mnt/user/appdata/ /mnt/user/unRaidBackup/[email protected] root 13036 5.3 0.0 92192 3768 ? SN 23:15 0:05 /usr/bin/rsync -avXHq --delete --exclude /mnt/user/docker.img --exclude /mnt/user/appdata/Community_Applications_VM_XML_Backup/ --exclude /mnt/user/appdata/deluge/ --exclude /mnt/user/appdata/EmbyServer/ --exclude /mnt/user/appdata/mariadb/ --exclude /mnt/user/appdata/plexmediaserver/ --exclude /mnt/user/appdata/sabnzbd/ --exclude /mnt/user/appdata/sickrage/ --exclude /mnt/user/appdata/sonarr/ --exclude /mnt/user/appdata/Sync/ --log-file=/var/lib/docker/unraid/ca.backup.datastore/appdata_backup.log /mnt/user/appdata/ /mnt/user/unRaidBackup/[email protected] When selecting which folders to exclude, it now adds them with absolutes paths which is causing the exclusion to fail I think.

Hi @Squid I want to report a bug with CA Backup / Restore Appdata 2017.06.12 There seems to be a problem with long folder names, that get truncated with "..." when adding via the UI and so the exclude does not work. Sep 23 01:33:04 unraid root: Using command: /usr/bin/rsync -avXHq --delete --exclude "/mnt/user/docker.img" --exclude "Community_Applications_VM_XML_Bac..." --exclude "deluge" --exclude "EmbyServer" --exclude "mariadb" --exclude "plexmediaserver" --exclude "sabnzbd" --exclude "sickrage" --exclude "sonarr" --exclude "Sync" --log-file="/var/lib/docker/unraid/ca.backup.datastore/appdata_backup.log" "/mnt/user/appdata/" "/mnt/user/unRaidBackup/[email protected]" > /dev/null 2>&1 As you can see I wanted to exclude "Community_Applications_VM_XML_Backup", but it changes it into --exclude "Community_Applications_VM_XML_Bac..." and so it does not get excluded.

Thanks for the tip, but I just tested this solution and it does not work for me. Just to be sure that everybody understands what I mean with 'warm' and 'cold' reboot. A 'warm' reboot is when I do a 'reboot' from inside the OS, without stopping the VM container. A 'cold' reboot is the first boot after starting the VM container. So I only have the issue when I 'warm' reboot my VM. And the messages start after the system is booted for about 588 seconds and repeat about every 30 seconds. But I do think the issue is indeed related to the 'clock' or 'timer' because I can consistently reproduce the issue as well as the consistent interval of the messages which in my opinion rules out a hardware issue. Also see http://m.blog.itpub.net/35489/viewspace-84530/ "These messages occur because the kernel ignores the Advanced Configuration and Power Interface (ACPI) timer override for the system timer" So adding to my previous list of already tried and failed tweaks: - adding boot option clocksource=acpi_pm - adding boot option acpi=off => results in unbootable VM - adding <timer name='kvmclock' present='no'/> in kvm.xml

After switching my unRAID from virtualized to BM, and removing some usb keys that were giving 'errors', the layout is working again for me.

Hi, Since a few days I'm running BM unraid and no longer running unRAID in a VM on ESXi and unfortunately I'm seeing the same style of messages. Message from syslogd@host at Sep 19 21:07:24 ... kernel:Uhhuh. NMI received for unknown reason 21 on CPU 0. Message from syslogd@host at Sep 19 21:07:24 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@host at Sep 19 21:07:24 ... kernel:Dazed and confused, but trying to continue These messages seem to start exactly 10min after a 'warm' reboot of a centos 7 VM. If I do a cold reboot, I do not get the messages. I've already tried the following changes to the VM, but none helped. - setting acpi_pcm=off - nmi_watchdog=0 - chaning pc-q35-2.7 to pc-q35-2 unRAID hw is: - supermicro x9scm-f - xeon E3 1230 - 32GB ECC - 2x m1015 in it mode

Thanks for confirming there is no issue with unRAID.

You are probably right, but it would be nice to have confirmation from 'Lime Technology' directly. E.g. synology mentions that RAID 5, RAID 6, RAID F1, or SHR with more than 3 disks are impacted.

Hi, Is unraid impacted by the 'skip_copy' problem described below? https://forum.synology.com/enu/viewtopic.php?t=135059 http://www.sbsfaq.com/?p=4277&doing_wp_cron=1505991093.5444660186767578125000 http://www.sbsfaq.com/?p=4321 Regards,

I just noticed by accident the same issue on my server. I saw 1 cpu pegged at 100% and it turned out to be cache_dirs. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7270 root 20 0 10760 3036 2048 R 100.0 0.0 795:53.95 cache_dirs lsof showed me # lsof |grep -i 7270 cache_dir 7270 root cwd DIR 0,2 380 2 / cache_dir 7270 root rtd DIR 0,2 380 2 / cache_dir 7270 root txt REG 0,2 1094752 298 /bin/bash cache_dir 7270 root mem REG 0,2 174816 2419 /lib64/ld-2.24.so cache_dir 7270 root mem REG 0,2 18436 2376 /lib64/libtermcap.so.2.0.8 cache_dir 7270 root mem REG 0,2 18808 2431 /lib64/libdl-2.24.so cache_dir 7270 root mem REG 0,2 2067512 2425 /lib64/libc-2.24.so cache_dir 7270 root 0r FIFO 0,8 0t0 59140270 pipe cache_dir 7270 root 1w CHR 1,3 0t0 1029 /dev/null cache_dir 7270 root 2w CHR 1,3 0t0 1029 /dev/null cache_dir 7270 root 6r REG 0,2 2727 6243 /usr/local/emhttp/update.htm cache_dir 7270 root 10r CHR 1,3 0t0 1029 /dev/null cache_dir 7270 root 63r FIFO 0,8 0t0 59140270 pipe Running unraid 6.3.5 This is the first time I had this problem, and the only thing that change in my environment is - upgrade of my docker plex image - switch my htpc to using LibreELEC (Krypton) v8.0.2 from gotham I have now reverted my htpc back to gotham and will see if the problem returns or not..

Just noticed the same thing on my server, running identical versions.

My parity check times in a mixed 2TB, 3TB, 6TB and 8TB archive drives. 22 hr, 55 min, 33 sec 96,9 MB/s 22 hr, 13 min, 11 sec 100,0 MB/s 22 hr, 58 sec 101,0 MB/s

Hi, Thanks for the suggestion regarding upgrading to 6.5. I'll keep it in mind when planning my ESXi upgrade at a later date. Right now I don't want to spend the rest of the weekend fixing potential issues. As for the 404, indeed this seems to be a browser/cache (chrome) issue of some sort because I do not see the issue when using IE. EDIT: clearing browser cached fixed the 404 issue.

Also took the plunge and updated from 6.1.9 to 6.3.5 mainly because of the wanacry risk. I'm running virtualized unraid on supermicro X9SCM platform since forever. Running ESXi 6.0.0 I also had the slow UI issue in addition to my /boot/config become read-only. Turns out this was due to the USB 1-1 ESXi reset issue. Using the workaround of doing a passthrough of a second USB stick/device to my unraid VM resolved this issue. The USB 1-1 reset message is gone and the UI is much snappier. But I still have a strange issue with dynamix. After doing 'apply' in the UI, the UI redirects to /update.htm and then ends up on /undefined page with 404 Not Found. Re-loading http://host/ brings the UI back. I already removed /boot/config/plugins/dynamix.plg and rebooted. Other than this behaviour, the server seems to work ok.

Hi, I want to report a minor issue with apcupsd running on unraid 6.1.9 (virtualized under esxi) I recently switched from apcupsd to nut. (better compatibility with rest of my setup). I have disabled apcupsd service in unraid, but it's being restarted by logrotate /etc/logrotate.d/apcupsd. For now I have just deleted the file, but I guess it will get recreated after reboot, so I'm thinking about putting 'rm -f /etc/logrotate.d/apcupsd' in my 'go' file. Would this be the 'right' way to go?

Below the results of a preclear of a seagate 8TB shingled drive. Device Model: ST8000AS0002-1NA17Z Serial Number: xxxxxxx LU WWN Device Id: 5 000c50 0908f403f Firmware Version: AR15 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5980 rpm Device is: Not in smartctl database [for details use: -P showall] 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: Tue Apr 5 08:28:36 2016 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Preclear Successful^n... Total time 73:43:58^n... Pre-Read time 19:55:32 (111 MB/s)^n... Zeroing time 17:38:39 (125 MB/s)^n... Post-Read time 36:08:27 (61 MB/s) ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = 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: 31C, Elapsed Time: 73:43:58 ========================================================================1.15 == ST8000AS0002-1NA17Z == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 100 6 ok 74771072 Seek_Error_Rate = 73 100 30 ok 21528871 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 = 69 77 45 near_thresh 31 Temperature_Celsius = 31 23 0 ok 31 Hardware_ECC_Recovered = 114 100 0 ok 74771072 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@Tower:/usr/local/emhttp# This was run on: unraid 6.1.6 Intel® Core™2 Duo CPU E6550 @ 2.33GHz 2GB ram ibm m1015 it mode

How is ESXi 5.5 working for you? Is everything working as it should, including the Health Status? What bios are you running on your supermicro? Regards, tm

Hello all, Just reporting in that I just upgraded from rc8a to final, doing the format / make_bootable / restore config directory procedure. I'm running a virtual unraid VM, booting plop/usb and it booted up without any problems. One thing I did do was to exclude the plugins directory from the config directory which contained open_vm_tools package (my VM is using e1000 nic so I could safely do this) Does anybody know where I can find a compatible open vm tools version for 5.0 final? http://unraid.zeron.ca/ only lists up to 5.0rc16c ? I read it should be compatible but can anybody confirm this? Regards, Werner