sureguy
-
Posts
914 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by sureguy
-
-
5 hours ago, limetech said:
Correct.
Is that helpful from a usability standpoint? To me it seems confusing and unintuitive, perhaps I'm in the minority on that.
Aside from that the upgrade was successful
-
1
-
-
18 minutes ago, ogi said:
I just updated from 6.5.1 (via Tools -> Update OS) and am unable to load the webgui (get 502 Bad Gateway error).
I am able to ssh into the system. Welcome troubleshooting steps
See here for a possible solution:
What happens if you boot using safe mode?
-
58 minutes ago, gzibell said:
Anything in this version address realtek nic issues? Had to roll my server back from 6.6.0 to 6.5.3 as I kept losing all network connectivity.
Hold out hope for this or should I just order up an Intel nic?
Were I you, if I had an available slot I'd get an Intel nic that has (known) good Linux support. Intel has an important reputation that they need to maintain, more-so than Realtek. I don't know a single person that looks specifically for Realtek nics when building something mission critical. Probably not what you want to hear, I know, but I've been using an Intel nic in Unraid since about 2012 (82574L) without any real issues (jumbo frames seem not to work in Unraid).
A card with the same chipset can be had for less than $20 USD via ebay.
-
Still appears to be down for me, same error message as above. Legacy mode appears to work. I'm running 6.6.0-rc3, not sure if that is the cause.
-
I was never able to get this sorted out. I was able to boot into a live Ubuntu install and use Jumbo frames properly. Both my onboard NIC (Broadcom BCM57781) and an Intel Corporation 82574L Gigabit Network Connection did not work properly
I've subsequently replaced my router with an ER-X which doesn't support Jumbo frames, so no reason to pursue it on my end.
-
13 hours ago, cowboytronic said:
No not yet. It's easy to see the UPS power info I want at the command line with `apcaccess` but I don't know how to get the info into telegraf -> InfluxDB -> Grafana.
Yeah, I have auto-update for Docker containers, and every so often I lose all of my (non-HDD) temp sensors. When I notice a blank spot in my temperature chart I have to do this:
docker exec -ti telegraf /bin/sh apk update apk add lm_sensorsWhich is annoying. Anybody know how to either make lm_sensors stay added permanently, or auto-run these commands on any update?
I requested it on their git page - but aside from one other person asking for the same thing there's been no other traction.
You could just make a script that you can run after it's updated - you'd have to run it manually, but it's easier than having to remember the commands (apt vs apk etc).
-
Just a heads up gfjardim (the plugin creator) appears to have updated the preclear plugin for 6.5.0 compatibility.
It's available at:
https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/preclear.disk.plg
-
1
-
-
1 hour ago, realies said:
@limetech, good luck trolling. Let me know when you get bored of trying to reinvent the wheel.
@Frank1940, which webGui features in particular are "tied hand-in-hand" with the latest version of the OS? As to how one would expect this to be done, look at software packaging.
To be honest, I wouldn't get too hung up on the terminology - it's been discussed and the naming scheme is unlikely to change. I like how Squid explained it here :
-
On 1/14/2018 at 5:41 AM, sureguy said:
Sensors (CPU temperature etc):
The docker image doesn't come with lm_sensors - you need to add it:
ssh into unRAID and do the following:docker exec -ti telegraf /bin/sh apk update apk add lm_sensorsEdit your telegraf.conf and remove the # in front of [[inputs.sensors]]
Restart your telegraf docker.
15Just a small note that if there is a docker update you will have to perform the above steps again. At least I did after the last docker update.
-
I successfully precleared a 1TB drive with 3 cycles (pre and post read enabled). Notifications via notification agent worked.
-
12 minutes ago, Frank1940 said:
Oh, one more thing. Could someone download both versions and run the Linux command that lists the differences between these two files to make sure that the change documented is the only one! (I would do it but I have forgotten the command...)
1Done:
I downloaded both md5 summed them and ran diff against them - here's the output:
bishop@ubuntu-pihole:~$ md5sum preclear.new preclear.old 9b38439b09c9a763d50414a4a328485d preclear.new 739681c3298b9be7bacbf1ca5f5fc802 preclear.old bishop@ubuntu-pihole:~$ diff preclear.new preclear.old 395c395 < '7.2.0'|'7.3.0') --- > '7.2.0') -
31 minutes ago, wgstarks said:
I don’t see a link.
If you look at my post above, it's in there.
https://raw.githubusercontent.com/dohlin/unRAID-plugins/master/plugins/preclear.disk.plg
-
2 hours ago, John_M said:
Since the only change they made was to replace
case $gcc_version in '7.2.0')with
case $gcc_version in '7.3.0')won't that result in the wrong version of tmux being installed?
If you install the linked plugin it maintains backward compatibility as it replaces the gcc version line like so:
case $gcc_version in '7.2.0'|'7.3.0') -
1 minute ago, John_M said:
Since the only change they made was to replace
case $gcc_version in '7.2.0')
with
case $gcc_version in '7.3.0')
won't that result in the wrong version of tmux being installed?
Doesn't seem to. Tmux is probably being used in order to show the progress window (that's the only reason I can imagine that it's needed). And I'm running a preclear right now - and it's being used and outputting progress:
root@Phatstore:~# uname -a Linux Phatstore 4.14.16-unRAID #1 SMP PREEMPT Wed Jan 31 08:51:39 PST 2018 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux root@Phatstore:~# ps axu | grep tmux root 17733 0.0 0.0 27864 6304 ? Ss 11:28 0:06 /usr/bin/tmux new-session -d -x 140 -y 200 -s preclear_disk_5VP8L3B3 root 27355 0.0 0.0 9764 2108 pts/3 S+ 13:33 0:00 grep tmuxIncluded is a screenshot showing tmux installed by preclear_disk in nerd tools, and the current progress report.
-
1
-
-
55 minutes ago, wgstarks said:
That’s good to know. Which variable is used?
The script appears to use the mail command, which is not installed by default on unRAID (and isn't available from NerdPack). Without that installed email notifications will not work and the command will probably fail.
The options in the script would be:
-m [email protected] = optional recipient address. If blank and -M option is used, it will default to default e-mail address of "root" -M 1 = Will send an e-mail message at the end of the final results (default if -m is used, but no other -M option given) -M 2 = Will send an e-mail same as 1 plus at the end of a cycle (if multiple cycles are specified) -M 3 = Will send an e-mail same as 2 plus at the start and end of the pre-read, zeroing, post-read -M 4 = Will send an e-mail same as 3 plus also at intervals of 25% during the long tests The -m, -M options requires that a valid working mail command is installed. -
Dontlookoverthere over on the unRAID subreddit figured out how to get the plugin running again with a simple edit to the plg:
https://www.reddit.com/r/unRAID/comments/7wjpus/preclear_working_on_641/
Caveat emptor and all that. I'm testing it on a drive in my server presently, it seems to be working properly.
ohlin5 in the same post has provided an installable version that works with 6.4.1 and should maintain backwards compatiblity here:
https://raw.githubusercontent.com/dohlin/unRAID-plugins/master/plugins/preclear.disk.plg
-
6
-
1
-
-
6 hours ago, garycase said:
Compatibility with testing software isn't an issue -- any Windows system has a plethora of options (as I listed above); and there are several testing utilities for Macs as well.
It's true the system used to test a drive does indeed have to be on for the duration of the test -- whether it's your UnRAID server or another system.
As for the advantage of doing the test on your server -- that's a very minor advantage. It takes perhaps 20 seconds to pop a drive in my eSATA dock and start the testing. You do, of course, then have to install the drive in whatever system it's destined for after the test. If it's a drive destined for one of my UnRAID servers I suppose you can argue that's 20 seconds wasted -- but I think most would agree that's not much of a factor
.
You can't simply take your use case scenario, and then apply it to everyone else. Some people use unRAID simply as a media server and don't necessarily have a PC that can be on for extended periods of time for this work (a road warrior with only a laptop for work for instance). Some people may only have a work laptop, and consume media with hardware other than a PC. Most people won't have an e-sata dock like you have - e-sata was never a very popular technology. Your proposed solution requires a financial investment on the part of some of the (probably less technically savvy) members of the community for something that once required none.
If the preclear script can be made to work in unRAID 6.4.1 I really don't see the harm.
-
5 hours ago, garycase said:
Rather than "fiddle" with pre-clear issues, I simply no longer use it. Note that the utility was written for two purposes: (1) to eliminate the long downtime in an array when you added a disk -- which was not useable until it had cleared the new disk (this was arguably Joe's primary motivation for writing it); and (2) to test new disks to be sure there weren't any "infant mortality" issues.
#1 is completely obsolete => v6 clears new disks without any impact on array functionality.
#2 is easily done with any of the manufacturer's diagnostic utilities. I use WD's Data Lifeguard, but SeaTools, HGST's WinDFT, Toshiba's Storage Diagnostic, or any of the various 3rd party disk testing utilities (HDTune, Crystal Disk, etc.) can do this ... and these have the advantage that you can test your disk on another system without impacting the server.
When I get a new disk, I attach it to a spare SATA port on my desktop; then run Data Lifeguard and do a Short Test, Long Test, full Erase, and then repeat the short and long tests. ANY errors and I return the disk -- otherwise I add it to whatever system I bought it for (whether UnRAID, an HTPC, or one of our desktops).
To point #2 this assumes the user has a second system that is compatible with the software, and they want to run that system for an extended period of time (presumably without restarting it, etc). There is some advantage to doing a preclear on an unRAID system, especially if the intention is to add the drive to the array if it passes testing.
-
1
-
-
56 minutes ago, Frank1940 said:
Where (or at what point) in the preclear operation is this causing a problem? What are the symptoms? I seem to recall that someone had actually used Joe L's script successfully with 6..4.1.
If you run
preclear_disk.sh -lThe following error is generated as part of the output: ./preclear_disk.sh: line 236: strings: command not found
In regards to the /root/mdcmd issue, I'm not sure when that's called, I only noticed it because the same line also calls strings. Apparently the script still works with these issues - it will preclear the disk. The first instance of the strings command is reading super.dat. Off the top of my head that could be used to discern what drives shouldn't be precleared as they're part of the array.
-
Looks like unRAID 6.4.1 (not sure about 6.4.0) no longer has strings as a command, but does have strings-BSD which appears to output the same thing. There is also a call to /root/mdcmd which now resides in /usr/local/sbin/mdcmd - The following command will resolve both these issues:
sed -i -e "s|strings|strings-BSD|" -e "s|\/root\/mdcmd|\/usr\/local\/sbin\/mdcmd|" preclear_disk.sh
-
1
-
-
27 minutes ago, dmacias said:
I'll check into it
There's a strings-BSD in my unRAID
strings-BSD generates the same output as strings so I guess updating the script would be best. Thanks!
-
Any chance of getting strings as an installable command?
As the preclear plugin is no longer working, and users wanting to preclear need to rely on the script, it would be nice if it didn't generate any errors. Line 236 of the script calls strings but the command is not found.
I checked my Ubuntu VM, and my raspberry pi and both distros have the command included.
I don't know if this used to be part of the unRAID install and was removed for a valid reason or not - but it doesn't seem like a harmful utility:
Usage: strings [option(s)] [file(s)] Display printable strings in [file(s)] (stdin by default)Thanks.
-
6 hours ago, aptalca said:
Huh, you're right. I still get an error when listing (./preclear_disk.sh: line 236: strings: command not found) but the actual preclear works
Thanks
Looks like the strings command is missing - I'll ask if it can be added to Nerd Pack
Found a solution to the error, and another line that is incorrect. Issue the following to fix these errors:
sed -i -e "s|strings|strings-BSD|" -e "s|\/root\/mdcmd|\/usr\/local\/sbin\/mdcmd|" preclear_disk.sh
-
9 minutes ago, Squid said:
Are you sure the template that's showing in Previous Apps isn't identical (name, tag, etc) to the one you've got installed?
Yes. If I try to re-add the docker, it fails (as the ports are in use by the running dockers). I tried to add the docker, changing the ports/name (named it Influxdb2) which worked, but then 2 instances of the docker showed up under previous apps, One of the previous apps was named Influxdb and the other was Influxdb2
.
[Support] for atribe's repo Docker images
in Docker Containers
Posted
I have this strange issue with both the grafana and influxDB docker templates where Community Applications is convinced they're not installed but they are. I've tried recreating them (deleting the xml files and docker container image information) and then redownloading them via community apps and reconfiguring them. I keep my appdata in /mnt/cache/Docker/xxxxxxx which I know isn't standard, but this doesn't break any other docker container configurations.
Any thoughts?