perhansen

You need to update the plugin. Logs are only available from version 1.1.0. Thanks. Now i see the logs. Sent from my iPhone using Tapatalk

Logs not working for me, not even after a restart of the plugin. unRaid ver. 6.2.2 Plugin ver. 1.0.6 App ver. 2.3.0 on iOS. Sent from my iPhone using Tapatalk

Just updated from 6.2.1. Had trouble with some old plugins, that broke the gui. Deleted the plugin from the usb, rebooted and everything where fine. Again thanks for the great work Limetech and all the other developers. Sent from my iPhone using Tapatalk

I think one of the main functions of the plugin is that you can make multiply users to the app, with different privileges. Sent from my iPhone using Tapatalk

Hi perhansen, it's a requested featured (https://feedback.userreport.com/b5864402-1922-4c3e-810c-0e427f4d204a/#ideas/popular), but a bit low in votes. Thanks for the link. I just gave it my vote. Sent from my iPhone using Tapatalk

Damn... i messed up... i think. This morning everything worked fine. I was trying to add peter_sm fix for the warning in nextcloud, but that ended up i a "502 bad gateway" page. I then removed the line i just add, but that didn't changed anything, still bad gateway. I tried different browsers, restarted nextcloud and letsencrypt docker, without any luck. this is my nextcloud config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'octetfa9q409', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.x.xxx:xxx', 1 => 'www.xxx.dk', 2 => 'xxx.dk', ), 'trusted_proxies' => array ( 0 => '192.168.xx.xxx', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'xxxx.dk', 'overwrite.cli.url' => 'https://192.168.xx.xxx:xxx/nextcloud', 'dbtype' => 'mysql', 'version' => '9.1.1.5', 'dbname' => 'nextcloud', 'dbhost' => '192.168.xx.xxx:3305', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'oc_xxxxxxx', 'dbpassword' => 'xxxx', 'logtimezone' => 'UTC', 'installed' => true, ); This i added to letsencrypt default site-confs location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.x.xxx:xxx/nextcloud; } } ---edit--- started from scratch, now everything is working again.

Is there a reason why disks mounted through Unassigned Devices, not is showing on the disks summary page?

16GB ECC Sent from my iPhone using Tapatalk

Thought I would add my banner to.

We're waiting patiently for the 6.2 version. Thanks for the info. Sent from my iPhone using Tapatalk

Hi there I tried to run the utility, but get the following error: unRAID Tunables Tester v2.2 by Pauven Please select what type of test you would like to perform: (V) Veryfast - 4 Second Test Pass, produces inaccurate results (F) Fast - 20 Second Test Pass, produces rough results *(N) Normal - 2 Minute Test Pass, produces good results (T) Thorough - 4 Minute Test Pass, produces great results (E) Extreme - 10 Minute Test Pass, produces accurate results (FULLAUTO) - Automatic test takes 2.1-2.3 Hours. Recommended. (C) Cancel Enter V F N T E or FULLAUTO to continue or C to cancel: FULLAUTO unRAID Tunables Tester v2.2 by Pauven FULLY AUTOMATIC TEST This test runs 2 passes, starting with a Rough Pass that covers the full range of assignable values in granular fashion to find what range suits your hardware. Then a Final Pass targets the fastest range in more detail and hones in on the best values for your server. THIS TEST WILL TAKE 2.1 TO 2.3 HOURS! FOR ACCURATE RESULTS, DO NOT ACCESS YOUR SERVER DURING THE TEST! Are You Sure? (Y to continue): Y unRAID Tunables Tester v2.2 by Pauven --- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)--- /root/mdcmd: line 11: echo: write error: Invalid argument Test 1 - md_sync_window=512 - Completed in 179.578 seconds = 108.9 MB/s /root/mdcmd: line 11: echo: write error: Invalid argument Test 2 - md_sync_window=640 - Completed in 179.529 seconds = 109.0 MB/s /root/mdcmd: line 11: echo: write error: Invalid argument Test 3 - md_sync_window=768 - Completed in 179.584 seconds = 109.0 MB/s /root/mdcmd: line 11: echo: write error: Invalid argument Test 4 - md_sync_window=896 - Completed in 179.575 seconds = 108.9 MB/s /root/mdcmd: line 11: echo: write error: Invalid argument Test 5 - md_sync_window=1024 - Completed in 179.564 seconds = 109.0 MB/s /root/mdcmd: line 11: echo: write error: Invalid argument Test 6 - md_sync_window=1152 - Completed in 179.588 seconds = 109.1 MB/s /root/mdcmd: line 11: echo: write error: Invalid argument Test 7 - md_sync_window=1280 - Completed in 179.572 seconds = 109.1 MB/s /root/mdcmd: line 11: echo: write error: Invalid argument

I thought the same happend to me, but i was wrong. When you have changed the text size and return to the server list, then your server is gone. Then swipe down the screen to refresh and you server will be back. Sent from my iPhone using Tapatalk

Working great on iPhone 6 and iOS 10. Server manually added. Can control both VMs and dockers. Sent from my iPhone using Tapatalk

Great news with the iOS app, thanks man. Both autodetect and manual get stuck when adding server. Text is typed in the fields, but dosen't get showen. Running iOS 10 Sent from my iPhone using Tapatalk

