archedraft

You haven't had to click that button since June 2015. (Part of the reason it says "Don't Click Me - Why Are You Clicking Me?" on its pop up) Unless you're talking about Plugins - Check For Updates, in which case, yes you will now have lots of spare time on your hands to spend with your better-half. Hmmm, well in that case I would like a feature request to blow up the auto update feature into oblivion... The better-half always has something for me to accomplish [emoji51]

Whooo I don't have to click the community app update button daily!! I'm not sure what I will do with all my newly found free time... ?

Definitely Tito Puente!

So what does it feel like to be a rockstar?

I forget the excatly how but you need to add "rcp2" to the end. *I think* something like this: No user name or password is needed. You may need to change it to http: at the beginning though scgi://localhost:5000/rpc2

Could you elaborate more on this? Do we need to remove our /transcode location in our docker and then Plex manages it?

I like the idea of making it less clicks to verify data. Another idea based on johnnie's post. It would be pretty awesome to add a row for each disk on the dashboard that had a green check or whatever symbol stating that all data on that disk was good and a red X if it found that data was corrupt.

Ok, found the issue and made a correction. New version 2016.03.20 is available. This version also addresses compatibility with unRAID v6.2. Users are encouraged to update to this version. Please re-apply settings after upgrading to make them effective. Just tested with low and it works. Thank you. Another question for you from your quote below. Does this mean that new files do not get a checksum or exported automatically? Meaning any new files we add must be manually added to FIP?

Interesting, what happens when you manually execute the command? nice -n19 ionice -c2 -n7 /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker This is what happens: nice -n19 ionice -c2 -n7 /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker bunker v2.5 - Copyright (c) 2015-2016 Bergware International Usage: bunker -a|A|v|V|u|e|t|i|c|C|r|R [-fdDsSlLnq] [-md5|-b2] path [!] [mask] -a add hash key attribute for files, specified in path and optional m ask -A same as -a option with implicit export function (may use -f) -v verify hash key attribute and report mismatches (may use -f) -V same as -v option with updating of mismatched keys (may use -f) -u update mismatched or corrupted hash keys with new hash key attribu te (may use -f) -e export hash key attributes to the export file (may use -f) -t touch file, i.e. copy file modified time to extended attribute -i import hash key attributes from file and restore them (must use -f ) -c check hash key attributes from input file (must use -f) -C same as -c option and correct mismatched hash key in extended attr ibute (must use -f) -r remove hash key extended attribute from specified selection (may u se -f) -R same as -r option and remove all other values too (may use -f) -f <file> optional set file reference to <file>. Defaults to /tmp/bunker.sto re.log -d <days> optional only verify/update/remove files which were scanned <days> or longer ago -D <time> optional only add/verify/update/export/remove files newer than <ti me>, time = NNs,m,h,d,w -s <size> optional only include files smaller than <size> -S <size> optional only include files greater than <size> -l optional create log entry in the syslog file -L optional, same as -l but only create log entry when changes are pr esent -n optional send notifications when file corruption is detected -q optional quiet mode, suppress all output. Use for background proce ssing -md5 optional use md5 hashing algorithm instead of sha256 -b2 optional use blake2 hashing algorithm instead of sha256 path path to starting directory, mandatory with some exceptions (see ex amples) mask optional filter for file selection. Default is all files when path or mask names have spaces, then place names between quot es precede mask with ! to change its operation from include to exclud e Examples: bunker -a /mnt/user/tv add SHA key for files in share tv bunker -a -S 10M /mnt/user/tv add SHA key for files gre ater than 10 MB in share tv bunker -a /mnt/user/tv *.mov add SHA key for .mov file s only in share tv bunker -a /mnt/user/tv ! *.mov add SHA key for all files in share tv except .mov files bunker -A -f /tmp/keys.hash /mnt/user/tv add SHA key for files in share tv and export to file keys.hash bunker -v -n /mnt/user/files verify SHA key for previo usly scanned files and send notifications bunker -V /mnt/user/files verify SHA key for scanne d files and update any mismatches bunker -v -d 90 /mnt/user/movies verify SHA key for files scanned 90 days or longer ago bunker -v -f /tmp/errors.hash /mnt/user/movies verify SHA key and save m ismatches in file errors.hash bunker -u /mnt/disk1 update SHA key for mismat ching files bunker -u -D 12h /mnt/disk1 update SHA key for mismat ching files created in the last 12 hours bunker -e -f /tmp/disk1_keys.hash /mnt/disk1 export SHA key to file di sk1_keys.hash bunker -i -f /tmp/disk1_keys.hash import and restore SHA ke y from user defined file - no path bunker -c -f /tmp/disk1_keys.hash check SHA key from user d efined input file - no path bunker -C -f /tmp/disk1_keys.hash check SHA key and correct mismatched attribute (omit corruptions) - no path bunker -r /mnt/user/tv remove SHA key for files in share tv bunker -r -f /tmp/errors.hash remove SHA key for files listed in file errors.hash - no path

