tazire

You were spot on. IPMI and BIOS update solved all the issues I was having. I'm just waiting on a slimsas to 2xminisas cable to arrive to finally deploy the thing. Made the mistake of ordering it on ebay and now its been stuck in NL for the last 10 days waiting to be forwarded on! I ordered a replacement from amazon which should hopefully arrive on time!

Cheers for the advice. No I hadnt updated either.. I'll do that shortly and hopefully solves all my issues.... I was looking on the SM website and it would put you off doing an update on either of them unless you have a serious issue!

cheers. Thats what ill do then. How are you finding the IPMI on that motherboard? I have been having a couple of little niggles with it. In that the temp sensors are showing active but give no information. It also doesnt show my fan speeds. And the fan control doesnt seem to have any effect. Ofc that could be down to the fans rather than the board.

Finally getting around to making my upgrades... I've kinda changed my plan for upgrading and just gone for the whole lot.... and a very similar build to yourself. Gooxi 24-bay Chassis with 12Gb SAS3 Expander EPYC 7402 Arctic Freezer 4U SP3 SM H12SSL-i 256GB 2666 ECC RAM Onboard SlimSAS 8i for the main case 2x LSI 9201 16e (for JBOD) Melenox connectx3 10GB SFP+ NIC Cyberpower PR2200ERT2U Still waiting on a few parts to arrive... Slim sas to SFF 8654 is the main hold up atm. So havent posted its own thread about it. Just curious about the noctua A12 fans you got were you able to put them into the hotswap casing? or did you just mount them directly to the chassis? not that it makes a whole lot of difference. Having a few issues with the Motherboard too as it happens but hopefully nothing thats going to be a long term problem.

So my current setup works ok. I have some niggles with some of my dockers but nothing that breaks anything. I'm about to do a fairly substantial upgrade on it and wanted to look into make everything work a little more how I want it to. In the mean time I have got myself a test server to test everything and see how I want my dockers setup etc. I am now in a position where I much much prefer the docker and path setup on my test server. So now as I'm about to begin the upgrade I'm wondering is it possible to use my test server setup and migrate the data drives from my main server into that? Or would it just be easier to gut my docker setup on my main server and set that up as I have my test server?

I'm looking to try and follow the zero trust hosting and reverse proxy guide https://www.linuxserver.io/blog/zero-trust-hosting-and-reverse-proxy-via-cloudflare-swag-and-authelia just wondering if anyone has tried this or got it working? I'm having difficulty with the cloudflare connection atm. Also not sure how to add the "extra_hosts: - lsio-test.com:127.0.0.1"?? just an extra parameter? EDIT: Disregard... figured out that my cloudflare.ini hadnt updated with the api token. fixed this and im up and running. also found the --add-host command that solved the extra hosts portion.

cheers for the response. The particular pi would be solely to run nextcloud & mariadb... just the vital containers for nextcloud to continue to function. I wouldnt need onlyoffice or any of the other addons for this. Its just to keep it going should my server ever go down for whatever reason. I would have swag/NPM on its own pi also so I can keep the load to just nextcloud related. I could also go the k3 route as I have 4 pi 4 4gb's that I have been playing with. Both my nextcloud and mariadb are linuxserver (obviously!) repo images. So if they support arm it should be as simple as setting them up on my pi and have the unraid files rsync to the pi?

I'm interested in using one of my raspberry pi's as a quick spin up backup server. I'm just curious if anyone is doing anything similar or is it even possible? I have backups to B2 etc but I'd like to be able to just spin up the raspberry pi and practically instantly be back up and running again.

I will but it might take a while. The plan is to do it in stages. Stage 1 case change. Stage 2 change the guts of it to epyc. Stage 3 add the jbod. So god knows how long before I get it finished. The case alone will cost me the guts off 1k.... then another 1-1.5k for stage 2 and then maybe 500 for the jbod addition. I dont have the funds to get it all done right away unfortunately.

Very nice setup. I'm looking into a similar setup... a few gens older than yours mind you but its great to see what will be an option. I'm on consumer hard ware atm (3900x) which is absolutely fine but ive just filled up a 24bay server and the lack of pcie lanes is a big issue for me now. So im looking to move to an epyc setup with the same case you are using and then use my 2nd 24bay as a jbod. Do you think you might go with a zfs cache if/when that becomes natively available?

Mine show exactly the same as you posted here. R/W on all permissions. And the owner option doesnt actually show who the owner is but its the same as yours and gives nobody as the default option? should I try make it the new owner? EDIT Just to add to this... I am also unable to come out of maintenance mode. It spits out the same errors when i try to turn it off. So at present my nextcloud is unusable. EDIT2 Ok I just ran both the change the permissions and change owner options you mentioned to have everything r/w and the owner be nobody... not sure if this is the best idea from a security perspective but it worked for me to at least get the update done and be able to use nextcloud again. I now just get the error.. Last background job execution ran 21 hours ago. Something seems wrong.

Currently trying to upgrade from 25.0.1 to 25.0.2 via CLI and got the following error docker exec -it nextcloud occ upgrade Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Cannot write into "config" directory. This can usually be fixed by giving the web server write access to the config directory. See https://docs.nextcloud.com/server/25/go.php?to=admin-dir_permissions. Or, if you prefer to keep config.php file read only, set the option "config_is_read_only" to true in it. See https://docs.nextcloud.com/server/25/go.php?to=admin-config Cannot write into "apps" directory. This can usually be fixed by giving the web server write access to the apps directory or disabling the App Store in the config file. An unhandled exception has been thrown: Exception: Environment not properly prepared. in /config/www/nextcloud/lib/private/Console/Application.php:166 Stack trace: #0 /config/www/nextcloud/console.php(99): OC\Console\Application->loadCommands() #1 /config/www/nextcloud/occ(11): require_once('...') I'm guessing I need to change permissions on the config and apps files as stated? or should I set it to read only?

