BRiT

Where is this documented? Deep within the forums in a post somewhere.

You can not have a .page and .php file with the same base name. They must be combined in a single file or you must change the basenames.

If you do use dhcp, set up your dhcp server to use static settings for your known boxes.

Dynamix UI is built in to the latest available unRAID v6. You do not need to do anything.

I just wanted to add some more information related to this. Here are the readings from my Tyan 5512 based system: # ipmitool sdr CPU DTS value | 28 degrees C | ok CPU below tmax | 66 degrees C | ok PCI Area | 25 degrees C | ok SAS Case | 48 degrees C | ok CPU MOS Area | 24 degrees C | ok Ambient | disabled | ns DIMMA0 | 22 degrees C | ok DIMMA1 | disabled | ns DIMMB0 | 23 degrees C | ok DIMMB1 | disabled | ns CPU Vcore | 1.07 Volts | ok 3.3V | 3.29 Volts | ok 5V | 5.09 Volts | ok 12V | 12.19 Volts | ok VBAT | 3.36 Volts | ok Sys.1(CPU) | 1980 RPM | ok Sys.2(Front 1) | no reading | ns Sys.3(Front 2) | no reading | ns Sys.4(Rear 1) | no reading | ns Sys.5(Rear 2) | no reading | ns Sys.6 | no reading | ns Sys.7 | no reading | ns Sys.8 | no reading | ns Sys.9 | no reading | ns Sys.10 | no reading | ns PSU1 Present | Not Readable | ns PSU2 Present | Not Readable | ns And Sensors output to compare against, where I reconfigured the labels of the coretemp values so they would show up on the dashboard. # sensors acpitz-virtual-0 Adapter: Virtual device temp1: +27.8 C (crit = +95.0 C) temp2: +29.8 C (crit = +95.0 C) coretemp-isa-0000 Adapter: ISA adapter MB Temp: +28.0 C (high = +74.0 C, crit = +94.0 C) Core 0: +24.0 C (high = +74.0 C, crit = +94.0 C) Core 1: +25.0 C (high = +74.0 C, crit = +94.0 C) CPU Temp: +26.0 C (high = +74.0 C, crit = +94.0 C) Core 3: +23.0 C (high = +74.0 C, crit = +94.0 C) #ipmitool sdr| awk -F \| 'BEGIN{cpu="-";mb="-";fan="-"}{if(/^CPU DTS value/) cpu=$2*1; else if (/^CPU MOS Area/) mb=$2*1; else if (/Sys.1\(CPU\)/) fan=$2*1} END {print cpu,mb,fan}' 28 24 1980

You will likely want to do this in a Screen session, otherwise any disconnection in your telnet session will kill your preclear.

It's also a part of the NerdPack plugin.

cpio works fine for v6. I did that to check out the updates before being able to install them on my server. The only difference if there ever was any would be in what compression level it uses.

The registry for that docker isn't public or no longer exists. This can be verified by looking here: https://registry.hub.docker.com/repos/sparklyballs/

Latestis the version tag. This is needed to allow for proper use of dockers. This way the containers can be versioned just like the applications they run. It should work under beta14. I readded all of my docker co tainers under b14 without issue. If I have time, I'll see if I can add that particular docker you're using.

I assume your customized docker container is the none:none? If so, you need to signup for an account to the docker hub registry so you can store your container up there. Then once youre signed up, you need to commit and push your changes to the account and registry you setup. Then you can sagely readd your docker container using your new registry. The other option is you will have to manually recreate that custom docker from scratch. This is all beyond the scope of this thread. I suggest you create a new thread asking how to push your custom docker into docker hub registry.

Did you do a docker commit and docker push to a repository? If not, then you need to do that. You also need to add the docker through the ui so you create a my-templatefor it. Otherwise you will have to redo all the steps again.

And this is exactly why I use the modified script, since it makes 3 cycle preclear times a bit more manageable. A 3 cycle run on 4TB HGST drive is 74-75 hours. == invoked as: ./preclear_bjp.sh -f -c 3 -A /dev/sde == HGSTHDN724040ALE640 == Disk /dev/sde has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 12:11:43 (91 MB/s) == Last Cycle's Zeroing time : 8:39:55 (128 MB/s) == Last Cycle's Post Read Time : 12:17:47 (90 MB/s) == Last Cycle's Total Time : 20:58:46 == == Total Elapsed Time 75:07:02 == == Disk Start Temperature: 32C == == Current Disk Temperature: 35C, == invoked as: ./preclear_bjp.sh -f -c 3 -A /dev/sdc == HGSTHDN724040ALE640 == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 12:02:23 (92 MB/s) == Last Cycle's Zeroing time : 8:32:16 (130 MB/s) == Last Cycle's Post Read Time : 12:07:32 (91 MB/s) == Last Cycle's Total Time : 20:40:53 == == Total Elapsed Time 74:04:51 == == Disk Start Temperature: 28C == == Current Disk Temperature: 31C,