Interesting, what happens when you manually execute the command? nice -n19 ionice -c2 -n7 /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker I will test and find out. Before I do, is there a command to stop bunker from verifying each disk? I would hate to have multiple instances running.

Wow alright I figured it out after 60 mins of changes settings. If priority is set to "low" it doesn't start but if it is set to "normal" then it runs!

No, parity check only happens on the first of the month. I can change it to "continue" if that is the issue?

Can you show the content of the following files: # cat [b]/etc/cron.d/root[/b] # Generated file integrity check schedule: 50 11 * * 1 /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null cat [b][b]/boot/config/plugins/dynamix.file.integrity/integrity-check.sh[/b][/b] #!/bin/bash # This is an auto-generated file, do not change manually! # bunker=/usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker [[ $((10#$(date +%W)%5)) -eq 0 ]] && $bunker -Vqj -b2 -n -L /mnt/disk1 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 0 ]] && $bunker -Vqj -b2 -n -L /mnt/disk2 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 1 ]] && $bunker -Vqj -b2 -n -L /mnt/disk3 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 1 ]] && $bunker -Vqj -b2 -n -L /mnt/disk4 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 2 ]] && $bunker -Vqj -b2 -n -L /mnt/disk5 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 2 ]] && $bunker -Vqj -b2 -n -L /mnt/disk6 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 3 ]] && $bunker -Vqj -b2 -n -L /mnt/disk7 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 3 ]] && $bunker -Vqj -b2 -n -L /mnt/disk8 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 4 ]] && $bunker -Vqj -b2 -n -L /mnt/disk9 >/dev/null & [[ $((10#$(date +%W)%5)) -eq 4 ]] && $bunker -Vqj -b2 -n -L /mnt/disk10 >/dev/null & exit 0 With notifications ON (see settings) you would see messages as indicated below: 17-03-2016 19:41 Dynamix file integrity [disk3] Notice [VESTA] - Verify task for disk3 finished Duration: 5 hr, 10 min, 1 sec. 17-03-2016 19:22 Dynamix file integrity [disk5] Notice [VESTA] - Verify task for disk5 finished Duration: 4 hr, 50 min, 41 sec. 17-03-2016 14:31 Dynamix file integrity [disk3] Notice [VESTA] - Verify task for disk3 started Total files size: 2.22 TB 17-03-2016 14:31 Dynamix file integrity [disk5] Notice [VESTA] - Verify task for disk5 started Total files size: 2.13 TB cat /etc/cron.d/root # Generated file integrity check schedule: 5 0 19 * * /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /de v/null # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate .php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 0 1 * * * /usr/local/sbin/mover |& logger # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated array status check schedule: 20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null cat /boot/config/plugins/dynamix.file.integrity/integrity-check.sh #!/bin/bash # This is an auto-generated file, do not change manually! # bunker=nice -n19 ionice -c2 -n7 /usr/local/emhttp/plugins/dynamix.file.integrity/scripts/bunker [[ $(grep -Po '^mdResync=\K\S+' /proc/mdcmd) -ne 0 ]] && exit 0 [[ $((10#$(date +%m)%1)) -eq 0 ]] && $bunker -Vqj -b2 -n -L -f /boot/config/plugins/dynamix.file.integrity/logs/disk1.export.$(date +%Y%m%d).bad.log /mnt/disk1 >/dev/null & [[ $((10#$(date +%m)%1)) -eq 0 ]] && $bunker -Vqj -b2 -n -L -f /boot/config/plugins/dynamix.file.integrity/logs/disk2.export.$(date +%Y%m%d).bad.log /mnt/disk2 >/dev/null & [[ $((10#$(date +%m)%1)) -eq 0 ]] && $bunker -Vqj -b2 -n -L -f /boot/config/plugins/dynamix.file.integrity/logs/disk3.export.$(date +%Y%m%d).bad.log /mnt/disk3 >/dev/null & exit 0

So FIP did not run this morning. I even tried the "update_cron" command after I changed the schedule yesterday just for good measure... Is everyone else not experiencing this?

Thanks for the quick update! I set my integrity check for tomorrow morning at 0:05 AM so I'll report back on if the check ran as scheduled.

I believe it should if you have "Save new hashing results to flash" enabled. I don't. I do have "Save new hashing results to flash" enabled, however, it does not update the existing export file.