Thank you for this. I cant exclude the docker.img however as it is in the appdata folder and not in its own folder within the appdata folder. I'll change this and i'm sure ill be able to exclude it then.

This is true but not the issue. I dont want to exclude it. I want the plugin to stop all containers before it starts the backup. In its current form it only stops docker containers within the specified appdata folder. In my setup I have all my plex appdata on its own dedicated SSD. As a result the plugin does not stop this container.... which in turn mean that plex makes changes to docker.img and causes the error I am experiencing. Or at least I believe this to be the issue in my case. I could be wrong. Is it possible to have the plugin stop the docker service before starting the backup? I imagine that would stop all docker containers not just those within the appdata folder.

I am having the same issue but its the docker.img that is changing as its being read. although looking at my logs there is no log for plex stopping. I have my plex appdata on its own ssd which I'm guessing is the issue here? As you would expect the plex app data doesnt appear as an option to exclude and also doesnt get backed up through the app (i have an rclone setting for that). I'm guessing this plugin doesnt stop the docker service and just stops each individual docker and because plex isnt in the normal appdata folder is doesnt stop it? Is there a way to set a schedule for plex to stop/start with this plugin when its on its own ssd?

Having a strange issue which i'm 90% sure is probably just a hardware thing. After updating I had drives presenting as errored after I started the array (they appeared fine prior to starting the array). After the first reboot I had 2 drives present like this. After the 2nd reboot the original 2 problematic drives were fine but another drive presented as erroring. Finally after the 3rd reboot all started up fine. I didnt change any hardware nor did I check wiring or seating of hardware. Everything running perfectly after that.

Not a big issue/ probably not an issue at all but just some unexpected behaviour... Prior to the update my browser shortcut to my server (https://xxx.xxx.x.xx) would always re direct me to the long url assigned when generating the SSL cert and now it does not. Connecting using my shortcut no longer uses the secure cert and shows up as unsecure in my browser and i also get the security alert prior to connecting. Is this normal behaviour since the update? I am coming from 6.9.3. According to my Management Access tab https://xxx.xxx.x.x/ should use the cert as should https://xxxxx.local:xxx/ and finally the long url. Long URL uses the cert just fine (and i have no problem just using this in future) but i'm just curious is this normal behaviour?

I just followed the ibracorp video and have it up and running. My only change was to the config. I have the following... tunnel: UUID credentials-file: /home/nonroot/.cloudflared/UUID.json # NOTE: You should only have one ingress tag, so if you uncomment one block comment the others # forward all traffic to Reverse Proxy w/ SSL ingress: - service: https://REVERSEPROXYIP:PORT originRequest: noTLSVerify: true #forward all traffic to Reverse Proxy w/ SSL and no TLS Verify #ingress: # - service: https://REVERSEPROXYIP:PORT # originRequest: # noTLSVerify: true # forward all traffic to reverse proxy over http #ingress: # - service: http://REVERSEPROXYIP:PORT I kept getting errors with "originServerName: yourdomain.com" in my config.

My issue seems to have progressed to the following error now... [Warning] Aborted connection 69 to db: 'nextcloud' user: '*****' host: '172.19.0.1' (Got an error reading communication packets)

Yes I have tried different pc's different browsers and still nothing. Also noticed my auto uploads from my phone have stopped working. I did post in mariadb about a warning I was getting in relation to a mysql upgrade but having done that the problem still persists with nextcloud! no warnings in logs either which is making it a real pain to try diagnose.

Thank you... this has solved the warnings I was getting however my underlying nextcloud issue persists.... I assumed it was a DB issue as my files tab just wont load in at all since a recent update and the only errors/warnings I could see were those mentioned... Looks like im off to the nextcloud support to try solve it...

Got an error with Mariadb since a recent update to Nextcloud 23.0.2. I get the following error in logs.... 220221 03:39:47 mysqld_safe Logging to '/config/databases/75c70985ee01.err'. 220221 03:39:47 mysqld_safe Starting mariadbd daemon with databases from /config/databases In the corresponding .err file i get the following reoccurring... 2022-02-21 21:53:59 0 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade running mysql_upgrade in the container console just spits out the following... Version check failed. Got the following error when calling the 'mysql' command line client ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) FATAL ERROR: Upgrade failed EDIT Ok since this I have managed to login as root on mariadb but mysql_upgrade still has no effect. Any help at all would be much appreciated.

Started getting a strange issue with the files tab on the webgui... It wont populate for me at all.... Just updated recently to 23.0.2 which seemed to be fine but now this. Functionally its fine in every other aspect. Photos tab shows all the most recent uploaded photos etc. Anyone else experienced this? Have updates the container just there this evening too and the problem persists. Is this possibly a mariadb issue?

As I'm not sure if that is the source of the issue or a symptom of a different issue I thought it best to put it in the general support section. I can put it in the UD section if that is the best place for it. Is there another way to mount the share without using UD? Just to see if that solves my issue.

Basically what seems to happen is UD has issues with the NFS share to my truenas server... this in turn seems to cause my docker service to drop completely. All containers no longer available. 1 cpu core gets pegged to 100%. I can stop my docker service and it seems to stop just fine. but i can not restart it. This will cause the server to hang completely. I can not unmount/remove the NFS share at all. And when I try to reboot the server it hangs and requires a hard shut down... This is the 2nd time this has happened. Server has been up 18 days without issue since this last happened. I've included my diagnostics. any help is much appreciated. Oh and my truenas is still working just fine btw. Can access it and see all the files using my personal rig. Thanks in advance. server-diagnostics-20220110-1244.zip