Just upgraded from 6.1.9. VMs and dockers running. Installing second parity as we speak. Everything is running smooth. Thanks LT and other contributers for making this product so awesome. Sent from my iPhone using Tapatalk

Try SeaBIOS instead of OVMF, under BIOS selection.

How is your temps? Have you done a memory test?

So you dident manage to do a bios recovery, with the newest release. I would try that again a couple af times before giving up, and make sure that the files on your usb is correct spelled with upper and lowercase characters. Also give it som time to complete.

You have to make sure that the parity drive is the same. If you put one of your data disk in parity slot, then you data on that disk will be gone.

Completely agree, I would never run them for sustained periods like this but since I had everything connected initially and then ran into this issue I had to clean everything in an effort to re-test. Again I would definitely never run this for any length of time without being next to it to monitor temperatures. The CPU's never got hot because the board is never truly turning on. You see the lights on and the fans run for a brief moment but that's it. No BIOS, no video output, nothing so after testing every other way I figured I'd reattach everything minus thermal paste and heatsinks just to test again. Anyways in the video the top left is not CPU AUX but CPU 2 PWR whereas Top Right is CPU 1 PWR and Bottom Right is Main PWR. Didn't think I needed to plug it in since there was no CPU 2 installed but I tested it that way as well with no luck. Right now I have both installed as I had it originally and still no luck and same exact results. It does not POST, no video, just the exact same results. Also it will not perform a BIOS Recovery. I've tried it with the latest firmware and the step up from where I am now. Only thing that works is BMC Web Console. In the console it reports seeing both CPUs even when they are not installed. It sees all 16 DIMMS occupied with other memory not the eight slots I have installed.Super weird issues with this motherboard. Not sure anymore what to do other than look for a replacement. Have you updated the bmc? And does the bmc confirm the bios-update? Is it possible to update from within the BMC Web Console? I could not find any option within the console. If the process differs than what I've tried when attempting to update or recover BIOS then no I haven't, but if it involves getting to the EFI bootup to do so, well then I'd say I'm SOL since the board doesn't boot. No, its not possible to update from bmc, but dosent it tell you what version of bios your board have? Then you properly could tell if your board is updated or not. I have seen the same thing with my supermicro x10slm-f board, it was a bad memory chip, and bad flashed bios. I did a bios recovery and added new memory, then everything worked. Thats why i won't you to be sure that you bios is updated to the newest release.

Completely agree, I would never run them for sustained periods like this but since I had everything connected initially and then ran into this issue I had to clean everything in an effort to re-test. Again I would definitely never run this for any length of time without being next to it to monitor temperatures. The CPU's never got hot because the board is never truly turning on. You see the lights on and the fans run for a brief moment but that's it. No BIOS, no video output, nothing so after testing every other way I figured I'd reattach everything minus thermal paste and heatsinks just to test again. Anyways in the video the top left is not CPU AUX but CPU 2 PWR whereas Top Right is CPU 1 PWR and Bottom Right is Main PWR. Didn't think I needed to plug it in since there was no CPU 2 installed but I tested it that way as well with no luck. Right now I have both installed as I had it originally and still no luck and same exact results. It does not POST, no video, just the exact same results. Also it will not perform a BIOS Recovery. I've tried it with the latest firmware and the step up from where I am now. Only thing that works is BMC Web Console. In the console it reports seeing both CPUs even when they are not installed. It sees all 16 DIMMS occupied with other memory not the eight slots I have installed.Super weird issues with this motherboard. Not sure anymore what to do other than look for a replacement. Have you updated the bmc? And does the bmc confirm the bios-update?

Upper left corner of his board, right next to the empty CPU socket, beneth the memory slots. I think thats the CPU aux power connector? When it is, its defently not connected. Whats your board model?

There is no change to the number of storage devices you can use with a Plus license in 6.2. This would mean that the limits are the same for the free and Basic license if free is increased to 6. This seems to remove much of the incentive to ever move from Free to Basic licenses. I would have thought you should reduce the limit for Free back to 4 or 5 (I agree 3 was too low) or increase the limits for Basic. A suggestion might be something like 8 for Basic and 15 for Plus. This seems more in line with the increase in the Pro limits. I vote for that.

Is this a one-time validation OR is this new version crippled unless it phones home at EVERY reboot???? HOPEFULLY this only will apply to the beta and evaluation versions. If I can't start my server because my internet happens to be down... > Has there been any word on this? I prevent outside network access on my unRAID box at the firewall (and won't be changing it). I thought our keys were tied to the USB, what's to authenticate? For -beta and -rc releases, of all key types, the server must validate at boot time. The reason is that this lets us "invalidate" a beta release. That is, if a beta gets out there with a major snafu we can prevent it being run by new users who stumble upon the release zip file. For example, if there is a bug in P+Q handling. Remember the reiserfs snafu last year? We want to minimize that. For stable releases, Basic/Plus/Pro keys do not validate at boot time, that is, works the same as it always has. Starting with 6.2, Trials will require validation with key server. This is in preparation for making the Trial experience easier. Finally some answer to this topic. Great feature btw, to invalidate betas. Keep up the good work.

I think you have a "bad-flashed" bios. Many servergrade boards have the ability to re-flash the bios, when something went wrong last time. That is even when you dont have picture on the screen.