1. Received the same message last night. Shouldn't FIP automatically update the export file? 2. I scheduled an integrity check for last night and I didn't get any notifications that it ran. So either notifications are not working (which probably isn't the case because I am getting other notifications from FIP) or the cron job isn't running as scheduled. Is there anything from my config files that might help figure out why the check isn't running?

I had a similar experience. 95% of the time it worked great as a VM but it was the other 5% that was a real pain in the butt. I was always glad I kept my old pfSense box when those issues cropped up. I would just start up the old pfSense box and get whatever the issue was resolved. The problem was that each issue would normal take ~2-3 hours to mess with and now that I have a stand alone box, I do not have to waste those hours.

Sorry I missed this request earlier. Currently when notifications are enabled in the settings of file integrity, it will only produce a message when something unusual is found, in other words: checks without any corruptions (normal condition) are not reported. I can add a log entry + notification telling the start/stop times. No worries, I am sure it is hard to keep up with all your forums. Thank you for taking a look at the notifications.

Interesting, I am 99% sure mine didn't run. I ran it the next day (from when it is suppose to run) and it found a good amount of files that were corrupt. I am assuming that if it ran it should have given me the same file corruption report.

Thought I would bring this back up because I'm sure at the time you were very busy with the 6.2 release. I would also like to add the my monthly bunker cron did not start this month. Do you have any idea why it wouldn't start? also, It would be nice to be notified each month that bunker has started checking files just for peace of mind.

Yes, I have ran a pfSense VM on unRAID and it can "work". You need to VT-d and a spare dual NIC card to give to pfSense. Advice, don't do it! It is way too much work. For example, if for some reason the pfSense VM doesn't boot when you restart unRAID, you will not be able to access the unRAID webGUI because you won't get in IP address from pfSense. You are forced to use unRAID's console and try to figure out why it didn't start. Another hurtle, what happens when you need to put unRAID in maintenance mode to replace a failing disk. The VMs are stopped when you stop the array, luckily if you already had internet you can still access the unRAID webGUI because your laptop/computer still has an IP but I am not sure what happens if your in maintenance mode for a long time and your laptop wants to renew its IP? Get yourself something like this and thank me (I like beer). http://www.newegg.com/Product/Product.aspx?Item=N82E16856107153

Yeah I have also always received these messages, it is for my Radeon HD6450 so I wonder if it doesn't like being passed through? Mar 15 09:38:55 kernel: DMAR:[fault reason 06] PTE Read access is not set Mar 15 09:38:55 kernel: dmar: DRHD: handling fault status reg 3 Mar 15 09:38:55 kernel: dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr f002fe000

Please disregard the above post. Turned out to be the "enclosure" I was trying to use. Switched to a different one and works just fine.

I am trying to use UD to mount an USB harddrive to copy off some files from to server for backup purposes. unRAID see the USB hard drive get plugged in but it never shows up on UD. Every time I click refresh disks I get the following message: Any thoughts on why it isn't showing up? Mar 13 20:56:38 Pithos kernel: usb 1-1.6: new high-speed USB device number 12 using ehci-pci Mar 13 20:56:38 Pithos kernel: usb-storage 1-1.6:1.0: USB Mass Storage device detected Mar 13 20:56:38 Pithos kernel: scsi host9: usb-storage 1-1.6:1.0 Mar 13 20:56:39 Pithos kernel: scsi 9:0:0:0: Direct-Access WD My Book 1230 1065 PQ: 0 ANSI: 6 Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: Attached scsi generic sg9 type 0 Mar 13 20:56:39 Pithos kernel: scsi 9:0:0:1: Enclosure WD SES Device 1065 PQ: 0 ANSI: 6 Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: [sdj] Unit Not Ready Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: [sdj] Sense Key : 0x4 [current] Mar 13 20:56:39 Pithos kernel: sd 9:0:0:0: [sdj] ASC=0x30 <<vendor>>ASCQ=0x89 Mar 13 20:56:39 Pithos kernel: scsi 9:0:0:1: Attached scsi generic sg10 type 13 Mar 13 20:57:03 Pithos udevd[2433]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [2485] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4029]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4073] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4031]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4079] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4028]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4072] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4036]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4082] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4035]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4080] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4033]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4077] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4034]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4084] terminated by signal 7 (Bus error) Mar 13 20:58:09 Pithos udevd[4026]: '/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned reload >/dev/null 2>&1 & disown' [4081] terminated by signal 7 (Bus error) Mar 13 20:59:39 Pithos kernel: sd 9:0:0:0: timing out command, waited 180s SCSI Devices [0:0:0:0] disk Patriot Memory PMAP /dev/sda [1:0:0:0] disk ATA WDC WD40EZRX-00S 0A80 /dev/sdb [2:0:0:0] disk ATA TOSHIBA DT01ACA2 ABB0 /dev/sdc [3:0:0:0] disk ATA WDC WD50EZRZ-32G 0A80 /dev/sdd [4:0:0:0] disk ATA WDC WD7500BPKX-0 1A01 /dev/sde [5:0:0:0] disk ATA WDC WD40EZRX-00S 0A80 /dev/sdf [6:0:0:0] disk ATA Samsung SSD 840 BB0Q /dev/sdg [7:0:0:0] disk ATA WDC WD10EACS-00Z 1B01 /dev/sdh [8:0:0:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdi [9:0:0:0] disk WD My Book 1230 1065 - [9:0:0:1] enclosu WD SES Device 1065 -