exist2resist

Yeah I rebuilt last night, after I started rebuild I had a thought that the config might be a quicker way to accomplish the same. Having said this the OS might benefit from a "accept disk and reenable" button, or "mark drive as good".

PSU died during my move. Had to replace the power supply. I have a dual parity system and both disabled disks contents are now emulated. During the many reboots I have performed the disks became disabled. Both short and long SMART test come back without errors for both disks. I tried to clear statistics and reboot, however when I reboot the drives are still disabled and contents are emulated. How do I tell Unraid that the disk it fine and it should use it. Maintenance mode? Anything else than a rebuild?

You shouldn't be changing anything in your ssl.conf, all your changes should happen in proxy-confs. I leave my ssl.conf alone, haven't touched it in years. Duck DNS?

This will steer you in the right direction. https://github.com/Exist2Resist/docker-templates/blob/master/exist2resist/Onlyoffice.xml I created the template and am using it successfully.

Having issues with screen, did a reinstall still can not start it. As you can see it exists on my system looks like the right permissions as well. Any ideas?

It was the preview folder and database file locations that didn't add up. I purged the appdata_xxxxxxxxx/preview folder, ran file scan and regenerated the previews from scratch. Ran a bunch of occ repairs on the file system, database stuff, etc. Realistically I just need to migrate to a new and clean instance. All these upgrades from version 15 left too much stuff behind.

I believe that my upgrade broke something with the Photo viewer and I am getting error 404 for previews. The photo tab intermittently displays the photos. I tried all kinds of occ commands. What table do I look in to find fileID and corresponding file loaction? Also can someone shine some light on how to clear the file cache and the file cache table, is this recommended?

Actually there is a file you need to purge as per their github.