Something isn't right with those, your Pre-Read times are significantly slower than it should be. Here's snippets from January for 2 drives I precleared concurrently using the faster preclear script; first was 1 cycle, then both were run for 2 more cycles. ========================================================================1.15b == invoked as: ./preclear_bjp.sh -f -A /dev/sdl == HGSTHDN724040ALE640 == Disk /dev/sdl has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 12:08:15 (91 MB/s) == Last Cycle's Zeroing time : 8:36:35 (129 MB/s) == Last Cycle's Post Read Time : 12:12:10 (91 MB/s) == Last Cycle's Total Time : 32:58:09 == == Total Elapsed Time 32:58:09 == == Disk Start Temperature: 36C == == Current Disk Temperature: 37C, ========================================================================1.15b == invoked as: ./preclear_bjp.sh -f -A /dev/sdd == HGSTHDN724040ALE640 == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 12:01:58 (92 MB/s) == Last Cycle's Zeroing time : 8:30:13 (130 MB/s) == Last Cycle's Post Read Time : 12:06:48 (91 MB/s) == Last Cycle's Total Time : 32:40:07 == == Total Elapsed Time 32:40:07 == == Disk Start Temperature: 35C == == Current Disk Temperature: 36C, ========================================================================1.15b == invoked as: ./preclear_bjp.sh -f -c 2 -A /dev/sdl == HGSTHDN724040ALE640 == Disk /dev/sdl has been successfully precleared == with a starting sector of 1 == Ran 2 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 12:07:51 (91 MB/s) == Last Cycle's Zeroing time : 8:36:52 (129 MB/s) == Last Cycle's Post Read Time : 12:12:39 (91 MB/s) == Last Cycle's Total Time : 20:50:36 == == Total Elapsed Time 53:50:05 == == Disk Start Temperature: 35C == == Current Disk Temperature: 36C, ========================================================================1.15b == invoked as: ./preclear_bjp.sh -f -c 2 -A /dev/sdd == HGSTHDN724040ALE640 == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 2 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 12:01:55 (92 MB/s) == Last Cycle's Zeroing time : 8:30:12 (130 MB/s) == Last Cycle's Post Read Time : 12:06:54 (91 MB/s) == Last Cycle's Total Time : 20:38:11 == == Total Elapsed Time 53:18:20 == == Disk Start Temperature: 33C == == Current Disk Temperature: 35C,

This and other mini base images have been aleeady talked about and discarded as being viable due to one reason or another within these very forums.

Alright, based on that output your issue isnt caused from a full filesystem. Your cache drive and docker.img have plenty of free space. At least they report as such. I dont exactly know what steps to take next on trying to fix the btrfs issues. There is a filesystem check profram. Hopefully jonp or eric or LimeTech or one of the moderators can step in to help further.

I only have one BTRFS-disk, the cache disk. Not exactly true. Inside the docker.img itself is a BTRFS filesystem.

What does the following command show for /var/lib/docker and /mnt/cache? df -h Your docker.img might be full and needs to be recreated, or your cache drive might have issues. Its hard for me to tell from the log which BTRFs is having the issue.

Also, I'm thinking that the archival programs such as most up to date versions of rar, unrar, 7zip, unzip, tar, par2 should be contained in their own Archival Plugin Pack. Then the developer tools like git, subversion, cvs, rcs would be in their own Developer Repository Plugin Pack as well.

If git doesn't have large dependencies you could try pulling this then using "installpkg" on it: wget http://mirrors.slackware.com/slackware/slackware64-14.1/slackware64/d/git-1.8.4-x86_64-1.txz -O /tmp/git-1.8.4-x86_64-1.txz installpkg /tmp/git-1.8.4-x86_64-1.txz

Its been known to take 2 to 3 minutes depending on what sensors your motherboard has. Im going off my personal experience as documented in this thread. Its possible other systems could take 3 seconds or could take 10 minutes or more. But during this time the page showed as busy with the browser status spinning until it completes.

After you hit [Detect] did you hit [save]? The detect button switches to save after it's finished.

It takes anywhere from 2 to 3 minutes to complete all because of the 1 sensor it's trying to probe. I'll have that output in a couple minutes. The part that takes the 2-3 minutes is this driver: Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH) The real driver that I used when I ran my own kernel on full slackware64bit was ipmi (something), which I have asked to be compiled and included in the next unRAID release. And now the full output... # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # System: TYAN S5512 [empty] This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors' (but not activated) Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Found `IPMI BMC KCS' at 0xca8... Success! (confidence 8, driver `to-be-written') Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH) Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca8 Chip `IPMI BMC KCS' (confidence: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules.

It takes anywhere from 2 to 3 minutes to complete all because of the 1 sensor it's trying to probe. I'll have that output in a couple minutes.

That results in finding the 2 drivers, where one is yet to-be-written. ~# yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*" coretemp to-be-written Try again with the svn version: wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect yes ''|perl /tmp/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*" Similar results, but when I put the change into the dynamix page setting I get 1 more to select in the dropdown (acpitz) wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect --2015-02-03 19:02:16-- http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect Resolving www.lm-sensors.org (www.lm-sensors.org)... 160.45.254.26 Connecting to www.lm-sensors.org (www.lm-sensors.org)|160.45.254.26|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 209836 (205K) [text/plain] Saving to: ‘/tmp/sensors-detect’ 100%[=====================================================>] 209,836 172KB/s in 1.2s 2015-02-03 19:02:18 (172 KB/s) - ‘/tmp/sensors-detect’ saved [209836/209836] # yes ''|perl /tmp/sensors-detect 2>&1|grep -Po "^Driver.{2}\K[^\']*" to-be-written coretemp For completeness, here's the patched changes into TempSettings.page function detect_modules(){ $mods = array(); exec("yes ''|perl /usr/sbin/sensors-detect 2>&1|grep -Po \"^Driver.{2}\K[^\']*\"", $matches); foreach ($matches as $mod) if (exec("modprobe -D $mod 2>/dev/null")) $mods[]=$mod ; return $mods; }