RobJ

I added tips on the Tips and Tweaks wiki page for ken-ji's tips on disabling FTP and Telnet. Naturally, it would be nice to see a built-in method in unRAID for controlling net services, but until then this should help. I'd appreciate any critiquing of the wording I used.

Sorry for the lack of any responses, and I'm no help either! I suppose we would be looking for any improvement in network speed, under various conditions such as a single huge file transfer, multiple simultaneous file transfers, heavy multi-user use, etc. Timing and comparing a single transfer would be a fair measurement, I think. You could time the single transfer by itself, then while other transfers are also happening, and while other heavy usage is transpiring. Time them under lower and higher RX and TX values. Maybe it won't make any significant difference! (which would be good to know!)

I know you said earlier that "I don't think this plugin should be making unRAID system changes", so I suspect you won't be interested! Have a look at this thread. It's about disabling Telnet and FTP, something that would be nice, safer for many. This would of course be a stopgap measure, be better built into unRAID, but would be nice for now.

Just an observation, from a lazy observer, feeling too lazy to properly study every one of the long reports here - I can't see any point in testing with nr_requests=128. I did a cursory search and never saw a test where nr_requests=128 was better (beyond margin of error) than nr_requests=8 or 16. Even at 128's best, 8 or 16 was essentially the same. I think I would test at 16 only, and determine the best of the other numbers, then at the end just 2 more tests, both 8 and 32, and pick the best of these 3. If you wish and 32 is better, then you could test 128. Or if 8 is better, then test 4. But I think you're essentially done once you've picked between 8, 16, and 32. Just my opinion, based on less experience than either of you. (Or you can do all tests at 8 only, then test upward at the end.)

I'm sure you've thought of it, but you could do your own updating, drop the -f that keeps it open. tail; save; display; wait 15 or 30 seconds; (or 5 - 60?) tail; compare with saved; if same continue looping; if different: save; display; continue;

