gfjardim

Will try to add it, since I based this script on Joe L. version, not bjp999 one. Will run a diff and see what I need to change.

Hi guys, this is a simple plugin that allows users to clear their disks before add them to the array. The main characteristics of this plugin are: Modularity: can be used standalone or in conjunction with Joe L. or bjp999 scripts; Ease of use: with a few clicks you can start a clear session on your disk; Integration: you can always access the plugin under Tools > Preclear Disk menu. If you have Unassigned Devices installed, you can start/stop/view preclear sessions directly from Main > Unassigned Devices. All dependencies included: you don't need SCREEN to run a preclear session in the background; all jobs are executed in the background by default, so you can close your browser while the preclear runs. You can install it directly or via Community Apps. Q & A: Q) Why Joe L. or bjp999 scripts are not included? A) I'm not authorized by Joe L. to redistribute his script, so you need to download a copy from the topic above and put it under /boot/config/plugins/preclear.disk/ renaming it to preclear_disk.sh if necessary. bjp999 modifications are unofficial, so I decided not to include it by default. A) the bjp999 script is now included by default. Q) By default, I see a "gfjardim" script always available. Why? A) Since I'm not authorized to redistribute Joe L. script and the recent slow support by the author, I decided a major code rewrite in the script was needed. The new script is being actively supported, compatible with unRAID notifications, is faster than bjp999 script and has a cleaner output so users can easily visualizes what's going on with their disks. Q) I want to use one of the older scripts(Joe L. or bjp999) in conjunction with notifications. Is that possible? A) Yes. I've made some adjustments on both scripts so they become compatible with unRAID notifications; Joe L. version can be found here and bjp999 can be found here. A) the bjp999 script is now included by default; it includes support for Unraid notifications. Q) Is there any howtos available? A) gridrunner made a awesome video explaining why preclearig a hard disk is a good idea, and how you can accomplish that: Q) The plugin asked me to send some statistics information. How does the statistics report system work? Is it safe? Is it anonymous? A) To better track the usage of the plugin, a statistics report system was put in place. The main goals I intend to archive are: know number of disks that gets precleared; fix any silent bugs that gets reported on the logs; know average size of disks, their model, their average speed and elapsed time we should expect from that model; success rate; rate of disks with SMART problems; This system is totally optional and users will get prompted if they want to send each report. It is also safe and totally anonymous, since all data is sent to Google Forms and no identifying data is exported, like disks serial numbers. Detailed info can be found here. The statistics are public and can be found here. Q) How can I download a copy of the plugin log? A) Please go to Tools, then Pleclear Disk, and click on the Download icon: Q) Which are the differences between Erase and Clear? A) The Clear option uses zeroes to fill the drive; at the end, the drive can be added to the array the array immediately. The Erase All the Disk option uses random data to wipe out the drive; the resulting drive can't be quickly added to the array. If you want to add if after erase, you must select Erase and Clear the Disk. Troubleshooting: Q) After Zeroing the disk, the Post-Read operation fails saying my drive isn't zeroed. A) When zeroing the disk, the script uses a zero filled data stream produced by the pseudo-device /dev/zero. If a Post-Read fails just after a Zeroing operation, chances are that you have bad RAM memory, or less frequently bad PSU, bad cables or bad SAS/SATA card. Please run some rounds of MEMTEST on your machine to test your RAM modules. Q) A Pre-Read operation failed and I see Pending Sectors on the SMART report. A) Pending Sectors will lead to read errors, and the Pre-Read operation will fail. To force the hard drive firmware to remap those sectors, you have to run a Preclear session with the Skip Pre-Read option checked. Q) I've lost communication with the webgui, can I manage preclear sessions from the terminal? A) Yes, you can. If you lost communication with the webgui or want to use the command line interface to manage your preclear sessions, you just need to type preclear on your terminal to start/stop or observe a preclear session.

It depends of what services/steps you need your plugin to precede/supervene. LT just postponed VMs and Docker init from disks_mounted to started. I think I will do it for my VirtualBox plugin as well. What is the equivalent unmounting state? When does LT stop the VM and Docker? stopping_svcs event.

It depends of what services/steps you need your plugin to precede/supervene. LT just postponed VMs and Docker init from disks_mounted to started.

It's an additional container on my repository. Wow, I'm not sure how I missed this! I want to try it out, but I've been reviewing the code: https://github.com/gfjardim/docker-containers/tree/master/crashplan-desktop and it seems like it stores everything inside the Docker container? Would you considering setting it up a little more like the standard crashplan: https://github.com/gfjardim/docker-containers/blob/master/crashplan/config.sh so we don't have to adopt the account and re-synchronize every time the docker changes? That's just the GUI. There's no backup service running into it.

