gfjardim

You're welcome!

Attached. Err, wrong command... Could you please try again? bash -x /usr/local/emhttp/plugins/preclear.disk.beta/script/preclear_disk.sh /dev/sde >/boot/preclear_beta.txt 2>&1 Thanks

Please run the command below and send the the file preclear_beta.txt created on your flash drive: bash -x /usr/local/emhttp/plugins/preclear.disk.beta/script/preclear_disk.sh /dev/sde >/boot/preclear_beta.txt

# source unRAID version . /etc/unraid-version download_install() { local dest="&plugin;/packages/${1}" local src="&repo;/packages/${1}" local md5=$2 if [ ! -f "${dest}" ]; then curl --location --silent --fail "${src}" --output "${dest}" fi file_md5=$(/usr/bin/md5sum ${dest}) if [ "${file_md5:0:32}" != "${md5:0:32}" ]; then echo "Wrong '${1}' package md5 hash." rm "${dest}" exit 1 else /sbin/installpkg "$dest" fi } if [ "$version" == "6.2.0-beta18" ]; then spl_pkg="spl-0.6.5.5-unRAID6.2.0-beta18.x86_64.tgz" spl_md5="6bab826e24b0c3ccc08b962e8a64058c" zfs_pkg="zfs-0.6.5.5-unRAID6.2.0-beta18.x86_64.tgz" zfs_md5="1ee9e5c1d85155ef87138aaee78aefb6" elif [ "$version" == "6.1.9" ]; then spl_pkg="spl-0.6.5.4-unRAID6.1.9.x86_64.tgz" spl_md5="ef09a51f6fcc069ad4897b5e06088d00" zfs_pkg="zfs-0.6.5.4-unRAID6.1.9.x86_64.tgz" zfs_md5="74ee8f3698cd6f64839bcdf09abe5534" elif [ "$version" == "6.1.8" ]; then spl_pkg="spl-0.6.5.4-unRAID6.1.8.x86_64.tgz" spl_md5="3ef7a7eb63bac07475dc7e9eee5132c5" zfs_pkg="zfs-0.6.5.4-unRAID6.1.8.x86_64.tgz" zfs_md5="ae2c5bd933f1376b52a73a07862db2bc" elif [ "$version" == "6.1.7" ]; then spl_pkg="spl-0.6.5.4-unRAID6.1.7.x86_64.tgz" spl_md5="288b0b4c242fe947f41a2a4a1f731982" zfs_pkg="zfs-0.6.5.4-unRAID.1.7.x86_64.tgz" zfs_md5="57e386538e4726dd222c8bd682975705" elif [ "$version" == "6.1.4" ]; then spl_pkg="spl-0.6.5.3-unRAID6.1.4.x86_64.tgz" spl_md5="41700aaec22f70d2ae257544d6f53695" zfs_pkg="zfs-0.6.5.3-unRAID6.1.4.x86_64.tgz" zfs_md5="31b8ee8c406f211a78c7dbf56ba2609e" elif [ "$version" == "6.1.3" ]; then spl_pkg="spl-0.6.5.3-unRAID6.1.3.x86_64.tgz" spl_md5="8b0c880280b722fb1948dd9d0e3362b9" zfs_pkg="zfs-0.6.5.3-unRAID6.1.3.x86_64.tgz" zfs_md5="33401b97ae99a5f17aef4524bd5122cc" elif [ "$version" == "6.1.2" ]; then spl_pkg="spl-0.6.5.1-unRAID6.1.2.x86_64.tgz" spl_md5="644f7c6a682b6b9d607f5a7337205d16" zfs_pkg="zfs-0.6.5.1-unRAID6.1.2.x86_64.tgz" zfs_md5="cdefbb81f0de70cdb876a4625abb4c88" else exit 1 fi download_install "${spl_pkg}" "${spl_md5}" download_install "${zfs_pkg}" "${zfs_md5}"

Here it is, guys: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/preclear.disk.beta.plg It will add a Preclear Disk Beta icon under Settings. How to test it: 1) Pick a formatted disk or format it with Unassigned Devices and copy some files to it; 2) Go to Settings/PreclearBeta and start a Clear operation; 3) Once it's over, please run a Verify All the Disk operation; 4) If successful, please run both Test and Run the post-read verify operations from the older plugin; 5) If possible, assign the precleared disk to the array and start a Check Parity operation. All feedbacks are pretty much appreciated.

Seem like the timming is almost perfect. The new script is mostly completed. The only significant missing feature is the SMART relatories. Will try to speedup things.

I appreciate if you all can test it soon.

I'll license it under GPL like I did on Unassigned Devices. Developing a plugin is one task, it's concentrated in time, but bugfixes, improvements and support are long term tasks that may need some succession in development. Guys, I need some people to test/validate this new script. I'll release a testing version of the new Preclear Plugin within the next week or so.