Looks like your overwrite.cli.url might be wrong. <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'something', 'passwordsalt' => 'klsjsadhflkasjdhflakshf', 'secret' => 'lkashdjflaskjhdflakshdflka', 'trusted_domains' => array ( 0 => '192.168.1.151:444', 1 => 'something.something.duckdns.org', ), 'dbtype' => 'mysql', 'version' => '20.0.7.1', 'overwrite.cli.url' => 'https://something.something.duckdns.org:443', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.151:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'oc_admin', 'dbpassword' => 'klasdhgflkashflashf', 'installed' => true, 'theme' => '', 'loglevel' => 2, 'maintenance' => false, 'twofactor_enforced' => 'false', 'twofactor_enforced_groups' => array ( ), 'twofactor_enforced_excluded_groups' => array ( ), 'mail_from_address' => 'myuser', 'mail_smtpmode' => 'smtp', 'mail_smtphost' => 'mail.server.ca', 'mail_smtpport' => '25', 'mail_sendmailmode' => 'smtp', 'mail_domain' => 'server.ca', 'preview_max_x' => '2048', 'preview_max_y' => '2048', 'jpeg_quality' => '60', 'updater.release.channel' => 'stable', 'has_rebuilt_cache' => true, 'app_install_overwrite' => array ( 0 => 'passman', ), ); Subdomain conf: server { listen 443 ssl; listen [::]:443 ssl; #HTTP Strict Transport Security for NextCloud add_header Strict-Transport-Security "max-age=15552000; includeSubDomains" always; server_name cloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud 192.168.1.151; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:444; } } Note I use the static ip of my server not the internal docker names or IPs, I find those rarely work. Then you make sure that in your nginx.conf the following line... include /config/nginx/site-confs/*; ...is not commented.

What is the file I need to delete after each update again? There is a file in the configuration folder.

Yes you need to reboot so the BIOS can take control of the fans again.

I found this.... https://github.com/lm-sensors/lm-sensors/issues/10 How do I go about booting my system with; acpi_enfore_resources=lax ? Do I just paste the line in go file? Resolved; needed to edit /boot/syslinux/syslinux.cfg file Added acpi enforce resources to the first label Here is what it looks like. I can now read my PWM fans. cat /boot/syslinux/syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append acpi_enforce_resources=lax initrd=/bzroot label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest

Currently controlling fan speed vis BIOS. Trying to configure Dynamix Auto Fan Control. I tried setting up fan sensors for my unRAID box running on a Rampage V Extreme. Followed these instructions: https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing However no luck. Sensors only show core temp. It found these two drivers using sensors-detect. root@Tower:~# sensors coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +46.0°C (high = +90.0°C, crit = +100.0°C) Core 0: +37.0°C (high = +90.0°C, crit = +100.0°C) Core 1: +36.0°C (high = +90.0°C, crit = +100.0°C) Core 2: +42.0°C (high = +90.0°C, crit = +100.0°C) Core 3: +37.0°C (high = +90.0°C, crit = +100.0°C) Core 4: +38.0°C (high = +90.0°C, crit = +100.0°C) Core 5: +36.0°C (high = +90.0°C, crit = +100.0°C) root@Tower:~# sensors-detect # sensors-detect version 3.6.0 # System: ASUS All Series # Board: ASUSTeK COMPUTER INC. RAMPAGE V EXTREME # Kernel: 4.19.107-Unraid x86_64 # Processor: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (6/63/2) 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): YES 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 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 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): YES 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 NCT6791D Super IO Sensors' Success! (address 0x290, driver `nct6775') 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): YES Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No 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): yes 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): YES Using driver `i2c-i801' for device 0000:00:1f.3: Wellsburg (PCH) Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at 0580 (i2c-0) Do you want to scan it? (YES/no/selectively): YES Client found at address 0x48 Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM73'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `SMSC EMC1023'... No Probing for `SMSC EMC1043'... No Probing for `SMSC EMC1053'... No Probing for `SMSC EMC1063'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `nct6775': * ISA bus, address 0x290 Chip `Nuvoton NCT6791D Super IO Sensors' (confidence: 9) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): NO To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp modprobe nct6775 /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Unloading i2c-dev... OK Obviously the driver does not exist or is not being detected, Is there an alternative?

Pulled my disk accidentally and it generated 10 read errors, now contents of disk are emulated. I cleared disk statistics and rebooted unraid. Butni can't readd the disk to the array again. How to I go about doing that. Do I have to clear the whole array etc.?

Upgraded from NC 15 to 19 today, yeah I know, long overdue. When I go to help I have Nextcloud 15 support documentation, how to I purge the old version of this page? Secondary issue I'm having is the Additionaly Settings page is missing under Settings. Prints a '1' on the page. This is not the Additional Settings that is under Administration.

Where can I find a full version or example of supported tags in v2 xml... I'm trying to figure out if this is a valid tag, or if one exists like this...

Auto Update doesn't spin up new instances of a few containers I have after an update attempt. The image is updated, but then they just disappear and aren't spun back up again. I can bring them back up manually by using the User Templates section in the Templates drop down. So not quite sure why Auto Update wouldn't spin them up again even though the template still exists for the containers. If I update the containers manually it works just fine. Also note worthy these are my own unraid templates, https://github.com/Exist2Resist/docker-templates/tree/master/exist2resist The containers that don't spin back up are Collabora, and Gitlab-CE after updates, all the other ones update fine.

Right now I am doing the following in the Docker Template Schema <ExtraParams>--hostname your.domain.org</ExtraParams> Is there such a config type as a Hostname for use in the Docker Template Schema? Something like the following... <Config Type="Hostname" Name="Hostname of the Container" ....>your.domain.org</Config>

Yeah this is what was weird the disk SMART was fine so I tried to rebuild the config since it had 4 read errors. But when I rebuilt it it got a lot more errors. The disk is still sitting there but it is not in the array anymore. I have a Norco 24 bay drive case with a sas back plane connected to dell perc cards in IT mode. I will shut down the server and check the cables. EDIT: Not bad cables, bad drive, Error 187. Unraid did no notify me of this, and the drive was green until I rebooted the server. Once I replaced that drive the array is functioning as normal.

Thanks, here you go. tower-diagnostics-20200922-2321.zip

Unraid Parity sync / Data rebuild: 13-09-2020 04:23 Notice [TOWER] - Parity sync / Data rebuild finished (1 errors) Duration: 10 hours, 5 minutes, 33 seconds. Average speed: 110.1 MB/s What do I do with a data rebuild that rebuilt with 1 error? Now when I run parity check I get a single error. How do I handle this?

It's not broken mine has been working without hiccup for over a year now. You need to create a chatid file under /boot/config/telegram. From the command line run the following; touch /boot/config/telegram/chatid In that file you need to input the chatid of your user not your bot. You can obtain this by going to the following url; https://api.telegram.org/bot{bot token}/getUpdates Or running a curl command from the command line; curl https://api.telegram.org/bot{bot token}/getUpdates Where {bot token} is your bot api token... in the format of 1111111111:AAasdflakjhsflaskdhalskdjyYo You will see json formated text spit out. Look for the first instance of a chat id that belongs to your user name and not the bot. "chat":{"id":206646491,"first_name":"Max","last_name":"Power","username":"MPower" The above is the chat id you insert into your chatid file on the server. Just the number nothing else. Run this in command line; echo "206646491" > /boot/config/telegram/chatid

Yeah I was looking at that. Didn't know you could do S3, Amazon Glacier 10GB free tier too so that's not a bad choice. That's pretty cool. I see it supports Amazon as well among other services.

Meh, I'm just going to share it out via my nextcloud. Thanks.

I preformed useradd -m -d /location/of/ftp/folder ftp then passwd ftp to set the password. However when I log into the FPT server the user can see and access my entire array. Where do I restrict this access?