It's an additional container on my repository.

jonp, I was thinking, this method of yours, the two step passthrough, is much safer than the simple passthrough without the pci-stub step. This could make passthrough of USB/SATA/Ethernet pretty much doable via the VM Manager plugin. Is Eric working on something like this on the present moment? PS: little code to find in which pci bus is unRAID's usb drive: udevadm info -q path -n /dev/disk/by-label/UNRAID |grep -Po '0000:\K\w{2}:\w{2}\.\w{1}'

I know that. This code only shows you which NIC is eth(n) and the PCI id. It's designed to gather info for your method, not to replace it. If, for an example, I wish to passthrough the unconnected NIC of my board, I can easily do so. It makes easier to pin a NIC to the physical port.

A easier method of discovering the right card to passthrough is running: #!/bin/bash for ETH in $(find /sys/devices/ -type d -iname "eth[0-9]"); do port=$(basename $ETH); export $(cat $ETH/device/uevent); link_status=$(cat $ETH/operstate); desc=$(lspci -d $PCI_ID| cut -d ':' -f3) pci_bus=$(echo $PCI_SLOT_NAME|sed -e 's#0000:##') echo -e "Found NIC: $port\n Name: $desc\n PCI id: $PCI_ID\n PCI bus: $pci_bus\n Status: $link_status\n" done

Digital Devices Cine v6.5: 03:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter

Added a container for CrashPlan Desktop GUI. It's based on SparklyBalls desktops and can be reached by RDP at port 3389.

Updated DropBox and ownCloud, both with invaluable contribution of HurricaneHernandez!

Added port maps (still default to host network since it's an UPnP server) and rename it to Emby. Container got updated too.

Hi, Bungy. Could you add support for this? http://lime-technology.com/forum/index.php?topic=39106.msg365627#msg365627 Thanks in advance!

Hi, Spants. Could you add support for this? http://lime-technology.com/forum/index.php?topic=39106.msg365627#msg365627 Thanks in advance!

Here it is, guys, a centralized topic for support to my containers. For specific container support, please go to the appropriate topic: CrashPlan: http://lime-technology.com/forum/index.php?topic=33864.0 ownCloud: http://lime-technology.com/forum/index.php?topic=33891.0 If you need needo's support, please go here: http://lime-technology.com/forum/index.php?topic=33822.msg312539.0 Update requests can be made here or by PM.

That's mean! We have so many projects that somethings just got lost in the way.

So I'm having the same problem. I looked to make sure that the ip/port settings are correct. I even redeployed the docker several times, and on redeploy I'm able to connect to CrashPlan for a while. Then I'm not able to reconnect, the launcher on Windows just stays open, but does not say unable to connect to server. And it will actually stay open for a while and close when I shutdown the docker. So I know there is some sort of connection being formed. The only thing that I've come across is: http://support.code42.com/CrashPlan/Latest/Troubleshooting/Unable_To_Connect_To_The_Backup_Engine#Linux_Solution And I noticed in the docker file that one language is not en_US like the rest. I don't know if this is related or not as I haven't figured out yet how to manually edit the docker file. Ok, found the potential flaw, now I'll try to solve it.

Thanks. I've patched this a while ago, just waiting bonienl to release the update.

Can you post the output for these?

Your sysfs structure is very different from mine. Let's try some other commands: ls -la `dirname $(find /sys/devices -iname "fan*_input")` ls -la `dirname $(find /sys/devices -iname "pwm[0-9]")`

Please post the result of this command: find -L /sys/class/hwmon/ -maxdepth 5 -iname "pwm[0-9]" 2>/dev/null Here you go: /sys/class/hwmon/hwmon1/device/pwm1 /sys/class/hwmon/hwmon1/device/pwm2 /sys/class/hwmon/hwmon1/device/pwm3 Those are the three possible pwm controls from my it87 board. Ok, I need one last command output: find /sys/devices -iname "hwmon[0-9]" -exec echo {} \; -exec ls -la {} \;

Please post the result of this command: find -L /sys/class/hwmon/ -maxdepth 5 -iname "pwm[0-9]" 2>/dev/null

Yes, I modified that script to import variables from a file. It's working fine right now. Will keep you posted about any news.

I followed these steps also, and got these drivers... coretemp nct6775 I already had coretemp working, but wanted to see if nct6775 would give me fan speed info, so I put that in the available drivers box, hit detect, then hit load drivers, and now I have more stuff available in my dropdown boxes; see attached. I don't really know which one goes with which, but it feels like progress. I use coretemp - Physical id 0 to CPU and SYSTIN to Motherboard.