What we use in the diagnostics is lspci -knn and lsscsi -vgl (that's a lowercase L). All you need (I think) is lspci and lsscsi -v. Unfortunately, it's not straightforward, as some PCI devices are used directly, and others are used through other PCI devices. For example, given the following from mine - root@JacoBack:/boot# lspci 00:00.0 RAM memory: NVIDIA Corporation MCP55 Memory Controller (rev a1) 00:01.0 ISA bridge: NVIDIA Corporation MCP55 LPC Bridge (rev a2) 00:01.1 SMBus: NVIDIA Corporation MCP55 SMBus Controller (rev a2) 00:01.2 RAM memory: NVIDIA Corporation MCP55 Memory Controller (rev a2) 00:02.0 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a1) 00:02.1 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a2) 00:04.0 IDE interface: NVIDIA Corporation MCP55 IDE (rev a1) 00:05.0 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:05.1 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:05.2 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:06.0 PCI bridge: NVIDIA Corporation MCP55 PCI bridge (rev a2) 00:0a.0 PCI bridge: NVIDIA Corporation MCP55 PCI Express bridge (rev a2) 00:0b.0 PCI bridge: NVIDIA Corporation MCP55 PCI Express bridge (rev a2) 00:0d.0 PCI bridge: NVIDIA Corporation MCP55 PCI Express bridge (rev a2) 00:0e.0 PCI bridge: NVIDIA Corporation MCP55 PCI Express bridge (rev a2) 00:0f.0 PCI bridge: NVIDIA Corporation MCP55 PCI Express bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 03:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02) 03:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02) 04:00.0 Mass storage controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01) 05:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 06:00.0 VGA compatible controller: NVIDIA Corporation NV44 [GeForce 7100 GS] (rev a1) root@JacoBack:/boot# lsscsi -v [0:0:0:0] disk PNY USB 2.0 FD PMAP /dev/sda dir: /sys/bus/scsi/devices/0:0:0:0 [/sys/devices/pci0000:00/0000:00:02.1/usb1/1-2/1-2:1.0/host0/target0:0:0/0:0:0:0] [2:0:0:0] disk ATA ST3250620AS E /dev/sdd dir: /sys/bus/scsi/devices/2:0:0:0 [/sys/devices/pci0000:00/0000:00:0d.0/0000:04:00.0/ata3/host2/target2:0:0/2:0:0:0] [4:0:0:0] disk ATA WDC WD6401AALS-0 3B01 /dev/sdb dir: /sys/bus/scsi/devices/4:0:0:0 [/sys/devices/pci0000:00/0000:00:05.0/ata5/host4/target4:0:0/4:0:0:0] [5:0:0:0] disk ATA ST3500630AS K /dev/sdc dir: /sys/bus/scsi/devices/5:0:0:0 [/sys/devices/pci0000:00/0000:00:05.0/ata6/host5/target5:0:0/5:0:0:0] [6:0:0:0] disk ATA SAMSUNG SP2504C 0-33 /dev/sde dir: /sys/bus/scsi/devices/6:0:0:0 [/sys/devices/pci0000:00/0000:00:0d.0/0000:04:00.0/ata4/host6/target6:0:0/6:0:0:0] [7:0:0:0] disk ATA ST2000DM001-9YN1 CC47 /dev/sdf dir: /sys/bus/scsi/devices/7:0:0:0 [/sys/devices/pci0000:00/0000:00:0b.0/0000:03:00.0/ata7/host7/target7:0:0/7:0:0:0] [8:0:0:0] disk ATA ST3500630AS E /dev/sdh dir: /sys/bus/scsi/devices/8:0:0:0 [/sys/devices/pci0000:00/0000:00:05.1/ata9/host8/target8:0:0/8:0:0:0] [9:0:0:0] disk ATA ST2000DM001-9YN1 CC49 /dev/sdg dir: /sys/bus/scsi/devices/9:0:0:0 [/sys/devices/pci0000:00/0000:00:0b.0/0000:03:00.0/ata8/host9/target9:0:0/9:0:0:0] [10:0:0:0] disk ATA ST3000DM001-1CH1 CC27 /dev/sdi dir: /sys/bus/scsi/devices/10:0:0:0 [/sys/devices/pci0000:00/0000:00:05.1/ata10/host10/target10:0:0/10:0:0:0] [11:0:0:0] disk ATA TOSHIBA MD04ACA5 FP2A /dev/sdj dir: /sys/bus/scsi/devices/11:0:0:0 [/sys/devices/pci0000:00/0000:00:0e.0/0000:05:00.0/ata11/host11/target11:0:0/11:0:0:0] [14:0:0:0] disk ATA Hitachi HDS72101 A39C /dev/sdl dir: /sys/bus/scsi/devices/14:0:0:0 [/sys/devices/pci0000:00/0000:00:05.2/ata15/host14/target14:0:0/14:0:0:0] [15:0:0:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdk dir: /sys/bus/scsi/devices/15:0:0:0 [/sys/devices/pci0000:00/0000:00:0e.0/0000:05:00.0/ata12/host15/target15:0:0/15:0:0:0] [16:0:0:0] disk ATA TOSHIBA DT01ACA3 ABB0 /dev/sdm dir: /sys/bus/scsi/devices/16:0:0:0 [/sys/devices/pci0000:00/0000:00:05.2/ata16/host16/target16:0:0/16:0:0:0] The drive sdb is on a motherboard port. The drive sdk is on the Asmedia card, through the 0000:00:0e.0 bridge.

All 3 drives are fine, no issues seen. The white label drive looks like a WD, same SMART attributes.

I've modified the XFS conversion post (found here), and added warnings to it, marked in blue. I'm afraid it never occurred to me that anyone would be modifying the original drive during the conversion, but it's probably a relatively common occurrence. I often do things differently than most people, and need feedback like yours to correct me. Please review what I've written, and tell me if it could be improved, and any other suggestions you may have.

For some, perhaps for many, the tail is all they want or need. It's hard for me to imagine wanting to study an entire syslog on a small screen.

No, "near threshold" values are almost always false positives, and the feature should probably have been fixed a long time ago. Apart from 2 numbers, it looks like any other modern Seagate SMART report, for first month usage. They have discontinued Runtime_Bad_Block, which doesn't surprise me as it was redundant, confusing therefore. One mildly troubling number is Hardware_ECC_Recovered, which has already dropped to 8. It is encoded into the same number fields as Raw_Read_Error_Rate (same RAW number), but it's not marked as a 'critical attribute' so can't fail the drive. Raw_Read_Error_Rate *is* a critical one, and looks possibly worrisome, having dropped already to 64 (usually 100 or higher for the first years). Everything else looks fine. Since this is the first instance we've seen of the drive, it may be too soon to draw any conclusions yet, about your specific drive.

Just ignore it. I have to check the time against an internet server that reports the unix epoch time and if something happens on it then the error also results. I just re-ran the tests and everything is ok, so whatever issues that server was having is now fixed. Another example, with a little more detail: No problem on Aug 11, claims clock off by 5 hours 8 minutes (so not a timezone issue) on Aug 12. Noticed this message about 9:30am, did a plugin check at 9:47am just to put a timestamp into log, and it was perfect. No apparent clock corrections, just a check against the wrong time (under some condition, randomly generated?). (still on 6.1.9)

I'm a little late here, but there's a wiki page that may be of help - Files on v6 boot drive The last section of the page is about Starting Over.

Setup of the card looks fine, no issues at all that I could see. But nothing happens afterward, even after a long delay. I don't see any evidence of even setting up the individual drive channels, let alone the drives themselves. I'd check your configuration, I don't think it's setup right. Make sure it's set to JBOD or individual drive access, with the right firmware. No other ideas...

Additional FAQ entries requested - * linking between containers, ie between sab and sickbeard - this might be best for specific author support FAQ's, as to how their containers should be linked * folder mapping - sufficiently covered yet? more needed? * port mapping - probably need both a general FAQ here, and individual FAQ's for many of the containers * location for the image file - answered in Upgrading to UnRAID v6 guide, but should be here too * where to put appdata - probably need a general FAQ here, but could use individual FAQ's for some containers Squid, or anyone else, I know you're busy, but if/when you have time, could you comment on the list above - which ones are covered sufficiently, and which could use more or better info?

Bumping this for knowledgeable authors ...

Squid has created an excellent guide to creating your own Docker templates (in the Docker FAQ) - How Do I Create My Own Docker Templates?

There are a number of issues - * You have IDE emulation turned on for some of your onboard SATA ports, and at the moment the SSD is using one. In fact, perhaps because the BIOS is from early 2011, something about the SSD is odd enough that the kernel slowed down the speed to the SSD, to UDMA/33, because it thinks it's using a "40-wire cable", instead of the standard 80-wire IDE cable! When you next boot, go into the BIOS settings and look for any SATA modes, and change it to a native SATA mode, preferably AHCI if available, anything but IDE emulation mode. It should be faster, and a little safer. * You really need to clean up the plugins loaded. Your system is an unhappy mix of old and new. It looks like you may have started with a v6 beta from early 2015, and never cleaned off the old stuff installed back then. - You are installing dynamix.kvm.manager.plg, which is almost certainly incompatible. - It finds and tries to install an old version of dynamix.plg, but recognizes it as old and skips it. - It installs both the Preclear beta plugin and the Preclear plugin, which is a problem, because it installs the beta plugin first and all of its dependencies, then installs the older Preclear plugin, and uninstalls(!) all of the dependencies of the beta plugin, then installs the older versions of those dependencies for itself. So you are trying to run the Preclear beta plugin without the dependency functions it was designed for. - It installs both the old and incompatible SNAP plugin, and the new and current Uninstalled Devices plugin. - It starts UnMENU, and I can't tell what it loads, but it should be checked to see if it's loading something that's too old. - Some or all of the above are almost certainly affecting stable behavior of the system. Difficulty running any Preclears is not at all surprising. * At some point, it would be a good idea (I think) to re-prepare your unRAID boot drive, and only add those functions you truly need. With a 1.5GHz processor, you will have some difficulty running very much at the same time, so you may want to limit how much is installed.

I assume you want wine from the faucet too!

So i have question on the "Edited unofficial faster Preclear script (command line only)" part of the comment above for the beta plugin. If the script is stand alone and there is not script to run in the folder \\tower\flash\config\plugins\preclear.disk.beta how is this run. I think you may have missed his point, those are 4 separate choices for Preclearing with 6.2. You can use the beta (which doesn't need a script), or you can use the regular Preclear with either of the scripts (modified), or you can use either of the scripts (probably modified) at the command line.

That guide does still work. However, I've made some improvements, and documented a complete step by step procedure here. I think once you've read and understood the details of how both procedures work, you can invent your own customized procedure.

I've seen at least 2 users successfully using them, but I don't remember if allowed yet as an array drive.

Nice! Anyone with a zero byte super.dat will especially appreciate it. Still no separate destination though, so ultimately you have to start the array (and therefore assign at least one disk) to get at the assignments (if you don't print them out), but my new routine seems to be bouncing back and forth between plugs now. Would be nice to have that file on the flash drive!

Nice! Anyone with a zero byte super.dat will especially appreciate it.

It's working for others, without that issue, so I still lean toward the controller not handling it properly. USB 3.0 ports and controllers have clearly been more problematic, so you may want to try a USB 2.0 port, or a USB 2.0 flash drive.

The first question always has to be - are you sure it works with your system? S3 sleep is never guaranteed, requires compatible motherboard, software, and all devices, and it sounds like at least one of your USB controllers does not support it correctly. You can try fiddling with the USB config in the BIOS, and you can try plugging your flash drive into a different controller, e.g front vs back, or an internal plug, etc. Did it ever work for you before?