I can't get in touch with him. He won't respond to PM or topic questions. I think he knows what I'm doing, but he won't participate. Either way, it's a bummer. The original script was written while unRAID used BASH 3.2., I guess. The code is linear, and it's difficult to modify one thing without borking others. It's more a rework of the original code, incorporating things like associative arrays and trying to contain the variables inside functions, avoiding the disseminated use of global variables. No other functionality is planned beyond the actual scope. They are basically the same code. When bjp999 took the code to improve it, he was hands tied. He couldn't modify it extensively, so he opted to use a binary executable to speedup the post-zeroing verification. The problem in the original code is that post-zeroing read executes two reads on the same area, so it actually reads twice the disk. It's not necessary and it makes the code confusing. I removed that part. Other problem I corrected is that some of the last blocks of the disk eventually weren't read, and that I got fixed too. I fixed that disks.cfg and super.dat problem too. I'm not removing the support to the original script right now. I'm proposing a new code that would eventually meet the same confidence we have in the current one. It need a lot more testing before we can pull the plug. And the confusion always exists. We can't make a omelet without breaking some eggs. Have you any real news about that?

Since I can't get authorization of Joe L. to distribute the preclear script, I'm writing a new script for it. Right now I have all the basic functionality working, aka preclear and test preclear. Since support all legacy functions takes time, I want to know if anyone is preclearing disks with partition starting on block 63, and if anyone have converted from block 64 to block 63 or vice versa in the last year.

If your unRAID's time zone is set, CrashPlan should adopt it.

USB3 is at 00.1a.0, and USB4 at 00.1d.0.

USB3 and USB4 are on different pci devices....

With some flash drives attached, please sun this: echo "unRAID - > " $(udevadm info -q path -n /dev/disk/by-label/UNRAID |grep -Po '0000:\K\w{2}:\w{2}\.\w{1}' ) for d in /dev/disk/by-id/usb-*; do echo "$d -> " $(udevadm info -q path -n $d |grep -Po '0000:\K\w{2}:\w{2}\.\w{1}')|column -t ; done See if any device is on a different PCI bus.

This kind of problem usually is related to the Mover script moving files from the cache disk to the array... How do I stop this sorcery? Go to Shares, select appdata and then set Use cache disk: to Only. Hit apply and you're done.

This kind of problem usually is related to the Mover script moving files from the cache disk to the array...

It's just an alert to people; your question may being already answered, so take a look into the OP.

Please, guys, always look at the OP before asking a question:

Another script that will unmount the disk after server's backup using an Unassigned Devices disk: #!/bin/bash # Set UNRAID_ADDR to "172.17.42.1" and set UNRAID_PASS if your container's network is set to bridge. UNRAID_ADDR="127.0.0.1" UNRAID_PASS="" MOUNT="/backup" CHANNEL="1" # Available Channels # # 1 = notify using browser-popups only; # 2 = notify using e-mail only; # 3 = notify using browser-popups and e-mail; # 4 = notify using agents only; # 5 = notify using browser-popups and agents; # 6 = notify using e-mail and agents; # 7 = notify using browser popups, e-mail and agents; send_notify() { curl -s -d "cmd=add" \ -d "e=${1} " \ -d "s=${2}" \ -d "d=${3}" \ -d "i=normal ${CHANNEL}" \ -u "root:${UNRAID_PASS}" "http://${UNRAID_ADDR}/webGui/include/Notify.php" } unassigned_umount() { device=$(cat /proc/mounts 2>/dev/null|grep "${MOUNT}"|grep -v 'rootfs'|cut -d' ' -f1|head -n1) if [[ -n $device ]]; then send_notify "Unassigned Devices: umounting disk '$(basename ${device})'" \ "Unassigned Devices: the disk '$(basename ${device})' is being unmounted." curl -s -d "action=umount" \ -d "device=${device}" \ -u "root:${UNRAID_PASS}" "http://${UNRAID_ADDR}/plugins/unassigned.devices/UnassignedDevices.php" fi } CP_LOG="/config/log/history.log.0" while read line ; do # unRAID's backup finished if [[ $line =~ .?(Completed[[:space:]]backup[[:space:]]to[^:]*)(in .*) ]]; then send_notify "CrashPlan: Backup completed" "${BASH_REMATCH[1]}." "${BASH_REMATCH[@]}" unassigned_umount fi done < <(tail -fn0 $CP_LOG)

Mainly two: short file path and in the flash filesystem all scripts have the execution bit already set.

You're welcome! Just to help others, the problems were: 1) a script error, now fixed; 2) DOS line endings while saving the script. In this case, my advise is to open a SSH session using Putty and paste the content using VI or NANO. []'s

Very strange.

There's no need to cahnge the IP when you're using HOST network mode. When you change it, you must supply the webGui password too. Leave it as 127.0.0.1, it's the local IP address of your server. To test, simply start a backup.

That's the Docker IP; obviously, you can change it with your server IP address. You -can- ? Or you should ? My server is hosted on 192.168.1.13. Should I use that IP address ? I think it will give you the same results, that's why I used "can" instead of "should". Use your server's IP address and let me know if it works.

That's the Docker IP; obviously, you can change it with your server IP address.